Forum: Ruby Struggling With RubyGems

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
James G. (Guest)
on 2007-01-17 23:29
(Received via mailing list)
I can't seen to query or install gems over here.  Is anyone else
seeing something like this, or have I screwed up my local install?

$ gem query -r --name-matches highline

*** REMOTE GEMS ***
ERROR:  While executing gem ... (NoMethodError)
     undefined method `refresh' for #<Hash:0x57c704>

James Edward G. II
Jason R. (Guest)
on 2007-01-17 23:33
(Received via mailing list)
Using gem 0.9, ruby 1.8.5 (windows one-click), no problems here. you
might
have messed up your install.

Try doing:

gem list -r highline

Does the same thing, easier and shorter to type. If that still fails,
you
should reinstall gems or maybe even Ruby.

Jason
Gavin K. (Guest)
on 2007-01-17 23:40
(Received via mailing list)
James Edward G. II wrote:
> I can't seen to query or install gems over here.  Is anyone else
> seeing something like this, or have I screwed up my local install?
>
> $ gem query -r --name-matches highline
>
> *** REMOTE GEMS ***
> ERROR:  While executing gem ... (NoMethodError)
>      undefined method `refresh' for #<Hash:0x57c704>

May be just you. Mine's working:

C:\>gem query -r --name-matches highline

*** REMOTE GEMS ***
Bulk updating Gem source index for: http://gems.rubyforge.org

highline (1.2.4, 1.2.3, 1.2.2, 1.2.1, 1.2.0, 1.0.4, 1.0.2, 1.0.1,
1.0.0, 0.6.1, 0.6.0, 0.5.0, 0.4.0, 0.3.0, 0.2.0)
    HighLine is a high-level command-line IO library.

C:\>gem --version
0.9.0

C:\>ruby -v
ruby 1.8.5 (2006-08-25) [i386-mswin32]
Gregory S. (Guest)
on 2007-01-17 23:43
(Received via mailing list)
On Thu, Jan 18, 2007 at 06:29:09AM +0900, James Edward G. II wrote:
> I can't seen to query or install gems over here.  Is anyone else
> seeing something like this, or have I screwed up my local install?
>
> $ gem query -r --name-matches highline
>
> *** REMOTE GEMS ***
> ERROR:  While executing gem ... (NoMethodError)
>     undefined method `refresh' for #<Hash:0x57c704>

I'm getting the same thing after upgrading to 0.9.1, and on gem install
or
gem update as well. Help?

> James Edward G. II
--Greg
James G. (Guest)
on 2007-01-17 23:59
(Received via mailing list)
On Jan 17, 2007, at 3:42 PM, Gregory S. wrote:

> I'm getting the same thing after upgrading to 0.9.1, and on gem
> install or
> gem update as well. Help?

This does appear to be related to my upgrade to 0.9.1.  Downgrading
has resolved the issue, for now.

James Edward G. II
Chuck R. (Guest)
on 2007-01-18 00:14
(Received via mailing list)
On Jan 17, 2007, at 3:40 PM, Phrogz wrote:

> May be just you. Mine's working:
> C:\>gem --version
> 0.9.0
>
> C:\>ruby -v
> ruby 1.8.5 (2006-08-25) [i386-mswin32]

Mine is broken since I updated to 0.9.1 today.

~ cremes$ gem query -r --name-matches highline

*** REMOTE GEMS ***
Bulk updating Gem source index for: http://gems.rubyforge.org
ERROR:  While executing gem ... (NoMethodError)
     undefined method `source_index' for #<Hash:0x2db547c>
~ cremes$ gem --version
0.9.1
~ cremes$ ruby -v
ruby 1.8.4 (2005-12-24) [powerpc-darwin8.6.0]

cr
David G. (Guest)
on 2007-01-18 00:18
(Received via mailing list)
On 1/17/07, James Edward G. II <removed_email_address@domain.invalid> wrote:
> >>     undefined method `refresh' for #<Hash:0x57c704>
> >
> > I'm getting the same thing after upgrading to 0.9.1, and on gem
> > install or
> > gem update as well. Help?
>
> This does appear to be related to my upgrade to 0.9.1.  Downgrading
> has resolved the issue, for now.

I had the same issue. Deleting the 'source_cache' file from my gems
directory solved it for me.

Dave
James G. (Guest)
on 2007-01-18 01:22
(Received via mailing list)
On Jan 17, 2007, at 4:17 PM, David G. wrote:

>> >> *** REMOTE GEMS ***
> I had the same issue. Deleting the 'source_cache' file from my gems
> directory solved it for me.

Doing that with a 0.9.1 install does restore the ability to query.  I
cannot install with it though:

$ gem -v
0.9.1
$ gem query -r --name-matches highline

*** REMOTE GEMS ***
Bulk updating Gem source index for: http://gems.rubyforge.org

highline (1.2.5, 1.2.4, 1.2.3, 1.2.2, 1.2.1, 1.2.0, 1.0.4, 1.0.2,
1.0.1, 1.0.0, 0.6.1, 0.6.0, 0.5.0, 0.4.0, 0.3.0, 0.2.0)
     HighLine is a high-level command-line IO library.
$ sudo gem install highline
ERROR:  While executing gem ... (NoMethodError)
     undefined method `source_index' for #<Hash:0x2dbaa1c>

James Edward G. II
Tim P. (Guest)
on 2007-01-18 01:34
(Received via mailing list)
On 1/17/07, James Edward G. II <removed_email_address@domain.invalid> wrote:
> >> >> $ gem query -r --name-matches highline
> >> has resolved the issue, for now.
>
> *** REMOTE GEMS ***
> Bulk updating Gem source index for: http://gems.rubyforge.org
>
> highline (1.2.5, 1.2.4, 1.2.3, 1.2.2, 1.2.1, 1.2.0, 1.0.4, 1.0.2,
> 1.0.1, 1.0.0, 0.6.1, 0.6.0, 0.5.0, 0.4.0, 0.3.0, 0.2.0)
>      HighLine is a high-level command-line IO library.
> $ sudo gem install highline
> ERROR:  While executing gem ... (NoMethodError)
>      undefined method `source_index' for #<Hash:0x2dbaa1c>
>

James, did you clear out the source_cache for root?

Your query worked because you did it as you.  Your install did not
work because you tried to do it as root.

Just a thought.

Blessings,
TwP
Tim P. (Guest)
on 2007-01-18 01:36
(Received via mailing list)
On 1/17/07, Tim P. <removed_email_address@domain.invalid> wrote:
> > >> >>
> > >> This does appear to be related to my upgrade to 0.9.1.  Downgrading
> > $ gem query -r --name-matches highline
> >
>
> James, did you clear out the source_cache for root?
>
> Your query worked because you did it as you.  Your install did not
> work because you tried to do it as root.
>

Never mind.  There is only one source_cache :/  Doh!

I'll just go back to whatever it was I was doing over there ... ooh,
look! Butterfly!

TwP
James G. (Guest)
on 2007-01-18 01:51
(Received via mailing list)
On Jan 17, 2007, at 5:35 PM, Tim P. wrote:

>> James, did you clear out the source_cache for root?
>>
>> Your query worked because you did it as you.  Your install did not
>> work because you tried to do it as root.
>>
>
> Never mind.  There is only one source_cache :/  Doh!

Actually, I originally cleared ~/.gem/source_cache.  When you
mentioned it, I cleared the one in root's home folder as well.  When
you gave me this final hint though, I found the one in /usr/local/lib/
ruby/gems/ and nuking that one did the trick.  I can now query and
install.

Thanks for all the fresh ideas.

James Edward G. II
Eric H. (Guest)
on 2007-01-18 04:45
(Received via mailing list)
On Jan 17, 2007, at 15:50, James Edward G. II wrote:
> mentioned it, I cleared the one in root's home folder as well.
> When you gave me this final hint though, I found the one in /usr/
> local/lib/ruby/gems/ and nuking that one did the trick.  I can now
> query and install.

Please archive your source cache and send it to me, should you have
this in the future.

Also, what does 'gem sources' say?

--
Eric H. - removed_email_address@domain.invalid - http://blog.segment7.net

I LIT YOUR GEM ON FIRE!
James G. (Guest)
on 2007-01-18 05:39
(Received via mailing list)
On Jan 17, 2007, at 8:44 PM, Eric H. wrote:

> Also, what does 'gem sources' say?

$ gem sources
*** CURRENT SOURCES ***

http://gems.rubyforge.org

James Edward G. II
Eric H. (Guest)
on 2007-01-18 06:33
(Received via mailing list)
On Jan 17, 2007, at 19:38, James Edward G. II wrote:
> On Jan 17, 2007, at 8:44 PM, Eric H. wrote:
>
>> Also, what does 'gem sources' say?
>
> $ gem sources
> *** CURRENT SOURCES ***
>
> http://gems.rubyforge.org

oh, also 'sudo gem sources'

--
Eric H. - removed_email_address@domain.invalid - http://blog.segment7.net

I LIT YOUR GEM ON FIRE!
Lyle J. (Guest)
on 2007-01-18 18:04
(Received via mailing list)
On 1/17/07, Eric H. <removed_email_address@domain.invalid> wrote:

> Please archive your source cache and send it to me, should you have
> this in the future.

I am still having this problem, although I have not zapped my various
source_cache files yet. I will send copies of my source_cache files to
Eric, offline.
James G. (Guest)
on 2007-01-18 18:53
(Received via mailing list)
On Jan 17, 2007, at 10:32 PM, Eric H. wrote:

> oh, also 'sudo gem sources'
$ sudo gem sources
Password:
*** CURRENT SOURCES ***

Need to update 9 gems from http://gems.rubyforge.org
.........
complete
http://gems.rubyforge.org

James Edward G. II
Jason P. (Guest)
on 2007-01-18 19:04
(Received via mailing list)
On Jan 18, 2007, at 10:03 AM, Lyle J. wrote:

> On 1/17/07, Eric H. <removed_email_address@domain.invalid> wrote:
>
>> Please archive your source cache and send it to me, should you have
>> this in the future.
>
> I am still having this problem, although I have not zapped my various
> source_cache files yet. I will send copies of my source_cache files to
> Eric, offline.

FWIW, I was having the same problem, but sudo gem sources appears to
have fixed it.


--
Jason P.
removed_email_address@domain.invalid

"The computer allows you to make mistakes
faster than any other invention, with the
possible exception of handguns and tequila."

-Mitch Ratcliffe
James B. (Guest)
on 2007-01-24 20:18
I had this problem as well and executing

# gem sources

as root did not clear it until I had manually removed  the old
source_cache.

# rm /usr/lib/ruby/gems/1.8/source_cache

I have a tar archive available of the orginal source_cache if that would
be of any use.
This topic is locked and can not be replied to.