Bug 204339 - devel/rubygem-pry broke in svn commit 399570
Summary: devel/rubygem-pry broke in svn commit 399570
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-ports-bugs mailing list
Depends on: 204338
  Show dependency treegraph
Reported: 2015-11-06 18:01 UTC by Nick Hilliard
Modified: 2015-11-08 00:11 UTC (History)
3 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Nick Hilliard 2015-11-06 18:01:41 UTC
rubygem-pry was broken with commit 399570, which made it accept slop 4.2.0:


pry uses slop 3.x only and does not work with slop 4:

> % pry
> /usr/local/lib/ruby/gems/2.1/gems/pry-0.10.3/lib/pry/cli.rb:100:in `<top (required)>': undefined method `new' for Slop:Module (NoMethodError)
> 	from /usr/local/lib/ruby/site_ruby/2.1/rubygems/core_ext/kernel_require.rb:54:in `require'
> 	from /usr/local/lib/ruby/site_ruby/2.1/rubygems/core_ext/kernel_require.rb:54:in `require'
> 	from /usr/local/lib/ruby/gems/2.1/gems/pry-0.10.3/lib/pry.rb:150:in `<top (required)>'
> 	from /usr/local/lib/ruby/site_ruby/2.1/rubygems/core_ext/kernel_require.rb:54:in `require'
> 	from /usr/local/lib/ruby/site_ruby/2.1/rubygems/core_ext/kernel_require.rb:54:in `require'
> 	from /usr/local/lib/ruby/gems/2.1/gems/pry-0.10.3/bin/pry:9:in `<top (required)>'
> 	from /usr/local/bin/pry:23:in `load'
> 	from /usr/local/bin/pry:23:in `<main>'
> %

The correct freebsd fix is to add a slop3 port and make the pry port depend on devel/rubygem-slop3.  I've just submitted bug #204338 for this.
Comment 1 commit-hook freebsd_committer 2015-11-08 00:09:43 UTC
A commit references this bug:

Author: mmoll
Date: Sun Nov  8 00:09:07 UTC 2015
New revision: 401029
URL: https://svnweb.freebsd.org/changeset/ports/401029

  devel/rubygem-pry: use devel/rubygem-slop3

  PR:		204339

Comment 2 Michael Moll freebsd_committer 2015-11-08 00:11:04 UTC
Should be fixed now, thanks for reporting!