Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

bad gemspec #19

Closed
johnjansen opened this Issue Jul 10, 2012 · 5 comments

Comments

Projects
None yet
3 participants

Unfortunately, the gem pacer (0.8.5) has an invalid gemspec. As a result, Bundler cannot install this Gemfile. Please ask the gem author to yank the bad version to fix this issue. For more information, see http://bit.ly/syck-defaultkey.

Contributor

dcolebatch commented Jul 11, 2012

Unfortunately we can't yank the gem for the same reason and the ruby
gems team won't help us.

If you use bundler v1.0.22, it won't complain about that old gem
having a bad gem spec and 'gem install pacer' will work.

David Colebatch
p: +1 647-478-9696 New primary number
c: +1 416-822-2252

On 2012-07-10, at 7:16 PM, John Jansen
reply@reply.github.com
wrote:

Unfortunately, the gem pacer (0.8.5) has an invalid gemspec. As a result, Bundler cannot install this Gemfile. Please ask the gem author to yank the bad version to fix this issue. For more information, see http://bit.ly/syck-defaultkey.


Reply to this email directly or view it on GitHub:
#19

Owner

pangloss commented Jul 11, 2012

Alternatively, you can bundle install --full-index. Believe me, this is more frustrating for me than for you!

Owner

pangloss commented Jul 18, 2012

Latest bundler release candidate fixes this issue: gem install bundler --pre and you should be good to go (I hope, worked for me)!

nice work, i'll try that again once i clear my backlog

Owner

pangloss commented Jul 20, 2012

Ok, I had to hack at gemcutter itself a bit to do it, but the bad gems are finally yanked!

@pangloss pangloss closed this Jul 20, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment