Bug 214252 - www/rubygem-jekyll Update to 3.3.0 also the port is broken
Summary: www/rubygem-jekyll Update to 3.3.0 also the port is broken
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-ruby (Nobody)
URL:
Keywords:
Depends on: 214251
Blocks:
  Show dependency treegraph
 
Reported: 2016-11-05 21:43 UTC by Sir l33tname
Modified: 2016-12-04 21:43 UTC (History)
3 users (show)

See Also:
sirl33tname: maintainer-feedback? (ruby)


Attachments
updates rubygem-jekyll to 3.3.0 (1.38 KB, patch)
2016-11-05 21:43 UTC, Sir l33tname
no flags Details | Diff
upgrade to 3.3.1 (1.38 KB, patch)
2016-11-19 14:33 UTC, Sir l33tname
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Sir l33tname 2016-11-05 21:43:14 UTC
Created attachment 176666 [details]
updates rubygem-jekyll to 3.3.0

The update depends on bug #214251.

If you run jekyll it fails with error messages like this one (this applies before and after the update to 3.3.0):

/usr/local/lib/ruby/site_ruby/2.2/rubygems/dependency.rb:310:in `to_specs': Could not find 'rouge' (~> 1.7) - did find: [rouge-2.0.5] (Gem::MissingSpecVersionError)

The Problem is that the gems (rubygem-listen and rubygem-rouge) are to new in the ports tree.

rubygem-listen is on 3.1.5
rubygem-rouge is on 2.0.5

I thought about just patching the .gemspec files but it looks like there is a good reason that jekyll is still using the old rouge gem https://github.com/jekyll/jekyll/pull/5230 and there is also a reason that jekyll-watch which is used by rubygem-jekyll doesn't work with the latest listen gem https://github.com/jekyll/jekyll-watch/commit/85290563aa2dc3d6c8ab4f55e29e43aea885e8cb

I 'fixed' it with installing old version for these gems.
pkg install /var/cache/pkg/rubygem-rouge-1.10.1.txz
pkg install /var/cache/pkg/rubygem-listen-3.0.6.txz

What is the proper solution here?
Comment 1 Zsolt Udvari freebsd_committer freebsd_triage 2016-11-18 12:29:09 UTC
Maybe it's useful to update port to 3.3.1 (it's released some days ago): http://jekyllrb.com/news/2016/11/14/jekyll-3-3-1-released/
Comment 2 Sir l33tname 2016-11-19 08:53:47 UTC
(In reply to Zsolt Udvari from comment #1)
I can do that but it will still suffer from the same problems.
Comment 3 Zsolt Udvari freebsd_committer freebsd_triage 2016-11-19 09:10:34 UTC
(In reply to Sir l33tname from comment #2)
I thought in the new release fixed this problem (I didn't check the github-links and the full changelog).
Comment 4 Sir l33tname 2016-11-19 14:33:23 UTC
Created attachment 177184 [details]
upgrade to 3.3.1

I just tested it and it's not fixed according to the github issue it's probably in jekyll 3.4
Comment 5 Mark Felder freebsd_committer freebsd_triage 2016-12-04 21:43:38 UTC
3.3.1 is already in ports tree