What?
sandal:prawn $ sudo gem install fastercsv -v 1.2.3
Password:
Successfully installed fastercsv-1.2.3
1 gem installed
Installing ri documentation for fastercsv-1.2.3...
Installing RDoc documentation for fastercsv-1.2.3...
http://rubyforge.org/frs/?group_id=1102
Sound like you've got something br0ken in your RubyGems. :)
I will unlock the version number on the next release since FasterCSV's
API is not going to change.
But I don't think we have a crisis here.
-greg
--
Technical Blaag at: http://blog.majesticseacreature.com
Non-tech stuff at: http://metametta.blogspot.com
"Ruby Best Practices" Book now in O'Reilly Roughcuts:
http://rubybestpractices.com
Ok I was incorrect about it being unavailable, but I think it's
understandable why one would think this:
$ sudo gem install ruport
ERROR: Error installing ruport:
ruport requires fastercsv (= 1.2.3, runtime)
This is a pretty stupid error from the gem command since the dependency
is installable as you've shown. The error indicates, to me anyway, that
Ruport is not installable. This is using rubygems 1.2.0, which is what
comes with Ubuntu 8.10, I don't know if it's fixed in the latest version
(and I don't wish to ruin my packaging system to find out).
I don't know how Rubyforge works, I thought you would be able to fix the
gem spec independently without having to make any other changes like
incrementing the version number.
Regards,
Andrew
> This is a pretty stupid error from the gem command since the dependency
> is installable as you've shown. The error indicates, to me anyway, that
> Ruport is not installable. This is using rubygems 1.2.0, which is what
> comes with Ubuntu 8.10, I don't know if it's fixed in the latest version
> (and I don't wish to ruin my packaging system to find out).
I was able to repeat this on RubyGems 1.2.0. That sucks. I'm not
sure what's going on here. It's not clear to me however that bumping
the version of FCSV is going to fix this. Is there a reason why you
assume it will?
> I don't know how Rubyforge works, I thought you would be able to fix the
> gem spec independently without having to make any other changes like
> incrementing the version number.
This messes up the file distribution mirrors which hash the packages
by filename. You should never release changed code without
incrementing at least the tiny version number, even if it's a minimal
change. It's a release integrity / security issue. You don't want to
tag some code as a snapshot and then change it. That's why systems
like git don't even let you do that.
I confirmed this is fixed in v 1.3.1 of RubyGems.
sandal:rubygems-1.3.1 $ gem -v
1.3.1
sandal:rubygems-1.3.1 $ sudo gem install ruport
Successfully installed fastercsv-1.2.3
Successfully installed ruport-1.6.1
2 gems installed
Installing ri documentation for fastercsv-1.2.3...
Installing ri documentation for ruport-1.6.1...
Installing RDoc documentation for fastercsv-1.2.3...
Installing RDoc documentation for ruport-1.6.1...
I will remove the lock in the next major release of Ruport (or in a
bug fix release if we need to roll one out anytime between now and
then), but at this point it's clear the issue is with RubyGems, and
that it has been resolved in newer versions.
Ruport users are advised to upgrade RubyGems, and if that is not
possible, to build a gem from source. I've updated the git
repository:
http://github.com/ruport/ruport