[Rubygems-developers] invalid Gem::Specification format

[Jeremy d]

Hello,
I'm currently using rubygems version 1.0.1 with the
--no-update-sources option. Basically, I'm doing a 'gem sources -u'
to refresh the index, and then a gem install rails --version 1.2.3
--no-update-sources for speedup reasons. When the new mirror came
online this weekend gem was no longer able to find gems in the sources
cache. I'm including the debug output below, it seems that one of the
gemspecs is not recognized by version 1.0.1 as a valid format
(possible the version string?)

Is this behavior a bug or desired behavior? Without the
--no-update-sources option gem successfully does a bulk update and the
installation succeeds.

Thanks!
-Jeremy

Exception `TypeError' at
/usr/lib/ruby/site_ruby/1.8/rubygems/specification.rb:271 - invalid
Gem::Specification format ["1.1.1", 3, "geminstaller", #<Gem::Version
"0.4.2">, Thu Jun 19 03:00:00 -0400 2008, "Automated Gem installation,
activation, and much more!", #<Gem::Requirement:0xb6675ed8
@version=nil, @requirements=[[">=", #<Gem::Version "0">]]>,
#<Gem::Requirement:0xb6675dd4 @version=nil, @requirements=[[">=",
#<Gem::Version "0">]]>, "ruby", [], "geminstaller",
"thewoo...@gmail.com", ["Chad Woolley"], "Automated Gem
installation, activation, and much more! == FEATURES: GemInstaller
provides automated installation, loading and activation of RubyGems.
It uses a simple YAML config file to: * Automatically install the
correct versions of all required gems wherever your app runs. *
Automatically ensure installed gems and versions are consistent across
multiple applications, machines, platforms, and environments *
Automatically activate correct versions of gems on the ruby load path
when your app runs ('require_gem'/'gem') * Automatically reinstall
missing dependency gems (built in to RubyGems &gt; 1.0) *
Automatically detect correct platform to install for multi-platform
gems (built in to RubyGems &gt; 1.0) * Print YAML for \"rogue gems\"
which are not specified in the current config, to easily bootstrap
your config file, or find gems that were manually installed without
GemInstaller. * Allow for common configs to be reused across projects
or environments by supporting multiple config files, including common
config file snippets, and defaults with overrides. * Allow for dynamic
selection of gems, versions, and platforms to be used based on
environment vars or any other logic. * Avoid the \"works on demo,
breaks on production\" syndrome * Solve world hunger, prevent the
global energy crisis, and wash your socks. == SYNOPSYS:", " by
Chad Woolley", true, "ruby"]
Exception `Gem::GemNotFoundException' at
/usr/lib/ruby/site_ruby/1.8/rubygems/dependency_installer.rb:87 -
could not find rails locally or in a repository
ERROR: could not find rails locally or in a repository
_______________________________________________
Rubygems-developers mailing list
Rubygems-...@rubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-developers

[Chad Woolley]

On Tue, Jun 24, 2008 at 9:53 AM, Jeremy d <jeremyd...@gmail.com> wrote:
> Exception `TypeError' at
> /usr/lib/ruby/site_ruby/1.8/rubygems/specification.rb:271 - invalid
> Gem::Specification format ["1.1.1", 3, "geminstaller", #<Gem::Version
> "0.4.2">, Thu Jun 19 03:00:00 -0400 2008, "Automated Gem installation,

Hi,

This was apparently because I built the GemInstaller 0.4.2 gem with a
pre-1.2.0 release of RubyGems.

I have since re-released GemInstaller 0.4.3 built with RubyGems 1.2.0
official, and deleted the 0.4.2 release off of RubyForge. I hope this
fixes everything!

[Ryan Davis]

On Jun 24, 2008, at 13:41 , Chad Woolley wrote:

> On Tue, Jun 24, 2008 at 9:53 AM, Jeremy d
> <jeremyd...@gmail.com> wrote:
>> Exception `TypeError' at
>> /usr/lib/ruby/site_ruby/1.8/rubygems/specification.rb:271 - invalid
>> Gem::Specification format ["1.1.1", 3, "geminstaller", #<Gem::Version
>> "0.4.2">, Thu Jun 19 03:00:00 -0400 2008, "Automated Gem
>> installation,
>
> Hi,
>
> This was apparently because I built the GemInstaller 0.4.2 gem with a
> pre-1.2.0 release of RubyGems.
>
> I have since re-released GemInstaller 0.4.3 built with RubyGems 1.2.0
> official, and deleted the 0.4.2 release off of RubyForge. I hope this
> fixes everything!

deletions don't replicate, unfortunately... it'd be quicker and easier
(until we get ahold of tom) to push another 0.4.2. Sucks... I've been
bitten by this before too.

[Jeremy d]

Chad,
The re-release of 0.4.2 fixed the problem I was encountering. Thanks!

-Jeremy