On Sun, Nov 22, 2009 at 4:03 PM, Assaf Arkin <as...@labnotes.org> wrote:
> On Sun, Nov 22, 2009 at 8:30 AM, Alex Boisvert <alex.boisv...@gmail.com > >wrote: > > > Does anybody want to update our release scripts to update the gemcutter > > index? I'm not too familiar with gemcutter yet. It is only a matter of > > adding "gem push" ? > > > > Yep. Simpler and faster. Only problem is transferring ownership from > rubyforge to gemcutter. When I run gem migrate it hangs, does it work for > you? > Doesn't work either but for a different reason. boisv...@smudge:~$ gem migrate buildr Starting migration of buildr from RubyForge... A migration token has been created. Uploading the migration token to buildr.rubyforge.org. Successfully uploaded your token. Asking Gemcutter to verify the upload... Gemcutter is still looking for your migration token. boisv...@smudge:~$ > > Also, this just in: https://www.javagems.org/ > > "Created because we'd rather not use Maven. JavaGems provides gem hosting > and gem creation for the JVM-based-language community. Instantly > publish your gems and install them. Use the API to interact and find out > more information about available gems." > Revolutions never go backwards ;) alex
