On Sep 15, 2009, at 12:21 PM, aslak hellesoy wrote:
From rubygems' perspective though, I wish it didn't query *all* of
the .gemspec.rz's though :/
Thanks for dealing with this so quickly Nick!
I'll still add the workaround, since rubygems will bail if *one*
server (even if it is the last one in the --source list) doesn't
have a gem.
Is this a known issue, rubygems folks? Should I file a bug?
A very brief look through the tracker led to this:
http://rubyforge.org/tracker/index.php?func=detail&aid=25816&group_id=126&atid=575
Same issue? If so, please drop any extra info you have on that ticket.
Thanks!
~ j.
Aslak
-Nick
On Tue, Sep 15, 2009 at 3:03 PM, aslak hellesoy <aslak.helle...@gmail.com
> wrote:
On Tue, Sep 15, 2009 at 8:22 PM, darrinholst
<darrin.ho...@gmail.com> wrote:
I was having that problem earlier today, are you still getting that
error? I'm not anymore, but I'm on a different internet connection
now. I suppose if rubyforge was have some problems you would see that,
but 0.3.100 is out on gemcutter too, so both of them would have to be
down (assuming you're using 0.3.100).
This seems to be a combination of unreliable gem servers and a bug
in rubygems (at least with rubygems 1.3.3, which is bundled with
jruby 1.3.1):
jruby -S gem install --source http://gems.rubyforge.org celerity -
v0.0.7 -V
GET 304 Not Modified: http://gems.rubyforge.org/specs.4.8.gz
Installing gem celerity-0.0.7
/usr/local/jruby-1.3.1/lib/ruby/gems/1.8/gems/celerity-0.0.7/
History.txt
/usr/local/jruby-1.3.1/lib/ruby/gems/1.8/gems/celerity-0.0.7/
License.txt
(snip)
Successfully installed celerity-0.0.7
1 gem installed
Installing ri documentation for celerity-0.0.7...
Installing RDoc documentation for celerity-0.0.7...
Could not find main page README.rdoc
Could not find main page README.rdoc
Could not find main page README.rdoc
Could not find main page README.rdoc
OK!
jruby -S gem install --source http://gems.rubyforge.org --source http://gemcutter.org
celerity -v0.0.7 -V
GET 304 Not Modified: http://gems.rubyforge.org/specs.4.8.gz
GET 200 OK: http://gemcutter.org/specs.4.8.gz
connection reset after 2 requests, retrying
GET 500 Internal Server Error:
http://gemcutter.org/quick/Marshal.4.8/celerity-0.0.7.gemspec.rz
Error fetching remote data: bad response Internal Server
Error 500 (http://gemcutter.org/quick/Marshal.4.8/celerity-0.0.7.gemspec.rz
)
Falling back to local-only install
ERROR: could not find gem celerity locally or in a repository
FAIL!
IMO, this is a bug in rubygems because it bails on the first 500
from one of the servers, not even trying the other one. It doesn't
help that it attempts the last server first. There is also something
wrong with gemcutter - it reports that the celerity gem is there: http://gemcutter.org/gems/celerity
. Still, download fails. While I'm at it - it might be wise to add
some 304 to gemcutter for improved performance...
I will resurrect the cuke4duke maven plugin <gem> syntax that lets
you specify *where* to get the gem from as a workaround for this
until rubygems and gemcutter are fixed...
Apologies to ittyad, whose ticket (http://github.com/aslakhellesoy/cuke4duke/issues/closed#issue/
22) I dismissed as user error.
Aslak
Darrin
On Sep 15, 5:57 am, torbjornvatn <torbj...@vatn.org> wrote:
> My cuke4duke project won't build any more when run with the -
> Dcucumber.installGems=true option.
>
> I found that the reason is an "ERROR: could not find gem cucumber
> locally or in a repository" error that occurs during the gem
install.
>
> If I run gem install on the command line it works if I remove the --
> source arguments all together or when I use the --sourcehttp://gems.rubyforge.org
.
> Both gemcutter and github source repos fail when use alone, but
> strangely the github one works in combination with rubyforge.
>
> Anyone got any ideas about what's causing this?
>
> /torbjørn
_______________________________________________
Rubygems-developers mailing list
http://rubyforge.org/projects/rubygems
Rubygems-developers@rubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-developers
