tag:help.rubygems.org,2010-01-19:/discussions/problems/25897-after-i-yanked-a-version-i-can-never-push-without-an-errorRubyGems.org: Discussion 2017-03-26T22:36:28Ztag:help.rubygems.org,2010-01-19:Comment/422054562017-03-22T01:23:43Z2017-03-22T01:23:43ZAfter I yanked a version, I can never push without an error<div><p><code>Repushing of gem versions is not allowed.</code></p>
<p>This prevents you from pushing a version with different behavior. Users depend on consistent behavior of gems.</p>
<p>Change the version to 6.8.2 or 6.8.1.1.</p></div>Eric Hodeltag:help.rubygems.org,2010-01-19:Comment/422054562017-03-23T09:07:43Z2017-03-23T09:07:43ZAfter I yanked a version, I can never push without an error<div><p>The version I removed was a LONG time ago. I'm not trying to push the same version.</p></div>justin.gordontag:help.rubygems.org,2010-01-19:Comment/422054562017-03-24T03:32:42Z2017-03-24T03:32:42ZAfter I yanked a version, I can never push without an error<div><p>Eric Hodel, is there any way that I can help you troubleshoot this. As you can see from the output, we get an error, yet 6.8.1 was released!</p>
<p>Does my script seem to be trying to push twice?</p>
<p><a href="https://github.com/shakacode/react_on_rails/blob/master/rakelib/release.rake#L64">https://github.com/shakacode/react_on_rails/blob/master/rakelib/rel...</a></p></div>justin.gordontag:help.rubygems.org,2010-01-19:Comment/422054562017-03-24T20:51:23Z2017-03-24T20:51:23ZAfter I yanked a version, I can never push without an error<div><p>I opened an issue here:</p>
<p><a href="https://github.com/shakacode/react_on_rails/issues/767">https://github.com/shakacode/react_on_rails/issues/767</a></p>
<p>I need to release 6.8.2 ASAP, and maybe I can collect some logs to troubleshoot? What shall I do?</p></div>justin.gordontag:help.rubygems.org,2010-01-19:Comment/422054562017-03-24T20:59:26Z2017-03-24T20:59:26ZAfter I yanked a version, I can never push without an error<div><p>What logs did you get from trying to release 6.8.2?</p></div>Eric Hodeltag:help.rubygems.org,2010-01-19:Comment/422054562017-03-25T05:19:25Z2017-03-25T05:19:25ZAfter I yanked a version, I can never push without an error<div><p>Erick, I have not yet tried pushing this. What's the best way to ensure we get good debug information?</p></div>justin.gordontag:help.rubygems.org,2010-01-19:Comment/422054562017-03-25T05:59:06Z2017-03-25T05:59:06ZAfter I yanked a version, I can never push without an error<div><p>I tried again. Gem is published. Server sends back an error mesage.<br></p>
<pre>
<code>+ react-on-rails@6.8.2
No distRepo provided, done.
cd /Users/justin/shakacode/react-on-rails/react_on_rails && gem release
WARNING: open-ended dependency on connection_pool (>= 0) is not recommended
if connection_pool is semantically versioned, use:
add_runtime_dependency 'connection_pool', '~> 0'
WARNING: open-ended dependency on rails (>= 3.2) is not recommended
if rails is semantically versioned, use:
add_runtime_dependency 'rails', '~> 3.2'
WARNING: open-ended dependency on addressable (>= 0) is not recommended
if addressable is semantically versioned, use:
add_runtime_dependency 'addressable', '~> 0'
WARNING: open-ended dependency on rspec (>= 0, development) is not recommended
if rspec is semantically versioned, use:
add_development_dependency 'rspec', '~> 0'
WARNING: open-ended dependency on coveralls (>= 0, development) is not recommended
if coveralls is semantically versioned, use:
add_development_dependency 'coveralls', '~> 0'
WARNING: open-ended dependency on generator_spec (>= 0, development) is not recommended
if generator_spec is semantically versioned, use:
add_development_dependency 'generator_spec', '~> 0'
WARNING: open-ended dependency on pry (>= 0, development) is not recommended
if pry is semantically versioned, use:
add_development_dependency 'pry', '~> 0'
WARNING: open-ended dependency on pry-byebug (>= 0, development) is not recommended
if pry-byebug is semantically versioned, use:
add_development_dependency 'pry-byebug', '~> 0'
WARNING: open-ended dependency on pry-stack_explorer (>= 0, development) is not recommended
if pry-stack_explorer is semantically versioned, use:
add_development_dependency 'pry-stack_explorer', '~> 0'
WARNING: open-ended dependency on pry-doc (>= 0, development) is not recommended
if pry-doc is semantically versioned, use:
add_development_dependency 'pry-doc', '~> 0'
WARNING: open-ended dependency on pry-state (>= 0, development) is not recommended
if pry-state is semantically versioned, use:
add_development_dependency 'pry-state', '~> 0'
WARNING: open-ended dependency on pry-toys (>= 0, development) is not recommended
if pry-toys is semantically versioned, use:
add_development_dependency 'pry-toys', '~> 0'
WARNING: open-ended dependency on pry-rescue (>= 0, development) is not recommended
if pry-rescue is semantically versioned, use:
add_development_dependency 'pry-rescue', '~> 0'
WARNING: open-ended dependency on binding_of_caller (>= 0, development) is not recommended
if binding_of_caller is semantically versioned, use:
add_development_dependency 'binding_of_caller', '~> 0'
WARNING: open-ended dependency on awesome_print (>= 0, development) is not recommended
if awesome_print is semantically versioned, use:
add_development_dependency 'awesome_print', '~> 0'
WARNING: open-ended dependency on gem-release (>= 0, development) is not recommended
if gem-release is semantically versioned, use:
add_development_dependency 'gem-release', '~> 0'
WARNING: See http://guides.rubygems.org/specification-reference/ for help
Successfully built RubyGem
Name: react_on_rails
Version: 6.8.2
File: react_on_rails-6.8.2.gem
Pushing gem to https://rubygems.org...
Successfully registered gem: react_on_rails (6.8.2)
Deleting left over gem file react_on_rails-6.8.2.gem
WARNING: open-ended dependency on connection_pool (>= 0) is not recommended
if connection_pool is semantically versioned, use:
add_runtime_dependency 'connection_pool', '~> 0'
WARNING: open-ended dependency on rails (>= 3.2) is not recommended
if rails is semantically versioned, use:
add_runtime_dependency 'rails', '~> 3.2'
WARNING: open-ended dependency on addressable (>= 0) is not recommended
if addressable is semantically versioned, use:
add_runtime_dependency 'addressable', '~> 0'
WARNING: open-ended dependency on rspec (>= 0, development) is not recommended
if rspec is semantically versioned, use:
add_development_dependency 'rspec', '~> 0'
WARNING: open-ended dependency on coveralls (>= 0, development) is not recommended
if coveralls is semantically versioned, use:
add_development_dependency 'coveralls', '~> 0'
WARNING: open-ended dependency on generator_spec (>= 0, development) is not recommended
if generator_spec is semantically versioned, use:
add_development_dependency 'generator_spec', '~> 0'
WARNING: open-ended dependency on pry (>= 0, development) is not recommended
if pry is semantically versioned, use:
add_development_dependency 'pry', '~> 0'
WARNING: open-ended dependency on pry-byebug (>= 0, development) is not recommended
if pry-byebug is semantically versioned, use:
add_development_dependency 'pry-byebug', '~> 0'
WARNING: open-ended dependency on pry-stack_explorer (>= 0, development) is not recommended
if pry-stack_explorer is semantically versioned, use:
add_development_dependency 'pry-stack_explorer', '~> 0'
WARNING: open-ended dependency on pry-doc (>= 0, development) is not recommended
if pry-doc is semantically versioned, use:
add_development_dependency 'pry-doc', '~> 0'
WARNING: open-ended dependency on pry-state (>= 0, development) is not recommended
if pry-state is semantically versioned, use:
add_development_dependency 'pry-state', '~> 0'
WARNING: open-ended dependency on pry-toys (>= 0, development) is not recommended
if pry-toys is semantically versioned, use:
add_development_dependency 'pry-toys', '~> 0'
WARNING: open-ended dependency on pry-rescue (>= 0, development) is not recommended
if pry-rescue is semantically versioned, use:
add_development_dependency 'pry-rescue', '~> 0'
WARNING: open-ended dependency on binding_of_caller (>= 0, development) is not recommended
if binding_of_caller is semantically versioned, use:
add_development_dependency 'binding_of_caller', '~> 0'
WARNING: open-ended dependency on awesome_print (>= 0, development) is not recommended
if awesome_print is semantically versioned, use:
add_development_dependency 'awesome_print', '~> 0'
WARNING: open-ended dependency on gem-release (>= 0, development) is not recommended
if gem-release is semantically versioned, use:
add_development_dependency 'gem-release', '~> 0'
WARNING: See http://guides.rubygems.org/specification-reference/ for help
Successfully built RubyGem
Name: react_on_rails
Version: 6.8.2
File: react_on_rails-6.8.2.gem
Pushing gem to https://rubygems.org...
Repushing of gem versions is not allowed.
Please use <code>gem yank</code> to remove bad gem releases.
rake aborted!
Command failed with status (1): [cd /Users/justin/shakacode/react-on-rails/...]
/Users/justin/shakacode/react-on-rails/react_on_rails/rakelib/task_helpers.rb:20:in <code>block in sh_in_dir&#39;
/Users/justin/shakacode/react-on-rails/react_on_rails/rakelib/task_helpers.rb:20:in</code>each'
/Users/justin/shakacode/react-on-rails/react_on_rails/rakelib/task_helpers.rb:20:in <code>sh_in_dir&#39;
/Users/justin/shakacode/react-on-rails/react_on_rails/rakelib/release.rake:64:in</code>block in <top (required)>'
/Users/justin/.rvm/gems/ruby-2.3.1@react_on_rails/gems/rake-12.0.0/exe/rake:27:in `<top (required)>'
Tasks: TOP => release
(See full trace by running task with --trace)</code>
</pre></div>justin.gordontag:help.rubygems.org,2010-01-19:Comment/422054562017-03-26T22:36:24Z2017-03-26T22:36:24ZAfter I yanked a version, I can never push without an error<div><p>I'm going to close this since it's not a rubygems problem, further discussion can happen on this issue: <a href="https://github.com/svenfuchs/gem-release/issues/63">https://github.com/svenfuchs/gem-release/issues/63</a></p></div>David Radcliffe