From: Ryan Davis <ryand-ruby@...>
Date: 2010-09-11T05:23:54+09:00
Subject: Re: rubyforge <-> gemcutter issues


On Sep 10, 2010, at 07:59 , ara.t.howard wrote:

> this is an issue gem publishers need to be aware off:
> 
>  http://help.rubygems.org/discussions/problems/318-original-sync-to-rubyforge-never-worked-what-now
> 
> until it's fixed it's possible that your releases are not making it to
> other people's machines during 'gem install'

From the ticket:

> for example, i own the options gem. it's been updated on rubyforge (via api) several times. over here we see (grep page for options) options 2.2.0 has been released:
> 
> http://rubyforge.org/frs/?group_id=1024&amp;release_id=43932
> 
> yet a search on gemcutter results in:
> 
> http://rubygems.org/search?utf8=%E2%9C%93&amp;query=options
> 
> in my case gemcutter has effectively stolen about 100 of my gems - the system owns them and i cannot release fixes.

Wasn't this latter issue addressable via `gem owner`?

    owner             Manage gem owners on RubyGems.org.

I seem to recall having to fire off a whole mess of those after the transition and haven't had many of the issues you're having. Tho I did adapt hoe to publish to gemcutter as well as to rubyforge, so I'm prolly masking it somewhat.