[ANN] RubyGems 1.2.0

ruby-talk
1

= Announce: RubyGems Release 1.2.0

Release 1.2.0 adds new features and fixes some bugs.

New features:

* RubyGems no longer performs bulk updates and instead only fetches the gemspec
   files it needs. Alternate sources will need to upgrade to RubyGems 1.2 to
   allow RubyGems to take advantage of the new metadata updater. If a pre 1.2
   remote source is in the sources list, RubyGems will revert to the bulk update
   code for compatibility.
* RubyGems now has runtime and development dependency types. Use
   #add_development_dependency and #add_runtime_dependency. All typeless
   dependencies are considered to be runtime dependencies.
* RubyGems will now require rubygems/defaults/operating_system.rb and
   rubygems/defaults/#{RBX_ENGINE}.rb if they exist. This allows packagers and
   ruby implementers to add custom behavior to RubyGems via these files. (If
   the RubyGems API is insufficient, please suggest improvements via the
   RubyGems list.)
* /etc/gemrc (and windows equivalent) for global settings
* setup.rb now handles --vendor and --destdir for packagers
* `gem stale` command that lists gems by last access time

Bugs Fixed:

* File modes from gems are now honored, patch #19737
* Marshal Gem::Specification objects from the future can now be loaded.
* A trailing / is now added to remote sources when missing, bug #20134
* Gems with legacy platforms will now be correctly uninstalled, patch #19877
* `gem install --no-wrappers` followed by `gem install --wrappers` no longer
   overwrites executables
* `gem pristine` now forces reinstallation of gems, bug #20387
* RubyGems gracefully handles ^C while loading .gemspec files from disk, bug
   #20523
* Paths are expanded in more places, bug #19317, bug #19896
* Gem::DependencyInstaller resets installed gems every install, bug #19444
* Gem.default_path is now honored if GEM_PATH is not set, patch #19502

Other Changes Include:

* setup.rb
   * stub files created by RubyGems 0.7.x and older are no longer removed. When
     upgrading from these ancient versions, upgrade to 1.1.x first to clean up
     stubs.
   * RDoc is no longer required until necessary, patch #20414
* `gem server`
   * Now completely matches the output of `gem generate_index` and
     has correct content types
   * Refreshes from source directories for every hit. The server will no longer
     need to be restarted after installing gems.
* `gem query --details` and friends now display author, homepage, rubyforge url
   and installed location
* `gem install` without -i no longer reinstalls dependencies if they are in
   GEM_PATH but not in GEM_HOME
* Gem::RemoteFetcher now performs persistent connections for HEAD requests,
   bug #7973

For a full list of changes to RubyGems and the contributor for each change, see
the ChangeLog file.

Special thanks to Chad Wooley for backwards compatibility testing and Luis
Lavena for continuing windows support.

== How can I get RubyGems?

NOTE: If you have installed RubyGems using a package system you may want to
install a new RubyGems through the same packaging system.

If you have a recent version of RubyGems (0.8.5 or later), then all
you need to do is:

   $ gem update --system (you might need to be admin/root)

(Note: You may have to run the command twice if you have any previosly
installed rubygems-update gems).

If you have an older version of RubyGems installed, then you can still
do it in two steps:

   $ gem install rubygems-update (again, might need to be admin/root)
   $ update_rubygems (... here too)

If you don't have any gems install, there is still the pre-gem
approach to getting software ... doing it manually:

1. DOWNLOAD FROM: http://rubyforge.org/frs/?group_id=126
2. UNPACK INTO A DIRECTORY AND CD THERE
3. INSTALL WITH: ruby setup.rb (you may need admin/root privilege)

== To File Bugs

The RubyGems bug tracker can be found on RubyForge at:
http://rubyforge.org/tracker/?func=add&group_id=126&atid=575

When filing a bug, `gem env` output will be helpful in diagnosing the issue.

If you find a bug where RubyGems crashes, please provide debug output. You can
do that with `gem --debug the_command`.

== Thanks

Keep those gems coming!

-- Jim & Chad & Eric (for the RubyGems team)

2

# = Announce: RubyGems Release 1.2.0

thank you very much for the update. it's now a lot faster and all my gems installed/uninstalled fine. all gems truelly updated.

···

From: Eric Hodel [mailto:drbrain@segment7.net]

3

Yahoo! I have been waiting for this!
The slower the internet access, the more appreciation you'll get.

Les

···

On Sun, Jun 22, 2008 at 5:30 AM, Eric Hodel <drbrain@segment7.net> wrote:

= Announce: RubyGems Release 1.2.0

Release 1.2.0 adds new features and fixes some bugs.

New features:

* RubyGems no longer performs bulk updates and instead only fetches the
gemspec
files it needs. Alternate sources will need to upgrade to RubyGems 1.2 to
allow RubyGems to take advantage of the new metadata updater. If a pre 1.2
remote source is in the sources list, RubyGems will revert to the bulk
update
code for compatibility.

4

* RubyGems no longer performs bulk updates and instead only fetches
the gemspec
   files it needs. Alternate sources will need to upgrade to RubyGems
1.2 to
   allow RubyGems to take advantage of the new metadata updater. If a
pre 1.2
   remote source is in the sources list, RubyGems will revert to the
bulk update
   code for compatibility.

Nice new features! Sweetness.

Some notes:
~ sudo gem update --system
Updating RubyGems
Bulk updating Gem source index for: http://gems.rubyforge.org/
Nothing to update
~ gem -v
1.1.1

1) I seem to be unable to upgrade. Hopefully this will be fixed soon by
some propagating gems.
2) It always does 'mass' bulk update each time I run this command,
despite the fact that my gem cache is up to date.

I look forward to installing it eventually, though :slight_smile:
-R

···

--
Posted via http://www.ruby-forum.com/\.

5

yes, we really all do love eric.

keep up the fantastic work man!

a @ http://codeforpeople.com/

···

On Jun 21, 2008, at 9:30 PM, Eric Hodel wrote:

= Announce: RubyGems Release 1.2.0

Release 1.2.0 adds new features and fixes some bugs.

--
we can deny everything, except that we have the possibility of being better. simply reflect on that.
h.h. the 14th dalai lama

6

FYI, You can include development dependencies during an install or
update with --development.

Also, a small API addition for folks doing conditional gem loading by
manually checking the source index or rescuing LoadError:

  Gem.available?(gem, *specs)

~ j.

···

On Sat, Jun 21, 2008 at 8:30 PM, Eric Hodel <drbrain@segment7.net> wrote:

= Announce: RubyGems Release 1.2.0

Release 1.2.0 adds new features and fixes some bugs.

New features:
* RubyGems now has runtime and development dependency types. Use
#add_development_dependency and #add_runtime_dependency. All typeless
dependencies are considered to be runtime dependencies.

7

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

OS : MacOS X 10.4.11
~%> ruby --version
ruby 1.8.6 (2007-09-24 patchlevel 111) [powerpc-darwin8.11.0]
~%> gem --version
1.1.0

···

Eric Hodel <drbrain@segment7.net> wrote:

Release 1.2.0 adds new features and fixes some bugs.

--
Une Bévue

8

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:

Any help would be greatly appreciated. Thanks.

9

Eric Hodel wrote:

= 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? :wink:
Cheers,
V.-

···

--
http://www.braveworld.net/riva

10

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.

···

--
Posted via http://www.ruby-forum.com/.

11

Peña, Botp wrote:

From: Eric Hodel [mailto:drbrain@segment7.net]
# = Announce: RubyGems Release 1.2.0

thank you very much for the update. it's now a lot faster and all my
gems installed/uninstalled fine. all gems truelly updated.

I second that thank you! I was worried because gem kept updating the
cache on every single command. Updating to 1.2.0 solved that.

-Ripta

···

--
Posted via http://www.ruby-forum.com/\.

12

Cool !
Thanks for the update !

Sandro

···

On Mon, Jun 23, 2008 at 6:17 AM, Leslie Viljoen <leslieviljoen@gmail.com> wrote:

On Sun, Jun 22, 2008 at 5:30 AM, Eric Hodel <drbrain@segment7.net> wrote:
> = Announce: RubyGems Release 1.2.0
>
> Release 1.2.0 adds new features and fixes some bugs.
>
> New features:
>
> * RubyGems no longer performs bulk updates and instead only fetches the
> gemspec
> files it needs. Alternate sources will need to upgrade to RubyGems 1.2
to
> allow RubyGems to take advantage of the new metadata updater. If a pre
1.2
> remote source is in the sources list, RubyGems will revert to the bulk
> update
> code for compatibility.

Yahoo! I have been waiting for this!
The slower the internet access, the more appreciation you'll get.

Les

--
Go outside! The graphics are amazing!

13

and more :

~%> sudo gem install amalgalite
Password:
Bulk updating Gem source index for: http://gems.rubyforge.org/
ERROR: could not find amalgalite locally or in a repository

···

Une Bévue <unbewusst.sein@weltanschauung.com.invalid> wrote:

I'm sorry to say i was unable to upgrade :

--
Une Bévue

14

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

···

On Jun 24, 12:50 am, Damien McKenna <damien@mc-kenna.com> wrote:

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

15

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.

···

On Jun 23, 2008, at 11:03 AM, Une Bévue wrote:

Eric Hodel <drbrain@segment7.net> wrote:

Release 1.2.0 adds new features and fixes some bugs.

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

16

This is an unfortunate bug in the self-updater of 1.2.0.

···

On Nov 28, 2010, at 21:55 , Manish Nautiyal wrote:

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.

17

Great...thanks for the update!
For a future release, I wish the install command would not reinstall
a gem already present in the system, or could give a warning that the
gem is already installed.

thanks,
saji

* Sandro Paganotti <sandro.paganotti@gmail.com> [2008-06-23 17:23:28 +0900]:

···

Cool !
Thanks for the update !

Sandro

On Mon, Jun 23, 2008 at 6:17 AM, Leslie Viljoen <leslieviljoen@gmail.com> > wrote:

> On Sun, Jun 22, 2008 at 5:30 AM, Eric Hodel <drbrain@segment7.net> wrote:
> > = Announce: RubyGems Release 1.2.0
> >
> > Release 1.2.0 adds new features and fixes some bugs.
> >
> > New features:
> >
> > * RubyGems no longer performs bulk updates and instead only fetches the
> > gemspec
> > files it needs. Alternate sources will need to upgrade to RubyGems 1.2
> to
> > allow RubyGems to take advantage of the new metadata updater. If a pre
> 1.2
> > remote source is in the sources list, RubyGems will revert to the bulk
> > update
> > code for compatibility.
>
> Yahoo! I have been waiting for this!
> The slower the internet access, the more appreciation you'll get.
>
> Les
>
>

--
Go outside! The graphics are amazing!

--
Saji N. Hameed

APEC Climate Center +82 51 668 7470
National Pension Corporation Busan Building 12F
Yeonsan 2-dong, Yeonje-gu, BUSAN 611705 saji@apcc21.net
KOREA

18

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

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

Here's my current gem setup

Macintosh:activerecord rick$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.1.0 (1.1.0)
  - RUBY VERSION: 1.8.6 (2007-09-23 patchlevel 110) [i686-darwin8.11.1]
  - INSTALLATION DIRECTORY: /opt/local/lib/ruby/gems/1.8
  - RUBY EXECUTABLE: /opt/local/bin/ruby
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-darwin-8
  - GEM PATHS:
     - /opt/local/lib/ruby/gems/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://gems.rubyforge.org
Macintosh:activerecord rick$ gem --version
1.1.0

···

On Mon, Jun 23, 2008 at 2:53 PM, Une Bévue <unbewusst.sein@weltanschauung.com.invalid> wrote:

Une Bévue <unbewusst.sein@weltanschauung.com.invalid> wrote:

> I'm sorry to say i was unable to upgrade :

--
Rick DeNatale

My blog on Ruby
http://talklikeaduck.denhaven2.com/

19

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

···

Eric Hodel <drbrain@segment7.net> wrote:

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.

--
Une Bévue

20

Why do you care?

···

On Jun 23, 2008, at 01:59 AM, Saji N. Hameed wrote:

For a future release, I wish the install command would not reinstall
a gem already present in the system, or could give a warning that the
gem is already installed.