Bug 197083 - [exp-run] devel/ruby-gems: update to 2.4.5
Summary: [exp-run] devel/ruby-gems: update to 2.4.5
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Ports Framework (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Steve Wills
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-26 04:27 UTC by Steve Wills
Modified: 2015-04-07 18:56 UTC (History)
2 users (show)

See Also:


Attachments
patch to update devel/ruby-gems to 2.4.5 and fix fallout (110.54 KB, patch)
2015-01-26 04:27 UTC, Steve Wills
no flags Details | Diff
updated patch fixing patch issues (115.35 KB, patch)
2015-02-13 16:02 UTC, Steve Wills
no flags Details | Diff
further updated patch (118.50 KB, patch)
2015-02-16 02:17 UTC, Steve Wills
no flags Details | Diff
updated patch (127.45 KB, patch)
2015-02-16 19:27 UTC, Steve Wills
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Wills freebsd_committer 2015-01-26 04:27:52 UTC
Created attachment 152148 [details]
patch to update devel/ruby-gems to 2.4.5 and fix fallout

Attached patch updates devel/ruby-gems to the latest.

One side effect of this update is that the gemspec file uses a different name and different format, so all the patches that touch those have to be redone. Attached patch also fixes that. This is hopefully a one time operation and has the nice side effect that in the future the filename for the gemspec won't change based on the version number so hopefully won't need to be touched when updating gems.

Please test the patch and assure me that I didn't break miss any fixes. I probably have them locally but may not have included them in the patch. Even if I don't, should be easy fixes.

Thanks,
Steve
Comment 1 Antoine Brodin freebsd_committer 2015-01-26 19:53:33 UTC
Take for exp-run
Comment 2 Antoine Brodin freebsd_committer 2015-01-26 21:20:17 UTC
The following ports fail to patch,  could you provide an updated patch?

www/rubygem-actionpack
devel/rubygem-bones
devel/rubygem-pygments.rb
net/rubygem-t
net-mgmt/rubygem-visage-app
net/rubygem-amqp-utils
devel/rubygem-travis

Also, it seems extensions are put in 3 different places ( lib/ruby/gems/2.0/extensions/$arch/2.0/$gemname/, lib/ruby/gems/2.0/gems/$gemname/ext/$gemname/,  and lib/ruby/gems/2.0/gems/$gemname/lib/ ), is this normal?
Comment 3 Antoine Brodin freebsd_committer 2015-02-04 22:32:40 UTC
waiting for an updated patch
Comment 4 Steve Wills freebsd_committer 2015-02-13 16:02:41 UTC
Created attachment 152938 [details]
updated patch fixing patch issues

Here's the updated patch, sorry for the delay. Having extensions in multiple places is normal.
Comment 5 Antoine Brodin freebsd_committer 2015-02-13 16:05:54 UTC
Take
Comment 6 Antoine Brodin freebsd_committer 2015-02-15 13:05:48 UTC
The following ports failed to patch:

www/rubygem-railties  (30 skipped)
www/rubygem-jekyll

There is a new failure:

science/rubygem-netcdf

failure log:

http://package18.nyi.freebsd.org/data/101amd64-default-197083/2015-02-15_08h40m51s/logs/errors/rubygem-netcdf-0.6.6.1_1.log
Comment 7 Steve Wills freebsd_committer 2015-02-16 02:17:30 UTC
Created attachment 153023 [details]
further updated patch

Will look into the netcdf issue. In the mean time, this should fix the railties and jekyll issues.
Comment 9 Steve Wills freebsd_committer 2015-02-16 19:27:22 UTC
Created attachment 153051 [details]
updated patch

Here's an updated patch which fixes the rubygem-netcdf issue.
Comment 10 Steve Wills freebsd_committer 2015-04-07 18:56:58 UTC
Done, closing.