[ANN] RubyGems 1.2.0

[Damien McKenna]

Personally I'm having a problem with the latest update - my mongrels
are throwing up on XHR:

Mon Jun 23 23:35:49 -0400 2008: HTTP parse error, malformed request
(127.0.0.1): #<Mongrel::HttpParserError: Invalid HTTP format, parsing
fails.>

It is only XHR, all plain HTML requests are fine. I tried going back
to 1.1.1 to no avail.

My submitted bug report:
http://rubyforge.org/tracker/index.php?func=detail&aid=20804&group_id=126&atid=575

Some additional details:
http://www.mc-kenna.com/2008/06/rubygems-120-causing-problems-for-anyone-else/

Any help would be greatly appreciated. Thanks.

 

[Damien McKenna]

Personally I'm having a problem with the latest update - my mongrels
are throwing up on XHR:

Not sure if this caused the problem, but I noticed my ~/.gemrc
included two references to github. I removed one of them, restarted
the mongrels and... it started working again. Very odd.

Apologies for the wasted braincells.

Damien

 

[Une Bévue]

I'm also having difficulties, it would appear that I can't successfully
access http://gems.rubyforge.org. I can't find the remote rails gem:

Macintosh:activerecord rick$ gem list --both rails

I've heard, weeks ago, that rubygems is broken over Mac OS X 10.4.11,
for a remote install, local is OK.

I'll try that way.

 

[Roger Pack]

It appears I am destined for poor luck with this upgrade.
Tried it in a fresh ubuntu install

sudo apt-get install ruby rubygems
# worked


sudo gem update --system
# said it worked


Now I get the infamous
/usr/bin/gem:23: uninitialized constant Gem::GemRunner (NameError)

Ahh well. Back to installing from scratch.
-R

 

[Tristin Davis]

[Note: parts of this message were removed to make it a legal post.]

You have to manually remove the old gem and everything associated with it. I
tried removing gem via apt, but it didn't work. The only way I fixed it was
the old fashioned way.

 

[Une Bévue]

Back to installing from scratch.

What do u mean by "installing from scratch" ?

that is, there is a clean way to uninstall rubygems and re-install it
afterwards ?

on Mac OS X (at least 10.4.11 version) it is known there is a prob with
rubygems remote install...

downloading the gem and installing it with the -l option works
generally, but not for rubygems itself...

 

[Roger Pack]

Une Bév

What do u mean by "installing from scratch" ?

that is, there is a clean way to uninstall rubygems and re-install it
afterwards ?

In my case I download rubygems.xxx.gz, unzipped it, ran sudo ruby
setup.rb [which installed gem1.8, for some reason, instead of gem], then
I renamed gem to replace my existing gem and it was good to go. That's
what I meant
Not very clean, no. I suppose I could have done an apt-get uninstall
rubygems first, but at least it seems to work this way.
-R

 

[Eric Hodel]

I'm also having difficulties, it would appear that I can't
successfully
access http://gems.rubyforge.org. I can't find the remote rails gem:

Macintosh:activerecord rick$ gem list --both rails

*** LOCAL GEMS ***

rails (2.0.2, 1.2.5, 1.2.3)

*** REMOTE GEMS ***

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

Macintosh:activerecord rick$

If I look at that url with firefox, I get a text page with links to
get a
yaml index, look at the gems online, and download ruby gems. If I
click on
the second one, I seem to get randomly redirected to different shadow
servers most of which result in a forbidden error. A sampling:

http://gemmirror.xaop.net/gems/ gives
Forbiddin
http://gems.rubyforge.vm.bytemark.co.uk/gems/ gets through
http://gems.rubyforge.mmmultiworks.com/gems/ gives Forbidden
http://rubyforge-gems.ruby-forum.com/gems/ gives Forbidden
http://rubyforge.rubyuser.de/gems/ gets
through

RubyGems itself never accesses these URLs. Forbidden here is ok.

Here's what happens when I try a system update:

Macintosh:activerecord rick$ sudo gem update --system
Password:
Updating RubyGems
Bulk updating Gem source index for: http://gems.rubyforge.org/
Updating rubygems-update
ERROR: While executing gem ... (Gem::GemNotFoundException)
could not find rubygems-update locally or in a repository

Can you try again today? There was an incompatibility in trunk before
RubyGems 1.2 was released, so gems released were incompatible and
broke the index. They've all been cleaned up now, re-released with
RubyGems 1.2.

