pages-gem: gh-pages version and jekyll version problem

I’m having a version problem when I do install or update. Instead of getting gh-pages 104 and jekyll 3.3.0, I’m getting 35/39 and 2.4.0

I do as follows

$ jekyll new darkhollow.github.io

And get

New jekyll site installed in /Users/roberto/Proyectos/darkhollow.github.io. 
Running bundle install in /Users/roberto/Proyectos/darkhollow.github.io... 
Fetching gem metadata from https://rubygems.org/...........
Fetching version metadata from https://rubygems.org/..
Fetching dependency metadata from https://rubygems.org/.
Resolving dependencies...
Using public_suffix 2.0.3
Using colorator 1.1.0
Using ffi 1.9.14
Using forwardable-extended 2.6.0
Using sass 3.4.22
Using rb-fsevent 0.9.8
Using kramdown 1.12.0
Using liquid 3.0.6
Using mercenary 0.3.6
Using rouge 1.11.1
Using safe_yaml 1.0.4
Using minima 2.0.0
Using bundler 1.13.6
Using addressable 2.5.0
Using rb-inotify 0.9.7
Using pathutil 0.14.0
Using jekyll-sass-converter 1.4.0
Using listen 3.0.8
Using jekyll-watch 1.5.0
Using jekyll 3.3.0
Using jekyll-feed 0.8.0
Bundle complete! 3 Gemfile dependencies, 21 gems now installed.
Use `bundle show [gemname]` to see where a bundled gem is installed.

And then

$ cd darkhollow.github.io/
$ vim Gemfile 

and I comment the line: gem "jekyll", "3.3.0" and I uncomment the line: gem "github-pages", group: :jekyll_plugins

Finally I do

$ bundle update

and I get this

Fetching gem metadata from https://rubygems.org/..................
Fetching version metadata from https://rubygems.org/...
Fetching dependency metadata from https://rubygems.org/..
Resolving dependencies...
Using RedCloth 4.2.9
Using concurrent-ruby 1.0.2
Using i18n 0.7.0
Using minitest 5.9.1
Using thread_safe 0.3.5
Using addressable 2.4.0 (was 2.5.0)
Using blankslate 2.1.2.4
Using fast-stemmer 1.0.2
Using coffee-script-source 1.10.0
Using execjs 2.7.0
Using colorator 0.1 (was 1.1.0)
Using ffi 1.9.14
Using multipart-post 2.0.0
Using gemoji 2.1.0
Using net-dns 0.8.0
Using public_suffix 1.5.3 (was 2.0.3)
Using jekyll-paginate 1.1.0
Using sass 3.4.22
Using rb-fsevent 0.9.8
Using kramdown 1.5.0 (was 1.12.0)
Using liquid 2.6.2 (was 3.0.6)
Using mercenary 0.3.6
Using posix-spawn 0.3.12
Using yajl-ruby 1.2.1
Using redcarpet 3.1.2
Using safe_yaml 1.0.4
Using mini_portile2 2.1.0
Using jekyll-sitemap 0.8.1
Using maruku 0.7.0
Using rdiscount 2.1.7
Using unicode-display_width 1.1.1
Using jekyll-feed 0.7.2 (was 0.8.0)
Using minima 2.0.0
Using bundler 1.13.6
Using tzinfo 1.2.2
Using parslet 1.5.0
Using classifier-reborn 2.0.4
Using coffee-script 2.4.1
Using ethon 0.9.1
Using rb-inotify 0.9.7
Using faraday 0.9.2
Using jekyll-sass-converter 1.2.0 (was 1.4.0)
Using pygments.rb 0.6.1
Using nokogiri 1.6.8.1
Using terminal-table 1.7.3
Using activesupport 5.0.0.1
Using toml 0.1.2
Using jekyll-coffeescript 1.0.1
Using typhoeus 0.8.0
Using listen 3.0.8
Using sawyer 0.7.0
Using html-pipeline 1.9.0
Using github-pages-health-check 0.3.2
Using jekyll-watch 1.5.0
Using octokit 4.4.1
Using jekyll-gist 1.4.0
Using jekyll 2.4.0 (was 3.3.0)
Using jekyll-mentions 0.2.1
Using jekyll-redirect-from 0.6.2
Using jemoji 0.4.0
Using github-pages 35
Bundle updated!

