Asp Forum - [ANN] RubyGems 1.0.0

Eric Hodel

12/20/2007 8:33:00 AM

Release 1.0.0 fixes several bugs.

Major New Features Include:

* RubyGems warns about various problems with gemspecs during gem
building
* More-consistent versioning for the RubyGems software

Other Changes Include:

* Fixed various bugs and problems with installing gems on Windows
* Fixed using `gem server` for installing gems
* Various operations are even more verbose with --verbose
* Built gems are now backwards compatible with 0.9.4
* Improved detection of RUBYOPT loading rubygems
* `ruby setup.rb` now has a --help option
* Gem::Specification#bindir is now respected on installation
* Executable stubs can now be installed to match ruby's name, so if
ruby is
installed as 'ruby18', foo_exec will be installed as 'foo_exec18'
* `gem unpack` can now unpack into a specific directory with --target
* OpenSSL is no longer required by default

Deprecations and Deletions:

* Kernel#require_gem has been removed
* Executables without a shebang will not be wrapped in a future
version, this
may cause such executables to fail to operate on installation
* Gem::Platform constants other than RUBY and CURRENT have been removed
* Gem::RemoteInstaller was removed
* Gem::Specification#test_suite_file and #test_suite_file= are
deprecated in
favor of #test_file and #test_file=
* Gem::Specification#autorequire= has been deprecated
* Time::today will be removed in a future version

== 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/?gr...
2. UNPACK INTO A DIRECTORY AND CD THERE
3. INSTALL WITH: ruby setup.rb (you may need admin/root privilege)

== Thanks

Keep those gems coming!

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

30 Answers

Eric Hodel

12/20/2007 9:00:00 AM

On Dec 20, 2007, at 24:33 AM, Eric Hodel wrote:

> Release 1.0.0 fixes several bugs.

There's an issue with installing on Ruby versions 1.8.5 and earlier.
I'll fix this tomorrow and re-release.

Daniel Lucraft

12/20/2007 10:24:00 AM

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

Many thanks for fixing the memory usage of the bulk update. Works
perfectly on my 256Mb VPS now.

thanks,
Dan
--
Posted via http://www.ruby-....

John Pywtorak

12/20/2007 8:00:00 PM

When I install my own gem on one of my systems rubygems adds a dash to
the filename, or gem name?

example:
~/box$ gem install ruby/email_agent-0.5.1.gem
Successfully installed email_agent, version 0.5.1
Installing ri documentation for email_agent-0.5.1-...
Installing RDoc documentation for email_agent-0.5.1-...

Why is that - after the version number there?

Anyone know. Thanks

Jim Morris

12/20/2007 8:57:00 PM

After trying to install both from the source and from gem update --system
I get

/usr/bin/gem:23: uninitialized constant Gem::GemRunner (NameError)

when I try to run it.

I am using ruby 1.8.6 on a Ubuntu system.

Thanks

Eric Hodel wrote:
> Release 1.0.0 fixes several bugs.
>
> Major New Features Include:
>
> * RubyGems warns about various problems with gemspecs during gem building
> * More-consistent versioning for the RubyGems software
>
> Other Changes Include:
>
> * Fixed various bugs and problems with installing gems on Windows
> * Fixed using `gem server` for installing gems
> * Various operations are even more verbose with --verbose
> * Built gems are now backwards compatible with 0.9.4
> * Improved detection of RUBYOPT loading rubygems
> * `ruby setup.rb` now has a --help option
> * Gem::Specification#bindir is now respected on installation
> * Executable stubs can now be installed to match ruby's name, so if ruby is
> installed as 'ruby18', foo_exec will be installed as 'foo_exec18'
> * `gem unpack` can now unpack into a specific directory with --target
> * OpenSSL is no longer required by default
>
> Deprecations and Deletions:
>
> * Kernel#require_gem has been removed
> * Executables without a shebang will not be wrapped in a future version,
> this
> may cause such executables to fail to operate on installation
> * Gem::Platform constants other than RUBY and CURRENT have been removed
> * Gem::RemoteInstaller was removed
> * Gem::Specification#test_suite_file and #test_suite_file= are
> deprecated in
> favor of #test_file and #test_file=
> * Gem::Specification#autorequire= has been deprecated
> * Time::today will be removed in a future version
>
> == 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/?gr...
> 2. UNPACK INTO A DIRECTORY AND CD THERE
> 3. INSTALL WITH: ruby setup.rb (you may need admin/root privilege)
>
> == Thanks
>
> Keep those gems coming!
>
> -- Jim & Chad & Eric (for the RubyGems team)
>
>
>
>

--
Jim Morris, http://blog.w...

Jim Morris

12/20/2007 9:05:00 PM

Seems to have somethign to do with having to sudo gem update, now if I runit with

