ANN: RubyGems 0.9.3 Released

Ruby
1

= Announce: RubyGems Release 0.9.3

Release 0.9.3 is a maintenance release of RubyGems that fixes a problem
with ZLib on Windows playforms.

If you are experiencing “Buffer Error” problems with RubyGems, we
recommend upgrading to RubyGems 0.9.3.

Bug Fixes Include:

The ZLib library on Windows will occasionally complains about a buffer
error when unpacking gems. The Gems software has a workaround for
that problem, but the workaround was only enabled for versions of ZLib
1.2.1 or earlier. We have received several reports of the error
occuring with ZLib 1.2.3, so we have permanently enabled the work
around on all versions.

== What is RubyGems?

RubyGems is a package management system for Ruby applications and
libraries. RubyGems one command download makes installing Ruby
software fun and enjoyable again. (Ok, not really.)

Many gems are available for download from the RubyForge site. Browse
the list of gems with a “gem list --remote” command and download what
you need with a simple “gem install ”. RubyGems takes
care of the details of installing, not only the gem you requested, but
also any gems needed by the software you selected.

== How can I get RubyGems?

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 all (you may need admin/root privilege)

== What’s Next

The next big thing on the plate is to integrate the local/remote gem
logic and make the whole thing more consistent.

== Thanks

Major contributors to this release include:

  • Jamis B. (for discovering the ZLib problem).

Keep those gems coming!

– Jim & Chad (for the RubyGems team)

2

On 5/11/07, Jim W. [email protected] wrote:

The ZLib library on Windows will occasionally complains about a buffer
software fun and enjoyable again. (Ok, not really.)
you need to do is:
$ update_rubygems (… here too)
The next big thing on the plate is to integrate the local/remote gem
– Jim & Chad (for the RubyGems team)

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

Has the “clean” option, which would remove all the outdated versions,
been removed with 0.9.3?

It doesn’t show up in ‘gem help commands’

If this is, in fact, the case - and it has been removed… how does
one perform the same action of removing all the outdated gems from the
tree?

3

On May 11, 2007, at 5:34 AM, Jim W. wrote:

= Announce: RubyGems Release 0.9.3

Release 0.9.3 is a maintenance release of RubyGems that fixes a
problem
with ZLib on Windows playforms.

If you are experiencing “Buffer Error” problems with RubyGems, we
recommend upgrading to RubyGems 0.9.3.

I’m not sure if it was intentional or not. But this release of
rubygems does not have the ‘cleanup’ command anymore. What should we
use instead of cleanup?

ey00-s00289 ~ # gem --version
0.9.3
ey00-s00289 ~ # gem cleanup mongrel_cluster
ERROR: While executing gem … (RuntimeError)
Unknown command cleanup

This worked fine with rubygems 0.9.2 and prior. I will file a ticket
in the tracker as well.

Thanks
– Ezra Z.
– Lead Rails Evangelist
– [email protected]
– Engine Y., Serious Rails Hosting
– (866) 518-YARD (9273)

4

After updating (using “gem update --system”), I’m now getting this error
when I attempt to install or update another gem:

