Since Manifest.txt is .gitignore-d, if you track the git repo using bundler, bundler will complain that the gemspec is asking for Manifest.txt but it can't find it. IE:
ragaskar@unicorn-vengeance: ~/workspace/testme$ bundle
Using builder (3.0.0)
Using ci_reporter (1.6.5) from git://github.com/ragaskar/ci_reporter.git (at master)
ci_reporter at /Users/ragaskar/.rvm/gems/ruby-1.9.2-p290@ci_reporter/bundler/gems/ci_reporter-af8674c7bddc did not have a valid gemspec.
This prevents bundler from installing bins or native extensions, but that may not affect its functionality.
The validation message from Rubygems was:
["Manifest.txt"] are not files
Using bundler (1.0.21)
Your bundle is complete! Use `bundle show [gemname]` to see where a bundled gem is installed.
This minor patch to gemspec fixes the problem.
Thanks for ci_reporter!
Only include Manifest.txt if it is present
This is affecting me too. I'm currently tracking HEAD because of the Errno::ENAMETOOLONG error bug. Any chance of applying this patch?
Add manifest to source control