You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’ve just come across the following problem when trying to run Shai Rosenfeld’s eycheck:
@@@
[Tim@iMac ~]$ eycheck tm50-s00146
/Library/Ruby/Site/1.8/rubygems.rb:233:in activate’: can’t activate highline (~> 1.5.2, runtime) for ["engineyard-1.1.0", "ronin-0.35.1", "eycheck-0.4.18"], already activated highline-1.6.1 for ["capistrano-2.5.19", "samurai-0.22.171", "eycheck-0.4.18"] (Gem::LoadError) from /Library/Ruby/Site/1.8/rubygems.rb:249:inactivate’
from /Library/Ruby/Site/1.8/rubygems.rb:248:in each’ from /Library/Ruby/Site/1.8/rubygems.rb:248:inactivate’
from /Library/Ruby/Site/1.8/rubygems.rb:249:in activate’ from /Library/Ruby/Site/1.8/rubygems.rb:248:ineach’
from /Library/Ruby/Site/1.8/rubygems.rb:248:in activate’ from /Library/Ruby/Site/1.8/rubygems.rb:249:inactivate’
from /Library/Ruby/Site/1.8/rubygems.rb:248:in each’ from /Library/Ruby/Site/1.8/rubygems.rb:248:inactivate’
from /Library/Ruby/Site/1.8/rubygems.rb:1082:in `gem’
from /usr/bin/eycheck:18
@@@
I had the following highline gems installed:
@@@
[Tim@iMac ~]$ gem list highline
*** LOCAL GEMS ***
highline (1.6.1, 1.5.2, 1.5.0)
@@@
After tyring to remove and reinstall various gems to get things working, I eventually modified the gemspec for the engineyard gem so that the dependency for highline was the following:
Change highline dependency in gemspec from "~> 1.5.2"
If all the tests pass with highline 1.6, then we can bump the dependency. I
don’t want to make it just > 1.6, though, as then an API-changing release of
highline could retroactively break installation of a whole bunch of versions
of the engineyard gem.
I’ve just come across the following problem when trying to run Shai Rosenfeld’s eycheck:
@@@
[Tim@iMac ~]$ eycheck tm50-s00146
/Library/Ruby/Site/1.8/rubygems.rb:233:in
activate’: can’t activate highline (~> 1.5.2, runtime) for ["engineyard-1.1.0", "ronin-0.35.1", "eycheck-0.4.18"], already activated highline-1.6.1 for ["capistrano-2.5.19", "samurai-0.22.171", "eycheck-0.4.18"] (Gem::LoadError) from /Library/Ruby/Site/1.8/rubygems.rb:249:in
activate’from /Library/Ruby/Site/1.8/rubygems.rb:248:in
each’ from /Library/Ruby/Site/1.8/rubygems.rb:248:in
activate’from /Library/Ruby/Site/1.8/rubygems.rb:249:in
activate’ from /Library/Ruby/Site/1.8/rubygems.rb:248:in
each’from /Library/Ruby/Site/1.8/rubygems.rb:248:in
activate’ from /Library/Ruby/Site/1.8/rubygems.rb:249:in
activate’from /Library/Ruby/Site/1.8/rubygems.rb:248:in
each’ from /Library/Ruby/Site/1.8/rubygems.rb:248:in
activate’from /Library/Ruby/Site/1.8/rubygems.rb:1082:in `gem’
from /usr/bin/eycheck:18
@@@
I had the following highline gems installed:
@@@
[Tim@iMac ~]$ gem list highline
*** LOCAL GEMS ***
highline (1.6.1, 1.5.2, 1.5.0)
@@@
After tyring to remove and reinstall various gems to get things working, I eventually modified the gemspec for the engineyard gem so that the dependency for highline was the following:
@@@ ruby
s.add_runtime_dependency(%q, [">= 1.5.2"])
@@@
I don’t know if this is going to bite other people soon, but thought I would open this ticket to see if this is something that should be changed?
The text was updated successfully, but these errors were encountered: