Push of new gem gives internal error
I'm trying to push a new gem up. This worked on Friday for me with a different one but this one seems to have problems. I've tried the gem on two machines and still get an internal error.
Here's the gemspec:
version = File.read(File.expand_path("../VERSION", __FILE__)).strip
Gem::Specification.new do |spec|
spec.platform = Gem::Platform::RUBY
spec.name = 'ninject'
spec.version = version
spec.files = Dir['lib/**/*']
spec.summary = 'Ninject is a lightweight dependency injection framework for .NET applications'
spec.description = 'Ninject is a lightweight dependency injection framework for .NET applications. It helps you split your application into a collection of loosely-coupled, highly-cohesive pieces, and then glue them back together in a flexible manner. By using Ninject to support your software’s architecture, your code will become easier to write, reuse, test, and modify.'
spec.author = 'Nate Kohari'
spec.email = '[email blocked]'
spec.homepage = 'http://ninject.org/'
spec.rubyforge_project = 'ninject'
end
And here's the output I'm getting:
C:\projects\ninject>gem push ninject-2.0.0.0.20100801.gem
Pushing gem to RubyGems.org...
<h1>Internal Server Error</h1>
I did a "gem update --system" but that hasn't helped.
Any thoughts?
2 Posted by bil.simser on 01 Aug, 2010 03:04 PM
Also here's my VERSION file that gets read in:
I've also tried it as
2.0.0.0
Neither works and produces the same error.
edit:
here's my ruby version as well:
C:\projects\ninject>ruby --version
ruby 1.9.1p378 (2010-01-10 revision 26273) [i386-mingw32]
3 Posted by bil.simser on 01 Aug, 2010 03:10 PM
Here's the metadata file when I created the gem:
4 Posted by bil.simser on 01 Aug, 2010 03:52 PM
Here's the .gem file if that helps too.
bil.simser closed this discussion on 01 Aug, 2010 04:04 PM.
bil.simser re-opened this discussion on 01 Aug, 2010 04:04 PM
5 Posted by bil.simser on 01 Aug, 2010 04:04 PM
Found the issue. There was an illegal character in the description. Thanks.
Support Staff 6 Posted by Nick Quaranto on 01 Aug, 2010 04:06 PM
Yeah, we need to catch that better. Glad this got figured out, going to keep this open until we really resolve it.