New Ticket     Tickets     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #12358 (closed defect: fixed)

Opened 6 years ago

Last modified 4 years ago

BUG: rb-activesupport install failing.

Reported by: jacoblanemcp@… Owned by: mr_bond@…
Priority: High Milestone:
Component: ports Version: 1.7.0
Keywords: Ruby rb-activesupport rb-gems Cc: rcavanaugh@…
Port:

Description

This has been a documented bug with MacPorts for some time now. Surprised it has not been resolved in the transition from 1.4 to 1.5. Again, when installing the Ruby suite of tools, rb-activesupport (and others) fail with the following error code below. This error seems to stem from the rb-gems install, which some claim needs to be installed manually ... as in, outside of MacPorts ... to work correctly. Other hacks and workarounds are also available. Maybe we could incorporate one that would resolve this? A ticket was issued for this bug over four months ago, but had been ignored to date:

Links to this issue:

http://www.mail-archive.com/macports-users@lists.macosforge.org/msg02181.html

http://trac.macports.org/projects/macports/ticket/11751

Is there anyone working on Ruby package issues there?

root# port install rb-activesupport
--->  Staging rb-activesupport into destroot
Error: Target org.macports.destroot returned: shell command "/opt/local/bin/gem install --local --force --install-dir /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_ruby_rb-activesupport/work/destroot/opt/local/lib/ruby/gems/1.8 /opt/local/var/macports/distfiles/ruby/activesupport-1.4.2" returned error 1
Command output: /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require': no such file to load -- sources (LoadError)
        from /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:27:in `require'
        from /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/source_info_cache.rb:6
        from /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require'
        from /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:27:in `require'
        from /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/remote_installer.rb:12
        from /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require'
        from /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:27:in `require'
        from /opt/local/lib/ruby/vendor_ruby/1.8/rubygems.rb:112:in `manage_gems'
        from /opt/local/bin/gem:10

Error: Status 1 encountered during processing.
root#

Change History

comment:1 Changed 6 years ago by nox@…

  • Priority changed from Blocker to High
  • Cc rcavanaugh@… added
  • Version 1.5.0 deleted
  • Summary changed from rb-gems / rb-activesupport install failing. to BUG: rb-activesupport install failing.

Added maintainers to Cc.

comment:2 Changed 6 years ago by noah@…

There is an easy workaround to the bug. The port rb-activesuppport is failing when it tries to install its dependency of rb-rubygems (I believe it may just be an out-of-date -- 0.9.1 -- version of rb-rubygems). If you install the rb-rubygems 0.9.4 port _first_ and then install rb-activesupport there is no problem.

comment:3 Changed 5 years ago by daniel.bond@…

http://trac.macosforge.org/projects/macports/ticket/13815 should fix this, once both a new macports version is rolled out (ruby.setup fetch method, and fixed ruby group resource file).

I'll make new portfiles for rb-activesupport, rb-rubyonrails etc, when I've got the new rubygems 1.1.0 commited.

comment:4 Changed 5 years ago by mr_bond@…

  • Status changed from new to assigned
  • Owner changed from macports-tickets@… to mr_bond@…

comment:5 Changed 5 years ago by mr_bond@…

  • Version set to 1.7.0

The ruby-portgroup is broken.

comment:6 Changed 5 years ago by mr_bond@…

for now use "gem install <gem>"

comment:7 Changed 5 years ago by pguyot@…

  • Status changed from assigned to closed
  • Resolution set to fixed

Fixed in r39397.

comment:8 Changed 4 years ago by anonymous

  • Milestone Port Bugs deleted

Milestone Port Bugs deleted

Note: See TracTickets for help on using tickets.