Forum: Ruby Gem mirrors not updating?

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
8c43ed7f065406bf171c0f3eb32cf615?d=identicon&s=25 Zed Shaw (Guest)
on 2006-04-06 21:22
(Received via mailing list)
Hi,

Just wondering if anyone else who maintains gems on rubyforge.org has
posted
a gem recently and seen it not migrate to the gem mirrors?  I post
Mongrel
0.3.12.3 and it's not there yet, but not sure if that's because I
formatted
it wrong or some such.

Thanks.

Zed A. Shaw
http://www.zedshaw.com/
http://mongrel.rubyforge.org/
C475cffda1800fbc3f3af17bc10c220f?d=identicon&s=25 Curt Hibbs (Guest)
on 2006-04-07 00:25
(Received via mailing list)
On 4/6/06, Zed Shaw <zedshaw@zedshaw.com> wrote:
> http://www.zedshaw.com/
> http://mongrel.rubyforge.org/

Its all automated, but if there's a problem then Tom Copeland would
probably be the one to talk to. I took the liberty of forwarding this
to him.

Curt
31e038e4e9330f6c75ccfd1fca8010ee?d=identicon&s=25 Gregory Brown (Guest)
on 2006-04-07 02:02
(Received via mailing list)
On 4/6/06, Zed Shaw <zedshaw@zedshaw.com> wrote:
> Hi,
>
> Just wondering if anyone else who maintains gems on rubyforge.org has posted
> a gem recently and seen it not migrate to the gem mirrors?  I post Mongrel
> 0.3.12.3 and it's not there yet, but not sure if that's because I formatted
> it wrong or some such.

This might be an obvious question, but did you build with 1.8.3

If so, you probably hit the dreaded bug which makes your gems never go
into rotation.
8c43ed7f065406bf171c0f3eb32cf615?d=identicon&s=25 Zed Shaw (Guest)
on 2006-04-07 21:27
(Received via mailing list)
Nope, 1.8.4 but they updated eventually.  I'd heard of the 1.8.3 and was
just wondering if there were other known things to avoid.

Zed A. Shaw
http://www.zedshaw.com/
http://mongrel.rubyforge.org/
560c83ff6b6600e39315a1cf75b7c229?d=identicon&s=25 Tom Copeland (Guest)
on 2006-04-11 00:20
(Received via mailing list)
On Sat, 2006-04-08 at 04:24 +0900, Zed Shaw wrote:
> Nope, 1.8.4 but they updated eventually.  I'd heard of the 1.8.3 and was
> just wondering if there were other known things to avoid.

Yup, it can be about an hour or so before a gem propagates out to all
the mirrors.  Dennis Oeklers and I are working on a method to push out
new gems that should reduce that delay considerably.

Yours,

Tom
560c83ff6b6600e39315a1cf75b7c229?d=identicon&s=25 Tom Copeland (Guest)
on 2006-04-11 00:24
(Received via mailing list)
On Thu, 2006-04-06 at 17:23 -0500, Curt Hibbs wrote:
> > Zed A. Shaw
> > http://www.zedshaw.com/
> > http://mongrel.rubyforge.org/
>
> Its all automated, but if there's a problem then Tom Copeland would
> probably be the one to talk to. I took the liberty of forwarding this
> to him.

Doh, sorry, I didn't see this because my mail filters put it in the
folder with the other (unread) ruby-lang messages.  Just catching up
now...

Yours,

Tom
560c83ff6b6600e39315a1cf75b7c229?d=identicon&s=25 Tom Copeland (Guest)
on 2006-04-11 01:06
(Received via mailing list)
On Tue, 2006-04-11 at 07:19 +0900, Tom Copeland wrote:
> On Sat, 2006-04-08 at 04:24 +0900, Zed Shaw wrote:
> > Nope, 1.8.4 but they updated eventually.  I'd heard of the 1.8.3 and was
> > just wondering if there were other known things to avoid.
>
> Yup, it can be about an hour or so before a gem propagates out to all
> the mirrors.  Dennis Oeklers and I are working on a method to push out
> new gems that should reduce that delay considerably.

Doh!  Sorry, that should be, Dennis _Oelkers_.

Yours,

Tom
This topic is locked and can not be replied to.