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/
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
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.Thanks.
Zed A. Shaw
http://www.zedshaw.com/
http://mongrel.rubyforge.org/
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.
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.
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
On 4/6/06 8:00 PM, "Gregory Brown" <gregory.t.brown@gmail.com> wrote:
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.
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
On Thu, 2006-04-06 at 17:23 -0500, Curt Hibbs wrote:
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.
>
> Thanks.
>
> 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.
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
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.
Doh! Sorry, that should be, Dennis _Oelkers_.
Yours,
Tom
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.