So jekyll goes back to 2.4.0 version and github-pages to 35 version.

If I delete the Gemfile.lock and do bundle install it gets the same versions.

And if I serve I get an error, I do

$ bundle exec jekyll serve

and get

  Configuration file: /Users/roberto/Proyectos/darkhollow.github.io/_config.yml
              Source: /Users/roberto/Proyectos/darkhollow.github.io
         Destination: /Users/roberto/Proyectos/darkhollow.github.io/_site
        Generating... 
       Build Warning: Layout 'post' requested in _posts/2016-11-05-welcome-to-jekyll.markdown does not exist.
    Liquid Exception: Included file '_includes/icon-github.html' not found in about.md
jekyll 2.4.0 | Error:  Included file '_includes/icon-github.html' not found

I guess it’s for the old versions I get when I do update

Last try, if I only write in the Gemfile source and the github pages gem, I get this versions

Fetching gem metadata from https://rubygems.org/...........
Fetching version metadata from https://rubygems.org/..
Fetching dependency metadata from https://rubygems.org/.
Resolving dependencies....
Using RedCloth 4.2.9
Using concurrent-ruby 1.0.2
Using i18n 0.7.0
Using minitest 5.9.1
Using thread_safe 0.3.5
Using addressable 2.4.0
Using blankslate 2.1.2.4
Using fast-stemmer 1.0.2
Using coffee-script-source 1.10.0
Using execjs 2.7.0
Using colorator 0.1
Using ffi 1.9.14
Using multipart-post 2.0.0
Using gemoji 2.1.0
Using net-dns 0.8.0
Using public_suffix 1.5.3
Using jekyll-paginate 1.1.0
Using sass 3.4.22
Using rb-fsevent 0.9.8
Using kramdown 1.5.0
Using liquid 2.6.2
Using mercenary 0.3.6
Using posix-spawn 0.3.12
Using yajl-ruby 1.2.1
Using redcarpet 3.3.2
Using safe_yaml 1.0.4
Using jekyll-feed 0.3.1
Using mini_portile2 2.1.0
Using jekyll-sitemap 0.8.1
Using maruku 0.7.0
Using rdiscount 2.1.7
Using unicode-display_width 1.1.1
Using bundler 1.13.6
Using tzinfo 1.2.2
Using parslet 1.5.0
Using classifier-reborn 2.0.4
Using coffee-script 2.4.1
Using ethon 0.9.1
Using rb-inotify 0.9.7
Using faraday 0.9.2
Using jekyll-sass-converter 1.3.0
Using pygments.rb 0.6.3
Using nokogiri 1.6.8.1
Using terminal-table 1.7.3
Using activesupport 5.0.0.1
Using toml 0.1.2
Using jekyll-coffeescript 1.0.1
Using typhoeus 0.8.0
Using listen 3.0.8
Using sawyer 0.7.0
Using html-pipeline 1.9.0
Using github-pages-health-check 0.3.2
Using jekyll-watch 1.5.0
Using octokit 4.4.1
Using jekyll-gist 1.4.0
Using jekyll 2.4.0
Using jekyll-mentions 0.2.1
Using jekyll-redirect-from 0.8.0
Using jemoji 0.5.0
Using github-pages 39
Bundle updated!

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Reactions: 11
  • Comments: 33 (3 by maintainers)

Commits related to this issue

Most upvoted comments

@nickmccurdy Not yet as the issue is still present because even if the fix has been merged into master, we still need to wait for next bundler gem release.

I have found that in Gemfile if instead of

gem "github-pages", group: :jekyll_plugins

I tell to use specific version

gem "github-pages", "104"

apparently works fine if you bundle update or bundle install again, but of course, I don’t think this is a fix.

Check here for dependency information: https://pages.github.com/versions/

I’m getting a varient of this issue. As at the top of this thread it’s with the github-pages gem.

