From: Tom Copeland <tom@...>
Date: 2008-04-24T10:47:25+09:00
Subject: Re: Rubyforge RubyGem propagation delay


On Mon, 2008-04-21 at 16:47 +0900, Michael Neumann wrote:
> Hi,
> 
> I noticed that when I upload a new gem to Rubyforge, it takes several
> hours until I can install it via "gem". If you try within that period
> you are getting a 404 error (at least here in Germany, maybe the mirror
> is very slow), which is annoying and leads to all kind of bug reports,
> and that you have to delay the announcement of a new version for hours.
> 
> I understand that mirrors are neccessary in this growing Ruby community,
> but if the index list (the list of available gems) would be fetched from
> the mirror, the 404 wouldn't happen.
> 
> Alternatively, a message other than 404 would be helpful to the user
> that he or she should retry later. Or what about the idea to
> contact the master rubyforge server, in case of 404?

Hi Michael -

Another option is for RubyForge to just serve up gems for the first 24
hours or so after they're released.  Jeremy Kemper did some nice rewrite
rules for this:

http://rubyforge.org/tracker/index.php?func=detail&aid=14803&group_id=5&atid=104

Just need to get that into place...

Yours,

Tom