Jekyll / gem: unresolved specifications
I am using Jekyll, I have two independent repos and I think I recently updated them. Everything worked great the last time I did my blog. Now only this:
$ jekyll serve --watch
WARN: Unresolved specs during Gem::Specification.reset:
redcarpet (~> 3.1)
jekyll-watch (~> 1.1)
classifier-reborn (~> 2.0)
WARN: Clearing out unresolved specs.
Please report a bug if this causes problems.
/var/lib/gems/2.1.0/gems/jekyll-2.5.2/bin/jekyll:21:in `block in <top (required)>': cannot load such file -- jekyll/version (LoadError)
from /var/lib/gems/2.1.0/gems/mercenary-0.3.5/lib/mercenary.rb:18:in `program'
from /var/lib/gems/2.1.0/gems/jekyll-2.5.2/bin/jekyll:20:in `<top (required)>'
from /usr/local/bin/jekyll:23:in `load'
from /usr/local/bin/jekyll:23:in `<main>'
What's happening? It seems like Jekyll or Jem killed themselves. How can I fix this?
How can I prevent Jekyll or Ruby from messing with the global install (I guess what happens is the two blogs are not independent of each other)? Can I ensure that each Jekyll directory is isolated from the other, for example in any descent language / assembly system?
Edit . I ran accidentally sudo gem cleanup && bundle install
. It seems that they removed (!?!) All the gems and then installed them again. Now I am getting another error:
WARN: Unresolved specs during Gem::Specification.reset:
listen (~> 2.7)
WARN: Clearing out unresolved specs.
Please report a bug if this causes problems.
Is it safe to assume that gem / bundle doesn't know what a transitive dependency is?
$ bundle show listen
/var/lib/gems/2.1.0/gems/listen-2.7.11
So there is a rumor. So why is Jekyll complaining?
source to share
It seems that you are not the only one with this problem. See the problem here .
I managed to get around this problem in two ways.
In Jekyll 2.5.x, deleting Gemfile
will simply result in an error.
If a Gemfile is required, a bundle exec jekyll serve
is fine.
source to share