Blog nconroy$ bundle update
The dependency tzinfo-data (>= 0) will be unused by any of the platforms Bundler is installing for. Bundler is installing for ruby but the dependency is only for x86-mingw32, x86-mswin32, x64-mingw32, java. To add those platforms to the bundle, run `bundle lock --add-platform x86-mingw32 x86-mswin32 x64-mingw32 java`.
Fetching gem metadata from https://rubygems.org/..........
Fetching gem metadata from https://rubygems.org/.
Resolving dependencies...
Bundler could not find compatible versions for gem "jekyll":
  In Gemfile:
    github-pages was resolved to 4, which depends on
      jekyll (= 1.1.2)

    jekyll-feed (~> 0.6) was resolved to 0.9.3, which depends on
      jekyll (~> 3.3)

This is related to https://github.com/bundler/bundler/issues/5154. For now you can use the following work around which @nickmccurdy pointed out:

source 'https://rubygems.org'
gem 'github-pages', '>=104', group: :jekyll_plugins

I found the expected issue https://github.com/bundler/bundler/issues/5154. This is almost certainly a bug of bundler. A workaround is:

source 'https://rubygems.org'

gem 'github-pages'
$ gem uninstall bundler
$ gem install bundler -v 1.12.6
$ bundle update
Fetching gem metadata from https://rubygems.org/
Fetching version metadata from https://rubygems.org/
Fetching dependency metadata from https://rubygems.org/
Resolving dependencies.....................................................................................................................
Using i18n 0.7.0
Using json 1.8.3
Using minitest 5.9.1
Using thread_safe 0.3.5
Using addressable 2.4.0
Using coffee-script-source 1.10.0
Using execjs 2.7.0
Using colorator 1.1.0
Using ffi 1.9.14
Using multipart-post 2.0.0
Using forwardable-extended 2.6.0
Using gemoji 2.1.0
Using net-dns 0.8.0
Using public_suffix 1.5.3
Using sass 3.4.22
Using rb-fsevent 0.9.8
Using kramdown 1.11.1
Using liquid 3.0.6
Using mercenary 0.3.6
Using rouge 1.11.1
Using safe_yaml 1.0.4
Using jekyll-feed 0.7.2
Using mini_portile2 2.1.0
Using jekyll-paginate 1.1.0
Using jekyll-swiss 0.4.0
Using minima 2.0.0 (was 1.2.0)
Using unicode-display_width 1.1.1
Using bundler 1.12.6
Using tzinfo 1.2.2
Using jekyll-sitemap 0.11.0
Using coffee-script 2.4.1
Using ethon 0.9.1
Using rb-inotify 0.9.7
Using faraday 0.9.2
Using pathutil 0.14.0
Using jekyll-sass-converter 1.3.0
Using nokogiri 1.6.8.1
Using terminal-table 1.7.3
Using activesupport 4.2.7
Using jekyll-coffeescript 1.0.1
Using typhoeus 0.8.0
Using listen 3.0.6
Using sawyer 0.7.0
Using html-pipeline 2.4.2
Using jekyll-watch 1.5.0
Using octokit 4.4.1
Using jekyll 3.3.0 (was 3.2.1)
Using github-pages-health-check 1.2.0
Using jekyll-gist 1.4.0
Using jekyll-github-metadata 2.2.0 (was 2.1.1)
Using jekyll-mentions 1.2.0
Using jekyll-redirect-from 0.11.0
Using jekyll-seo-tag 2.0.0
Using jemoji 0.7.0
Using github-pages 102 (was 100)
Bundle updated!

@falsandtru Expecify the Github pages gem version

source 'https://rubygems.org'
gem 'github-pages', '>=104', group: :jekyll_plugins

Use this as a temporary workaround.

Thanks @DarkHollow I can confirm that when the contents of my Gemfile is

source 'https://rubygems.org'
gem 'github-pages', '104', group: :jekyll_plugins

I am then able to run bundle update and then bundle exec jekyll serve and I’m back in action.

Thanks!

I’m having this issue again, but only when I’m using html-proofer in the same Gemfile like this.

source 'https://rubygems.org'

gem 'github-pages', group: :jekyll_plugins
gem 'html-proofer'

Sweet, this now works for me on a clean bundle install after deleting Gemfile.lock!

Now I can install the latest gh-pages gem via bundle update with bundler 1.13.6. However, I need to run that command two times.