Hi Daniel,
> > I finally understood what confused me at first: even with
> > --skip-bundle,
> > "jekyll new" creates a Gemfile. And until this Gemfile is removed,
> > "jekyll build" will try to go the bundle way all by itself.
>
> That is not true. As I explained earlier I'm using jekyll
Am Samstag, den 25.04.2020, 00:18 +0200 schrieb ydir...@free.fr:
> Hi Daniel,
>
> - Mail original -
> > 1) Use the Debian package management and don't use bunlder at all
> > (jekyll new
> > --skip-bundle). All the Jekyll plugins have been packaged and most of
> > them can
> > be found in
Hi Daniel,
- Mail original -
> 1) Use the Debian package management and don't use bunlder at all
> (jekyll new
> --skip-bundle). All the Jekyll plugins have been packaged and most of
> them can
> be found in stable-backports. If you are missing some please let me
> know. Just
> add the
Hi Daniel,
- Mail original -
> De: "Daniel Leidert"
> À: ydir...@free.fr, 942...@bugs.debian.org
> Envoyé: Lundi 20 Avril 2020 16:19:17
> Objet: Re: [DRE-maint] Bug#942596: jekyll and required bundles
>
> Am Sonntag, den 19.04.2020, 18:28 +0200 schrieb ydir..
Am Sonntag, den 19.04.2020, 18:28 +0200 schrieb ydir...@free.fr:
> Trying Jekyll for the first time, I get hit by the same issue.
>
> Indeed this flag is a good start, but afterwards:
>
> 1. we have to gather we should change the Gemfile to use:
>
> source "file:///usr/lib/ruby/vendor_ruby"
I could finally install the dependencies with the default Gemfile,
by downgrading ruby from 2.7 back to 2.5. Looks like eventmachine
does not have support for 2.7 yet (hint given by the ruby-eventmachine
package in experimental, which still uses 2.5).
"bundle exec jekyll build" now works. Good
Trying Jekyll for the first time, I get hit by the same issue.
Indeed this flag is a good start, but afterwards:
1. we have to gather we should change the Gemfile to use:
source "file:///usr/lib/ruby/vendor_ruby"
2. we get hit by missing bundles, that should surely be added as Recommends:
7 matches
Mail list logo
