Am Freitag, den 08.03.2019, 16:23 -0300 schrieb Antonio Terceiro: > On Fri, Mar 08, 2019 at 07:10:55PM +0100, Daniel Leidert wrote: > > Can we maybe change Gem.bin_path to fall back to /usr/bin or even > > $path? > > Not at this point in the release cycle.
That's a suboptimal situation. It seems, there are more reports about this issue, like https://bugs.debian.org/710814. However: If I apply your suggested fix (hardcode '/usr/bin/bundle') to jekyll, the result is: > jekyll new --force test > Running bundle install in /tmp/test... > > > Your user account isn't allowed to install to the system RubyGems. > You can cancel this installation and run: > > bundle install --path vendor/bundle > > to install the gems into ./vendor/bundle/, or you can enter your password > and install the bundled gems to RubyGems using sudo. > > Password: > So jekyll would need another fix to not try to install into the systems gems location but fall back to './vendor/bundle' too. IMHO jekyll is currently broken with ruby-bundler. Regards, Daniel
signature.asc
Description: This is a digitally signed message part
