[Rubygems-developers] gem dependencies not working in rubygems 1.2.0 on MacOS 10.5.3

Luis Lavena luislavena at gmail.com
Fri Jul 4 02:26:00 EDT 2008


On Fri, Jul 4, 2008 at 7:02 AM, Chad Woolley <thewoolleyman at gmail.com> wrote:
> On Thu, Jul 3, 2008 at 1:47 PM, Stephen Bannasch
> <stephen.bannasch at deanbrook.org> wrote:
>> sake didn't (dependencies listed, but not acted on)
>>
>> Perhaps there is a way the dependencies are defined in sake (and perhaps other gems) that used to work and stopped working with 1.2.0.
>
> Looks like a bug, I reproduced it.  Eric should take a look.  Here's
> the debug output:
>
> chadmac:~ woolley$ sudo gem install sake
> ERROR:  Error installing sake:
>        sake requires ParseTree (= 2.1.1, runtime)
> chadmac:~ woolley$ sudo gem install sake --debug --verbose
> Exception `NameError' at
> /Library/Ruby/Site/1.8/rubygems/command_manager.rb:134 - uninitialized
> constant Gem::Commands::InstallCommand
> HEAD 200 OK: http://gems.rubyforge.org/latest_specs.4.8
> Installing gem sake-1.0.15
> Exception `IOError' at /Library/Ruby/Site/1.8/rubygems/format.rb:50 -
> closed stream
> Exception `Gem::InstallError' at
> /Library/Ruby/Site/1.8/rubygems/installer.rb:175 - sake requires
> ParseTree (= 2.1.1, runtime)
> ERROR:  Error installing sake:
>        sake requires ParseTree (= 2.1.1, runtime)

I can confirm the same issue here.

If you manually install ParseTree:

gem install ParseTree --version '= 2.1.1'

It install properly...

-- 
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams


More information about the Rubygems-developers mailing list