Am Samstag, den 25.04.2020, 15:25 +0200 schrieb deivid:
I can reproduce this locally, and without having a closer look, I agree
there's room for improvement in bundler here (maybe in jekyll too), at
least in terms of better error messages. Feel free to report the issue
upstream so it doesn't get lost.
I'll do so. IMHO it should definitely not behave differently
depending on the
number of gems put in the block. IMHO at least this part is not a
question of
improving error messages.
To workaround the issue, you can run `bundle install` before running
jekyll so that version information for the new gems you added gets
added
to the lockfile. Note that even if the particular gem does not get
installed on your system, it's still used for resolution so that users
of the app on other platforms get a consistent version of those
dependencies when using the application.
The problem is I don't want to run bundle. I'm using the Debian
packages. My
expectation was that if I don't require the gem (because my platform
is not
listed in Gemfile) I shouldn't get an error message. If I run `
bundle install`
and if I have all the necessary dependencies installed, bundle won't
fetch gems
from the internet. But if it does it creates kind of a mess on Debian
systems
and that is nothing for inexperienced users (see [1] and follow-ups).
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942596#20
What do you think?