From: Quintus <sutniuq@...>
Date: 2010-09-11T05:29:28+09:00
Subject: Re: rubyforge <-> gemcutter issues

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 10.09.2010 21:37, schrieb ara.t.howard:
>> I disconnected gem publishing to RubyForge and now gems are pushed to
>> gemcutter only while .zip and tar to RubyForge for OS packagers.
>>
>> That is what I understood and assumed.
> 
> 
> agreed - but i cannot push to any of the gems i used to own, otherwise
> that would be an option.  i honestly don't completely understand the
> whole set of problems, but i think they fall into 4 categories
> 
> 1) ownership after transfer
> 2) syncing rubyforge -> gemcutter
> 3) gems never synced
> 4) lack of a simple README re: how it supposed to work.
> 
> cheers.
> -a
> 
> 

You say you can't publish newer version of gems you own? That's really
interesting, since when rubygems.org just had started out (with the name
"gemcutter"), I had the same problem. On rubyforge.org I owned the au3
and xdo gems, but as I tried to push a new version, I was told I did not
have the rights to do so. Since Nick Quaranto stated on gemcutter.org
that one should email him if issues with gems arise, I did likewise and
within two days I was able to publish gems again.
I'n not sure if that's related to your special issue, I just wanted to
throw my own experience in, in case it helps you.

Vale,
Marvin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkyKlOcACgkQDYShvwAbcNlbKwCdGBWvcfk1bPmxFDplX8oy+84P
TysAoIDi3dzS9XHRYpaAGkgSDjtEog3J
=EmkX
-----END PGP SIGNATURE-----