-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installation fails on some rubygems #6
Comments
|
also fails with Debian 'squeeze': ruby version:
gem version:
debian:
|
I could install riemann-dash on squeeze using the rubygems from sqeeze-backports (http://packages.debian.org/squeeze-backports/ruby/rubygems). It's version 1.8.15. |
Fails here too:
0.1.1 worked though.
|
[root@riemann-labs-berkshelf ~]# uname -a Happens with version 0.1.1 as well. I'm happy to provide a stack trace for that as well if it's helpful. |
Ahh, that trace is very useful, thank you. I've got access to a centos box running 1.3.7 so hopefully I'll be able to figure this out now. |
OK guys, think I've got this fixed in 0.2.1; and I can confirm it installs on centos with 1.3.7. If you have further problems let me know! :) |
How was this fixed? I'm encountering a similar issue when trying to install berkshelf gem, and don't see any obvious commits that would give me any hints. |
IIRC there was a bug in rubygems which caused issues depending on the box that did the packaging. Might have introduced a regression by packaging with the wrong version of rubygems. |
(btw, rubygems 1.3.7 is over three years old; might be time to upgrade) |
Installing on
ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
rubygems 1.3.7
Fails from rubygems on Wed Jan 30 11:48:35 PST 2013
Succeeds when built on 1.8.7p352, gems 1.3.7
Succeeds when built on 1.8.7p371, gems 1.8.11
Fails when built on 1.9.3rev32789, gems 1.8.10
The text was updated successfully, but these errors were encountered: