Bundler reports that gemspec is not valid about serverspec-aws HOT 5 CLOSED

Hi. Sorry about that. Should probably take out the gemspec file out of the repo. It is generated by a rake task using jeweler. And, of course, fix the task to generate a proper gemspec.

from serverspec-aws.

Found the issue. jeweler is not checking for duplicates when sourcing the dependencies. It can do this from both the rake task itself and from the supplied Gemfile. The issue is: when a dependency is specified in both places, it'll end up twice in the generated gemspec.

I also removed the gemspec from the repo. To generate a fresh one:

bundle install --with development
rake gemspec

However, the issue was not discovered for so long as I was using the rest of the rake tasks supplied by jeweler which don't use the generated gemspec to build/install the gem. From rake -T:

rake build                 # Build gem into pkg/
rake install               # Build and install gem using `gem install`

Also: for the moment I am not pushing this gem to RubyGems as the integration testing against AWS resources got delayed for quite a while and I don't feel like the work for this gem is complete.

from serverspec-aws.

Don't know if this is a separate issue, but according to:

rubygems/bundler#1880

In order to include a gem from source, it needs to include a gemspec - even if it's generated.

Or should I be using a different process I'm unaware of?

from serverspec-aws.

I can publish the gem to RubyGems to make things easier for everybody. I'll do this after dealing with your PR #3.

from serverspec-aws.

Ok that would be great thanks

from serverspec-aws.