On 10/14/05, Austin Ziegler <halostatue / gmail.com> wrote:

> Yes. This problem has been noted as something originating with 1.8.3
> and syck. The only reason, I think, that the Gems team doesn't have
> something out that could handle this and/or fix this is because most
> of them are heavily involved in RubyConf preparations.

Okay thanks Austin!

T.