RubyGems 1.1.1

miracleofmagick · April 11, 2008, 7:43am

Release 1.1.1 fixes some bugs.

Bugs Fixed:

Gem.prefix now returns non-nil only when RubyGems was installed
outside
sitelibdir or libdir.
The gem server gem list now correctly links to gem details.
gem update --system now passes --no-format-executable to setup.rb.
Gem::SourceIndex#refresh! now works with multiple gem repositories.
Downloaded gems now go into --install-dir’s cache directory.
Various fixes to downloading gem metadata.
gem install --force now ignores network errors too.
gem pristine now rebuilds extensions.
gem update --system now works on virgin Apple ruby.
Gem::RemoteFetcher handles Errno::ECONNABORTED.
Printing of release notes fixed.

For a full list of changes to RubyGems including credits, see the
ChangeLog
file.

== 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:

DOWNLOAD FROM: http://rubyforge.org/frs/?group_id=126
UNPACK INTO A DIRECTORY AND CD THERE
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)

miracleofmagick · April 11, 2008, 8:42am

On Apr 10, 2008, at 11:42 PM, Eric H. wrote:

Downloaded gems now go into --install-dir’s cache directory.

Various fixes to downloading gem metadata.

gem install --force now ignores network errors too.

gem pristine now rebuilds extensions.

gem update --system now works on virgin Apple ruby.

Gem::RemoteFetcher handles Errno::ECONNABORTED.

Printing of release notes fixed.

thanks very much eric - much appreciated!

a @ http://codeforpeople.com/

miracleofmagick · April 11, 2008, 12:10pm

Eric H. wrote:

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

Keep those gems coming!

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

‘Nothing to update’ return when I do ‘gem system update’ on gem version
1.1.0
The gem still not upload to Rubyforge?

C:\Documents and Settings\swong24>gem env
RubyGems Environment:

RUBYGEMS VERSION: 1.1.0 (1.1.0)
RUBY VERSION: 1.8.6 (2008-03-30 patchlevel 5000) [i386-mingw32]
INSTALLATION DIRECTORY:
C:/Devel/installer3/sandbox/ruby_mingw/lib/ruby/gems/1.8
RUBY EXECUTABLE: C:/Devel/installer3/sandbox/ruby_mingw/bin/ruby.exe
RUBYGEMS PLATFORMS:
- ruby
- x86-mingw32
GEM PATHS:
- C:/Devel/installer3/sandbox/ruby_mingw/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

C:\Documents and Settings\swong24>gem --version
1.1.0

C:\Documents and Settings\swong24>gem update --system
Updating RubyGems
Updating metadata for 17 gems from http://gems.rubyforge.org/
…
complete
Nothing to update

C:\Documents and Settings\swong24>gem --version
1.1.0

miracleofmagick · April 11, 2008, 3:46pm

Eric H. [email protected] wrote:

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

Seems to be working just great on my Mac OS X - thanks as always! m.

miracleofmagick · April 11, 2008, 12:15pm

Shin guey Wong wrote:

Eric H. wrote:

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

Forgot the following line:
C:\Documents and Settings\swong24>gem --debug update system
Exception `NameError’ at
C:/Devel/installer3/sandbox/ruby_mingw/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:133

uninitialized constant Gem::Commands::UpdateCommand
Updating installed gems
Exception `Gem::LoadError’ at
C:/Devel/installer3/sandbox/ruby_mingw/lib/ruby/site_ruby/1.8/rubygems.rb:499
Could not find RubyGem sources (> 0.0.1)

Nothing to update

miracleofmagick · April 11, 2008, 10:29pm

On Apr 11, 2008, at 03:10 AM, Shin guey Wong wrote:

version
1.1.0
The gem still not upload to Rubyforge?

I waited until it appeared in the index for me before posting.

C:\Documents and Settings\swong24>gem update --system
Updating RubyGems
Updating metadata for 17 gems from http://gems.rubyforge.org/
…
complete
Nothing to update