> sudo gem list

it works which I didn't have to do before.

I'll investigate further.

Jim Morris wrote:
> After trying to install both from the source and from gem update --system
> I get
>
> /usr/bin/gem:23: uninitialized constant Gem::GemRunner (NameError)
>
> when I try to run it.
>
> I am using ruby 1.8.6 on a Ubuntu system.
>
> Thanks
>
> Eric Hodel wrote:
>> Release 1.0.0 fixes several bugs.
>>
>> Major New Features Include:
>>
>> * RubyGems warns about various problems with gemspecs during gem building
>> * More-consistent versioning for the RubyGems software
>>
>> Other Changes Include:
>>
>> * Fixed various bugs and problems with installing gems on Windows
>> * Fixed using `gem server` for installing gems
>> * Various operations are even more verbose with --verbose
>> * Built gems are now backwards compatible with 0.9.4
>> * Improved detection of RUBYOPT loading rubygems
>> * `ruby setup.rb` now has a --help option
>> * Gem::Specification#bindir is now respected on installation
>> * Executable stubs can now be installed to match ruby's name, so if
>> ruby is
>> installed as 'ruby18', foo_exec will be installed as 'foo_exec18'
>> * `gem unpack` can now unpack into a specific directory with --target
>> * OpenSSL is no longer required by default
>>
>> Deprecations and Deletions:
>>
>> * Kernel#require_gem has been removed
>> * Executables without a shebang will not be wrapped in a future
>> version, this
>> may cause such executables to fail to operate on installation
>> * Gem::Platform constants other than RUBY and CURRENT have been removed
>> * Gem::RemoteInstaller was removed
>> * Gem::Specification#test_suite_file and #test_suite_file= are
>> deprecated in
>> favor of #test_file and #test_file=
>> * Gem::Specification#autorequire= has been deprecated
>> * Time::today will be removed in a future version
>>
>> == 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/?gr...
>> 2. UNPACK INTO A DIRECTORY AND CD THERE
>> 3. INSTALL WITH: ruby setup.rb (you may need admin/root privilege)
>>
>> == Thanks
>>
>> Keep those gems coming!
>>
>> -- Jim & Chad & Eric (for the RubyGems team)
>>
>>
>>
>>
>
>

--
Jim Morris, http://blog.w...

Joe Van Dyk

12/20/2007 9:19:00 PM

On Dec 20, 12:33 am, Eric Hodel <drbr...@segment7.net> wrote:
> Release 1.0.0 fixes several bugs.
>
> Major New Features Include:
>
> *RubyGemswarns about various problems with gemspecs during gem
> building
> * More-consistent versioning for theRubyGemssoftware
>
> Other Changes Include:
>
> * Fixed various bugs and problems with installing gems on Windows
> * Fixed using `gem server` for installing gems
> * Various operations are even more verbose with --verbose
> * Built gems are now backwards compatible with 0.9.4
> * Improved detection of RUBYOPT loadingrubygems
> * `ruby setup.rb` now has a --help option
> * Gem::Specification#bindir is now respected on installation
> * Executable stubs can now be installed to match ruby's name, so if
> ruby is
> installed as 'ruby18', foo_exec will be installed as 'foo_exec18'
> * `gem unpack` can now unpack into a specific directory with --target
> * OpenSSL is no longer required by default
>
> Deprecations and Deletions:
>
> * Kernel#require_gem has been removed
> * Executables without a shebang will not be wrapped in a future
> version, this
> may cause such executables to fail to operate on installation
> * Gem::Platform constants other than RUBY and CURRENT have been removed
> * Gem::RemoteInstaller was removed
> * Gem::Specification#test_suite_file and #test_suite_file= are
> deprecated in
> favor of #test_file and #test_file=
> * Gem::Specification#autorequire= has been deprecated
> * Time::today will be removed in a future version
>
> == How can I getRubyGems?
>
> NOTE: If you have installedRubyGemsusing a package you may want to
> install a
> newRubyGemsthrough the same packaging system.
>
> If you have a recent version ofRubyGems(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
> installedrubygems-update gems).
>
> If you have an older version ofRubyGemsinstalled, then you can still
> do it in two steps:
>
> $ gem installrubygems-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/?gr...
> 2. UNPACK INTO A DIRECTORY AND CD THERE
> 3. INSTALL WITH: ruby setup.rb (you may need admin/root privilege)
>
> == Thanks
>
> Keep those gems coming!
>
> -- Jim & Chad & Eric (for theRubyGemsteam)

I upgraded to RubyGems 1.0.0. Running ruby 1.8.6 on OS X.

When I try to run a spec file in my Rails project, I get:

/opt/local/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:144:in
`parse': Illformed requirement [""] (ArgumentError)
from /opt/local/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:
70:in `initialize'
from /opt/local/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:
69:in `map'
from /opt/local/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:
69:in `initialize'
from /opt/local/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:
45:in `new'
from /opt/local/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:
45:in `create'
from /opt/local/lib/ruby/site_ruby/1.8/rubygems/
specification.rb:413:in `required_rubygems_version='
from /opt/local/lib/ruby/gems/1.8/specifications/
builder-2.1.2.gemspec:7:in `load_specification'
from /opt/local/lib/ruby/site_ruby/1.8/rubygems/
specification.rb:540:in `initialize'
... 25 levels...
from ./spec/models/../spec_helper.rb:4:in `require'
from ./spec/models/../spec_helper.rb:4
from spec/models/puzzle_spec.rb:1:in `require'
from spec/models/puzzle_spec.rb:1

Any ideas? You need more data? Is it possible to downgrade to
rubygems 0.9.5?

Eric Hodel

12/20/2007 9:28:00 PM

On Dec 20, 2007, at 13:20 PM, Joe Van Dyk wrote:
> I upgraded to RubyGems 1.0.0. Running ruby 1.8.6 on OS X.
>
> When I try to run a spec file in my Rails project, I get:
>
> /opt/local/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:144:in
> `parse': Illformed requirement [""] (ArgumentError)
> from /opt/local/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:
> 70:in `initialize'
> from /opt/local/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:
> 69:in `map'
> from /opt/local/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:
> 69:in `initialize'
> from /opt/local/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:
> 45:in `new'
> from /opt/local/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:
> 45:in `create'
> from /opt/local/lib/ruby/site_ruby/1.8/rubygems/
> specification.rb:413:in `required_rubygems_version='
> from /opt/local/lib/ruby/gems/1.8/specifications/
> builder-2.1.2.gemspec:7:in `load_specification'
> from /opt/local/lib/ruby/site_ruby/1.8/rubygems/
> specification.rb:540:in `initialize'
> ... 25 levels...
> from ./spec/models/../spec_helper.rb:4:in `require'
> from ./spec/models/../spec_helper.rb:4
> from spec/models/puzzle_spec.rb:1:in `require'
> from spec/models/puzzle_spec.rb:1
>
> Any ideas? You need more data? Is it possible to downgrade to
> rubygems 0.9.5?

I'll need a full backtrace.

You can download RubyGems 0.9.5 and install it from the tarball to
revert.

Jim Morris

12/20/2007 10:00:00 PM

Jim Morris wrote:
> Seems to have somethign to do with having to sudo gem update, now if I
> runit with
>
> > sudo gem list
>
> it works which I didn't have to do before.
>
> I'll investigate further.
>
> Jim Morris wrote:
>> After trying to install both from the source and from gem update --system
>> I get
>>
>> /usr/bin/gem:23: uninitialized constant Gem::GemRunner (NameError)
>>
>> when I try to run it.
>>
>> I am using ruby 1.8.6 on a Ubuntu system.
>>
>> Thanks
>>

Ok this has something to do with the way Ubuntu installs ruby (surprise surprise!)

The work around for me was to nuke the /usr/lib/ruby directory by renaming it ruby.old

Install ruby from the source into /usr/local/ruby

copy all my gems from /usr/lib/ruby.old/gems to /usr/local/lib/ruby/gems

also nuke /usr/bin/gem* and install gem into /usr/local/bin

Seems to have fixed it, what a mess!!

--
Jim Morris, http://blog.w...

Eric Hodel

12/20/2007 10:40:00 PM

On Dec 20, 2007, at 12:57 PM, Jim Morris wrote:
> Eric Hodel wrote:
>> == 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.
>
> I get
>
> /usr/bin/gem:23: uninitialized constant Gem::GemRunner (NameError)
>
> when I try to run it.
>
> I am using ruby 1.8.6 on a Ubuntu system.

Did you see the NOTE? I think this is your problem.

Eric Hodel

12/21/2007 2:52:00 AM

On Dec 20, 2007, at 12:00 PM, John Pywtorak wrote:
> When I install my own gem on one of my systems rubygems adds a dash
> to the filename, or gem name?
>
> example:
> ~/box$ gem install ruby/email_agent-0.5.1.gem
> Successfully installed email_agent, version 0.5.1
> Installing ri documentation for email_agent-0.5.1-...
> Installing RDoc documentation for email_agent-0.5.1-...
>
> Why is that - after the version number there?

Can I see `gem env` output?

Also, what version of RubyGems was used to build the gem?

comp.lang.ruby

[ANN] RubyGems 1.0.0

Eric Hodel

Eric Hodel

Daniel Lucraft

John Pywtorak

Jim Morris

Jim Morris

Joe Van Dyk

Eric Hodel

Jim Morris

Eric Hodel

Eric Hodel

x Login to ForumsZone