ERROR: While executing gem … (NoMethodError)
undefined method `refresh’ for #Hash:0x14842a0

I’m using Ruby 1.8.4 on OS X.

I tried the manual install, too (downloading and running setup.rb), but
got
the same behavior. While running setup.rb, the output ended as follows:

Successfully built RubyGem
Name: sources
Version: 0.0.1
File: sources-0.0.1.gem
Removing old RubyGems RDoc and ri…
Installing rubygems-0.9.3 ri…

lib/rubygems/command_manager.rb:146:59: Skipping require of dynamic
string:
“rubygems/commands/#{command_name}_command”

lib/rubygems/digest/md5.rb:16:15: Couldn’t find MD5. Assuming it’s a
module

lib/rubygems/gem_commands.rb:192:49: Skipping require of dynamic string:
“rubygems/commands/#{name}_command”
Installing rubygems-0.9.3 rdoc…

lib/rubygems/command_manager.rb:146:59: Skipping require of dynamic
string:
“rubygems/commands/#{command_name}_command”

lib/rubygems/digest/md5.rb:16:15: Couldn’t find MD5. Assuming it’s a
module

lib/rubygems/gem_commands.rb:192:49: Skipping require of dynamic string:
“rubygems/commands/#{name}_command”

As of RubyGems 0.8.0, library stubs are no longer needed.
Searching $LOAD_PATH for stubs to optionally delete (may take a
while)…
…done.
No library stubs found.

I’m assuming the MD5 and “dynamic string” stuff is harmless, as it
wasn’t
treated as an error. Let me know if I should log a bug.

dean

5

On 11 mai 07, at 19:57, Ezra Z. wrote:

I’m not sure if it was intentional or not. But this release of
rubygems does not have the ‘cleanup’ command anymore.

I’m pretty sure it was not intentional. Having a look at the diff
between r1220 and r1222 I would say that it was just an involuntary
omission:

<http://viewvc.rubyforge.mmmultiworks.com/cgi/viewvc.cgi/trunk/lib/
rubygems/command_manager.rb?root=rubygems&r1=1220&r2=1222>

And by the way, there are already 4 duplicates of this bug in the
rubygems tracker (eh, I added the third one before realising there
were already two of them ;)) so no need to add more…

6

Luc H. wrote:

I’m pretty sure it was not intentional. Having a look at the diff
between r1220 and r1222 I would say that it was just an involuntary
omission:

Yep. It was unintentional. We will get a fix in soon and make a new
release probably after RailsConf.

– Jim

7

Jim W. wrote:

Luc H. wrote:

I’m pretty sure it was not intentional. Having a look at the diff
between r1220 and r1222 I would say that it was just an involuntary
omission:

Yep. It was unintentional. We will get a fix in soon and make a new
release probably after RailsConf.

– Jim

I’ve updated to the new version, but I still get buffer errors at times.

Seems to be mostly due to windows file modes not being binary by
default. For example, index_gem_repository.rb fails to write “yaml.Z” on
windows, and also fails to read it in for #paranoid (File.read is no
good for binary files either).

8

On May 11, 8:34 am, Jim W. [email protected] wrote:

= Announce: RubyGems Release 0.9.3

now I get this doing an update;

Updating installed gems…
Attempting remote update of rake
ERROR: While executing gem … (ArgumentError)
install directory #<Pathname:c:/ruby/lib/ruby/gems/1.8/gems/
rake-0.7.3> not absolute

filed a bug on the tracker. none of my gems will now update.

-stu

9

I have the same error:

Successfully built RubyGem
Name: sources
Version: 0.0.1
File: sources-0.0.1.gem
Removing old RubyGems RDoc and ri…
Installing rubygems-0.9.4 ri…
Installing rubygems-0.9.4 rdoc…

As of RubyGems 0.8.0, library stubs are no longer needed.
Searching $LOAD_PATH for stubs to optionally delete (may take a
while)…
…done.
No library stubs found.

I’m using RubyGems 0.9.4 on MacOsX with ruby 1.8.6 (2007-03-13
patchlevel 0) [powerpc-darwin8.10.0]

Error example:
/usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:304:in
`report_activate_error’: Could not find RubyGem nanoc (> 0)
(Gem::LoadError)

10

On Sep 19, 2007, at 11:21, Sglez Fms wrote:

As of RubyGems 0.8.0, library stubs are no longer needed.
Searching $LOAD_PATH for stubs to optionally delete (may take a
while)…
…done.
No library stubs found.

I don’t see any errors here.

I’m using RubyGems 0.9.4 on MacOsX with ruby 1.8.6 (2007-03-13
patchlevel 0) [powerpc-darwin8.10.0]

Error example:
/usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:304:in
`report_activate_error’: Could not find RubyGem nanoc (> 0)
(Gem::LoadError)

Do you have the gem installed? (gem list will say so)