= Announce: RubyGems Release 0.9.1 Finally, the much anticipated RubyGems version 0.9.1 is now available. This release includes a number of new features and bug fixes. The most important change in RubyGems 0.9.1 is that RubyGems no longer allows files to be installed outside of the installation directory. A separate security bulletin with full details will be posted shortly. RubyGems 0.9.1 is a required update. The RubyForge gem repository will soon disallow installation by older versions of RubyGems. Manual installation will still be allowed. == Upgrade note While require_gem was deprecated in 0.9.0, the bin stubs are still using it (oops!). To get rid of the warnings printed by rake or other bin stubs simply run 'gem pristine --all'. == Changes in RubyGems 0.9.1 Major changes include: * RubyGems no longer allows installation of files outside the gem directory * #require_gem will now print a warning, use #gem instead * RubyGems now requires ruby 1.8.2 or greater * RubyGems is -w clean Minor changes include: * gem command changes * new gem pristine command * new gem outdated command * new gem sources command * gem uninstall can uninstall multiple gems * gem install uses the cache instead of downloading * gem install returns non-zero exit code on failure * gem install can now set shebang on bin stubs (env or ruby) * gem help output now fits in 80 columns * many proxy installation improvements * gem cert improvements * RubyGems is now easier to use as a library * Easier programatic installs * Easier inspection of local and remote gems * extension building enhancements * error reporting enhancements (less odd exceptions) * require now loads .jar files Bug fixes: * installing from scratch fixed * gem install --force forces * installing from read-only location works * gem uninstall requires full name * gem install obeys GEM_HOME for bin scripts * RubyGems now installs on ruby 1.9 * fixed issue with Gem::Specification#hash for JRuby * RubyGems now installs RDoc and ri for itself * RubyGems is now tab-free == 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. 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 <name-of-gem>". RubyGems takes care of the details of installing, not only the gem you requested, but also any gems needed by the software you selected. == RubyGems Statistics * About 1250 different gems are available from RubyForge * Over 540 thousand downloads of the RubyGems software * Over 8 million gem downloads If you are interested in finding out when new gems are released, I maintain an RSS feed at http://onestepback.org/gemwatch.rss. == 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 $ gem pristine --all # ... here too (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 $ gem pristine --all # and here 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 For RubyGems 0.9.2 the RubyGems team is looking to add: * Integration of local and remote installation * Automatic installation of platform-specific gems == Thanks Contributors to this release include: Anatol Pomozov, Gavin Sinclair, David Lee, Ryan Davis, Robert James, Chris Morris, Sylvain Joyeux, Sava Chankov, Tom Pollard, Kevin Clark, Andy Shen. Keep those gems coming! -- Eric Hodel (for the RubyGems team)
0.9.1 is in (p.masked). Please test (especially upgrades from 0.8 and 0.9.0). I have also added src_test for rubygems, which currently fails test_gem_ext_configure_builder.rb (suspects gentoo-specific). USE flag server is not in use.local.desc on purpose.
(In reply to comment #1) > 0.9.1 is in (p.masked). Please test (especially upgrades from 0.8 and 0.9.0). I > have also added src_test for rubygems, which currently fails > test_gem_ext_configure_builder.rb (suspects gentoo-specific). USE flag server > is not in use.local.desc on purpose. > I tested this last night from upstream and had some difficulty following Eric's procedure as documented. Hopefully the ebuild is in better shape than his directions on how to install the gem. :) I ended up downloading the tarball and installing it anew, rather than doing the "update". Here's the email thread: On Jan 16, 2007, at 7:56 PM, M. Edward (Ed) Borasky wrote: > Parragh Szabolcs wrote: >> I even tried: >> >> $ wget http://rubyforge.org/frs/download.php/16451/rubygems-update-0.9.1.gem >> $ gem install rubygems-update-0.9.1.gem >> Successfully installed rubygems-update, version 0.9.1 >> $ gem -v 0.9.0 >> ... > I got the same thing -- I think you have to run something else after you install the rubygems-update gem. I ended up downloading the tarball from RubyForge and installing it directly. That worked and I'm now on RubyGems 0.9.1. To be clear, because of rubygems poisoning indexing has been turned off. Until gem indexing is back on, you must manually download and install the gem updater. The basic steps are: % wget http://rubyforge.org/frs/download.php/16451/rubygems-update-0.9.1.gem % sudo gem install rubygems-update-0.9.1.gem % sudo update_rubygems % sudo gem pristine --all If you miss any of those steps, then things will (obviously) go wrong. If you don't have rubygems installed, or your version is < 0.8.5, then you can't use those steps and must do a full install.
The ebuild installs OK on all three of my Gentoo systems -- all ~x86, but one is an Athlon XP, one is an Athlon Thunderbird and one is a Pentium III.
*** Bug 163342 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > USE flag server is not in use.local.desc on purpose. The purpose being? :) It's not really optional. http://devmanual.gentoo.org/general-concepts/use-flags/index.html
(In reply to comment #5) > (In reply to comment #1) > > USE flag server is not in use.local.desc on purpose. > > The purpose being? :) It's not really optional. > > http://devmanual.gentoo.org/general-concepts/use-flags/index.html > That is I will add that use flag when 0.9.1 is unmasked.
(In reply to comment #1) > 0.9.1 is in (p.masked). Please test (especially upgrades from 0.8 and 0.9.0). I > have also added src_test for rubygems, which currently fails > test_gem_ext_configure_builder.rb (suspects gentoo-specific). USE flag server > is not in use.local.desc on purpose. > Going from rubygems-0.9.0-r2 to 0.9.1, the gem command gives me the following error: raven ~ # gem install hpricot ERROR: While executing gem ... (NoMethodError) undefined method `refresh' for #<Hash:0xb7c4e9bc> So far the only solution I've seen has been to manually delete /usr/lib/ruby/gems/1.8/source_cache, and the one in ~/.gems/ if it exists. I didn't, as root, have a ~/.gems . gem ebuilds still seemed to work ok, it's just the gem command.
you might need to do # gem pristine --all after installing rubygems 0.9.1. At least that's the step that the rubygems developers said needed to be done on the "ruby-talk" mailing list. I guess the question is whether there should be a "gem pristine --all" in the ebuild. I'm totally clueless about the internals of RubyGems, so I just follow peoples' instructions and whine at them on their bug trackers when something breaks. :)
(In reply to comment #8) > # gem pristine --all > manuall running that command makes no difference.
FYI: new version 0.9.2
rubygems-0.9.2 added. I'll remove 0.9.1 soon if no one objects. Richard, I couldn't reproduce the error while switching from 0.9.0-r2 to 0.9.2. If you can, please run gem with --debug --backtrace
A new version of ZenTest is out (3.5.0) which requires rubygems 0.9.1 or better. Any idea when these versions of rubygems will be unmasked? In any case I finally got to test rubygems 0.9.2. With FEATURES="test" I got: /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require': no such file to load -- rubygems/gem_open_uri (LoadError) from /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' from ./test/gemutilities.rb:12 from /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require' from /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' from test/test_file_list.rb:11 Without testing the gem installs fine and seems to work as expected.
(In reply to comment #12) > A new version of ZenTest is out (3.5.0) which requires rubygems 0.9.1 or > better. Any idea when these versions of rubygems will be unmasked? It will when someone in the herd does :) I haven't had time lately for this bug. The main obstacle to me is upgrading from older versions. If you need it, just comment out src_test and unmask it.
(In reply to comment #13) > It will when someone in the herd does :) I haven't had time lately for this > bug. The main obstacle to me is upgrading from older versions. If you need it, > just comment out src_test and unmask it. I have unmasked rubygems-0.9.2 and upgraded without problems (from 0.9.0-r2). What remains to be done to unmask this? The upgrade issue seems to be with 0.9.1 only (at least I haven't seen it with 0.9.2).
(In reply to comment #14) > (In reply to comment #13) > > > It will when someone in the herd does :) I haven't had time lately for this > > bug. The main obstacle to me is upgrading from older versions. If you need it, > > just comment out src_test and unmask it. > > I have unmasked rubygems-0.9.2 and upgraded without problems (from 0.9.0-r2). > > What remains to be done to unmask this? The upgrade issue seems to be with > 0.9.1 only (at least I haven't seen it with 0.9.2). Nothing I guess then. Please make it!
I've removed rubygems-0.9.1 from the tree since we have at least some reports of trouble with upgrading, and I've removed the package.mask so that rubygems-0.9.2 is now available as it seems to work fine with the upgrades.
