Re: [rubygems.org] gem push rejected for existing gem

Nick Quaranto

unread,

Apr 6, 2013, 8:19:04 AM4/6/13

to rubyge...@googlegroups.com

Can you post the gemspec? @rubygems is happily tweeting new versions still so I doubt it's broken for everyone.

On Saturday, April 6, 2013, Mark Ryall wrote:

Hi,

I'm just trying to push a new version of an existing gem (chicanery) and get:

Pushing gem to https://rubygems.org...

<html>
<head><title>405 Not Allowed</title></head>
<body bgcolor="white">
<center><h1>405 Not Allowed</h1></center>

<hr><center>nginx</center>
</body>
</html>

I regenerated my api key and was able to push a new gem using the same credentials.

Anyone else experienced a similar issue?

Mark.

--
You received this message because you are subscribed to the Google Groups "rubygems.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubygems-org...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Nick Quaranto

unread,

Apr 6, 2013, 10:11:07 AM4/6/13

to rubyge...@googlegroups.com

Looks like nginx is rejecting pushes. I'm not sure what has changed in the past 12-24 hours to make this happen, and I'm not sure how to update the nginx configuration (or what box it even lives on).

Stuff like this shouldn't rely on one person to fix. We need a call tree, or something. Our bus factor should not be 1.

I've pinged the ops/rubygems-aws folks and waiting for a response.

On Sat, Apr 6, 2013 at 9:40 AM, Mark Ryall <mark....@gmail.com> wrote:

Same here:

# -*- encoding: utf-8 -*-
lib = File.expand_path('../lib', __FILE__)

$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
require 'chicanery'

Gem::Specification.new do |gem|
gem.name = "chicanery"

gem.version = Chicanery::VERSION
gem.authors = ["Mark Ryall"]
gem.email = ["m...@ryall.name"]

gem.description = %q{trigger various events related to a continuous integration environment}
gem.summary = %q{polls various resources related to a ci environment and performs custom notifications}

gem.homepage = "http://github.com/markryall/chicanery"

gem.files = `git ls-files`.split($/)

gem.executables = gem.files.grep(%r{^bin/}).map{ |f| File.basename(f) }
gem.test_files = gem.files.grep(%r{^(test|spec|features)/})
gem.require_paths = ["lib"]

gem.add_dependency 'nokogiri', '~>1'

gem.add_development_dependency 'rake', '~>0'
gem.add_development_dependency 'rspec', '~>2'

gem.add_development_dependency 'simplecov'
gem.add_development_dependency 'simplecov-gem-adapter'
gem.add_development_dependency 'vcr'
gem.add_development_dependency 'webmock', '<1.10'

end

I was able to yank an old version of the gem but not push a new one.

On Saturday, 6 April 2013 22:43:36 UTC+10, Mart Karu wrote:

Hi,

This seems to be pretty standard/generated gemspec, looks fine to me:

# -*- encoding: utf-8 -*-
lib = File.expand_path('../lib', __FILE__)
$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
require 'imagga/version'

Gem::Specification.new do |gem|

gem.name = "imagga"
gem.version = Imagga::VERSION
gem.authors = ["Mart Karu"]
gem.email = ["ka...@metal.ee"]

gem.description = %q{Ruby client for accessing Imagga API}
gem.summary = %q{Ruby client for accessing Imagga API}
gem.homepage = ""

gem.files = `git ls-files`.split($/)
gem.test_files = gem.files.grep(%r{^(test|spec|features)/})
gem.require_paths = ["lib"]

gem.add_dependency "httparty", "~> 0.10"

gem.add_dependency "json", "~> 1.7"
gem.add_dependency "color", "~> 1.4.1"

gem.add_development_dependency "rspec", "~> 2.12"

gem.add_development_dependency "rake"
gem.add_development_dependency "fakeweb"
end

Nick Quaranto

unread,

Apr 6, 2013, 11:55:30 AM4/6/13

to rubyge...@googlegroups.com

Yep! Fixed. Sorry about this.

On Sat, Apr 6, 2013 at 11:52 AM, Mart Karu <karu...@gmail.com> wrote:

It looks like it is resolved now, just puhsed the gem successfully.

Karl Krukow

unread,

Oct 2, 2013, 6:05:31 PM10/2/13

to rubyge...@googlegroups.com

On Saturday, April 6, 2013 4:11:07 PM UTC+2, Nick Quaranto wrote:

Looks like nginx is rejecting pushes. I'm not sure what has changed in the past 12-24 hours to make this happen, and I'm not sure how to update the nginx configuration (or what box it even lives on).

I've started seeing this tonight

gem push pkg/calabash-cucumber-0.9.159.gem

Pushing gem to https://rubygems.org...

<html>

<head><title>405 Not Allowed</title></head>

<center><h1>405 Not Allowed</h1></center>

<hr><center>nginx</center>

</body>

</html>

Stuff like this shouldn't rely on one person to fix. We need a call tree, or something. Our bus factor should not be 1.

Do we still have bus factor 1 ? :)

Reply all

Reply to author

Forward