tag:help.rubygems.org,2010-01-19:/discussions/problems/981-i-need-a-gem-permanently-removed-so-i-can-push-a-new-artifact-in-its-place-torquebox-server-200RubyGems.org: Discussion 2012-04-02T18:46:28Ztag:help.rubygems.org,2010-01-19:Comment/149622862012-04-02T16:26:24Z2012-04-02T16:26:26ZI need a gem permanently removed so I can push a new artifact in its place - torquebox-server 2.0.0<div><p>A team member accidentally pushed a torquebox-server 2.0.0 gem
back in October. He yanked it, but now we're ready to publish the
actual 2.0.0 gem, and cannot. He yanked it before we had released
any other version of that gem, and <a href=
"http://help.rubygems.org/kb/gemcutter/removing-a-published-rubygem">
http://help.rubygems.org/kb/gemcutter/removing-a-published-rubygem</a>
led us to believe that if someone else pushed the gem, we could
reclaim the namespace:</p>
<pre>
<code>Once you've yanked all versions of a gem the namespace is free for others to use. If you accidentally pushed the wrong name once yank it and it'll be free for others to use.</code>
</pre>
<p>Which we assumed would allow us to push the 2.0.0 version again
as well, but this is not the case.</p>
<p>We're trying to get this release out today, so any help you can
give would be greatly appreciated.</p></div>Toby Crawleytag:help.rubygems.org,2010-01-19:Comment/149622862012-04-02T18:46:28Z2012-04-02T18:46:28ZI need a gem permanently removed so I can push a new artifact in its place - torquebox-server 2.0.0<div><p>I've corrected the 2.0.0 version, you should be able to push it
now.</p></div>Evan Phoenix