There is one other bug with upgrading from RubyGems 1.1.1. If an
older rubygems-update is not installed RubyGems may report "nothing to
update". As a work-around, run `gem install rubygems-update -v 1.1.1`
before `gem update --system`.

 

[Eric Hodel]

I'm sorry to say i was unable to upgrade :
~%> sudo gem update --system
Updating RubyGems
Bulk updating Gem source index for: http://gems.rubyforge.org/
Updating rubygems-update
ERROR: While executing gem ... (Gem::GemNotFoundException)
could not find rubygems-update locally or in a repository

As I responded to Rick's message, this should now be fixed. If you =20
get the "nothing to update" response, the workaround is to `gem =20
install rubygems-update -v 1.1.1` before updating RubyGems.=

 

[Eric Hodel]

It appears I am destined for poor luck with this upgrade.
Tried it in a fresh ubuntu install

sudo apt-get install ruby rubygems
# worked


sudo gem update --system
# said it worked


Now I get the infamous
/usr/bin/gem:23: uninitialized constant Gem::GemRunner (NameError)

You either ignored the NOTE in the release notes, or did not read the
end of the update output. For my /usr/local/bin/ruby18 it prints:

RubyGems installed the following executables:
/usr/local/bin/gem18

If `gem` was installed by a previous RubyGems installation, you may
need
to remove it by hand.

It probably said something similar that you ignored (like RubyGems
installing /usr/bin/gem1.8)

 

[Une Bévue]

As I responded to Rick's message, this should now be fixed. If you
get the "nothing to update" response, the workaround is to `gem
install rubygems-update -v 1.1.1` before updating RubyGems.

unfortunately, nope ))

~%> sudo gem update --system
Password:
Updating RubyGems
Updating metadata for 34 gems from http://gems.rubyforge.org/
...................................
complete
Nothing to update^
^^^^^^^^^^^^^^^^^

~%> sudo gem install rubygems-update -v 1.1.1
ERROR: could not find rubygems-update locally or in a repository
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

then i cd to my gems dir :

~%> cd gems
~/gems%> sudo gem install rubygems-update -v 1.1.1
Successfully installed rubygems-update-1.2.0
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1 gem installed
^^^^^^^^^^^^^^^

however :
~/gems%> gem env
RubyGems Environment:
- RUBYGEMS VERSION: 1.1.0 (1.1.0)
- RUBY VERSION: 1.8.6 (2007-09-24 patchlevel 111)
[powerpc-darwin8.11.0]
.....

I'm running Mac OS X 10.4.11

 

[Neil Wilson]

It appears I am destined for poor luck with this upgrade.
Tried it in a fresh ubuntu install

sudo apt-get install ruby rubygems
# worked

sudo gem update --system
# said it worked

Now I get the infamous
/usr/bin/gem:23: uninitialized constant Gem::GemRunner (NameError)

Ahh well.  Back to installing from scratch.

I've kicked off a couple of groups on Launchpad to deal with the
problem of Ruby backports and Ruby packaging in general on Ubuntu.

https://edge.launchpad.net/~ubuntu-ruby-backports
https://edge.launchpad.net/~ubuntu-ruby

The package archives of those groups contain a backport of 1.1.1
rubygems and Phusion passenger.

If you can help with testing the packages, or better still help us
write stuff then we can get to the nirvana where 'apt' and 'gem' play
nicely together that much sooner.

Neil Wilson
Brightbox
www.brightbox.co.uk

 

[Sandor Szücs]

I've heard, weeks ago, that rubygems is broken over Mac OS X 10.4.11,
for a remote install, local is OK.

I can not confirm this.
Maybe a ppc or a macports issue?

$ gem env
RubyGems Environment:
- RUBYGEMS VERSION: 1.2.0
- RUBY VERSION: 1.8.7 (2008-06-20 patchlevel 22) [i686-darwin8.11.1]
- INSTALLATION DIRECTORY: /opt/local/lib/ruby/gems/1.8
- RUBY EXECUTABLE: /opt/local/bin/ruby
- EXECUTABLE DIRECTORY: /opt/local/bin
- RUBYGEMS PLATFORMS:
- ruby
- x86-darwin-8
- GEM PATHS:
- /opt/local/lib/ruby/gems/1.8
- GEM CONFIGURATION:
- :update_sources =3D> true
- :verbose =3D> true
- :benchmark =3D> false
- :backtrace =3D> false
- :bulk_threshold =3D> 1000
- REMOTE SOURCES:
- http://gems.rubyforge.org/
$ gem --version
1.2.0

