tag:help.rubygems.org,2010-01-19:/discussions/problems/188-gem-pushing-permissionsRubyGems.org: Discussion 2012-07-10T03:40:14Ztag:help.rubygems.org,2010-01-19:Comment/19580692010-06-14T19:30:03Z2011-09-02T15:29:42Zgem pushing permissions<div><p>I have a gem that still has source hosted on rubyforge svn;
eventually I'm going to move to github, but meanwhile I'd still
like to release a new gem version.</p>
<p>It was originally started by another developer; now both he and
I are committers, and both of us, ideally, would be able to push
new gem versions.</p>
<p>I've set up my Rakefile etc for jeweler. "rake build" works.
"rake release" does not, which maybe makes sense cause rake release
wants to deal with git, but this source is not in git. Okay, that's
fine.</p>
<p>So "rake gemcutter:release" ought to push to gemcutter, I think?
But I get permission denied. Probably because the gemcutter
permissions are set to the original developers account, since he
pushed a gem version back before gemcutter days.</p>
<p>How do I (or he) fix this so both of us can push released gems
to gemcutter?</p>
<p>The particular gem is 'cql-ruby',</p></div>jrochkindtag:help.rubygems.org,2010-01-19:Comment/19580692010-06-14T22:59:04Z2011-09-02T15:29:42Zgem pushing permissions<div><p>Update. The original developer, who pushed the original gem to
rubyforge, tried to push a new version using jeweler to gemcutter,
and had access denied too.</p>
<p>Much appreciated if you can help us figure out how to push a new
version of this gem</p>
<p>chickmac:CqlRuby2 chickmarkley$ rake gemcutter:release<br>
(in /Users/chickmarkley/Documents/Aptana RadRails
Workspace/CqlRuby2) Generated: cql-ruby.gemspec<br>
cql-ruby.gemspec is valid.<br>
Successfully built RubyGem Name: cql-ruby Version: 0.8.0 File:
cql-ruby-0.8.0.gem Executing "gem push
./pkg/cql-ruby-0.8.0.gem":<br>
gem push ./pkg/cql-ruby-0.8.0.gem<br>
Enter your RubyGems.org credentials.<br>
Don't have an account yet? Create one at <a href=
"http://rubygems.org/sign_up">http://rubygems.org/sign_up</a><br>
Email: [ chick at qrhino at com] Password:<br>
Signed in.<br>
Pushing gem to RubyGems.org...<br>
You do not have permission to push to this gem.<br>
rake aborted!<br>
Command failed with status (1): [gem push
./pkg/cql-ruby-0.8.0.gem...]</p></div>jrochkindtag:help.rubygems.org,2010-01-19:Comment/19580692010-06-15T01:11:46Z2010-06-15T01:11:46Zgem pushing permissions<div><p>Looks like the original developer's email is <a href=
"mailto:chick@diglib.org">chick@diglib.org</a>. If there's some
problem logging into Gemcutter with that account we can figure that
out, or if we need to merge accounts let me know.</p></div>Nick Quarantotag:help.rubygems.org,2010-01-19:Comment/19580692010-06-15T01:29:32Z2011-09-02T15:29:43Zgem pushing permissions<div><p>Thanks very much for the prompt reply. If he can log in with
that account,<br>
is there some way for him to add my account as authorized for gem
pushing?</p>
<p>If he can not (that's a very old email address he doesn't use
anymore), then<br>
we can get you to somehow either merge his new account... or add my
account<br>
as an authorized gem pusher?</p></div>jrochkindtag:help.rubygems.org,2010-01-19:Comment/19580692010-06-15T01:40:28Z2011-09-02T15:29:43Zgem pushing permissions<div><p>That is, basically, Chick is no longer actively maintaining this
software,<br>
he's given it over to me. He's made me a committer, great. But what
do<br>
people do on gemcutter in this situation, I somehow need the
ability to push<br>
out new gem releases too, is there some way to handle this?</p></div>jrochkindtag:help.rubygems.org,2010-01-19:Comment/19580692010-06-15T01:45:07Z2010-06-15T01:45:07Zgem pushing permissions<div><p>Usually what we do is that if he can respond to this thread from
<a href="mailto:chick@diglib.org">chick@diglib.org</a>, I'll
transfer the ownership over. If that's a dead email we can merge
the accounts then get it transferred over.</p></div>Nick Quarantotag:help.rubygems.org,2010-01-19:Comment/19580692010-06-15T01:46:12Z2010-06-15T01:46:12Zgem pushing permissions<div><p>And yes, he can use <code>gem owner</code> at any time once he's
in on that account:</p>
<p><a href=
"http://rubygems.org/pages/gem_docs#owner">http://rubygems.org/pages/gem_docs#owner</a></p></div>Nick Quarantotag:help.rubygems.org,2010-01-19:Comment/19580692010-06-15T15:01:15Z2011-09-02T15:29:43Zgem pushing permissions<div><p>While Chick said he didn't have access to <a href=
"mailto:chick@diglib.org">chick@diglib.org</a> anymore...<br>
somehow he managed to add me as an owner anyway. I won't worry
about the<br>
details, since all is well now. Thanks for the help.</p></div>jrochkindtag:help.rubygems.org,2010-01-19:Comment/19580692010-06-15T20:55:18Z2010-06-15T20:55:18Zgem pushing permissions<div><p>Well that was easy! Let me know if you need anything else.</p></div>Nick Quaranto