C:\Documents and Settings\swong24>gem --version
1.1.0

Does:

gem list -r rubygems-update

report a 1.1.1? If not, try:

gem list -r --all rubygems-update

miracleofmagick · April 12, 2008, 5:43am

Shin guey Wong wrote:

Shin guey Wong wrote:

Eric H. wrote:

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

C:\Documents and Settings\swong24>gem --debug update system

Does

gem update --system

not work?

N.B. The double dashes in front of “system”.

Regards,

miracleofmagick · April 11, 2008, 7:34pm

On Apr 10, 2008, at 10:42 PM, Eric H. wrote:

Downloaded gems now go into --install-dir’s cache directory.
Keep those gems coming!

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

Rock on Eric and the gems team!

Cheers-

Ezra Z.
– Founder & Software Architect
– [email protected]
– EngineYard.com

miracleofmagick · April 12, 2008, 9:47am

On 11 abr, 11:11, Luc H. [email protected] wrote:

% gem --version
1.1.0

If you try to update from a previous version (1.0.1) works without
issues, funny fact:

$gem update --system
Updating RubyGems
Bulk updating Gem source index for: http://gems.rubyforge.org/
Nothing to update

$gem install rubygems-update
Successfully installed rubygems-update-1.1.1
1 gem installed

Just run ‘update_rubygems’ after that

Tested under:
ruby 1.8.6 (2008-03-30 patchlevel 5000) [i386-mingw32]

But it seems the glitch is platform-irrelevant.

Regards,

miracleofmagick · April 16, 2008, 8:34am

On 4/11/08, Eric H. [email protected] wrote:

Does:

gem list -r rubygems-update

report a 1.1.1? If not, try:

gem list -r --all rubygems-update

Yes, it does. But gem update --system is not updating rubygems:

----------- 8< -----------
$ gem list -r rubygems-update

*** REMOTE GEMS ***

Bulk updating Gem source index for: http://gems.rubyforge.org/
rubygems-update (1.1.1, 1.1.0, 1.0.1, 1.0.0, 0.9.5, 0.9.4, 0.9.3,
0.9.2, 0.9.1, 0.9.0, 0.8.11, 0.8.10, 0.8.8, 0.8.6, 0.8.5, 0.8.4,
0.8.3, 0.8.1, 0.8.0)
$ sudo gem update --system
Updating RubyGems
Nothing to update
$ gem --version
1.1.0
----------- >8 -----------

miracleofmagick · April 16, 2008, 8:58am

On Apr 15, 2008, at 23:34 PM, Gerardo S. Gómez Garrido wrote:

0.9.2, 0.9.1, 0.9.0, 0.8.11, 0.8.10, 0.8.8, 0.8.6, 0.8.5, 0.8.4,
0.8.3, 0.8.1, 0.8.0)
$ sudo gem update --system
Updating RubyGems
Nothing to update
$ gem --version
1.1.0

sudo gem --version ?

miracleofmagick · April 16, 2008, 4:42pm

$ sudo gem --version
1.1.0

by the way, Rubygems was installed using NetBSD’s pkgsrc, on Solaris.

miracleofmagick · April 17, 2008, 8:38pm

On Apr 16, 2008, at 07:40 AM, Gerardo S. Gómez Garrido wrote:

$ sudo gem --version
1.1.0

by the way, Rubygems was installed using NetBSD’s pkgsrc, on Solaris.

I fear there may be a bug, does sudo update_rubygems fix it?

miracleofmagick · April 12, 2008, 9:14am

On 11 avr. 08, at 12:40, Bil K. wrote:

Does

gem update --system

not work?

Does not work for me either…

% gem --version
1.1.0

% gem env
RubyGems Environment:

RUBYGEMS VERSION: 1.1.0 (1.1.0)
RUBY VERSION: 1.8.6 (2007-09-24 patchlevel 111) [i686-darwin9.2.2]
INSTALLATION DIRECTORY: /opt/local/lib/ruby/gems/1.8
RUBY EXECUTABLE: /opt/local/bin/ruby
RUBYGEMS PLATFORMS:
- ruby
- x86-darwin-9
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

% sudo gem update --system
Updating RubyGems
Nothing to update

miracleofmagick · April 17, 2008, 10:38pm

On Apr 17, 2008, at 12:30 PM, Gerardo S. Gómez Garrido wrote:

It seems that the packager didn’t include update_rubygems. I found it
though, in the directory where rubygems was built:

$ sudo /usr/pkgsrc/misc/rubygems/work/rubygems-1.1.0/bin/
update_rubygems
Error: Cannot find RubyGems Update Path!

RubyGems has already been updated.
The rubygems-update gem may now be uninstalled.
E.g. gem uninstall rubygems-update

That is the RubyGems 1.1.0 updater, not 1.1.1.

It appears that something went wrong with the installation of rubygems-
update. Try it manually:

sudo gem install rubygems-update
sudo update_rubygems.

miracleofmagick · April 17, 2008, 9:31pm

It seems that the packager didn’t include update_rubygems. I found it
though, in the directory where rubygems was built:

$ sudo /usr/pkgsrc/misc/rubygems/work/rubygems-1.1.0/bin/update_rubygems
Error: Cannot find RubyGems Update Path!

RubyGems has already been updated.
The rubygems-update gem may now be uninstalled.
E.g. gem uninstall rubygems-update

miracleofmagick · April 17, 2008, 11:09pm

It worked!

Thank you

miracleofmagick · June 21, 2008, 3:12am

Eric H. wrote:

Release 1.1.1 fixes some bugs.

After updating I am seeing a bulk update every single time I install a
gem … AND things seem veeeery slow compared to normal. Any ideas?

miracleofmagick · June 21, 2008, 8:00am

On Jun 20, 2008, at 18:11 , Tim F. wrote:

Eric H. wrote:

Release 1.1.1 fixes some bugs.

After updating I am seeing a bulk update every single time I install a
gem … AND things seem veeeery slow compared to normal. Any ideas?

I did for a week or two… seems to be fixed for me. I assumed it was
on the server side.

% gem outdated
Updating metadata for 56 gems from http://gems.rubyforge.org/
…
complete
actionmailer (2.0.2 < 2.1.0)
actionpack (2.0.2 < 2.1.0)
activerecord (2.0.2 < 2.1.0)
activeresource (2.0.2 < 2.1.0)
activesupport (2.0.2 < 2.1.0)
acts_as_ferret (0.4.1 < 0.4.3)
capistrano (2.0.0 < 2.4.0)
daemons (1.0.9 < 1.0.10)
ferret (0.11.4 < 0.11.6)
highline (1.2.9 < 1.4.0)
libxml-ruby (0.3.8.4 < 0.5.4)
mechanize (0.7.2 < 0.7.6)
miniunit (1.2.0 < 1.2.1)
mongrel (1.1.4 < 1.1.5)
net-sftp (1.1.0 < 2.0.1)
net-ssh (1.1.2 < 2.0.2)
postgres (0.7.9.2007.12.22 < 0.7.9.2008.01.28)
rails (2.0.2 < 2.1.0)
rspec (1.1.3 < 1.1.4)
ruby-openid (1.1.4 < 2.0.4)
rubynode (0.1.4 < 0.1.5)
sqlite3-ruby (1.2.1 < 1.2.2)
% gem -v
1.1.1

miracleofmagick · June 21, 2008, 10:25pm

On Jun 20, 2008, at 18:11 PM, Tim F. wrote:

Eric H. wrote:

Release 1.1.1 fixes some bugs.

After updating I am seeing a bulk update every single time I install a
gem … AND things seem veeeery slow compared to normal. Any ideas?

RubyGems 1.2 comes out tonight Pacific Time. Wait a few hours.