OSX 10.4.11

$ port version
Version: 1.600

hth. regards, Sandor Sz=FCcs
--

 

[Vassilis Rizopoulos]

= Announce: RubyGems Release 1.2.0

Release 1.2.0 adds new features and fixes some bugs.

Very cool. One thing though:
I run into an issue with multiple gem servers: I added the datamapper
server for their gems (still at 1.1.0 at the time) and one day the DM
server started returning 404s for the yaml list of gems.
Now, the 1.1.0 version wouldn't even allow me to remove the server
because it would try to do a bulk update and bomb out on the 404.
Thankfully 1.2.0 fixed this .
Now the problem is that any problem with any of the servers interrupts
the gem operation. Gem should gracefully handle gem server failures and
attempt list, search, install and update with the remaining.
That's not much to ask for, is it?
Cheers,
V.-

 

[Une Bévue]

I can not confirm this.
Maybe a ppc or a macports issue?

Yes, i'm using G5-PPC, and have installed ruby using MacPorts.
But, afaik, rubygems has nothing to do with MacPorts, isn't it ?

my port version and mac os x version are the same as you...

are you using an Intel proc ?

it might be an issue on PPC only ?

regards,

 

[Sandor Szücs]

Yes, i'm using G5-PPC, and have installed ruby using MacPorts.
But, afaik, rubygems has nothing to do with MacPorts, isn't it ?

I am unsure, but I think you are right.

Btw. there is a package rb-rubygems from macports, but I
don't use it.
$ port provides /opt/local/bin/gem
/opt/local/bin/gem is not provided by a MacPorts port.
I use gem in the MacPorts path:
$ which gem
/opt/local/bin/gem
It's really a file not a symlink.
$ ls -l /opt/local/bin/gem
-rwxr-xr-x 1 root admin 788 May 6 10:18 /opt/local/bin/gem*

my port version and mac os x version are the same as you...

are you using an Intel proc ?

yes a macbook with x86

it might be an issue on PPC only ?

It looks like that.

regards, Sandor Sz=FCcs
--=

 

[Une Bévue]

It looks like that.

in my opinion, it's clear enough.
unfortunately the latest rubygems from MacPorts is 1.1.1 :
~%> port search rb-rubygems
rb-rubygems ruby/rb-rubygems 1.1.1 a package
management framework for Ruby

and, i think, it is not clean to install it from MacPorts after having
installed it from ruby, MacPorts will be confused and even might refuse
to install it.

i think here i have to report a sepcific issue for 10.4.11 && PPC...

best,

 

[Orion Delwaterman]

Uh something appears to be broken with sources other than the main ruby
site. We updated our gem server with ruby gems 1.2.0 and from another
server we are getting the following problems:

[root@AppFoot ~]# gem -v
1.2.0
[root@AppFoot ~]# gem list sonic_logger --remote

*** REMOTE GEMS ***

sonic_logger (0.1.3)
[root@AppFoot ~]# gem install sonic_logger
ERROR: could not find gem sonic_logger locally or in a repository

Anyone else having this issue?

 

[Eric Hodel]

unfortunately, nope ))

~%> sudo gem update --system
Password:
Updating RubyGems
Updating metadata for 34 gems from http://gems.rubyforge.org/
..................................
complete
Nothing to update^
^^^^^^^^^^^^^^^^^

~%> sudo gem install rubygems-update -v 1.1.1
ERROR: could not find rubygems-update locally or in a repository
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

then i cd to my gems dir :

~%> cd gems
~/gems%> sudo gem install rubygems-update -v 1.1.1
Successfully installed rubygems-update-1.2.0
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1 gem installed
^^^^^^^^^^^^^^^

If you run sudo rubygems_update now, does it install 1.2.0?=

 

[Eric Hodel]

Uh something appears to be broken with sources other than the main
ruby
site. We updated our gem server with ruby gems 1.2.0 and from another
server we are getting the following problems:

[root@AppFoot ~]# gem -v
1.2.0
[root@AppFoot ~]# gem list sonic_logger --remote

*** REMOTE GEMS ***

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:latform::RUBY.