RubyGems 1.0.1

= Announce: RubyGems Release 1.0.1

Release 1.0.1 fixes a few bugs.

Bugs Fixed:

  • Installation on Ruby 1.8.3 through 1.8.5 fixed
  • gem build on 1.8.3 fixed

Other Changes Include:

  • Since RubyGems 0.9.5, RubyGems is no longer supported on Ruby 1.8.2
    or older,
    this is official in RubyGems 1.0.1.

== How can I get RubyGems?

NOTE: If you have installed RubyGems using a package 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)

1.0.1 works great thus far on my OS X 10.4.11 with Ruby 1.8.4

On Dec 20, 10:25 pm, Eric H. [email protected] wrote:

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)

I have Ruby and RubyGems installed both in Windows using the “One-
Click” installer, and in Cygwin. At the DOS prompt, I have to type
“gem update --system” to update the Windows RubyGems. But in Cygwin,
RubyGems will update itself if I just do “gem update”, without
specifying the --system flag. Has anyone else seen this?

Eric H. [email protected] wrote:

Release 1.0.1 fixes a few bugs.

I get a prob on Mac OS X 10.4.11 the installation (sudo gem install
–system) ending with :

~%> sudo gem update --system
Password:
Updating RubyGems…
Updating metadata for 121 gems from http://gems.rubyforge.org


complete
Attempting remote update of rubygems-update
Successfully installed rubygems-update-1.0.1
1 gem installed
Updating version of RubyGems to 1.0.1
Installing RubyGems 1.0.1
install -c -m 0644 rbconfig/datadir.rb
/opt/local/lib/ruby/site_ruby/1.8/rbconfig/datadir.rb
install -c -m 0644 rubygems/builder.rb
/opt/local/lib/ruby/site_ruby/1.8/rubygems/builder.rb
[…]
/opt/local/lib/ruby/site_ruby/1.8/ubygems.rb
setup.rb:101: undefined method default_exec_format' for Gem:Module (NoMethodError) from setup.rb:97:ineach’
from setup.rb:97
from setup.rb:94:in `chdir’
from setup.rb:94
~%>

the ruby version i’m using being :

~%> ruby --version
ruby 1.8.6 (2007-03-13 patchlevel 0) [powerpc-darwin8.9.0]

Yvon

On Dec 21, 2007, at 06:39 AM, Karl von Laudermann wrote:

specifying the --system flag. Has anyone else seen this?
Can you post a screenshot of this behavior?

On Dec 21, 3:14 pm, Eric H. [email protected] wrote:

On Dec 21, 2007, at 06:39 AM, Karl von Laudermann wrote:

But in Cygwin,
RubyGems will update itself if I just do “gem update”, without
specifying the --system flag. Has anyone else seen this?

Can you post a screenshot of this behavior?

Well, it’s kinda too late now since I already upgraded. But there’s
really not much to show; Under DOS, I did “gem update”, and it just
updated one gem. Then I did “gem update --system”, and it updated
RubyGems to 1.0.1, printing out a whole ton of stuff. Then in Cygwin,
I did “gem update” and it printed out all the exact same stuff as “gem
update --system” did under DOS, after which “gem -v” indicated that it
was now version 1.0.1.

On 22 dic, 19:03, Karl von Laudermann [email protected]
wrote:

Well, it’s kinda too late now since I already upgraded. But there’s
really not much to show; Under DOS, I did “gem update”, and it just
updated one gem. Then I did “gem update --system”, and it updated
RubyGems to 1.0.1, printing out a whole ton of stuff. Then in Cygwin,
I did “gem update” and it printed out all the exact same stuff as “gem
update --system” did under DOS, after which “gem -v” indicated that it
was now version 1.0.1.

The ruby interperter you ran on cygwin was a cygwin ruby? (ruby -v
should indicate cygwin as platform).

I’m asking this since some users have ruby in they path mixing
native(vc6 or mingw) ruby with cygwin environment end in broken
things.

Eric H. wrote:

  • Installation on Ruby 1.8.3 through 1.8.5 fixed

Now fix it for 1.9.0. :stuck_out_tongue:

On Dec 22, 2007, at 04:54 AM, Peter B. wrote:

Eric H. wrote:

  • Installation on Ruby 1.8.3 through 1.8.5 fixed

Now fix it for 1.9.0. :stuck_out_tongue:

Lies.

$ gem19 -v
1.0.1
$ gem19 which rubygems
/usr/local/lib/ruby/1.9/rubygems.rb

On Dec 21, 2007, at 22:40 PM, Une Bévue wrote:

Updating RubyGems…
/opt/local/lib/ruby/site_ruby/1.8/rbconfig/datadir.rb
~%>

the ruby version i’m using being :

~%> ruby --version
ruby 1.8.6 (2007-03-13 patchlevel 0) [powerpc-darwin8.9.0]

Do you have RUBYOPT set?

What is it set to?

On Dec 20, 10:25 pm, Eric H. [email protected] wrote:

If you have a recent version of RubyGems (0.8.5 or later), then all
$ gem install rubygems-update (again, might need to be admin/root)

Keep those gems coming!

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

Using gem 1.0.1 install via gems update --system

C:\Documents and Settings\Owner>ruby -v
ruby 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32]

C:\Documents and Settings\Owner>gem -v
1.0.1

C:\Documents and Settings\Owner>gem which rubygems
(checking gem rubygems-update-1.0.1 for rubygems)
c:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb
C:\Documents and Settings\Owner>

How come it cannot “see” these gems which are available from
rubyforge?
win32-api-1.0.5-x86-mswin32-60.gem or
win32-service-0.6.0-x86-mswin32-60.gem

ps neither does gems -v 0.9.4

I downloaded the gems from rubyforge and did a local install
which worked out correctly – no problem that I know of.

Am I correct that it is not necessary to install rubygems-update if
I do a gem update --system?

Thank yous to the rubygems team, your work is much appreciated.

On 24 dic, 20:21, bbiker [email protected] wrote:

  • Installation on Ruby 1.8.3 through 1.8.5 fixed
    NOTE: If you have installed RubyGems using a package you may want to
  1. UNPACK INTO A DIRECTORY AND CD THERE
    You can
    C:\Documents and Settings\Owner>ruby -v
    How come it cannot “see” these gems which are available from
    rubyforge?
    win32-api-1.0.5-x86-mswin32-60.gem or
    win32-service-0.6.0-x86-mswin32-60.gem

ps neither does gems -v 0.9.4

I downloaded the gems from rubyforge and did a local install
which worked out correctly – no problem that I know of.

win32-service-0.6.0-x86-mswin32-60.gem:

platform: current
rubygems_version: 0.9.5

win32-api-1.0.5-x86-mswin32-60.gem:

platform: current
rubygems_version: 0.9.5

You may need to ask Daniel berger to re-release these packages since
they are made with 0.9.5, which was behaving badly for mswin32
platform.

RubyGems 1.0.1 now generates proper platform, so updated files will
work properly.

Am I correct that it is not necessary to install rubygems-update if
I do a gem update --system?

gem update --system actually download rubygems-update gem and executes
it, so this is done for you.

Thank yous to the rubygems team, your work is much appreciated.

Thank to you, and as Eric say: Keep those gems coming!

Regards,

Luis

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs