On Jun 27, 2008, at 15:01 PM, Orion Delwaterman wrote:
sonic_logger (0.1.3)
[root@AppFoot ~]# gem install sonic_logger
ERROR: could not find gem sonic_logger locally or in a repository
There was a bug fix post 1.2.0 for gems that have “” for a platform
instead of Gem::Platform::RUBY.
Sorry, i’m lost, not at this time :
~/gems%> sudo update_rubygems
Installing RubyGems 1.2.0
setup.rb:108: undefined method `ruby_version’ for Gem:Module
(NoMethodError)
~/gems%> gem env
For some reason I had a previous version of gem that was installed in
the wrong directory–like it should have been installed in
/user/rdp/home/i386/bin but instead it was in
/user/rdp/home/i386/bin/rdp/home/i386/bin or something.
Anyway, upgrading from this state,
download rubygems-1.2.0.tgz
ran ruby setup.rb on it.
now I get something similar:
/home/rdp/i386/bin/gem:14: undefined method `ruby_version’ for
Gem:Module (NoMethodError)
This means that [in this one system] even installing it from scratch
again doesn’t fix the problem. Not sure what to do.
Even deleting gem.rb from my ruby lib directory yields
/home/rdp/i386/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:29:
warning: already initialized constant OPS
/home/rdp/i386/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:32:
warning: already initialized constant OP_RE
/home/rdp/i386/usr/lib/ruby/site_ruby/1.8/rubygems/specification.rb:24:
Platform is not a module (TypeError)
from
/home/rdp/i386/usr/lib/ruby/site_ruby/1.8/rubygems/package.rb:15:in
require' from /home/rdp/i386/usr/lib/ruby/site_ruby/1.8/rubygems/package.rb:15 from /home/rdp/i386/usr/lib/ruby/site_ruby/1.8/rubygems/builder.rb:7:in
require’
from
/home/rdp/i386/usr/lib/ruby/site_ruby/1.8/rubygems/builder.rb:7
from /home/rdp/i386/lib/ruby/site_ruby/1.8/rubygems.rb:769:in
require' from /home/rdp/i386/lib/ruby/site_ruby/1.8/rubygems.rb:769 from /home/rdp/i386/bin/gem:8:in
require’
from /home/rdp/i386/bin/gem:8
Hmm. Thankfully it’s on a system where I don’t really NEED gems, but
they are convenient.
Thanks!
-R
Eric H. wrote:
On Jun 27, 2008, at 15:01 PM, Orion Delwaterman wrote:
sonic_logger (0.1.3)
[root@AppFoot ~]# gem install sonic_logger
ERROR: could not find gem sonic_logger locally or in a repository
There was a bug fix post 1.2.0 for gems that have “” for a platform
instead of Gem::Platform::RUBY.
How do I check or set the platform of my gem?
Roger P. wrote:
How do I check or set the platform of my gem?
~ irb
Gem::Platform::RUBY
=> “ruby”
?
Yeah mine is coming out as “ruby”. Anyway I just regenerated the index
on the server and that seemed to solve the issue. Strange though
/home/rdp/i386/usr/lib/ruby/site_ruby/1.8/rubygems/specification.rb:24:
Platform is not a module (TypeError)
from
/home/rdp/i386/usr/lib/ruby/site_ruby/1.8/rubygems/package.rb:15:in
require' from /home/rdp/i386/usr/lib/ruby/site_ruby/1.8/rubygems/package.rb:15 from /home/rdp/i386/usr/lib/ruby/site_ruby/1.8/rubygems/builder.rb:7:in
require’
from
/home/rdp/i386/usr/lib/ruby/site_ruby/1.8/rubygems/builder.rb:7
from /home/rdp/i386/lib/ruby/site_ruby/1.8/rubygems.rb:769:in
require' from /home/rdp/i386/lib/ruby/site_ruby/1.8/rubygems.rb:769 from /home/rdp/i386/bin/gem:8:in
require’
from /home/rdp/i386/bin/gem:8
As a note–was able to overcome this by doing rm -rf …/lib/ruby,
reinstalling ruby, and then reinstalling gems, in case it’s useful to
anyone else.
-=R
Orion Delwaterman wrote:
Roger P. wrote:
How do I check or set the platform of my gem?
~ irb
Gem::Platform::RUBY
=> “ruby”
?
Yeah mine is coming out as “ruby”. Anyway I just regenerated the index
on the server and that seemed to solve the issue. Strange though
Did you successfully install sonic_logger gem? I’m facing the same
problem as in your first post.
Can anyone tell me how to fix? where to find sonic_logger gem?
thanks
I’ve just had the same problem trying to upgrade rubygems from 1.2.0 to
1.3.7.
Setp-1)
So I just downloaded rubygems-update-1.3.7.gem from
http://rubyforge.org/frs/?group_id=126
Setp-2)
gem install rubygems-update-1.3.7.gem
Setp-3)
update_rubygems
and it work for me.
On Nov 28, 2010, at 21:55 , Manish N. wrote:
Setp-3)
update_rubygems
and it work for me.
This is an unfortunate bug in the self-updater of 1.2.0.