From luislavena at gmail.com  Wed Jul  1 20:47:26 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Wed, 1 Jul 2009 21:47:26 -0300
Subject: [Rubygems-developers] 1.3.5 soon
In-Reply-To: <10FC8EC5-899A-4C37-BE2A-C830257BDC1D@segment7.net>
References: <6D0B5E11-1149-4898-8FF6-C5727D7491BC@segment7.net> 
	<A48E17B7-57F3-4C2B-9B57-38F3F1136CE1@segment7.net>
	<2E2AF047-BBF5-4BE2-B0E4-7BA217699875@segment7.net> 
	<71166b3b0906262229l216ad0aby4b3fac3891f73368@mail.gmail.com> 
	<3D94512A-8548-46F6-98AF-0F7AE7C29862@segment7.net>
	<71166b3b0906291533t414f1141sde1492336f6e8060@mail.gmail.com> 
	<71166b3b0906291614n541e7f9avd70778cbd08ab528@mail.gmail.com> 
	<BAED9630-B211-49FE-8342-B23110ABF6DF@segment7.net>
	<71166b3b0906292004i14f4e2c7p5a95708e09b73cda@mail.gmail.com> 
	<10FC8EC5-899A-4C37-BE2A-C830257BDC1D@segment7.net>
Message-ID: <71166b3b0907011747l3b9918abha9f7f67c22dac84f@mail.gmail.com>

On Tue, Jun 30, 2009 at 8:03 PM, Eric Hodel<drbrain at segment7.net> wrote:
> On Jun 29, 2009, at 20:04, Luis Lavena wrote:
>>
>> On Mon, Jun 29, 2009 at 8:58 PM, Eric Hodel<drbrain at segment7.net> wrote:
>>>
>>> [...]
>>>
>>> I didn't upload a new gem after the UTF-8 change, I only merged to the
>>> 1_3
>>> branch.
>>>
>>> I'm not able to reproduce your issue, but I have a separate and possibly
>>> related one:
>>
>> I was able to reduce the issue and put it in the minimal sample:
>>
>> http://pastie.org/528957
>>
>> Trying to do File.read on ChangeLog is failing, however on 1.8.6 the
>> exact same command works flawlessly.
>
> It seems to only be on display:
>
> irb(main):002:0> b = File.read('ChangeLog')
> Errno::ENOMEM: Not enough space - <STDOUT>
> from
> C:/Users/Luis/Tools/Ruby/ruby-1.9.1-p129-i386-mingw32/lib/ruby/1.9.1/irb.rb:302:in
> `write'
>
> what about: b = File.read('ChangeLog'); nil
>
> I don't see any non-UTF-8 characters in the ChangeLog:
>
> $ iconv -t utf-8 < ChangeLog > ChangeLog2
> $ diff ChangeLog ChangeLog2
> $
>
> This seems to be a Windows-only issue though. ?Does adding a BOM to
> ChangeLog help?

No, but the new File.read_utf that newest Hoe has does.

The only thing is that lib/hoe.rb:360 remains using File.read,
manually changed to read_utf and worked.

At last:

http://pastie.org/531530

-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

From luislavena at gmail.com  Sun Jul  5 12:37:00 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Sun, 5 Jul 2009 13:37:00 -0300
Subject: [Rubygems-developers] Solving last stab of bugs for 1.3.5 release
Message-ID: <71166b3b0907050937v1ffc840fre2207a780734cabe@mail.gmail.com>

Hello guys,

I'm dealing with the last thing for 1.3.5 release:

http://rubyforge.org/tracker/?func=detail&atid=575&aid=26458&group_id=126
[#26458] gem bin scripts are broken if there are spaces in GEM_HOME
ENV variable on Windows

After further investigation of the commit that raised this, found two
things that originally justified the commit in the first place:

http://rubyforge.org/tracker/?group_id=126&atid=575&func=detail&aid=25734
[#25734] Gem::Ext::RakeBuilder fails under windows if ENV['rake'] not set

And other that duplicates what Gordon reported:
http://rubyforge.org/tracker/?func=detail&atid=575&aid=25935&group_id=126
[#25935] module installed by gem does not load when installation
directory path contains space

I did implemented a fix, and tests locally pass, but wanted to be sure
that is correct.

So, anyone knows of an existing gem that uses Rakefiles instead of
extconf for extensions?

Thank you.
-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

From noreply at rubyforge.org  Sun Jul  5 13:08:30 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun,  5 Jul 2009 13:08:30 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25935 ] module installed by
	gem does not load when installation directory path contains space
Message-ID: <20090705170830.8CAAB18580E4@rubyforge.org>

Bugs item #25935, was opened at 2009-05-16 10:40
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=25935&group_id=126

Category: RubyGems installer (setup.rb)
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: bazz bazz (bazz)
>Assigned to: Luis Lavena (luislavena)
Summary: module installed by gem does not load when installation directory path contains space

Initial Comment:
* The following is example.
I install RoR through gem. "rails" command does not work.
---
C:\>rails
C:/Program Files/ruby-1.8/bin/rails:19:in `load': no such file to load -- "C:/Pr
ogram Files/ruby-1.8/lib/ruby/gems/1.8/gems/rails-2.3.2/bin/rails" (LoadError)
        from C:/Program Files/ruby-1.8/bin/rails:19
---


* The investigation
line #386 in "rubygems.rb"
    File.join(spec.full_gem_path, spec.bindir, exec_name).sub(/.*\s.*/m, '"\&"')
      #=> Gem.bin_path returns "\C:/Program Files/ruby-1.8/lib/ruby/gems/1.8/gems/rails-2.3.2/bin/rails\"

line #19 in "rails" this file is installed by gem
	load Gem.bin_path('rails', 'rails', version)
	  #=> Load error


* Workaround
line #386 in "rubygems.rb"
    -File.join(spec.full_gem_path, spec.bindir, exec_name).sub(/.*\s.*/m, '"\&"')
    +File.join(spec.full_gem_path, spec.bindir, exec_name)

This way was confirmed only my environment.


* The following is my environment.
---
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.3
  - RUBY VERSION: 1.8.7 (2008-08-11 patchlevel 72) [i386-mswin32]
  - INSTALLATION DIRECTORY: C:/Program Files/ruby-1.8/lib/ruby/gems/1.8
  - RUBY EXECUTABLE: "C:/Program Files/ruby-1.8/bin/ruby.exe"
  - EXECUTABLE DIRECTORY: C:/Program Files/ruby-1.8/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mswin32-60
  - GEM PATHS:
     - C:/Program Files/ruby-1.8/lib/ruby/gems/1.8
     - C:/Documents and Settings/Administrator/.gem/ruby/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/
---



----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=25935&group_id=126

From noreply at rubyforge.org  Sun Jul  5 13:10:42 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun,  5 Jul 2009 13:10:42 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26199 ] zlib buffer error
	during gem update in v1.3.4 on 64-bit Windows Vista
Message-ID: <20090705171042.53B6C1678217@rubyforge.org>

Bugs item #26199, was opened at 2009-06-11 08:19
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26199&group_id=126

Category: `gem` commands (other)
Group: v1.3.x
>Status: Closed
>Resolution: Rejected
Priority: 3
Submitted By: Bob Holt (bobholt)
Assigned to: Luis Lavena (luislavena)
Summary: zlib buffer error during gem update in v1.3.4 on 64-bit Windows Vista

Initial Comment:
I have had this error in both my manual installation of Ruby and Rails as well as the InstantRails implementation. 

C:\ruby\rails_apps>gem update --debug rails
Exception `NameError' at C:/ruby/ruby/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:161 - uninitialized constant Gem::Commands::UpdateCommand
Exception `Gem::LoadError' at C:/ruby/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:826 - Could not find RubyGem test-unit (>= 0)

Updating installed gems
Exception `Gem::LoadError' at C:/ruby/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:826 - RubyGem version error: sources(0.0.1 not > 0.0.1)

Exception `Zlib::BufError' at C:/ruby/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:577 - buffer error
ERROR:  While executing gem ... (Zlib::BufError)
    buffer error
        C:/ruby/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:577:in `read'
        C:/ruby/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:577:in `gunzip'
        C:/ruby/ruby/lib/ruby/site_ruby/1.8/rubygems/remote_fetcher.rb:165:in `fetch_path'
        C:/ruby/ruby/lib/ruby/site_ruby/1.8/rubygems/spec_fetcher.rb:212:in `load_specs'
        C:/ruby/ruby/lib/ruby/site_ruby/1.8/rubygems/spec_fetcher.rb:191:in `list'
        C:/ruby/ruby/lib/ruby/site_ruby/1.8/rubygems/spec_fetcher.rb:187:in `each'
        C:/ruby/ruby/lib/ruby/site_ruby/1.8/rubygems/spec_fetcher.rb:187:in `list'
        C:/ruby/ruby/lib/ruby/site_ruby/1.8/rubygems/spec_fetcher.rb:122:in `find_matching'
        C:/ruby/ruby/lib/ruby/site_ruby/1.8/rubygems/commands/update_command.rb:169:in `which_to_update'
        C:/ruby/ruby/lib/ruby/site_ruby/1.8/rubygems/commands/update_command.rb:161:in `each'
        C:/ruby/ruby/lib/ruby/site_ruby/1.8/rubygems/commands/update_command.rb:161:in `which_to_update'
        C:/ruby/ruby/lib/ruby/site_ruby/1.8/rubygems/commands/update_command.rb:75:in `execute'
        C:/ruby/ruby/lib/ruby/site_ruby/1.8/rubygems/command.rb:257:in `invoke'
        C:/ruby/ruby/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:132:in `process_args'
        C:/ruby/ruby/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:102:in `run'
        C:/ruby/ruby/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:58:in `run'
        C:/ruby/ruby/bin/gem:21
		
C:\ruby\rails_apps>gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.4
  - RUBY VERSION: 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32]
  - INSTALLATION DIRECTORY: C:/ruby/ruby/lib/ruby/gems/1.8
  - RUBY EXECUTABLE: C:/ruby/ruby/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/ruby/ruby/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mswin32-60
  - GEM PATHS:
     - C:/ruby/ruby/lib/ruby/gems/1.8
     - C:/Users/bob/.gem/ruby/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/

----------------------------------------------------------------------

>Comment By: Luis Lavena (luislavena)
Date: 2009-07-05 14:10

Message:
This error is a Zlib and zlib1.dll issue with garbagecollect builds of Ruby.

Moving or migrating to MinGW based versions, as detailed here:

http://blog.mmediasys.com/2009/06/28/rubyinstaller-preview1-released/

Solves the problem.

Closing this since neither RubyGems nor One-Click Ruby Installer teams are responsible for the faulty binary extensions.

----------------------------------------------------------------------

Comment By: Bob Holt (bobholt)
Date: 2009-06-15 16:02

Message:
Luis,

Sorry for the delay - I switched to dual-booting Linux so
everything works right and haven't come back to Windows for
a while.

If I install everything under 32bit, it works. I'm running
late for an appointment, but I'll try 64 bit again later to
make sure it still breaks.

Bob

----------------------------------------------------------------------

Comment By: Luis Lavena (luislavena)
Date: 2009-06-11 18:37

Message:
Should not be related, but just for the sake of testing, can you open a 32bits prompt and try again on 186-26?

Run %windir%\SysWOW64\cmd.exe

Let me know how that ends.

----------------------------------------------------------------------

Comment By: Bob Holt (bobholt)
Date: 2009-06-11 09:18

Message:
Hi Luis,

I am hard-wired into a 30Mbps connection, and I uninstalled
and reinstalled 1.3.4 on 186-26 probably five different
times and tried updating a few different gems each time,
including some which had nothing to update. Each time I got
that same set of debug messages.

----------------------------------------------------------------------

Comment By: Luis Lavena (luislavena)
Date: 2009-06-11 09:09

Message:
Thank you Bob,

Maybe the Zlib error was triggered due a corrupt file download, since the Rails gems are not small and RubyGems uses open-uri which doesn't guarantee too much file integrity.

Have seen similar issues over slow network connections.

----------------------------------------------------------------------

Comment By: Bob Holt (bobholt)
Date: 2009-06-11 08:58

Message:
Just checked - rubygems 1.3.4 is fine under One-Click
Installer 186-27 (RC2). 

I rolled back to rubygems 1.3.3 under One-Click Installer
186-26 (Stable), and everything works fine there, too.

----------------------------------------------------------------------

Comment By: Luis Lavena (luislavena)
Date: 2009-06-11 08:38

Message:
Hello Bob,

Can you confirm this happens with One-Click Installer 186-27? (RC2).

Also, 64bits prompt do not play nice with 32bits processes, but I believe that is not the issue here.



----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26199&group_id=126

From noreply at rubyforge.org  Sun Jul  5 13:11:52 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun,  5 Jul 2009 13:11:52 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-24770 ] RubyGems 1.3.1
	doesn't install on MS VISTA Business
Message-ID: <20090705171152.170C61678297@rubyforge.org>

Bugs item #24770, was opened at 2009-03-22 21:11
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=24770&group_id=126

Category: RubyGems installer (setup.rb)
Group: None
>Status: Closed
>Resolution: Out of Date
Priority: 3
Submitted By: Luis V. Chavez (louiss)
Assigned to: Luis Lavena (luislavena)
Summary: RubyGems 1.3.1 doesn't install on MS VISTA Business

Initial Comment:
Hello
i want to report a big problem when i trying to install the rubygems from 1.2.0 to 1.3.1 
always when i install it and after when i want check it i get an error messages and not the normaly like gem -v
1.2.0
or 
1.3.1

i think this is a big problem because i reinstall my machine today and has update the windows and i have a frish installation of ruby and now i see this error.
unfortunately i can use rubyonrails on windows because rails need rubygems 1.3.1
to run the webapplications...


i hope you bring or fix the zip file from the webseite. thanksss.

----------------------------------------------------------------------

>Comment By: Luis Lavena (luislavena)
Date: 2009-07-05 14:11

Message:
Closing this due lack of feedback and error message.

I believe this is related to Zlib issues associated with garbagecollect binaries of Ruby.

----------------------------------------------------------------------

Comment By: Luis Lavena (luislavena)
Date: 2009-03-27 19:33

Message:
One-Click Installer has been in RC2 since 2 months.

That version has been quite stable without any major issue.

I think is time to upload a final 186-27.

In the Vista front, further details about the error are needed.


----------------------------------------------------------------------

Comment By: Luis V. Chavez (louiss)
Date: 2009-03-26 17:59

Message:
yes
in Vista i click always the option run as admin
when i want to start the ms-terminal and want to update the
rubygems

i will uninstall the ruby version and i want to try again to
install it with the actually rubygems..

----------------------------------------------------------------------

Comment By: Jirapong Nanta (jirapong)
Date: 2009-03-26 16:16

Message:
Did you try to run command-line with as admin?

----------------------------------------------------------------------

Comment By: Luis V. Chavez (louiss)
Date: 2009-03-23 05:14

Message:
additionally ..
i have tried to install it manually too..
this means i downloaded it and unpacked it and tried to
install it in the ms-terminal with root rights with ruby
setup.rb but it didnt help

----------------------------------------------------------------------

Comment By: Luis V. Chavez (louiss)
Date: 2009-03-23 05:12

Message:
hello
the problem occurs when i have installed  Ruby Version
1.8.6-26 Final Release	   2007-12-14 23:13
and try to update this version. i could update to the
rubygem version 1.2.0

but i found a currently solution for this error.
i installed the last ruby version for windows, unfortunately
it is a Release Candidate Version, 1.8.6-27 Release Candidate 2
and the problem is solved.

i dont know if i should use this Release.

----------------------------------------------------------------------

Comment By: Daniel Berger (djberg96)
Date: 2009-03-23 01:08

Message:
Was this caused by "gem update system"? Can you show us the error you received?

You can also try downloading rubygems and running "ruby setup.rb" manually. Does that work?

Regards,

Dan

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=24770&group_id=126

From noreply at rubyforge.org  Sun Jul  5 13:27:02 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun,  5 Jul 2009 13:27:02 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25935 ] module installed by
	gem does not load when installation directory path contains space
Message-ID: <20090705172702.457EA18580F4@rubyforge.org>

Bugs item #25935, was opened at 2009-05-16 10:40
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=25935&group_id=126

Category: RubyGems installer (setup.rb)
Group: v1.3.x
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: bazz bazz (bazz)
Assigned to: Luis Lavena (luislavena)
Summary: module installed by gem does not load when installation directory path contains space

Initial Comment:
* The following is example.
I install RoR through gem. "rails" command does not work.
---
C:\>rails
C:/Program Files/ruby-1.8/bin/rails:19:in `load': no such file to load -- "C:/Pr
ogram Files/ruby-1.8/lib/ruby/gems/1.8/gems/rails-2.3.2/bin/rails" (LoadError)
        from C:/Program Files/ruby-1.8/bin/rails:19
---


* The investigation
line #386 in "rubygems.rb"
    File.join(spec.full_gem_path, spec.bindir, exec_name).sub(/.*\s.*/m, '"\&"')
      #=> Gem.bin_path returns "\C:/Program Files/ruby-1.8/lib/ruby/gems/1.8/gems/rails-2.3.2/bin/rails\"

line #19 in "rails" this file is installed by gem
	load Gem.bin_path('rails', 'rails', version)
	  #=> Load error


* Workaround
line #386 in "rubygems.rb"
    -File.join(spec.full_gem_path, spec.bindir, exec_name).sub(/.*\s.*/m, '"\&"')
    +File.join(spec.full_gem_path, spec.bindir, exec_name)

This way was confirmed only my environment.


* The following is my environment.
---
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.3
  - RUBY VERSION: 1.8.7 (2008-08-11 patchlevel 72) [i386-mswin32]
  - INSTALLATION DIRECTORY: C:/Program Files/ruby-1.8/lib/ruby/gems/1.8
  - RUBY EXECUTABLE: "C:/Program Files/ruby-1.8/bin/ruby.exe"
  - EXECUTABLE DIRECTORY: C:/Program Files/ruby-1.8/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mswin32-60
  - GEM PATHS:
     - C:/Program Files/ruby-1.8/lib/ruby/gems/1.8
     - C:/Documents and Settings/Administrator/.gem/ruby/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/
---



----------------------------------------------------------------------

>Comment By: Luis Lavena (luislavena)
Date: 2009-07-05 14:27

Message:
Fix applied in revision 2272.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=25935&group_id=126

From noreply at rubyforge.org  Sun Jul  5 13:27:31 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun,  5 Jul 2009 13:27:31 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26458 ] gem bin scripts are
	broken if there are spaces in GEM_HOME ENV variable on Windows
Message-ID: <20090705172731.C7B4E18580F4@rubyforge.org>

Bugs item #26458, was opened at 2009-06-29 20:15
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26458&group_id=126

Category: `gem install` command
Group: v1.3.x
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: Eric Hodel (drbrain)
Assigned to: Luis Lavena (luislavena)
Summary: gem bin scripts are broken if there are spaces in GEM_HOME ENV variable on Windows

Initial Comment:
If you try to run a bin script created by rubygems, ruby is unable to
load the file inside the gem's bin dir.  This is because Gem.bin_path
wraps paths with spaces in quotes.  This was added for #25734.
Gem.bin_path was modified to work on the Windows command line, but is
broken when used with Kernel#load

C:\scripts\repo\rubygems>pik list
C:/Documents and Settings/gthiesfeld/.gem/ruby/1.8/bin/pik:19:in
`load': no such file to load -- "C:/documents and
settings/gthiesfeld/.gem/ruby/1.8/gems/pik-0.0.2/bin/pik" (LoadError)
       from C:/Documents and Settings/gthiesfeld/.gem/ruby/1.8/bin/pik:19

C:\scripts\repo\rubygems>cat "c:\Documents and
Settings\gthiesfeld\.gem\ruby\1.8\bin\pik" | grep -n load
19:load Gem.bin_path('pik', 'pik', version)

C:\scripts\repo\rubygems>svn blame lib\rubygems.rb | grep -n -A 2 -B 2 2183
384-  2064    drbrain     end
385-  2064    drbrain
386:  2183      raggi     File.join(spec.full_gem_path, spec.bindir,
exec_name).sub(/.*\s.*/m, '"\&"')
387-  2064    drbrain   end
388-  2064    drbrain

C:\scripts\repo\rubygems>svn log | grep -A 4 2183
r2183 | raggi | 2009-05-01 04:56:11 -0500 (Fri, 01 May 2009) | 2 lines

Gem.bin_path now escapes paths with spaces. Thanks to Luis Lavena in #25734.


----------------------------------------------------------------------

>Comment By: Luis Lavena (luislavena)
Date: 2009-07-05 14:27

Message:
Fix applied in revision 2272.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26458&group_id=126

From luislavena at gmail.com  Sun Jul  5 14:58:55 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Sun, 5 Jul 2009 15:58:55 -0300
Subject: [Rubygems-developers] Bug in Gem.bin_path - gem bin scripts are
	broken if there are spaces in GEM_HOME env. variable (on Windows)
In-Reply-To: <5A6A9553-4E01-4592-BF82-4187D1A2AA00@segment7.net>
References: <e9ece6840906290730s31e7fb21oa18a43697b7ec805@mail.gmail.com> 
	<5A6A9553-4E01-4592-BF82-4187D1A2AA00@segment7.net>
Message-ID: <71166b3b0907051158j76c87861nb3b7543723a18562@mail.gmail.com>

On Mon, Jun 29, 2009 at 8:16 PM, Eric Hodel<drbrain at segment7.net> wrote:
> On Jun 29, 2009, at 07:30, Gordon Thiesfeld wrote:
>
>> First of all, I apologize for not submitting this on the rubyforge
>> tracker. ?I can't log in to rubyforge from work because of a proxy,
>> and anonymous submissions are not allowed. ?I can submit it this
>> evening, if need be.
>
> I opened a ticket for you and assigned it to Luis.

Thank you Eric,

A commit for this has been made in 1_3 branch.

Should I backport it to master?
-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

From noreply at rubyforge.org  Mon Jul  6 13:59:32 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Mon,  6 Jul 2009 13:59:32 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25935 ] module installed by
	gem does not load when installation directory path contains space
Message-ID: <20090706175933.6E4461D787E5@rubyforge.org>

Bugs item #25935, was opened at 2009-05-16 22:40
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=25935&group_id=126

Category: RubyGems installer (setup.rb)
Group: v1.3.x
Status: Closed
Resolution: Accepted
Priority: 3
Submitted By: bazz bazz (bazz)
Assigned to: Luis Lavena (luislavena)
Summary: module installed by gem does not load when installation directory path contains space

Initial Comment:
* The following is example.
I install RoR through gem. "rails" command does not work.
---
C:\>rails
C:/Program Files/ruby-1.8/bin/rails:19:in `load': no such file to load -- "C:/Pr
ogram Files/ruby-1.8/lib/ruby/gems/1.8/gems/rails-2.3.2/bin/rails" (LoadError)
        from C:/Program Files/ruby-1.8/bin/rails:19
---


* The investigation
line #386 in "rubygems.rb"
    File.join(spec.full_gem_path, spec.bindir, exec_name).sub(/.*\s.*/m, '"\&"')
      #=> Gem.bin_path returns "\C:/Program Files/ruby-1.8/lib/ruby/gems/1.8/gems/rails-2.3.2/bin/rails\"

line #19 in "rails" this file is installed by gem
	load Gem.bin_path('rails', 'rails', version)
	  #=> Load error


* Workaround
line #386 in "rubygems.rb"
    -File.join(spec.full_gem_path, spec.bindir, exec_name).sub(/.*\s.*/m, '"\&"')
    +File.join(spec.full_gem_path, spec.bindir, exec_name)

This way was confirmed only my environment.


* The following is my environment.
---
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.3
  - RUBY VERSION: 1.8.7 (2008-08-11 patchlevel 72) [i386-mswin32]
  - INSTALLATION DIRECTORY: C:/Program Files/ruby-1.8/lib/ruby/gems/1.8
  - RUBY EXECUTABLE: "C:/Program Files/ruby-1.8/bin/ruby.exe"
  - EXECUTABLE DIRECTORY: C:/Program Files/ruby-1.8/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mswin32-60
  - GEM PATHS:
     - C:/Program Files/ruby-1.8/lib/ruby/gems/1.8
     - C:/Documents and Settings/Administrator/.gem/ruby/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/
---



----------------------------------------------------------------------

>Comment By: bazz bazz (bazz)
Date: 2009-07-07 02:59

Message:
Many thanks.


----------------------------------------------------------------------

Comment By: Luis Lavena (luislavena)
Date: 2009-07-06 02:27

Message:
Fix applied in revision 2272.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=25935&group_id=126

From noreply at rubyforge.org  Tue Jul  7 00:08:45 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  7 Jul 2009 00:08:45 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26540 ] 1.3.4 with ruby1.9 on
	Ubuntu 8.04 AMD64 fails
Message-ID: <20090707040845.3751D18580F4@rubyforge.org>

Bugs item #26540, was opened at 2009-07-07 04:08
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26540&group_id=126

Category: RubyGems installer (setup.rb)
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Nathan Zook (anoldhacker)
Assigned to: Nobody (None)
Summary: 1.3.4 with ruby1.9 on Ubuntu 8.04 AMD64 fails

Initial Comment:
:~/work/rubygems-1.3.4# ruby1.9 setup.rb 
Installing RubyGems
Installing gem executable
Removing old source_cache files
Removing old RubyGems RDoc and ri
Installing rubygems-1.3.4 ri into /usr/lib/ruby1.9/gems/1.9.0/doc/rubygems-1.3.4/ri
ERROR:  While executing gem ... (ArgumentError)
    invalid mbstring sequence

# This is from the Universe repository
~/work/rubygems-1.3.4# ruby --version
ruby 1.9.0 (2007-12-25 revision 14709) [x86_64-linux]

~/work/rubygems-1.3.4# ruby1.9 -v setup.rb >output 2>&1

# output.gz attached

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26540&group_id=126

From noreply at rubyforge.org  Tue Jul  7 00:11:33 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  7 Jul 2009 00:11:33 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26540 ] 1.3.4 with ruby1.9 on
	Ubuntu 8.04 AMD64 fails
Message-ID: <20090707041133.172C818580F4@rubyforge.org>

Bugs item #26540, was opened at 2009-07-07 01:08
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26540&group_id=126

Category: RubyGems installer (setup.rb)
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Nathan Zook (anoldhacker)
Assigned to: Nobody (None)
Summary: 1.3.4 with ruby1.9 on Ubuntu 8.04 AMD64 fails

Initial Comment:
:~/work/rubygems-1.3.4# ruby1.9 setup.rb 
Installing RubyGems
Installing gem executable
Removing old source_cache files
Removing old RubyGems RDoc and ri
Installing rubygems-1.3.4 ri into /usr/lib/ruby1.9/gems/1.9.0/doc/rubygems-1.3.4/ri
ERROR:  While executing gem ... (ArgumentError)
    invalid mbstring sequence

# This is from the Universe repository
~/work/rubygems-1.3.4# ruby --version
ruby 1.9.0 (2007-12-25 revision 14709) [x86_64-linux]

~/work/rubygems-1.3.4# ruby1.9 -v setup.rb >output 2>&1

# output.gz attached

----------------------------------------------------------------------

>Comment By: Luis Lavena (luislavena)
Date: 2009-07-07 01:11

Message:
I would say that you're trying to install an old, unstable version of Ruby 1.9 (1.9.0)

The stable and recommended version for 1.9 line is 1.9.1-p129.

I would recommend installing 1.9.1 at least, but leave this open for other to suggest better solutions.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26540&group_id=126

From noreply at rubyforge.org  Tue Jul  7 12:59:26 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  7 Jul 2009 12:59:26 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25509 ] exception using new
	generate_index in 1.3.2
Message-ID: <20090707165927.0B6FA19785A7@rubyforge.org>

Bugs item #25509, was opened at 2009-04-16 15:15
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=25509&group_id=126

Category: `gem` commands (other)
Group: v1.3.x
Status: Open
Resolution: Accepted
Priority: 3
Submitted By: Johnathan Conley (jconley)
Assigned to: Eric Hodel (drbrain)
Summary: exception using new generate_index in 1.3.2

Initial Comment:

After upgrading to 1.3.2, I wiped out my old indexes, and build a full index from scratch. Everything worked fine... but afterwards I rsyned with the upstream server, one new gem was available... and then I ran generate_index with the --update option and received this error...


receiving file list ... done
Onion-0.0.2.gem

sent 240 bytes  received 623761 bytes  83200.13 bytes/sec
total size is 4929983101  speedup is 7900.60

$ gem generate_index --no-legacy --update -d /home/mirror/www --backtrace
Loading 1 gems from /home/mirror/www
.
Loaded all gems
loaded: 0.004s
Generating Marshal quick index gemspecs for 1 gems
.
Complete
Generated Marshal quick index gemspecs: 0.001s
ERROR:  While executing gem ... (NoMethodError)
    undefined method `<=>' for nil:NilClass
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in `<=>'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in `sort'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in `update_specs_index'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:656:in `update_index'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems.rb:966:in `time'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:655:in `update_index'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/commands/generate_index_command.rb:125:in `execute'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command.rb:254:in `invoke'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:132:in `process_args'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:102:in `run'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:58:in `run'
	/opt/ruby/bin/gem:21


Below is the output from the first full index build... likely won't help since it completed without errors.

Complete
Generated Marshal quick index gemspecs: 11.859s
Generating specs index
WARNING:  Skipping invalid platform in gem: win32-api-1.0.4-x86-mswin32-60
Generated specs index: 0.483s
Generating latest specs index
Generated latest specs index: 0.094s
Generating prerelease specs index
Generated prerelease specs index: 0.000s
Compressing indicies
Compressed indicies: 0.068s


----------------------------------------------------------------------

>Comment By: Johnathan Conley (jconley)
Date: 2009-07-07 11:59

Message:
still happening in 1.3.4, now at indexer.rb:704:in `<=>'

----------------------------------------------------------------------

Comment By: Johnathan Conley (jconley)
Date: 2009-05-07 16:03

Message:
yes, still happening... same error and line

----------------------------------------------------------------------

Comment By: Daniel Berger (djberg96)
Date: 2009-05-05 22:39

Message:
Still happening with 1.3.3?

----------------------------------------------------------------------

Comment By: Johnathan Conley (jconley)
Date: 2009-04-16 19:24

Message:

Here is my latest run with -V

$ ./mirror-rubygems.sh
receiving file list ... done
./
gem_tools-0.2.0.gem
graph-1.1.0.gem
hoe-1.12.2.gem
mingle-macro-development-toolkit-1.2.gem
provisional-1.2.5.gem
rforce-0.3.gem
unicorn-0.5.2.gem

sent 378 bytes  received 796293 bytes  75873.43 bytes/sec
total size is 4930164349  speedup is 6188.46
Loading 8 gems from /home/mirror/www
1/8: mingle-macro-development-toolkit-1.2
2/8: hoe-1.12.2
3/8: graph-1.1.0
4/8: gem_tools-0.2.0
5/8: unicorn-0.5.2
6/8: Onion-0.0.2
7/8: provisional-1.2.5
8/8: rforce-0.3
Loaded all gems
loaded: 0.097s
Generating Marshal quick index gemspecs for 8 gems
1/8: gem_tools-0.2.0
2/8: provisional-1.2.5
3/8: graph-1.1.0
4/8: rforce-0.3
5/8: hoe-1.12.2
6/8: unicorn-0.5.2
7/8: Onion-0.0.2
8/8: mingle-macro-development-toolkit-1.2
Complete
Generated Marshal quick index gemspecs: 0.030s
ERROR:  While executing gem ... (NoMethodError)
    undefined method `<=>' for nil:NilClass
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in
`<=>'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in
`sort'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in
`update_specs_index'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:656:in
`update_index'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems.rb:966:in
`time'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:655:in
`update_index'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/commands/generate_index_command.rb:125:in
`execute'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command.rb:254:in
`invoke'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:132:in
`process_args'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:102:in
`run'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:58:in
`run'
        /opt/ruby/bin/gem:21


----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2009-04-16 15:40

Message:
Can you run with -V as well?

gem generate_index --no-legacy --update -d /home/mirror/www --backtrace -V

This should give the gem that's causing the problem.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=25509&group_id=126

From drbrain at segment7.net  Tue Jul  7 20:23:11 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Tue, 7 Jul 2009 17:23:11 -0700
Subject: [Rubygems-developers] Bug in Gem.bin_path - gem bin scripts are
	broken if there are spaces in GEM_HOME env. variable (on Windows)
In-Reply-To: <71166b3b0907051158j76c87861nb3b7543723a18562@mail.gmail.com>
References: <e9ece6840906290730s31e7fb21oa18a43697b7ec805@mail.gmail.com>
	<5A6A9553-4E01-4592-BF82-4187D1A2AA00@segment7.net>
	<71166b3b0907051158j76c87861nb3b7543723a18562@mail.gmail.com>
Message-ID: <DE43FDCE-F3A7-413A-BF1C-1B5FD6A80D8C@segment7.net>

On Jul 5, 2009, at 11:58, Luis Lavena wrote:
> On Mon, Jun 29, 2009 at 8:16 PM, Eric Hodel<drbrain at segment7.net>  
> wrote:
>> On Jun 29, 2009, at 07:30, Gordon Thiesfeld wrote:
>>
>>> First of all, I apologize for not submitting this on the rubyforge
>>> tracker.  I can't log in to rubyforge from work because of a proxy,
>>> and anonymous submissions are not allowed.  I can submit it this
>>> evening, if need be.
>>
>> I opened a ticket for you and assigned it to Luis.
>
> Thank you Eric,
>
> A commit for this has been made in 1_3 branch.
>
> Should I backport it to master?

Yes please.  You can probably just do a merge commit, something like

cd trunk; svn merge -rBEFORE:AFTER ../branches/1_3 .

From noreply at rubyforge.org  Tue Jul  7 20:30:16 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  7 Jul 2009 20:30:16 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25509 ] exception using new
	generate_index in 1.3.2
Message-ID: <20090708003016.19C0A185811A@rubyforge.org>

Bugs item #25509, was opened at 2009-04-16 13:15
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=25509&group_id=126

Category: `gem` commands (other)
Group: v1.3.x
Status: Open
Resolution: Accepted
Priority: 3
Submitted By: Johnathan Conley (jconley)
Assigned to: Eric Hodel (drbrain)
Summary: exception using new generate_index in 1.3.2

Initial Comment:

After upgrading to 1.3.2, I wiped out my old indexes, and build a full index from scratch. Everything worked fine... but afterwards I rsyned with the upstream server, one new gem was available... and then I ran generate_index with the --update option and received this error...


receiving file list ... done
Onion-0.0.2.gem

sent 240 bytes  received 623761 bytes  83200.13 bytes/sec
total size is 4929983101  speedup is 7900.60

$ gem generate_index --no-legacy --update -d /home/mirror/www --backtrace
Loading 1 gems from /home/mirror/www
.
Loaded all gems
loaded: 0.004s
Generating Marshal quick index gemspecs for 1 gems
.
Complete
Generated Marshal quick index gemspecs: 0.001s
ERROR:  While executing gem ... (NoMethodError)
    undefined method `<=>' for nil:NilClass
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in `<=>'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in `sort'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in `update_specs_index'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:656:in `update_index'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems.rb:966:in `time'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:655:in `update_index'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/commands/generate_index_command.rb:125:in `execute'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command.rb:254:in `invoke'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:132:in `process_args'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:102:in `run'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:58:in `run'
	/opt/ruby/bin/gem:21


Below is the output from the first full index build... likely won't help since it completed without errors.

Complete
Generated Marshal quick index gemspecs: 11.859s
Generating specs index
WARNING:  Skipping invalid platform in gem: win32-api-1.0.4-x86-mswin32-60
Generated specs index: 0.483s
Generating latest specs index
Generated latest specs index: 0.094s
Generating prerelease specs index
Generated prerelease specs index: 0.000s
Compressing indicies
Compressed indicies: 0.068s


----------------------------------------------------------------------

>Comment By: Eric Hodel (drbrain)
Date: 2009-07-07 17:30

Message:
What is the output of `gem spec Onion-0.0.2.gem`

Either name, version or platform appear to be nil, or your specs file is corrupt on input.

Can you attach Onion-0.0.2.gem to this ticket?

----------------------------------------------------------------------

Comment By: Johnathan Conley (jconley)
Date: 2009-07-07 09:59

Message:
still happening in 1.3.4, now at indexer.rb:704:in `<=>'

----------------------------------------------------------------------

Comment By: Johnathan Conley (jconley)
Date: 2009-05-07 14:03

Message:
yes, still happening... same error and line

----------------------------------------------------------------------

Comment By: Daniel Berger (djberg96)
Date: 2009-05-05 20:39

Message:
Still happening with 1.3.3?

----------------------------------------------------------------------

Comment By: Johnathan Conley (jconley)
Date: 2009-04-16 17:24

Message:

Here is my latest run with -V

$ ./mirror-rubygems.sh
receiving file list ... done
./
gem_tools-0.2.0.gem
graph-1.1.0.gem
hoe-1.12.2.gem
mingle-macro-development-toolkit-1.2.gem
provisional-1.2.5.gem
rforce-0.3.gem
unicorn-0.5.2.gem

sent 378 bytes  received 796293 bytes  75873.43 bytes/sec
total size is 4930164349  speedup is 6188.46
Loading 8 gems from /home/mirror/www
1/8: mingle-macro-development-toolkit-1.2
2/8: hoe-1.12.2
3/8: graph-1.1.0
4/8: gem_tools-0.2.0
5/8: unicorn-0.5.2
6/8: Onion-0.0.2
7/8: provisional-1.2.5
8/8: rforce-0.3
Loaded all gems
loaded: 0.097s
Generating Marshal quick index gemspecs for 8 gems
1/8: gem_tools-0.2.0
2/8: provisional-1.2.5
3/8: graph-1.1.0
4/8: rforce-0.3
5/8: hoe-1.12.2
6/8: unicorn-0.5.2
7/8: Onion-0.0.2
8/8: mingle-macro-development-toolkit-1.2
Complete
Generated Marshal quick index gemspecs: 0.030s
ERROR:  While executing gem ... (NoMethodError)
    undefined method `<=>' for nil:NilClass
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in
`<=>'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in
`sort'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in
`update_specs_index'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:656:in
`update_index'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems.rb:966:in
`time'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:655:in
`update_index'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/commands/generate_index_command.rb:125:in
`execute'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command.rb:254:in
`invoke'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:132:in
`process_args'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:102:in
`run'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:58:in
`run'
        /opt/ruby/bin/gem:21


----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2009-04-16 13:40

Message:
Can you run with -V as well?

gem generate_index --no-legacy --update -d /home/mirror/www --backtrace -V

This should give the gem that's causing the problem.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=25509&group_id=126

From drbrain at segment7.net  Tue Jul  7 20:46:51 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Tue, 7 Jul 2009 17:46:51 -0700
Subject: [Rubygems-developers] Solving last stab of bugs for 1.3.5
	release
In-Reply-To: <71166b3b0907050937v1ffc840fre2207a780734cabe@mail.gmail.com>
References: <71166b3b0907050937v1ffc840fre2207a780734cabe@mail.gmail.com>
Message-ID: <ABD081DF-9212-436D-B966-B5439032A0BD@segment7.net>

On Jul 5, 2009, at 09:37, Luis Lavena wrote:
> Hello guys,
>
> I'm dealing with the last thing for 1.3.5 release:
>
> http://rubyforge.org/tracker/?func=detail&atid=575&aid=26458&group_id=126
> [#26458] gem bin scripts are broken if there are spaces in GEM_HOME
> ENV variable on Windows
>
> After further investigation of the commit that raised this, found two
> things that originally justified the commit in the first place:
>
> http://rubyforge.org/tracker/?group_id=126&atid=575&func=detail&aid=25734
> [#25734] Gem::Ext::RakeBuilder fails under windows if ENV['rake']  
> not set
>
> And other that duplicates what Gordon reported:
> http://rubyforge.org/tracker/?func=detail&atid=575&aid=25935&group_id=126
> [#25935] module installed by gem does not load when installation
> directory path contains space
>
> I did implemented a fix, and tests locally pass, but wanted to be sure
> that is correct.
>
> So, anyone knows of an existing gem that uses Rakefiles instead of
> extconf for extensions?

I can't think of any offhand.  Can you post your change?

From luislavena at gmail.com  Tue Jul  7 21:10:43 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Tue, 7 Jul 2009 22:10:43 -0300
Subject: [Rubygems-developers] Solving last stab of bugs for 1.3.5
	release
In-Reply-To: <ABD081DF-9212-436D-B966-B5439032A0BD@segment7.net>
References: <71166b3b0907050937v1ffc840fre2207a780734cabe@mail.gmail.com> 
	<ABD081DF-9212-436D-B966-B5439032A0BD@segment7.net>
Message-ID: <71166b3b0907071810m5a4b2273t6101453863302ff5@mail.gmail.com>

On Tue, Jul 7, 2009 at 9:46 PM, Eric Hodel<drbrain at segment7.net> wrote:
> On Jul 5, 2009, at 09:37, Luis Lavena wrote:
>>
>> Hello guys,
>>
>> I'm dealing with the last thing for 1.3.5 release:
>>
>> http://rubyforge.org/tracker/?func=detail&atid=575&aid=26458&group_id=126
>> [#26458] gem bin scripts are broken if there are spaces in GEM_HOME
>> ENV variable on Windows
>>
>> After further investigation of the commit that raised this, found two
>> things that originally justified the commit in the first place:
>>
>> http://rubyforge.org/tracker/?group_id=126&atid=575&func=detail&aid=25734
>> [#25734] Gem::Ext::RakeBuilder fails under windows if ENV['rake'] not set
>>
>> And other that duplicates what Gordon reported:
>> http://rubyforge.org/tracker/?func=detail&atid=575&aid=25935&group_id=126
>> [#25935] module installed by gem does not load when installation
>> directory path contains space
>>
>> I did implemented a fix, and tests locally pass, but wanted to be sure
>> that is correct.
>>
>> So, anyone knows of an existing gem that uses Rakefiles instead of
>> extconf for extensions?
>
> I can't think of any offhand. ?Can you post your change?

Change is already committed to 1_3 branch, going to merge it back to trunk.

Tested locally with Ruby installed on C:\Program Files\Ruby, and it worked.

Also gems located in C:\Documents and Settings, and worked too. So
guess the fix worked.
-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

From drbrain at segment7.net  Tue Jul  7 22:09:51 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Tue, 7 Jul 2009 19:09:51 -0700
Subject: [Rubygems-developers] 1.3.5 showstoppers?
Message-ID: <C27C644B-925B-427E-91E9-23CC5C287DA6@segment7.net>

I will release what's on branches/1_3 as 1.3.5 tomorrow barring any  
other showstoppers appearing.

From luislavena at gmail.com  Wed Jul  8 07:26:45 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Wed, 8 Jul 2009 08:26:45 -0300
Subject: [Rubygems-developers] 1.3.5 showstoppers?
In-Reply-To: <C27C644B-925B-427E-91E9-23CC5C287DA6@segment7.net>
References: <C27C644B-925B-427E-91E9-23CC5C287DA6@segment7.net>
Message-ID: <71166b3b0907080426tc02620p108192da9346300a@mail.gmail.com>

On Tue, Jul 7, 2009 at 11:09 PM, Eric Hodel<drbrain at segment7.net> wrote:
> I will release what's on branches/1_3 as 1.3.5 tomorrow barring any other
> showstoppers appearing.

I think we are cool with latest changes I've introduced.

Going now to backport 1_3 commits to trunk.
-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

From luislavena at gmail.com  Wed Jul  8 08:55:21 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Wed, 8 Jul 2009 09:55:21 -0300
Subject: [Rubygems-developers] Bug in Gem.bin_path - gem bin scripts are
	broken if there are spaces in GEM_HOME env. variable (on Windows)
In-Reply-To: <DE43FDCE-F3A7-413A-BF1C-1B5FD6A80D8C@segment7.net>
References: <e9ece6840906290730s31e7fb21oa18a43697b7ec805@mail.gmail.com> 
	<5A6A9553-4E01-4592-BF82-4187D1A2AA00@segment7.net>
	<71166b3b0907051158j76c87861nb3b7543723a18562@mail.gmail.com> 
	<DE43FDCE-F3A7-413A-BF1C-1B5FD6A80D8C@segment7.net>
Message-ID: <71166b3b0907080555y5e628df3of55df5dd8d256293@mail.gmail.com>

On Tue, Jul 7, 2009 at 9:23 PM, Eric Hodel<drbrain at segment7.net> wrote:
>
> Yes please. ?You can probably just do a merge commit, something like
>
> cd trunk; svn merge -rBEFORE:AFTER ../branches/1_3 .

Done, revision 2273.

Please, go ahead, you have green light from here to release 1_3 branch
as version 1.3.5!

Thank you!
-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

From noreply at rubyforge.org  Thu Jul  9 04:52:30 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu,  9 Jul 2009 04:52:30 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26567 ] Using gems including
	option what is '--debug ', we watch this err what is 'NameError'.
Message-ID: <20090709085230.8D6FA185811A@rubyforge.org>

Bugs item #26567, was opened at 2009-07-09 08:52
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26567&group_id=126

Category: other
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: K Y (kohei)
Assigned to: Nobody (None)
Summary: Using gems including option what is '--debug ',we watch this err what is 'NameError'. 

Initial Comment:
Using gems including option what is '--debug ',
we watch this err what is 'NameError'. 



Example

$gem install rails --debug

=>
Exception `NameError' at /opt/local/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:134 - uninitialized constant Gem::Commands::InstallCommand

This err is no smart!

For info, part of my RubyGems Environment:
  - RUBYGEMS VERSION: 1.2.0 -- 1.3.4
  - Ruby 1.8.7 (2009-04-08 patchlevel 160) [powerpc-darwin8]
  - INSTALLATION DIRECTORY /opt/local/lib/ruby/gems
  - RUBY EXECUTABLE: /opt/local/bin

-----------


Do Debug Quickly!

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26567&group_id=126

From noreply at rubyforge.org  Thu Jul  9 19:20:38 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu,  9 Jul 2009 19:20:38 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26567 ] Using gems including
	option what is '--debug ', we watch this err what is 'NameError'.
Message-ID: <20090709232039.0B6A81779931@rubyforge.org>

Bugs item #26567, was opened at 2009-07-09 01:52
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26567&group_id=126

Category: other
>Group: v1.3.x
>Status: Closed
>Resolution: Rejected
Priority: 3
Submitted By: K Y (kohei)
>Assigned to: Eric Hodel (drbrain)
Summary: Using gems including option what is '--debug ',we watch this err what is 'NameError'. 

Initial Comment:
Using gems including option what is '--debug ',
we watch this err what is 'NameError'. 



Example

$gem install rails --debug

=>
Exception `NameError' at /opt/local/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:134 - uninitialized constant Gem::Commands::InstallCommand

This err is no smart!

For info, part of my RubyGems Environment:
  - RUBYGEMS VERSION: 1.2.0 -- 1.3.4
  - Ruby 1.8.7 (2009-04-08 patchlevel 160) [powerpc-darwin8]
  - INSTALLATION DIRECTORY /opt/local/lib/ruby/gems
  - RUBY EXECUTABLE: /opt/local/bin

-----------


Do Debug Quickly!

----------------------------------------------------------------------

>Comment By: Eric Hodel (drbrain)
Date: 2009-07-09 16:20

Message:
This error is ok, it arrises from $DEBUG = true

See Gem::CommandManager#load_and_instantiate which rescues the exception and requires the correct file (lazy loading).

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26567&group_id=126

From noreply at rubyforge.org  Sun Jul 12 19:52:17 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun, 12 Jul 2009 19:52:17 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25509 ] exception using new
	generate_index in 1.3.2
Message-ID: <20090712235218.2E74A18581DD@rubyforge.org>

Bugs item #25509, was opened at 2009-04-16 15:15
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=25509&group_id=126

Category: `gem` commands (other)
Group: v1.3.x
Status: Open
Resolution: Accepted
Priority: 3
Submitted By: Johnathan Conley (jconley)
Assigned to: Eric Hodel (drbrain)
Summary: exception using new generate_index in 1.3.2

Initial Comment:

After upgrading to 1.3.2, I wiped out my old indexes, and build a full index from scratch. Everything worked fine... but afterwards I rsyned with the upstream server, one new gem was available... and then I ran generate_index with the --update option and received this error...


receiving file list ... done
Onion-0.0.2.gem

sent 240 bytes  received 623761 bytes  83200.13 bytes/sec
total size is 4929983101  speedup is 7900.60

$ gem generate_index --no-legacy --update -d /home/mirror/www --backtrace
Loading 1 gems from /home/mirror/www
.
Loaded all gems
loaded: 0.004s
Generating Marshal quick index gemspecs for 1 gems
.
Complete
Generated Marshal quick index gemspecs: 0.001s
ERROR:  While executing gem ... (NoMethodError)
    undefined method `<=>' for nil:NilClass
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in `<=>'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in `sort'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in `update_specs_index'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:656:in `update_index'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems.rb:966:in `time'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:655:in `update_index'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/commands/generate_index_command.rb:125:in `execute'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command.rb:254:in `invoke'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:132:in `process_args'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:102:in `run'
	/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:58:in `run'
	/opt/ruby/bin/gem:21


Below is the output from the first full index build... likely won't help since it completed without errors.

Complete
Generated Marshal quick index gemspecs: 11.859s
Generating specs index
WARNING:  Skipping invalid platform in gem: win32-api-1.0.4-x86-mswin32-60
Generated specs index: 0.483s
Generating latest specs index
Generated latest specs index: 0.094s
Generating prerelease specs index
Generated prerelease specs index: 0.000s
Compressing indicies
Compressed indicies: 0.068s


----------------------------------------------------------------------

>Comment By: Johnathan Conley (jconley)
Date: 2009-07-12 18:52

Message:
It's not specific to that gem... as long as any new gem is
added to the repo before performing a reindex with --update.
As you'll note in a subsequent post, there are a totally
different set of updated gems pulled before the reindex.

This should be reproducible as I'm replicating the master
rubyforge gems repository:
rsync -av --del --exclude-from=rubygems.excludes
rsync://master.mirror.rubyforge.org/gems/ $GEM_MIRROR_BASE/gems 

rubygems.excludes includes a few gems which had spec
problems affecting other bugs in the past:
win32-api-1.0.4-x86-mswin32-60.gem
facets-2005.10.10.gem
facets-2005.10.11.gem
facets-2005.10.15.gem
facets-2005.10.30.gem

I am running generate_index with the following params:
gem generate_index --no-legacy -d $GEM_MIRROR_BASE
--backtrace -V


----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2009-07-07 19:30

Message:
What is the output of `gem spec Onion-0.0.2.gem`

Either name, version or platform appear to be nil, or your specs file is corrupt on input.

Can you attach Onion-0.0.2.gem to this ticket?

----------------------------------------------------------------------

Comment By: Johnathan Conley (jconley)
Date: 2009-07-07 11:59

Message:
still happening in 1.3.4, now at indexer.rb:704:in `<=>'

----------------------------------------------------------------------

Comment By: Johnathan Conley (jconley)
Date: 2009-05-07 16:03

Message:
yes, still happening... same error and line

----------------------------------------------------------------------

Comment By: Daniel Berger (djberg96)
Date: 2009-05-05 22:39

Message:
Still happening with 1.3.3?

----------------------------------------------------------------------

Comment By: Johnathan Conley (jconley)
Date: 2009-04-16 19:24

Message:

Here is my latest run with -V

$ ./mirror-rubygems.sh
receiving file list ... done
./
gem_tools-0.2.0.gem
graph-1.1.0.gem
hoe-1.12.2.gem
mingle-macro-development-toolkit-1.2.gem
provisional-1.2.5.gem
rforce-0.3.gem
unicorn-0.5.2.gem

sent 378 bytes  received 796293 bytes  75873.43 bytes/sec
total size is 4930164349  speedup is 6188.46
Loading 8 gems from /home/mirror/www
1/8: mingle-macro-development-toolkit-1.2
2/8: hoe-1.12.2
3/8: graph-1.1.0
4/8: gem_tools-0.2.0
5/8: unicorn-0.5.2
6/8: Onion-0.0.2
7/8: provisional-1.2.5
8/8: rforce-0.3
Loaded all gems
loaded: 0.097s
Generating Marshal quick index gemspecs for 8 gems
1/8: gem_tools-0.2.0
2/8: provisional-1.2.5
3/8: graph-1.1.0
4/8: rforce-0.3
5/8: hoe-1.12.2
6/8: unicorn-0.5.2
7/8: Onion-0.0.2
8/8: mingle-macro-development-toolkit-1.2
Complete
Generated Marshal quick index gemspecs: 0.030s
ERROR:  While executing gem ... (NoMethodError)
    undefined method `<=>' for nil:NilClass
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in
`<=>'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in
`sort'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in
`update_specs_index'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:656:in
`update_index'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems.rb:966:in
`time'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:655:in
`update_index'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/commands/generate_index_command.rb:125:in
`execute'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command.rb:254:in
`invoke'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:132:in
`process_args'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:102:in
`run'
       
/opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:58:in
`run'
        /opt/ruby/bin/gem:21


----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2009-04-16 15:40

Message:
Can you run with -V as well?

gem generate_index --no-legacy --update -d /home/mirror/www --backtrace -V

This should give the gem that's causing the problem.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=25509&group_id=126

From djberg96 at gmail.com  Mon Jul 13 10:25:17 2009
From: djberg96 at gmail.com (Daniel Berger)
Date: Mon, 13 Jul 2009 08:25:17 -0600
Subject: [Rubygems-developers] Two failures in trunk
Message-ID: <4A5B43CD.6090400@gmail.com>

Hi,

Just got back from vacation yesterday. :)

I ran the tests in trunk (after installing the latest Hoe) and got this:

Ruby 1.8.6 (one click)
Windows XP
Rake 0.8.7


   2) Failure:
test_install_env_shebang(TestGemDependencyInstaller) 
[./test/test_gem_dependency_installer.rb:262]:
Expected /\A#!\/\S+\/env ruby\n/ to match "#! ruby\n#\n# This file was 
generated by RubyGems.\n#\n# The application 'a'
is installed as part of a gem, and\n# this file is here to facilitate 
running it.\n#\n\nrequire 'rubygems'\n\nversion =
\">= 0\"\n\nif ARGV.first =~ /^_(.*)_$/ and Gem::Version.correct? $1 
then\n  version = $1\n  ARGV.shift\nend\n\ngem 'a',
  version\nload Gem.bin_path('a', 'a_bin', version)\n".

   9) Failure:
test_shebang_env_shebang(TestGemInstaller) 
[./test/test_gem_installer.rb:785]:
Expected "#!/usr/bin/env ruby", not "#! ruby".

Regards,

Dan

From luislavena at gmail.com  Mon Jul 13 10:45:49 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Mon, 13 Jul 2009 11:45:49 -0300
Subject: [Rubygems-developers] Two failures in trunk
In-Reply-To: <4A5B43CD.6090400@gmail.com>
References: <4A5B43CD.6090400@gmail.com>
Message-ID: <71166b3b0907130745j4fe0e323q8d164e5d5970535b@mail.gmail.com>

On Mon, Jul 13, 2009 at 11:25 AM, Daniel Berger<djberg96 at gmail.com> wrote:
> Hi,
>
> Just got back from vacation yesterday. :)
>
> I ran the tests in trunk (after installing the latest Hoe) and got this:
>
> Ruby 1.8.6 (one click)

By one click you mean VC6 build of Ruby?

I've neglected mswin32 builds of Ruby for so long, mostly due next
installer is not going to be powered by VC6:

http://blog.mmediasys.com/2009/06/28/rubyinstaller-preview1-released/

Will try with mswin32 and let you know.
-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

From luislavena at gmail.com  Thu Jul 16 00:04:29 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Thu, 16 Jul 2009 01:04:29 -0300
Subject: [Rubygems-developers] Two failures in trunk
In-Reply-To: <71166b3b0907130745j4fe0e323q8d164e5d5970535b@mail.gmail.com>
References: <4A5B43CD.6090400@gmail.com>
	<71166b3b0907130745j4fe0e323q8d164e5d5970535b@mail.gmail.com>
Message-ID: <71166b3b0907152104n4808c75bybf8472f203f274a5@mail.gmail.com>

On Mon, Jul 13, 2009 at 11:45 AM, Luis Lavena<luislavena at gmail.com> wrote:
> On Mon, Jul 13, 2009 at 11:25 AM, Daniel Berger<djberg96 at gmail.com> wrote:
>> Hi,
>>
>> Just got back from vacation yesterday. :)
>>
>> I ran the tests in trunk (after installing the latest Hoe) and got this:
>>
>> Ruby 1.8.6 (one click)
>
> By one click you mean VC6 build of Ruby?
>
> I've neglected mswin32 builds of Ruby for so long, mostly due next
> installer is not going to be powered by VC6:
>
> http://blog.mmediasys.com/2009/06/28/rubyinstaller-preview1-released/
>
> Will try with mswin32 and let you know.


Verified, got the same failures on mswin32.

My understanding is that the new 1.3.5 release is going to be from 1_3
branch, not master.

Eric: please confirm just to be safe.
-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

From noreply at rubyforge.org  Thu Jul 16 21:51:54 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 16 Jul 2009 21:51:54 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Feature Requests-26640 ] different
	dependencies per version of ruby
Message-ID: <20090717015154.595051779931@rubyforge.org>

Feature Requests item #26640, was opened at 2009-07-17 01:51
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=578&aid=26640&group_id=126

Category: `gem install` command
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Roger Pack (rogerdpack)
Assigned to: Nobody (None)
Summary: different dependencies per version of ruby

Initial Comment:
Sorry if I asked this previously.
Anyway, currently if you need the ParseTree gem for 1.8 users but 1.9 users, there seems to be no easy way to distinguish this in the gemspec.
Thanks much.
=r

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=578&aid=26640&group_id=126

From noreply at rubyforge.org  Fri Jul 17 03:38:04 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 17 Jul 2009 03:38:04 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-8993 ] ERROR: While executing
	gem ... (Gem::RemoteFetcher::FetchError)
Message-ID: <20090717073804.A1EEF197858D@rubyforge.org>

Bugs item #8993, was opened at 2007-03-02 11:26
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=8993&group_id=126

Category: None
Group: None
Status: Closed
Resolution: None
Priority: 3
Submitted By: Michael Yates (mjyates)
Assigned to: Nobody (None)
Summary: ERROR:  While executing gem ... (Gem::RemoteFetcher::FetchError)  

Initial Comment:
Running --

C:\ruby\rubygems-0.9.2>ruby -v
ruby 1.8.5 (2006-08-25) [i386-mswin32]

Installing rubygems --

  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.2 ri...
Installing rubygems-0.9.2 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.

Attempting rails install --

C:\ruby\rubygems-0.9.2>gem install rails
ERROR:  While executing gem ... (Gem::RemoteFetcher::FetchError)
    A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address
was supplied.(Errno::ENOTCONN)

I'm not sure, but this seems to be a bug.

----------------------------------------------------------------------

Comment By: joseph george (zapping)
Date: 2009-07-17 02:38

Message:
I too had the same problem but there was no proxy on my system. But had firewall and anti-virus running. After disabling both was able to do gem update and install.

----------------------------------------------------------------------

Comment By: Keith Hyland (khylo)
Date: 2007-12-09 13:26

Message:
I had the same problem. For me it was a http_proxy system variable that was causing the problem. You may need to add or remove a proxy to access the web. THis can be done by simply adding or removing the http_proxy system variable.

I've written about it on my blogpage

http://khylo.blogspot.com/2007/12/ruby-on-rails-headaches.html

----------------------------------------------------------------------

Comment By: Michael Yates (mjyates)
Date: 2007-07-26 09:15

Message:
Eric: Thank you for looking into this. I can't do the 
upgrade and check as I don't have a Windows system anymore, 
only Linux. Sorry.
Michael Yates

----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2007-07-26 02:31

Message:
Michael: Can you upgrade to 0.9.4 and try again?  Reopen if you get the same behavior.

Jim: You probably can't resolve gems.rubyforge.org.  Check your DNS.

----------------------------------------------------------------------

Comment By: Jim Jacobs (jacobs2k)
Date: 2007-04-15 18:23

Message:

I've run into the same problem. Neither _gem_ nor _ruby_ seem to be able to connect to a remote host. I'd be quite delighted to find what silly thing I've done to break this. I had ruby and instiki running in the past, but after recently reinstalling both, I've had this puzzling error.

So, if its a bug, I can confirm its existence. If its the result of an installation error of some sort, you know you're not alone.

Anyone have a clue of the cause/solution to this?

Here's a example error message:
    C:\>gem -v
    0.9.2

    C:\>gem install instiki
    ERROR:  While executing gem ... (Gem::RemoteFetcher::FetchError)
        getaddrinfo: no address associated with hostname.(SocketError)
    
    C:\>ruby -v
    ruby 1.8.6 (2007-03-13 patchlevel 0) [i386-mswin32]


jljfwray at gmail.com


----------------------------------------------------------------------

Comment By: Jim Jacobs (jacobs2k)
Date: 2007-04-15 18:18

Message:

I've run into the same problem. Neither _gem_ nor _ruby_ seem to be able to connect to a remote host. I'd be quite delighted to find what silly thing I've done to break this. I had ruby and instiki running in the past, but after recently reinstalling both, I've had this puzzling error.

So, if its a bug, I can confirm its existence. If its the result of an installation error of some sort, you know you're not alone.

Anyone have a clue of the cause/solution to this?

Here's a example error message:
    C:\>gem -v
    0.9.2

    C:\>gem install instiki
    ERROR:  While executing gem ... (Gem::RemoteFetcher::FetchError)
        getaddrinfo: no address associated with hostname.(SocketError)
    
    C:\>ruby -v
    ruby 1.8.6 (2007-03-13 patchlevel 0) [i386-mswin32]


jljfwray at gmail.com


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=8993&group_id=126

From noreply at rubyforge.org  Fri Jul 17 14:21:32 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 17 Jul 2009 14:21:32 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Patches-26648 ] gem cleanup
	--keep-dependencies
Message-ID: <20090717182132.A864F1858133@rubyforge.org>

Patches item #26648, was opened at 2009-07-17 11:21
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=577&aid=26648&group_id=126

Category: `gem` commands (other)
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Bryan Soto (bsoto)
Assigned to: Nobody (None)
Summary: gem cleanup --keep-dependencies

Initial Comment:
Adds a flag to gem cleanup, either -k or --keep-dependencies which automatically skips trying to uninstall gem versions that are dependencies of other gems.


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=577&aid=26648&group_id=126

From thewoolleyman at gmail.com  Mon Jul 20 22:16:07 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Mon, 20 Jul 2009 19:16:07 -0700
Subject: [Rubygems-developers] RubyGems test failures related to multiple
	interpreters and executable prefix/suffix
Message-ID: <e3af97510907201916r739a6386v7af58948f4b3514a@mail.gmail.com>

I'm trying to debug a RubyGems test failure on a system which has
multiple ruby interpreter installs and 'ruby' symlinked to
'ruby1.8.6'.

Here is the test failure [1]:

1) Error:
test_execute_prerelease(TestGemCommandsUninstallCommand):
Gem::Installer::ExtensionBuildError:
ERROR: Failed to build gem native extension.

/usr/local/lib/ruby1.8.6/bin/ruby1.8.6 mkrf_conf.rb

rake1.8.6 RUBYARCHDIR=/tmp/test_rubygems_17720/gemhome/gems/pre-2.b/lib
RUBYLIBDIR=/tmp/test_rubygems_17720/gemhome/gems/pre-2.b/lib
sh: rake1.8.6: command not found


Questions:

* What is supposed to get a suffix?  All gem executables from
installed gems, or just 'official' ruby executables such as ri, irb,
etc?

* If the former is true, then there are bugs, because when I install
gems via 'ruby1.8.6', the executables do not have suffixes.

* If the latter is true, what category is Rake in?  Is it just a
normal gem?  If so, it should never be used with an extension, but it
is, which causes this test failure above 'rake1.8.6' not found
(because the actual executable is just 'rake').

Thanks,
-- Chad

[1] http://ci.thewoolleyweb.com/builds/RubyGems/265468d.3

From luislavena at gmail.com  Mon Jul 20 22:31:32 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Mon, 20 Jul 2009 23:31:32 -0300
Subject: [Rubygems-developers] RubyGems test failures related to
	multiple interpreters and executable prefix/suffix
In-Reply-To: <e3af97510907201916r739a6386v7af58948f4b3514a@mail.gmail.com>
References: <e3af97510907201916r739a6386v7af58948f4b3514a@mail.gmail.com>
Message-ID: <71166b3b0907201931v5a6dd14emefb16aed10e279f8@mail.gmail.com>

On Mon, Jul 20, 2009 at 11:16 PM, Chad Woolley<thewoolleyman at gmail.com> wrote:
> I'm trying to debug a RubyGems test failure on a system which has
> multiple ruby interpreter installs and 'ruby' symlinked to
> 'ruby1.8.6'.
>

What is the output of this:

ruby -rrbconfig -e "puts RbConfig::CONFIG['ruby_install_name']"

> Here is the test failure [1]:
>
> 1) Error:
> test_execute_prerelease(TestGemCommandsUninstallCommand):
> Gem::Installer::ExtensionBuildError:
> ERROR: Failed to build gem native extension.
>
> /usr/local/lib/ruby1.8.6/bin/ruby1.8.6 mkrf_conf.rb
>
> rake1.8.6 RUBYARCHDIR=/tmp/test_rubygems_17720/gemhome/gems/pre-2.b/lib
> RUBYLIBDIR=/tmp/test_rubygems_17720/gemhome/gems/pre-2.b/lib
> sh: rake1.8.6: command not found
>
>
> Questions:
>
> * What is supposed to get a suffix? ?All gem executables from
> installed gems, or just 'official' ruby executables such as ri, irb,
> etc?
>

What is the value of ENV['rake'] when Rake has been loaded?

It shouldn't be prefixing it, unless is trying to resolve the symlink,
which is doubtful.
-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

From thewoolleyman at gmail.com  Tue Jul 21 04:38:17 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Tue, 21 Jul 2009 01:38:17 -0700
Subject: [Rubygems-developers] RubyGems test failures related to
	multiple interpreters and executable prefix/suffix
In-Reply-To: <71166b3b0907201931v5a6dd14emefb16aed10e279f8@mail.gmail.com>
References: <e3af97510907201916r739a6386v7af58948f4b3514a@mail.gmail.com> 
	<71166b3b0907201931v5a6dd14emefb16aed10e279f8@mail.gmail.com>
Message-ID: <e3af97510907210138h18b74432u1897c3f4e926b4ed@mail.gmail.com>

Thanks for your help Luis...

On Mon, Jul 20, 2009 at 7:31 PM, Luis Lavena<luislavena at gmail.com> wrote:
> What is the output of this:
>
> ruby -rrbconfig -e "puts RbConfig::CONFIG['ruby_install_name']"

"ruby1.8.6" on both machines

> What is the value of ENV['rake'] when Rake has been loaded?

$ cat Rakefile
task :default do
  puts ENV['rake']
end

$ rake
(in /tmp)
nil


>
> It shouldn't be prefixing it, unless is trying to resolve the symlink,
> which is doubtful.

It must be following the symlink, or figuring it out somehow.  Here is
the line that blow up in Gem::Ext::RakeBuilder.build:

cmd = ENV['rake'] || "#{Gem.ruby} -rubygems #{Gem.bin_path('rake')}"
rescue Gem.default_exec_format % 'rake'

...it is getting to the rescue clause, because Gem.bin_path('rake')
fails with "can't find gem rake (>= 0)"

Thanks,
-- Chad

From darix at web.de  Tue Jul 21 08:26:11 2009
From: darix at web.de (Marcus Rueckert)
Date: Tue, 21 Jul 2009 14:26:11 +0200
Subject: [Rubygems-developers] RubyGems test failures related to
	multiple interpreters and executable prefix/suffix
In-Reply-To: <e3af97510907201916r739a6386v7af58948f4b3514a@mail.gmail.com>
References: <e3af97510907201916r739a6386v7af58948f4b3514a@mail.gmail.com>
Message-ID: <20090721122611.GI25378@pixel.global-banlist.de>

On 2009-07-20 19:16:07 -0700, Chad Woolley wrote:
> * What is supposed to get a suffix?  All gem executables from
> installed gems, or just 'official' ruby executables such as ri, irb,
> etc?

there was a bug report a few weeks ago that asked for exactly that. all
binaries installed via gem should get the suffix.

    darix

-- 
           openSUSE - SUSE Linux is my linux
               openSUSE is good for you
                   www.opensuse.org

From docwhat at gmail.com  Tue Jul  7 14:38:57 2009
From: docwhat at gmail.com (Christian Holtje)
Date: Tue, 7 Jul 2009 14:38:57 -0400
Subject: [Rubygems-developers] --format-executable should be the default
Message-ID: <1095EA03-2A0C-451F-84FF-1A9B024687A6@gmail.com>

Hello!

I'm really enjoying ruby; the gem framework is absolutely amazing.

When I was trying to use multiple versions of Ruby on the same system,  
I ran across this one confusing aspect: the executables for gems  
didn't have the same naming convention as the "ruby" and "irb"  
executables.

So I filed bug 1728[1] and Eric Hodel was kind enough to point me to  
this mailing list.

It seems that "gem --format-executable" should default to "true"  
because the binaries created  have the name of the "ruby" executable  
embedded in them (in the #! at the top).
Here are two use cases to help illustrate:
----use case 1-----------------------
I install ruby 1.8.

I use "./configure" when compiling it.
The binaries are in /usr/bin/ and do not have a suffix.

I decide I want to work on ruby 1.9.1 as well.
I use "./configure --program-suffix=19" when compiling it.
The binaries are also in /usr/bin but all end with "19", such as "/usr/ 
bin/ruby19".

Lets say I ZenTest for 1.8:
$ gem install ZenTest

This creates /usr/bin/autotest. This executable is intimately tied to  
ruby 1.8; it begins with "#!/usr/bin/ruby -ws" -- it cannot be used  
for ruby 1.9 (yet) because the libraries are not installed in ruby 1.9  
and the executable it points to is the 1.8 executable.

Now lets say I want to install autotest for ruby 1.9:
$ gem19 install ZenTest

By default, no new binaries are created since they already exists.

The executable /usr/bin/autotest is *still* tied to ruby 1.8.

This causes confusion by the user; they just installed autotest for  
ruby 1.9 but it still is running ruby 1.8.
-----------------------------------

----use case 2-----------------------
My system administrator installs ruby 1.8 using "./configure" with no  
arguments.
My system administrator installs ruby 1.9.1 using "./configure -- 
program-suffix=19"

I (a non-system-administrator) wants to install ZenTest for both:
$ gem install ZenTest
[output showing it is installed to ~/.gem]
$ gem19 install ZenTest
[output showing it is installed to ~/.gem]

So now I have two "autotest" binaries:
~/.gem/ruby/1.8/bin/autotest
and
~/.gem/ruby/1.9.1/bin/autotest

If my PATH includes both, then which "autotest" I get depends on my  
PATH order.  The only way I can distinguish between the two  
executables is by changing my PATH on the fly.  Not very useful if I  
want to be able to easily switch between both versions to verify it  
works in both versions of Ruby.
-----------------------------------

As you can see it can be rather confusing for "--format-executable"  
not to be the default.

It was doubly confusing for me because everything else worked so  
well. :-)

Ciao!

[1] http://redmine.ruby-lang.org/issues/show/1728

From randy.j.parker at gmail.com  Wed Jul  8 13:57:11 2009
From: randy.j.parker at gmail.com (Randy Parker)
Date: Wed, 8 Jul 2009 13:57:11 -0400
Subject: [Rubygems-developers] "gem update" Fails,
	but "gem update X" works fine
In-Reply-To: <735c8b860907081050u6bd42c5dw3c883ac082285e03@mail.gmail.com>
References: <735c8b860907081050u6bd42c5dw3c883ac082285e03@mail.gmail.com>
Message-ID: <735c8b860907081057r69f34bf2wa642a3c13001cbc7@mail.gmail.com>

When I do a general "sudo gem update" on my mac, I get "could not find gem X
locally or in a repository".
But if I do "sudo gem update X", the gem gets updated without incident.

This would be no big deal if "X" were the only gem suffering this
problem.  However, the failure to update is happening to 100% of the
gems I have installed that can be updated.  So far, I've had to
manually spell out the name of two dozen gems that "couldn't be found"
until I tried to update them by their specific name.  All 24 of these
failures updated successfully when I spelled them out.

I posted my experience to my local Atlanta IRC channel.  Three of the
four folks who tested "gem update" had the same problem.  I first
noticed the problem on Tuesday, 6.30.2009.  It continued to occur on
Weds 7.1.2009, did not happen on Thursday 7.2.2009, and is happening to me
again today, 7.8.2009.

sw_vers ==> Mac OS X 10.5.7

gem --version ==> 1.3.4

ruby --version ==> ruby 1.8.6 (2008-08-11 patchlevel 287) [universal-
darwin9.0]

gem sources ==> http://gems.rubyforge.org/     http://gems.github.com

The one guy for whom the entire set of installed gems updated cleanly
was also on a Mac running 10.5.7
ddollar guessed that the gem mirrors aren't syncing, so that sometimes you
get an index from one mirror, and then try to pull the actual gem from a
different mirror that doesn't have it.  Does anyone know if that is really
happening?  If so, what would it take to fix?

- Randy
-- 
http://mobiledyne.com

From william.c.brennan at lmco.com  Mon Jul 13 18:41:43 2009
From: william.c.brennan at lmco.com (Brennan, William C)
Date: Mon, 13 Jul 2009 18:41:43 -0400
Subject: [Rubygems-developers] Problem installing rubygems-1.3.4 under Cygwin
Message-ID: <249DC7180F301445BCA2E01EAAFDF4091554A97B@emss04m05.us.lmco.com>

I wanted to install rubygems under Cygwin on a Intel machine running
Windows XP.

 

When I attempted to install rubygems-1.3.4, the installation didn't seem
to install much, and then (with the aid of the debug option) I received
some error messages after the"gem update --system" command.  Then the
process just hanged.  See below.

 

Just to see if an earlier version of rubygems might install for me, I
tried rubygems 1.3.1.  This seemed to install with greater success.
However, when I attempted to do the "gem update --system", the processor
hanged in this case, too.  See below.

 

I tried to clean up newly installed files between different installation
attempts (which I attempted repeatedly), but might have missed some here
and there.

 

Can anyone offer any suggestions how to get rubygems running on my
system?  I'd be happy with ANY version in the past 2 years.

 

-- Bill

 

 

============= Start of installation of rubygems-1.3.4
==========================================

$ ruby setup.rb install

Installing RubyGems

Installing gem executable

Removing old source_cache files

Removing old RubyGems RDoc and ri

Installing rubygems-1.3.4 ri into
/usr/lib/ruby/gems/1.8/doc/rubygems-1.3.4/ri

Installing rubygems-1.3.4 rdoc into
/usr/lib/ruby/gems/1.8/doc/rubygems-1.3.4/rdoc

 

------------------------------------------------------------------------
------

 

Oh-no! Unable to find release notes!

 

------------------------------------------------------------------------
------

 

RubyGems installed the following executables:

        /usr/bin/gem

 

$ gem --debug update --system

Exception `NameError' at
/usr/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:161

- uninitialized constant Gem::Commands::UpdateCommand

Exception `Gem::LoadError' at
/usr/lib/ruby/site_ruby/1.8/rubygems.rb:826 - Could not

 find RubyGem test-unit (>= 0)

 

Updating RubyGems

Exception `Gem::LoadError' at
/usr/lib/ruby/site_ruby/1.8/rubygems.rb:826 - Could not

 find RubyGem sources (> 0.0.1)

<.......  my processor hangs ........>

============= End of installation of rubygems-1.3.4
==========================================

 

============= Start of installation of rubygems-1.3.1
==========================================

$ ruby setup.rb install

mkdir -p /usr/lib/ruby/site_ruby/1.8

mkdir -p /usr/bin

mkdir -p /usr/lib/ruby/site_ruby/1.8/rbconfig

install -c -m 0644 rbconfig/datadir.rb
/usr/lib/ruby/site_ruby/1.8/rbconfig/datadir.rb

mkdir -p /usr/lib/ruby/site_ruby/1.8/rubygems

install -c -m 0644 rubygems/builder.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/builder.rb

install -c -m 0644 rubygems/command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/command.rb

mkdir -p /usr/lib/ruby/site_ruby/1.8/rubygems/commands

install -c -m 0644 rubygems/commands/build_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/build_command.rb

install -c -m 0644 rubygems/commands/cert_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/cert_command.rb

install -c -m 0644 rubygems/commands/check_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/check_command.rb

install -c -m 0644 rubygems/commands/cleanup_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/cleanup_command.rb

install -c -m 0644 rubygems/commands/contents_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/contents_command.rb

install -c -m 0644 rubygems/commands/dependency_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/dependency_command.rb

install -c -m 0644 rubygems/commands/environment_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/environment_command.rb

install -c -m 0644 rubygems/commands/fetch_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/fetch_command.rb

install -c -m 0644 rubygems/commands/generate_index_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/generate_index_command.rb

install -c -m 0644 rubygems/commands/help_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/help_command.rb

install -c -m 0644 rubygems/commands/install_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb

install -c -m 0644 rubygems/commands/list_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/list_command.rb

install -c -m 0644 rubygems/commands/lock_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/lock_command.rb

install -c -m 0644 rubygems/commands/mirror_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/mirror_command.rb

install -c -m 0644 rubygems/commands/outdated_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/outdated_command.rb

install -c -m 0644 rubygems/commands/pristine_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/pristine_command.rb

install -c -m 0644 rubygems/commands/query_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/query_command.rb

install -c -m 0644 rubygems/commands/rdoc_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/rdoc_command.rb

install -c -m 0644 rubygems/commands/search_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/search_command.rb

install -c -m 0644 rubygems/commands/server_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/server_command.rb

install -c -m 0644 rubygems/commands/sources_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/sources_command.rb

install -c -m 0644 rubygems/commands/specification_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/specification_command.rb

install -c -m 0644 rubygems/commands/stale_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/stale_command.rb

install -c -m 0644 rubygems/commands/uninstall_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/uninstall_command.rb

install -c -m 0644 rubygems/commands/unpack_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/unpack_command.rb

install -c -m 0644 rubygems/commands/update_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/update_command.rb

install -c -m 0644 rubygems/commands/which_command.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/commands/which_command.rb

install -c -m 0644 rubygems/command_manager.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb

install -c -m 0644 rubygems/config_file.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/config_file.rb

install -c -m 0644 rubygems/custom_require.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb

install -c -m 0644 rubygems/defaults.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/defaults.rb

install -c -m 0644 rubygems/dependency.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/dependency.rb

install -c -m 0644 rubygems/dependency_installer.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/dependency_installer.rb

install -c -m 0644 rubygems/dependency_list.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/dependency_list.rb

mkdir -p /usr/lib/ruby/site_ruby/1.8/rubygems/digest

install -c -m 0644 rubygems/digest/digest_adapter.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/digest/digest_adapter.rb

install -c -m 0644 rubygems/digest/md5.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/digest/md5.rb

install -c -m 0644 rubygems/digest/sha1.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/digest/sha1.rb

install -c -m 0644 rubygems/digest/sha2.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/digest/sha2.rb

install -c -m 0644 rubygems/doc_manager.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/doc_manager.rb

install -c -m 0644 rubygems/exceptions.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/exceptions.rb

mkdir -p /usr/lib/ruby/site_ruby/1.8/rubygems/ext

install -c -m 0644 rubygems/ext/builder.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/ext/builder.rb

install -c -m 0644 rubygems/ext/configure_builder.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/ext/configure_builder.rb

install -c -m 0644 rubygems/ext/ext_conf_builder.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/ext/ext_conf_builder.rb

install -c -m 0644 rubygems/ext/rake_builder.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/ext/rake_builder.rb

install -c -m 0644 rubygems/ext.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/ext.rb

install -c -m 0644 rubygems/format.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/format.rb

install -c -m 0644 rubygems/gem_openssl.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/gem_openssl.rb

install -c -m 0644 rubygems/gem_path_searcher.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb

install -c -m 0644 rubygems/gem_runner.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb

install -c -m 0644 rubygems/indexer.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/indexer.rb

install -c -m 0644 rubygems/installer.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/installer.rb

install -c -m 0644 rubygems/install_update_options.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/install_update_options.rb

install -c -m 0644 rubygems/local_remote_options.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/local_remote_options.rb

install -c -m 0644 rubygems/old_format.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/old_format.rb

mkdir -p /usr/lib/ruby/site_ruby/1.8/rubygems/package

install -c -m 0644 rubygems/package/f_sync_dir.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/package/f_sync_dir.rb

install -c -m 0644 rubygems/package/tar_header.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/package/tar_header.rb

install -c -m 0644 rubygems/package/tar_input.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/package/tar_input.rb

install -c -m 0644 rubygems/package/tar_output.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/package/tar_output.rb

mkdir -p /usr/lib/ruby/site_ruby/1.8/rubygems/package/tar_reader

install -c -m 0644 rubygems/package/tar_reader/entry.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/package/tar_reader/entry.rb

install -c -m 0644 rubygems/package/tar_reader.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/package/tar_reader.rb

install -c -m 0644 rubygems/package/tar_writer.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/package/tar_writer.rb

install -c -m 0644 rubygems/package.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/package.rb

install -c -m 0644 rubygems/platform.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/platform.rb

install -c -m 0644 rubygems/remote_fetcher.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/remote_fetcher.rb

install -c -m 0644 rubygems/requirement.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/requirement.rb

install -c -m 0644 rubygems/require_paths_builder.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/require_paths_builder.rb

install -c -m 0644 rubygems/rubygems_version.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/rubygems_version.rb

install -c -m 0644 rubygems/security.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/security.rb

install -c -m 0644 rubygems/server.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/server.rb

install -c -m 0644 rubygems/source_index.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/source_index.rb

install -c -m 0644 rubygems/source_info_cache.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/source_info_cache.rb

install -c -m 0644 rubygems/source_info_cache_entry.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/source_info_cache_entry.rb

install -c -m 0644 rubygems/specification.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/specification.rb

install -c -m 0644 rubygems/spec_fetcher.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/spec_fetcher.rb

install -c -m 0644 rubygems/test_utilities.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/test_utilities.rb

install -c -m 0644 rubygems/timer.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/timer.rb

install -c -m 0644 rubygems/uninstaller.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb

install -c -m 0644 rubygems/user_interaction.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/user_interaction.rb

install -c -m 0644 rubygems/validator.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/validator.rb

install -c -m 0644 rubygems/version.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/version.rb

install -c -m 0644 rubygems/version_option.rb
/usr/lib/ruby/site_ruby/1.8/rubygems/version_option.rb

install -c -m 0644 rubygems.rb /usr/lib/ruby/site_ruby/1.8/rubygems.rb

install -c -m 0644 ubygems.rb /usr/lib/ruby/site_ruby/1.8/ubygems.rb

cp gem /cygdrive/c/DOCUME~1/wcbrenna/LOCALS~1/Temp/gem

install -c -m 0755 /cygdrive/c/DOCUME~1/wcbrenna/LOCALS~1/Temp/gem
/usr/bin/gem

rm /cygdrive/c/DOCUME~1/wcbrenna/LOCALS~1/Temp/gem

install -c -m 0755 /cygdrive/c/DOCUME~1/wcbrenna/LOCALS~1/Temp/gem.bat
/usr/bin/gem.bat

rm /cygdrive/c/DOCUME~1/wcbrenna/LOCALS~1/Temp/gem.bat

rm -f /cygdrive/d/wcb_home/.gem/source_cache

rm -f /usr/lib/ruby/gems/1.8/source_cache

Removing old RubyGems RDoc and ri

Installing rubygems-1.3.1 ri into
/usr/lib/ruby/gems/1.8/doc/rubygems-1.3.1/ri

Installing rubygems-1.3.1 rdoc into
/usr/lib/ruby/gems/1.8/doc/rubygems-1.3.1/rdoc

 

------------------------------------------------------------------------
------

 

= Announce: RubyGems Release 1.3.0

 

NOTE:  RubyGems 1.1 and 1.2 have problems upgrading when there is no

rubygems-update installed.  You will need to follow the second set of
update

instructions if you see "Nothing to update".

 

Release 1.3.0 fixes some bugs.

 

Bugs fixed:

 

* Disregard ownership of ~ under Windows while creating ~/.gem.  Fixes

  issues related to no uid support under Windows.

* Fix requires for Gem::inflate, Gem::deflate, etc.

* Make Gem.dir respect :gemhome value from config.  (Note: this feature
may be

  removed since it is hard to implement on 1.9.)

* Kernel methods are now private.  Patch #20801 by Stefan Rusterholz.

* Gem::location_of_caller now behaves on Windows.  Patch by Daniel
Berger.

* Silence PATH warning.

 

Deprecation Notices:

 

* Gem::manage_gems will be removed on or after March 2009.

 

For a full list of changes to RubyGems and the contributor for each
change, see

the ChangeLog file.

 

Special thanks to Chad Wooley for backwards compatibility testing and
Luis

Lavena for continuing windows support.

 

== 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:  RubyGems 1.1 and 1.2 have problems upgrading when there is no

rubygems-update installed.  You will need to follow the second set of
update

instructions if you see "Nothing to update".

 

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)

 

 

------------------------------------------------------------------------
------

 

RubyGems installed the following executables:

        /usr/bin/gem

 

If `gem` was installed by a previous RubyGems installation, you may need

to remove it by hand.

 

$ gem --debug update --system

Exception `NameError' at
/usr/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:134-
uninitialized constant Gem::Commands::UpdateCommand

Updating RubyGems

Exception `Gem::LoadError' at
/usr/lib/ruby/site_ruby/1.8/rubygems.rb:636 - Could not find RubyGem
sources (> 0.0.1)

 

Exception `Errno::ENOENT' at /usr/lib/ruby/1.8/fileutils.rb:243 - No
such file or directory -
/cygdrive/d/wcb_home/.gem/specs/gems.rubyforge.org%80

Exception `Errno::ENOENT' at /usr/lib/ruby/1.8/fileutils.rb:243 - No
such file or directory -

Exception `Errno::EEXIST' at /usr/lib/ruby/1.8/fileutils.rb:243 - File
exists - /cygdrive

Exception `Errno::EACCES' at /usr/lib/ruby/1.8/fileutils.rb:243 -
Permission denied - /cygdrive/d

Exception `Errno::EEXIST' at /usr/lib/ruby/1.8/fileutils.rb:243 - File
exists - /cygdrive/d/wcb_home

Exception `Errno::EEXIST' at /usr/lib/ruby/1.8/fileutils.rb:243 - File
exists - /cygdrive/d/wcb_home/.gem

Updating rubygems-update

Exception `Errno::ENOENT' at /usr/lib/ruby/1.8/fileutils.rb:243 - No
such file or directory -
/cygdrive/d/wcb_home/.gem/specs/gems.rubyforge.org%80/quick/Marshal.4.8

Exception `Errno::ENOENT' at /usr/lib/ruby/1.8/fileutils.rb:243 - No
such file or directory -

Exception `Errno::EEXIST' at /usr/lib/ruby/1.8/fileutils.rb:243 - File
exists - /cygdrive

Exception `Errno::EACCES' at /usr/lib/ruby/1.8/fileutils.rb:243 -
Permission denied - /cygdrive/d

Exception `Errno::EEXIST' at /usr/lib/ruby/1.8/fileutils.rb:243 - File
exists - /cygdrive/d/wcb_home

Exception `Errno::EEXIST' at /usr/lib/ruby/1.8/fileutils.rb:243 - File
exists - /cygdrive/d/wcb_home/.gem

Exception `Errno::EEXIST' at /usr/lib/ruby/1.8/fileutils.rb:243 - File
exists - /cygdrive/d/wcb_home/.gem/specs

Exception `Errno::EEXIST' at /usr/lib/ruby/1.8/fileutils.rb:243 - File
exists - /cygdrive/d/wcb_home/.gem/specs/gems.rubyforge.org%80

<.......  my processor hangs ........>

============= End of installation of rubygems-1.3.1
==========================================

 


From randy.j.parker at gmail.com  Wed Jul 15 12:09:30 2009
From: randy.j.parker at gmail.com (Randy Parker)
Date: Wed, 15 Jul 2009 12:09:30 -0400
Subject: [Rubygems-developers] 'gem update' Fails, but 'gem update X' Works
Message-ID: <735c8b860907150909p47165eeenf78d542d5dd1ff0f@mail.gmail.com>

When I do a general "sudo gem update" on my mac, I get "could not find  gem
X locally or in a repository".

But if I do "sudo gem update X", the gem gets updated without  incident.

This would be no big deal if "X" were the only gem suffering this
problem.  However, the failure to update is happening to 100% of the
gems I have installed that can be updated.  So far, I've had to
manually spell out the name of two dozen gems that "couldn't be found"
until I tried to update them by their specific name.  All 24 of these
failures updated successfully when I spelled them out.

I posted my experience to my local Atlanta IRC channel.  Three of the
four folks who tested "gem update" had the same problem.  I first
noticed the problem on Tuesday, 6.30.2009.  It continues to occur through
today, July 15.


sw_vers ==> Mac OS X 10.5.7

gem --version ==> 1.3.4

ruby --version ==> ruby 1.8.6 (2008-08-11 patchlevel 287)
[universal- darwin9.0]


gem sources ==> http://gems.rubyforge.org/     http://gems.github.com


The one guy for whom the entire set of installed gems updated cleanly  was
also on a Mac running 10.5.7


ddollar guessed that the gem mirrors aren't syncing, so that sometimes you
get an index from one mirror, and then try to pull the actual gem from a
different mirror that doesn't have it.  Does anyone know if that is really
happening?  If so, what would it take to fix?

- Randy
-- 
http://mobiledyne.com

From drbrain at segment7.net  Tue Jul 21 18:02:12 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Tue, 21 Jul 2009 15:02:12 -0700
Subject: [Rubygems-developers] Moderator queue delay
Message-ID: <0DCFE386-25CE-4C87-B878-E8CB31B84365@segment7.net>

Sorry, I was away in Japan so I didn't get to the moderation queue in  
a timely fashion.  I didn't have much access to email while I was away.

From luislavena at gmail.com  Tue Jul 21 18:05:45 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Tue, 21 Jul 2009 19:05:45 -0300
Subject: [Rubygems-developers] 'gem update' Fails,
	but 'gem update X' 	Works
In-Reply-To: <735c8b860907150909p47165eeenf78d542d5dd1ff0f@mail.gmail.com>
References: <735c8b860907150909p47165eeenf78d542d5dd1ff0f@mail.gmail.com>
Message-ID: <71166b3b0907211505r4d6a558fgb5162e525a37ddee@mail.gmail.com>

On Wed, Jul 15, 2009 at 1:09 PM, Randy Parker<randy.j.parker at gmail.com> wrote:
> When I do a general "sudo gem update" on my mac, I get "could not find ?gem
> X locally or in a repository".
>
> But if I do "sudo gem update X", the gem gets updated without ?incident.
>

What is X?

Perhaps X hasn't been spread to all the gem mirrors and making it fail.

Please provide the output of sudo gem update X --debug

And please tell the name of the gem, being hosted at RubyForge there
is no mystery about we seen you using that particular gem.
-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

From randy.j.parker at gmail.com  Tue Jul 21 18:24:33 2009
From: randy.j.parker at gmail.com (Randy Parker)
Date: Tue, 21 Jul 2009 18:24:33 -0400
Subject: [Rubygems-developers] 'gem update' Fails,
	but 'gem update X' 	Works
In-Reply-To: <71166b3b0907211505r4d6a558fgb5162e525a37ddee@mail.gmail.com>
References: <735c8b860907150909p47165eeenf78d542d5dd1ff0f@mail.gmail.com>
	<71166b3b0907211505r4d6a558fgb5162e525a37ddee@mail.gmail.com>
Message-ID: <735c8b860907211524l2324d007gbe0c21b9b0071763@mail.gmail.com>

X stands for every gem that has a more recent version available.Depending on
the day I run gem update, X can stand for every one of several dozen
specific gems.

It will do no good to send you the
debug output.  The whole point is that as soon as I specify the
specific name of the gems, then "gem update" works.  Today, for
example, the first X I encounter is "actionmailer"

On Tue, Jul 21, 2009 at 6:05 PM, Luis Lavena <luislavena at gmail.com> wrote:

> On Wed, Jul 15, 2009 at 1:09 PM, Randy Parker<randy.j.parker at gmail.com>
> wrote:
> > When I do a general "sudo gem update" on my mac, I get "could not find
>  gem
> > X locally or in a repository".
> >
> > But if I do "sudo gem update X", the gem gets updated without  incident.
> >
>
> What is X?
>
> Perhaps X hasn't been spread to all the gem mirrors and making it fail.
>
> Please provide the output of sudo gem update X --debug
>
> And please tell the name of the gem, being hosted at RubyForge there
> is no mystery about we seen you using that particular gem.
> --
> Luis Lavena
> AREA 17
> -
> Perfection in design is achieved not when there is nothing more to add,
> but rather when there is nothing more to take away.
> Antoine de Saint-Exup?ry
> _______________________________________________
> Rubygems-developers mailing list
> http://rubyforge.org/projects/rubygems
> Rubygems-developers at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubygems-developers
>



-- 
http://mobiledyne.com

From drbrain at segment7.net  Tue Jul 21 20:18:37 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Tue, 21 Jul 2009 17:18:37 -0700
Subject: [Rubygems-developers] [ANN] RubyGems 1.3.5
Message-ID: <DA04E0D9-A1F5-4E55-8A5C-12B309F327C0@segment7.net>

rubygems-update version 1.3.5 has been released!

* <http://rubygems.rubyforge.org/>
* <http://rubyforge.org/projects/rubygems>
* <http://rubygems.org/>

RubyGems is a package management framework for Ruby.

This gem is an update for the RubyGems software. You must have an
installation of RubyGems before this update can be applied.

See Gem for information on RubyGems (or `ri Gem`)

To upgrade to the latest RubyGems, run:

   $ gem install --system  # you might need to be an administrator or  
root

NOTE:  RubyGems 1.1 and 1.2 have problems upgrading when there is no
rubygems-update installed.  You will need to use the following  
instructions
if you see "Nothing to update".

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 RubyGems 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

For more details and other options, see:

   ruby setup.rb --help

Changes:

### 1.3.5 / 2009-07-21

Bug fixes:

* Fix use of prerelease gems.
* Gem.bin_path no longer escapes path with spaces. Bug #25935 and  
#26458.

Deprecation Notices:

* Bulk index update is no longer supported (the code currently  
remains, but not
   the tests)
* Gem::manage_gems was removed in 1.3.3.
* Time::today was removed in 1.3.3.


From luislavena at gmail.com  Wed Jul 22 00:44:23 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Wed, 22 Jul 2009 01:44:23 -0300
Subject: [Rubygems-developers] 'gem update' Fails,
	but 'gem update X' 	Works
In-Reply-To: <735c8b860907211524l2324d007gbe0c21b9b0071763@mail.gmail.com>
References: <735c8b860907150909p47165eeenf78d542d5dd1ff0f@mail.gmail.com> 
	<71166b3b0907211505r4d6a558fgb5162e525a37ddee@mail.gmail.com> 
	<735c8b860907211524l2324d007gbe0c21b9b0071763@mail.gmail.com>
Message-ID: <71166b3b0907212144y141ab21fr296af75d981af4ba@mail.gmail.com>

On Tue, Jul 21, 2009 at 7:24 PM, Randy Parker<randy.j.parker at gmail.com> wrote:
> X stands for every gem that has a more recent version available.Depending on
> the day I run gem update, X can stand for every one of several dozen
> specific gems.
>
> It will do no good to send you the
> debug output. ?The whole point is that as soon as I specify the
> specific name of the gems, then "gem update" works. ?Today, for
> example, the first X I encounter is "actionmailer"
>

The debug output is helpful for us to pinpoint the root of the issue.

There are some weird mirror issues I've spotted several times with
RubyForge that is making RubyGems behave incorrectly.

That's why I ask you please send the --debug output when doing gem
update, so in that way we can see if: the problems are the quick
indexes, the contact to the mirror, unpacking issues, etc.

-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

From randy.j.parker at gmail.com  Wed Jul 22 09:58:11 2009
From: randy.j.parker at gmail.com (Randy Parker)
Date: Wed, 22 Jul 2009 09:58:11 -0400
Subject: [Rubygems-developers] 'gem update' Fails,
	but 'gem update X' 	Works
In-Reply-To: <71166b3b0907212144y141ab21fr296af75d981af4ba@mail.gmail.com>
References: <735c8b860907150909p47165eeenf78d542d5dd1ff0f@mail.gmail.com>
	<71166b3b0907211505r4d6a558fgb5162e525a37ddee@mail.gmail.com>
	<735c8b860907211524l2324d007gbe0c21b9b0071763@mail.gmail.com>
	<71166b3b0907212144y141ab21fr296af75d981af4ba@mail.gmail.com>
Message-ID: <735c8b860907220658rb82a7efsf20b84eee3a43038@mail.gmail.com>

Louis asked:
> Please provide the output of sudo gem update X --debug
> ...
> so in that way we can see if: the problems are the quick
> indexes, the contact to the mirror, unpacking issues, etc.


~ $ sudo gem update --debug
Exception `NameError' at
/Library/Ruby/Site/1.8/rubygems/command_manager.rb:161 - uninitialized
constant Gem::Commands::UpdateCommand
Exception `Gem::LoadError' at /Library/Ruby/Site/1.8/rubygems.rb:827 - Could
not find RubyGem test-unit (>= 0)

Updating installed gems
Updating crack
Exception `Errno::EPIPE' at
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/protocol.rb:175
- Broken pipe
Exception `Gem::RemoteFetcher::FetchError' at
/Library/Ruby/Site/1.8/rubygems/remote_fetcher.rb:172 - Errno::EPIPE: Broken
pipe (http://gems.rubyforge.org/quick/Marshal.4.8/crack-0.1.4.gemspec.rz)
Exception `Gem::RemoteFetcher::FetchError' at
/Library/Ruby/Site/1.8/rubygems/spec_fetcher.rb:76 - Errno::EPIPE: Broken
pipe (http://gems.rubyforge.org/quick/Marshal.4.8/crack-0.1.4.gemspec.rz)
Exception `Gem::GemNotFoundException' at
/Library/Ruby/Site/1.8/rubygems/dependency_installer.rb:200 - could not find
gem crack locally or in a repository
ERROR:  While executing gem ... (Gem::GemNotFoundException)
    could not find gem crack locally or in a repository
/Library/Ruby/Site/1.8/rubygems/dependency_installer.rb:200:in
`find_spec_by_name_and_version'
/Library/Ruby/Site/1.8/rubygems/dependency_installer.rb:213:in `install'
/Library/Ruby/Site/1.8/rubygems/commands/update_command.rb:87:in `execute'
/Library/Ruby/Site/1.8/rubygems/commands/update_command.rb:81:in `each'
/Library/Ruby/Site/1.8/rubygems/commands/update_command.rb:81:in `execute'
/Library/Ruby/Site/1.8/rubygems/command.rb:257:in `invoke'
/Library/Ruby/Site/1.8/rubygems/command_manager.rb:132:in `process_args'
/Library/Ruby/Site/1.8/rubygems/command_manager.rb:102:in `run'
/Library/Ruby/Site/1.8/rubygems/gem_runner.rb:58:in `run'
/usr/bin/gem:21
~ $

From drbrain at segment7.net  Wed Jul 22 17:42:55 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Wed, 22 Jul 2009 14:42:55 -0700
Subject: [Rubygems-developers] Two failures in trunk
In-Reply-To: <71166b3b0907152104n4808c75bybf8472f203f274a5@mail.gmail.com>
References: <4A5B43CD.6090400@gmail.com>
	<71166b3b0907130745j4fe0e323q8d164e5d5970535b@mail.gmail.com>
	<71166b3b0907152104n4808c75bybf8472f203f274a5@mail.gmail.com>
Message-ID: <81985D11-25C8-42D9-BF73-64645AAECBED@segment7.net>

On Jul 15, 2009, at 21:04, Luis Lavena wrote:
> On Mon, Jul 13, 2009 at 11:45 AM, Luis Lavena<luislavena at gmail.com>  
> wrote:
>> On Mon, Jul 13, 2009 at 11:25 AM, Daniel Berger<djberg96 at gmail.com>  
>> wrote:
>>> Hi,
>>>
>>> Just got back from vacation yesterday. :)
>>>
>>> I ran the tests in trunk (after installing the latest Hoe) and got  
>>> this:
>>>
>>> Ruby 1.8.6 (one click)
>>
>> By one click you mean VC6 build of Ruby?
>>
>> I've neglected mswin32 builds of Ruby for so long, mostly due next
>> installer is not going to be powered by VC6:
>>
>> http://blog.mmediasys.com/2009/06/28/rubyinstaller-preview1-released/
>>
>> Will try with mswin32 and let you know.
>
>
> Verified, got the same failures on mswin32.
>
> My understanding is that the new 1.3.5 release is going to be from 1_3
> branch, not master.
>
> Eric: please confirm just to be safe.

I made the release from the 1_3 branch

From drbrain at segment7.net  Wed Jul 22 17:52:22 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Wed, 22 Jul 2009 14:52:22 -0700
Subject: [Rubygems-developers] --format-executable should be the default
In-Reply-To: <1095EA03-2A0C-451F-84FF-1A9B024687A6@gmail.com>
References: <1095EA03-2A0C-451F-84FF-1A9B024687A6@gmail.com>
Message-ID: <90681D1F-18E7-469C-81C7-D880C113E616@segment7.net>

On Jul 7, 2009, at 11:38, Christian Holtje wrote:
> I'm really enjoying ruby; the gem framework is absolutely amazing.
>
> When I was trying to use multiple versions of Ruby on the same  
> system, I ran across this one confusing aspect: the executables for  
> gems didn't have the same naming convention as the "ruby" and "irb"  
> executables.
>
> So I filed bug 1728[1] and Eric Hodel was kind enough to point me to  
> this mailing list.
>
> It seems that "gem --format-executable" should default to "true"  
> because the binaries created  have the name of the "ruby" executable  
> embedded in them (in the #! at the top).

I would like to make --format-executable the default for 1.4+.  It  
seems many more people are running multiple versions of ruby these days.


From drbrain at segment7.net  Wed Jul 22 17:56:32 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Wed, 22 Jul 2009 14:56:32 -0700
Subject: [Rubygems-developers] Problem installing rubygems-1.3.4 under
	Cygwin
In-Reply-To: <249DC7180F301445BCA2E01EAAFDF4091554A97B@emss04m05.us.lmco.com>
References: <249DC7180F301445BCA2E01EAAFDF4091554A97B@emss04m05.us.lmco.com>
Message-ID: <04B4E776-0405-43A6-89A3-27641839664F@segment7.net>

On Jul 13, 2009, at 15:41, Brennan, William C wrote:

> I wanted to install rubygems under Cygwin on a Intel machine running
> Windows XP.
>
> When I attempted to install rubygems-1.3.4, the installation didn't  
> seem
> to install much
>
> ============= Start of installation of rubygems-1.3.4
> ==========================================
>
> $ ruby setup.rb install
> Installing RubyGems
> Installing gem executable
> Removing old source_cache files
> Removing old RubyGems RDoc and ri
> Installing rubygems-1.3.4 ri into
> /usr/lib/ruby/gems/1.8/doc/rubygems-1.3.4/ri
> Installing rubygems-1.3.4 rdoc into
> /usr/lib/ruby/gems/1.8/doc/rubygems-1.3.4/rdoc
>
> ------------------------------------------------------------------------
> ------
>
> Oh-no! Unable to find release notes!
>
> ------------------------------------------------------------------------
> ------
>
> RubyGems installed the following executables:
>
>        /usr/bin/gem


It installed successfully.  Try `gem env --version` next time.

From jeremy at bitsweat.net  Wed Jul 22 17:58:50 2009
From: jeremy at bitsweat.net (Jeremy Kemper)
Date: Wed, 22 Jul 2009 14:58:50 -0700
Subject: [Rubygems-developers] --format-executable should be the default
In-Reply-To: <90681D1F-18E7-469C-81C7-D880C113E616@segment7.net>
References: <1095EA03-2A0C-451F-84FF-1A9B024687A6@gmail.com>
	<90681D1F-18E7-469C-81C7-D880C113E616@segment7.net>
Message-ID: <69a2885c0907221458p49c2d8desa27ea1c6dc749c45@mail.gmail.com>

On Wed, Jul 22, 2009 at 2:52 PM, Eric Hodel<drbrain at segment7.net> wrote:
> On Jul 7, 2009, at 11:38, Christian Holtje wrote:
>>
>> I'm really enjoying ruby; the gem framework is absolutely amazing.
>>
>> When I was trying to use multiple versions of Ruby on the same system, I
>> ran across this one confusing aspect: the executables for gems didn't have
>> the same naming convention as the "ruby" and "irb" executables.
>>
>> So I filed bug 1728[1] and Eric Hodel was kind enough to point me to this
>> mailing list.
>>
>> It seems that "gem --format-executable" should default to "true" because
>> the binaries created ?have the name of the "ruby" executable embedded in
>> them (in the #! at the top).
>
> I would like to make --format-executable the default for 1.4+. ?It seems
> many more people are running multiple versions of ruby these days.

Hoo-rah! Strongly in favor.

jeremy

From drbrain at segment7.net  Wed Jul 22 18:06:40 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Wed, 22 Jul 2009 15:06:40 -0700
Subject: [Rubygems-developers] 'gem update' Fails,
	but 'gem update X' 	Works
In-Reply-To: <735c8b860907220658rb82a7efsf20b84eee3a43038@mail.gmail.com>
References: <735c8b860907150909p47165eeenf78d542d5dd1ff0f@mail.gmail.com>
	<71166b3b0907211505r4d6a558fgb5162e525a37ddee@mail.gmail.com>
	<735c8b860907211524l2324d007gbe0c21b9b0071763@mail.gmail.com>
	<71166b3b0907212144y141ab21fr296af75d981af4ba@mail.gmail.com>
	<735c8b860907220658rb82a7efsf20b84eee3a43038@mail.gmail.com>
Message-ID: <29397D20-CF08-48DE-9942-024DB7253760@segment7.net>

On Jul 22, 2009, at 06:58, Randy Parker wrote:

> Louis asked:
>> Please provide the output of sudo gem update X --debug
>> ...
>> so in that way we can see if: the problems are the quick
>> indexes, the contact to the mirror, unpacking issues, etc.
>
>
> ~ $ sudo gem update --debug
> Exception `NameError' at
> /Library/Ruby/Site/1.8/rubygems/command_manager.rb:161 - uninitialized
> constant Gem::Commands::UpdateCommand
> Exception `Gem::LoadError' at /Library/Ruby/Site/1.8/rubygems.rb:827  
> - Could
> not find RubyGem test-unit (>= 0)
>
> Updating installed gems
> Updating crack
> Exception `Errno::EPIPE' at
> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/ 
> 1.8/net/protocol.rb:175
> - Broken pipe
> Exception `Gem::RemoteFetcher::FetchError' at
> /Library/Ruby/Site/1.8/rubygems/remote_fetcher.rb:172 -  
> Errno::EPIPE: Broken
> pipe (http://gems.rubyforge.org/quick/Marshal.4.8/crack-0.1.4.gemspec.rz 
> )
> Exception `Gem::RemoteFetcher::FetchError' at
> /Library/Ruby/Site/1.8/rubygems/spec_fetcher.rb:76 - Errno::EPIPE:  
> Broken
> pipe (http://gems.rubyforge.org/quick/Marshal.4.8/crack-0.1.4.gemspec.rz 
> )
> Exception `Gem::GemNotFoundException' at
> /Library/Ruby/Site/1.8/rubygems/dependency_installer.rb:200 - could  
> not find
> gem crack locally or in a repository
> ERROR:  While executing gem ... (Gem::GemNotFoundException)
>    could not find gem crack locally or in a repository
> /Library/Ruby/Site/1.8/rubygems/dependency_installer.rb:200:in
> `find_spec_by_name_and_version'
> /Library/Ruby/Site/1.8/rubygems/dependency_installer.rb:213:in  
> `install'
> /Library/Ruby/Site/1.8/rubygems/commands/update_command.rb:87:in  
> `execute'
> /Library/Ruby/Site/1.8/rubygems/commands/update_command.rb:81:in  
> `each'
> /Library/Ruby/Site/1.8/rubygems/commands/update_command.rb:81:in  
> `execute'
> /Library/Ruby/Site/1.8/rubygems/command.rb:257:in `invoke'
> /Library/Ruby/Site/1.8/rubygems/command_manager.rb:132:in  
> `process_args'
> /Library/Ruby/Site/1.8/rubygems/command_manager.rb:102:in `run'
> /Library/Ruby/Site/1.8/rubygems/gem_runner.rb:58:in `run'
> /usr/bin/gem:21
> ~ $

Looks like you have some kind of network issue.  Can you run:

$ sudo gem update -V --debug
Exception `NameError' at /Library/Ruby/Site/1.8/rubygems/ 
command_manager.rb:161 - uninitialized constant  
Gem::Commands::UpdateCommand
Exception `Gem::LoadError' at /Library/Ruby/Site/1.8/rubygems.rb:827 -  
Could not find RubyGem test-unit (>= 0)

Updating installed gems
GET 200 OK: http://gems.rubyforge.org/latest_specs.4.8.gz
Updating ZenTest
Installing gem ZenTest-4.1.3
Downloading gem ZenTest-4.1.3.gem
Exception `EOFError' at /System/Library/Frameworks/Ruby.framework/ 
Versions/1.8/usr/lib/ruby/1.8/net/protocol.rb:133 - end of file reached
Exception `EOFError' at /System/Library/Frameworks/Ruby.framework/ 
Versions/1.8/usr/lib/ruby/1.8/net/protocol.rb:120 - end of file reached
connection reset after 2 requests, retrying
GET 302 Found: http://gems.rubyforge.org/gems/ZenTest-4.1.3.gem
GET 200 OK: http://gems.rubyforge.vm.bytemark.co.uk/gems/ZenTest-4.1.3.gem
[...installs OK]

From thewoolleyman at gmail.com  Wed Jul 22 18:08:40 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Wed, 22 Jul 2009 15:08:40 -0700
Subject: [Rubygems-developers] Two failures in trunk
In-Reply-To: <81985D11-25C8-42D9-BF73-64645AAECBED@segment7.net>
References: <4A5B43CD.6090400@gmail.com>
	<71166b3b0907130745j4fe0e323q8d164e5d5970535b@mail.gmail.com> 
	<71166b3b0907152104n4808c75bybf8472f203f274a5@mail.gmail.com> 
	<81985D11-25C8-42D9-BF73-64645AAECBED@segment7.net>
Message-ID: <e3af97510907221508k7e153489v688b2713a449593c@mail.gmail.com>

On Wed, Jul 22, 2009 at 2:42 PM, Eric Hodel <drbrain at segment7.net> wrote:

> I made the release from the 1_3 branch
>

Why?  Was there a reason not to merge to trunk before release?  Is it merged
now?  Where should I run tests/write patches against?

From drbrain at segment7.net  Wed Jul 22 18:58:20 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Wed, 22 Jul 2009 15:58:20 -0700
Subject: [Rubygems-developers] Two failures in trunk
In-Reply-To: <e3af97510907221508k7e153489v688b2713a449593c@mail.gmail.com>
References: <4A5B43CD.6090400@gmail.com>
	<71166b3b0907130745j4fe0e323q8d164e5d5970535b@mail.gmail.com>
	<71166b3b0907152104n4808c75bybf8472f203f274a5@mail.gmail.com>
	<81985D11-25C8-42D9-BF73-64645AAECBED@segment7.net>
	<e3af97510907221508k7e153489v688b2713a449593c@mail.gmail.com>
Message-ID: <4A696C35-3245-4F41-B1C7-DA84FD939647@segment7.net>

On Jul 22, 2009, at 15:08, Chad Woolley wrote:
> On Wed, Jul 22, 2009 at 2:42 PM, Eric Hodel <drbrain at segment7.net>  
> wrote:
>> I made the release from the 1_3 branch
>
> Why?

I dropped support for ruby 1.8.5 in trunk and didn't want to do that  
officially in a maintenance release.

> Was there a reason not to merge to trunk before release?  Is it merged
> now?

Changes were made in trunk and merged to the branch as needed.  No  
development should be done on a branch.

> Where should I run tests/write patches against?

trunk, unless I post a mail like "1.3.5 soon" that specifically  
mentions a branch.

From jbarnette at gmail.com  Wed Jul 22 23:12:52 2009
From: jbarnette at gmail.com (John Barnette)
Date: Wed, 22 Jul 2009 20:12:52 -0700
Subject: [Rubygems-developers] --format-executable should be the default
In-Reply-To: <90681D1F-18E7-469C-81C7-D880C113E616@segment7.net>
References: <1095EA03-2A0C-451F-84FF-1A9B024687A6@gmail.com>
	<90681D1F-18E7-469C-81C7-D880C113E616@segment7.net>
Message-ID: <D825D6A6-A276-4E32-A5B2-655DA8CCAC01@gmail.com>

On Jul 22, 2009, at 2:52 PM, Eric Hodel wrote:
> I would like to make --format-executable the default for 1.4+.  It  
> seems many more people are running multiple versions of ruby these  
> days.

I'm very much in favor of this. Looks like it's a super-simple change,  
but let me know if you want a patch instead of doing it yourself.


~ j.


From thewoolleyman at gmail.com  Thu Jul 23 06:18:38 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Thu, 23 Jul 2009 03:18:38 -0700
Subject: [Rubygems-developers] Trunk version is wrong
Message-ID: <e3af97510907230318w94fbdd1mec707a2fe4bccfbd@mail.gmail.com>

So (I almost hesitate to ask), shouldn't the trunk version not be 1.3.4
anymore?  I still believe >1.3.5 would be most appropriate (and kind to API
clients), but I'm positive 1.3.4 is incorrect.  I would fix it, but last
time I touched the version I was reprimanded.  You're missing the date in
History.txt too...

By the way, here is the silly hackery required to support my regression
tests against the RubyGems API, because you refuse to allow a bump of
unreleased versions:

http://github.com/thewoolleyman/geminstaller/blob/72a2a12f57c0579dfbe3171a8a0890073269d9fd/spec/helper/test_gem_home.rb#L164

    def
self.hack_in_correct_rubygems_version_because_rubygems_refuses_to_allow_it_to_be_changed_in_trunk
      #
http://rubyforge.org/pipermail/rubygems-developers/2009-June/004749.html
      #
http://rubyforge.org/pipermail/rubygems-developers/2009-June/004750.html
      return unless rubygems_dist == 'trunk'
      correct_version = Gem::RubyGemsVersion + '.1'
      Gem.send(:remove_const,:RubyGemsVersion)
      Gem.send(:remove_const,:VERSION)
      Gem.const_set(:RubyGemsVersion, correct_version)
      Gem.const_set(:VERSION, correct_version)
    end

Persistently yours,
-- Chad

From thewoolleyman at gmail.com  Thu Jul 23 06:15:59 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Thu, 23 Jul 2009 03:15:59 -0700
Subject: [Rubygems-developers] --format-executable should be the default
In-Reply-To: <90681D1F-18E7-469C-81C7-D880C113E616@segment7.net>
References: <1095EA03-2A0C-451F-84FF-1A9B024687A6@gmail.com> 
	<90681D1F-18E7-469C-81C7-D880C113E616@segment7.net>
Message-ID: <e3af97510907230315i7d4eaadbr4e9729b860136ca5@mail.gmail.com>

On Wed, Jul 22, 2009 at 2:52 PM, Eric Hodel <drbrain at segment7.net> wrote:

> I would like to make --format-executable the default for 1.4+.  It seems
> many more people are running multiple versions of ruby these days.
>

I've committed this to trunk in rev 2278.  Didn't write any new tests, but I
tried it out and it worked for me.  Please test and report any problems.

Thanks,
-- Chad

From randy.j.parker at gmail.com  Thu Jul 23 10:01:43 2009
From: randy.j.parker at gmail.com (Randy Parker)
Date: Thu, 23 Jul 2009 10:01:43 -0400
Subject: [Rubygems-developers] 'gem update' Fails,
	but 'gem update X' 	Works
In-Reply-To: <29397D20-CF08-48DE-9942-024DB7253760@segment7.net>
References: <735c8b860907150909p47165eeenf78d542d5dd1ff0f@mail.gmail.com>
	<71166b3b0907211505r4d6a558fgb5162e525a37ddee@mail.gmail.com>
	<735c8b860907211524l2324d007gbe0c21b9b0071763@mail.gmail.com>
	<71166b3b0907212144y141ab21fr296af75d981af4ba@mail.gmail.com>
	<735c8b860907220658rb82a7efsf20b84eee3a43038@mail.gmail.com>
	<29397D20-CF08-48DE-9942-024DB7253760@segment7.net>
Message-ID: <735c8b860907230701u36de1f8akc9e710e0a5182d11@mail.gmail.com>

> Eric wrote:
> Looks like you have some kind of network issue
I've had the same update behavior
100% of the time for almost a month using 2 different connections
located 10 miles apart.  One is Comcast, the other is a CBeyond
T1.   And don't forget that 3 out of 4 of the guys in the Atlanta Ruby
Users Group that responded to my IRC request for confirmation reported
the exact same problem.  The probability of a network problem whose
sole manifestation is "gem update" is very low.

 > Can you run:  $ sudo gem update -V --debug

~ $ gem --version
1.3.5


~ $ sudo gem update -V --debug
Password:
Exception `NameError' at
/Library/Ruby/Site/1.8/rubygems/command_manager.rb:161 - uninitialized
constant Gem::Commands::UpdateCommand
Exception `Gem::LoadError' at /Library/Ruby/Site/1.8/rubygems.rb:827 - Could
not find RubyGem test-unit (>= 0)

Updating installed gems
GET 200 OK: http://gems.rubyforge.org/latest_specs.4.8.gz
GET 200 OK: http://gems.github.com/latest_specs.4.8.gz
Updating crack
Exception `Errno::EPIPE' at
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/protocol.rb:175
- Broken pipe
Exception `Gem::RemoteFetcher::FetchError' at
/Library/Ruby/Site/1.8/rubygems/remote_fetcher.rb:172 - Errno::EPIPE: Broken
pipe (http://gems.rubyforge.org/quick/Marshal.4.8/crack-0.1.4.gemspec.rz)
Exception `Gem::RemoteFetcher::FetchError' at
/Library/Ruby/Site/1.8/rubygems/spec_fetcher.rb:76 - Errno::EPIPE: Broken
pipe (http://gems.rubyforge.org/quick/Marshal.4.8/crack-0.1.4.gemspec.rz)
Error fetching remote data: Errno::EPIPE: Broken pipe (
http://gems.rubyforge.org/quick/Marshal.4.8/crack-0.1.4.gemspec.rz)
Falling back to local-only install
Exception `Gem::GemNotFoundException' at
/Library/Ruby/Site/1.8/rubygems/dependency_installer.rb:200 - could not find
gem crack locally or in a repository
ERROR:  While executing gem ... (Gem::GemNotFoundException)
    could not find gem crack locally or in a repository
/Library/Ruby/Site/1.8/rubygems/dependency_installer.rb:200:in
`find_spec_by_name_and_version'
/Library/Ruby/Site/1.8/rubygems/dependency_installer.rb:213:in `install'
/Library/Ruby/Site/1.8/rubygems/commands/update_command.rb:87:in `execute'
/Library/Ruby/Site/1.8/rubygems/commands/update_command.rb:81:in `each'
/Library/Ruby/Site/1.8/rubygems/commands/update_command.rb:81:in `execute'
/Library/Ruby/Site/1.8/rubygems/command.rb:257:in `invoke'
/Library/Ruby/Site/1.8/rubygems/command_manager.rb:132:in `process_args'
/Library/Ruby/Site/1.8/rubygems/command_manager.rb:102:in `run'
/Library/Ruby/Site/1.8/rubygems/gem_runner.rb:58:in `run'
/usr/bin/gem:21


-- Randy Parker
http://mobiledyne.com

From devnull+rubygems-ci at pivotallabs.com  Thu Jul 23 17:56:20 2009
From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com)
Date: Thu, 23 Jul 2009 21:56:20 +0000
Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2279 failed
Message-ID: <4a68dc84b9a7b_6358..fdbdd5b849a8@ci.pivotallabs.com.tmail>

The build failed.

CHANGES
-------
New revision 2279 detected
Revision 2279 committed by drbrain on 2009-07-23 21:45:38
Bump version from branch release.
  M /trunk/README
  M /trunk/Rakefile
  M /trunk/lib/rubygems.rb



TEST FAILURES AND ERRORS
-----------------------
Name: test_generate_index(TestGemIndexer)
Type: Failure
Message: Expected "<?xml version=\"1.0\"?>\n<rss version=\"2.0\">\n  <channel>\n    <title>ExampleForge gems</title>\n    <link>http://example.com</link>\n    <description>Recently released gems from http://example.com</description>\n    <generator>RubyGems v1.3.4</generator>\n    <docs>http://cyber.law.harvard.edu/rss/rss.html</docs>\n    <item>\n      <title>a-2</title>\n      <description>\n&lt;pre&gt;This is a test description&lt;/pre&gt;\n      </description>\n      <author>example at example.com (A User)</author>\n      <guid>a-2</guid>\n      <enclosure url=\"http://gems.example.com/gems/a-2.gem\"\n                 length=\"3072\" type=\"application/octet-stream\" />\n      <pubDate>Thu, 23 Jul 2009 00:00:00 +0000</pubDate>\n      <link>http://example.com</link>\n    </item>\n    <item>\n      <title>a-3.a</title>\n      <description>\n&lt;pre&gt;This is a test description&lt;/pre&gt;\n      </description>\n      <author>example at example.com (A User)</author>\n      <guid>
 a-3.a</guid>\n      <enclosure url=\"http://gems.example.com/gems/a-3.a.gem\"\n                 length=\"3072\" type=\"application/octet-stream\" />\n      <pubDate>Thu, 23 Jul 2009 00:00:00 +0000</pubDate>\n      <link>http://example.com</link>\n    </item>\n    <item>\n      <title>a_evil-9</title>\n      <description>\n&lt;pre&gt;This is a test description&lt;/pre&gt;\n      </description>\n      <author>example at example.com (A User)</author>\n      <guid>a_evil-9</guid>\n      <enclosure url=\"http://gems.example.com/gems/a_evil-9.gem\"\n                 length=\"3072\" type=\"application/octet-stream\" />\n      <pubDate>Thu, 23 Jul 2009 00:00:00 +0000</pubDate>\n      <link>http://example.com</link>\n    </item>\n    <item>\n      <title>b-2</title>\n      <description>\n&lt;pre&gt;This is a test description&lt;/pre&gt;\n      </description>\n      <author>example at example.com (A User)</author>\n      <guid>b-2</guid>\n      <enclosure url=\"http://gems.example.com/gems/
 b-2.gem\"\n                 length=\"3072\" type=\"application/octet-stream\" />\n      <pubDate>Thu, 23 Jul 2009 00:00:00 +0000</pubDate>\n      <link>http://example.com</link>\n    </item>\n    <item>\n      <title>c-1.2</title>\n      <description>\n&lt;pre&gt;This is a test description&lt;/pre&gt;\n      </description>\n      <author>example at example.com (A User)</author>\n      <guid>c-1.2</guid>\n      <enclosure url=\"http://gems.example.com/gems/c-1.2.gem\"\n                 length=\"3072\" type=\"application/octet-stream\" />\n      <pubDate>Thu, 23 Jul 2009 00:00:00 +0000</pubDate>\n      <link>http://example.com</link>\n    </item>\n    <item>\n      <title>d-2.0.a</title>\n      <description>\n&lt;pre&gt;This is a test description&lt;/pre&gt;\n      </description>\n      <author>example at example.com (A User)</author>\n      <guid>d-2.0.a</guid>\n      <enclosure url=\"http://gems.example.com/gems/d-2.0.a.gem\"\n                 length=\"3072\" type=\"application/oc
 tet-stream\" />\n      <pubDate>Thu, 23 Jul 2009 00:00:00 +0000</pubDate>\n      <link>http://example.com</link>\n    </item>\n    <item>\n      <title>d-2.0.b</title>\n      <description>\n&lt;pre&gt;This is a test description&lt;/pre&gt;\n      </description>\n      <author>example at example.com (A User)</author>\n      <guid>d-2.0.b</guid>\n      <enclosure url=\"http://gems.example.com/gems/d-2.0.b.gem\"\n                 length=\"3072\" type=\"application/octet-stream\" />\n      <pubDate>Thu, 23 Jul 2009 00:00:00 +0000</pubDate>\n      <link>http://example.com</link>\n    </item>\n    <item>\n      <title>pl-1-x86-linux</title>\n      <description>\n&lt;pre&gt;This is a test description&lt;/pre&gt;\n      </description>\n      <author>example at example.com (A User)</author>\n      <guid>pl-1-x86-linux</guid>\n      <enclosure url=\"http://gems.example.com/gems/pl-1-x86-linux.gem\"\n                 length=\"3072\" type=\"application/octet-stream\" />\n      <pubDate>Thu, 2
 3 Jul 2009 00:00:00 +0000</pubDate>\n      <link>http://example.com</link>\n    </item>\n    <item>\n      <title>a-1</title>\n      <description>\n&lt;pre&gt;This line is really, really long.  So long, in fact, that it is more than\neighty characters long!  The purpose of this line is for testing wrapping\nbehavior because sometimes people don't wrap their text to eighty characters. \nWithout the wrapping, the text might not look good in the RSS feed.\n\nAlso, a list:\n  * An entry that's actually kind of sort\n  * an entry that's really long, which will probably get wrapped funny. \nThat's ok, somebody wasn't thinking straight when they made it more than\neighty characters.&lt;/pre&gt;\n      </description>\n      <author>example at example.com (Example), example2 at example.com (Example2)</author>\n      <guid>a-1</guid>\n      <enclosure url=\"http://gems.example.com/gems/a-1.gem\"\n                 length=\"3584\" type=\"application/octet-stream\" />\n      <pubDate>Wed, 22 J
 ul 2009 00:00:00 +0000</pubDate>\n      <link>http://a.example.com</link>\n    </item>\n  </channel>\n</rss>\n", not "<?xml version=\"1.0\"?>\n<rss version=\"2.0\">\n  <channel>\n    <title>ExampleForge gems</title>\n    <link>http://example.com</link>\n    <description>Recently released gems from http://example.com</description>\n    <generator>RubyGems v1.3.5</generator>\n    <docs>http://cyber.law.harvard.edu/rss/rss.html</docs>\n    <item>\n      <title>a-2</title>\n      <description>\n&lt;pre&gt;This is a test description&lt;/pre&gt;\n      </description>\n      <author>example at example.com (A User)</author>\n      <guid>a-2</guid>\n      <enclosure url=\"http://gems.example.com/gems/a-2.gem\"\n                 length=\"3072\" type=\"application/octet-stream\" />\n      <pubDate>Thu, 23 Jul 2009 00:00:00 +0000</pubDate>\n      <link>http://example.com</link>\n    </item>\n    <item>\n      <title>a-3.a</title>\n      <description>\n&lt;pre&gt;This is a test description&
 lt;/pre&gt;\n      </description>\n      <author>example at example.com (A User)</author>\n      <guid>a-3.a</guid>\n      <enclosure url=\"http://gems.example.com/gems/a-3.a.gem\"\n                 length=\"3072\" type=\"application/octet-stream\" />\n      <pubDate>Thu, 23 Jul 2009 00:00:00 +0000</pubDate>\n      <link>http://example.com</link>\n    </item>\n    <item>\n      <title>a_evil-9</title>\n      <description>\n&lt;pre&gt;This is a test description&lt;/pre&gt;\n      </description>\n      <author>example at example.com (A User)</author>\n      <guid>a_evil-9</guid>\n      <enclosure url=\"http://gems.example.com/gems/a_evil-9.gem\"\n                 length=\"3072\" type=\"application/octet-stream\" />\n      <pubDate>Thu, 23 Jul 2009 00:00:00 +0000</pubDate>\n      <link>http://example.com</link>\n    </item>\n    <item>\n      <title>b-2</title>\n      <description>\n&lt;pre&gt;This is a test description&lt;/pre&gt;\n      </description>\n      <author>example at example
 .com (A User)</author>\n      <guid>b-2</guid>\n      <enclosure url=\"http://gems.example.com/gems/b-2.gem\"\n                 length=\"3072\" type=\"application/octet-stream\" />\n      <pubDate>Thu, 23 Jul 2009 00:00:00 +0000</pubDate>\n      <link>http://example.com</link>\n    </item>\n    <item>\n      <title>c-1.2</title>\n      <description>\n&lt;pre&gt;This is a test description&lt;/pre&gt;\n      </description>\n      <author>example at example.com (A User)</author>\n      <guid>c-1.2</guid>\n      <enclosure url=\"http://gems.example.com/gems/c-1.2.gem\"\n                 length=\"3072\" type=\"application/octet-stream\" />\n      <pubDate>Thu, 23 Jul 2009 00:00:00 +0000</pubDate>\n      <link>http://example.com</link>\n    </item>\n    <item>\n      <title>d-2.0.a</title>\n      <description>\n&lt;pre&gt;This is a test description&lt;/pre&gt;\n      </description>\n      <author>example at example.com (A User)</author>\n      <guid>d-2.0.a</guid>\n      <enclosure url=
 \"http://gems.example.com/gems/d-2.0.a.gem\"\n                 length=\"3072\" type=\"application/octet-stream\" />\n      <pubDate>Thu, 23 Jul 2009 00:00:00 +0000</pubDate>\n      <link>http://example.com</link>\n    </item>\n    <item>\n      <title>d-2.0.b</title>\n      <description>\n&lt;pre&gt;This is a test description&lt;/pre&gt;\n      </description>\n      <author>example at example.com (A User)</author>\n      <guid>d-2.0.b</guid>\n      <enclosure url=\"http://gems.example.com/gems/d-2.0.b.gem\"\n                 length=\"3072\" type=\"application/octet-stream\" />\n      <pubDate>Thu, 23 Jul 2009 00:00:00 +0000</pubDate>\n      <link>http://example.com</link>\n    </item>\n    <item>\n      <title>pl-1-x86-linux</title>\n      <description>\n&lt;pre&gt;This is a test description&lt;/pre&gt;\n      </description>\n      <author>example at example.com (A User)</author>\n      <guid>pl-1-x86-linux</guid>\n      <enclosure url=\"http://gems.example.com/gems/pl-1-x86-linux
 .gem\"\n                 length=\"3072\" type=\"application/octet-stream\" />\n      <pubDate>Thu, 23 Jul 2009 00:00:00 +0000</pubDate>\n      <link>http://example.com</link>\n    </item>\n    <item>\n      <title>a-1</title>\n      <description>\n&lt;pre&gt;This line is really, really long.  So long, in fact, that it is more than\neighty characters long!  The purpose of this line is for testing wrapping\nbehavior because sometimes people don't wrap their text to eighty characters. \nWithout the wrapping, the text might not look good in the RSS feed.\n\nAlso, a list:\n  * An entry that's actually kind of sort\n  * an entry that's really long, which will probably get wrapped funny. \nThat's ok, somebody wasn't thinking straight when they made it more than\neighty characters.&lt;/pre&gt;\n      </description>\n      <author>example at example.com (Example), example2 at example.com (Example2)</author>\n      <guid>a-1</guid>\n      <enclosure url=\"http://gems.example.com/gems/a-1.ge
 m\"\n                 length=\"3584\" type=\"application/octet-stream\" />\n      <pubDate>Wed, 22 Jul 2009 00:00:00 +0000</pubDate>\n      <link>http://a.example.com</link>\n    </item>\n  </channel>\n</rss>\n".

./test/test_gem_indexer.rb:300




See http://ci.pivotallabs.com:3333/builds/RubyGems/2279 for details.

From drbrain at segment7.net  Thu Jul 23 18:00:15 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Thu, 23 Jul 2009 15:00:15 -0700
Subject: [Rubygems-developers] 'gem update' Fails,
	but 'gem update X' 	Works
In-Reply-To: <735c8b860907230701u36de1f8akc9e710e0a5182d11@mail.gmail.com>
References: <735c8b860907150909p47165eeenf78d542d5dd1ff0f@mail.gmail.com>
	<71166b3b0907211505r4d6a558fgb5162e525a37ddee@mail.gmail.com>
	<735c8b860907211524l2324d007gbe0c21b9b0071763@mail.gmail.com>
	<71166b3b0907212144y141ab21fr296af75d981af4ba@mail.gmail.com>
	<735c8b860907220658rb82a7efsf20b84eee3a43038@mail.gmail.com>
	<29397D20-CF08-48DE-9942-024DB7253760@segment7.net>
	<735c8b860907230701u36de1f8akc9e710e0a5182d11@mail.gmail.com>
Message-ID: <F839CC1C-6D7A-41AD-8500-8437584ADBF0@segment7.net>

On Jul 23, 2009, at 07:01, Randy Parker wrote:

>> Eric wrote:
>> Looks like you have some kind of network issue
> I've had the same update behavior
> 100% of the time for almost a month using 2 different connections
> located 10 miles apart.  One is Comcast, the other is a CBeyond
> T1.   And don't forget that 3 out of 4 of the guys in the Atlanta Ruby
> Users Group that responded to my IRC request for confirmation reported
> the exact same problem.  The probability of a network problem whose
> sole manifestation is "gem update" is very low.

At the same time, only four people out of thousands (or more?) are  
reporting this issue...

>> Can you run:  $ sudo gem update -V --debug
>
> ~ $ gem --version
> 1.3.5
>
>
> ~ $ sudo gem update -V --debug
> Password:
> Exception `NameError' at
> /Library/Ruby/Site/1.8/rubygems/command_manager.rb:161 - uninitialized
> constant Gem::Commands::UpdateCommand
> Exception `Gem::LoadError' at /Library/Ruby/Site/1.8/rubygems.rb:827  
> - Could
> not find RubyGem test-unit (>= 0)
>
> Updating installed gems
> GET 200 OK: http://gems.rubyforge.org/latest_specs.4.8.gz
> GET 200 OK: http://gems.github.com/latest_specs.4.8.gz
> Updating crack
> Exception `Errno::EPIPE' at
> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/ 
> 1.8/net/protocol.rb:175
> - Broken pipe
> Exception `Gem::RemoteFetcher::FetchError' at
> /Library/Ruby/Site/1.8/rubygems/remote_fetcher.rb:172 -  
> Errno::EPIPE: Broken
> pipe (http://gems.rubyforge.org/quick/Marshal.4.8/crack-0.1.4.gemspec.rz 
> )

Does adding Errno::EPIPE to line 340 of lib/rubygems/remote_fetcher.rb  
in #request help?  Looks like somebody is closing the connection on  
you early...

From randy.j.parker at gmail.com  Thu Jul 23 18:11:59 2009
From: randy.j.parker at gmail.com (Randy Parker)
Date: Thu, 23 Jul 2009 18:11:59 -0400
Subject: [Rubygems-developers] 'gem update' Fails,
	but 'gem update X' 	Works
In-Reply-To: <F839CC1C-6D7A-41AD-8500-8437584ADBF0@segment7.net>
References: <735c8b860907150909p47165eeenf78d542d5dd1ff0f@mail.gmail.com>
	<71166b3b0907211505r4d6a558fgb5162e525a37ddee@mail.gmail.com>
	<735c8b860907211524l2324d007gbe0c21b9b0071763@mail.gmail.com>
	<71166b3b0907212144y141ab21fr296af75d981af4ba@mail.gmail.com>
	<735c8b860907220658rb82a7efsf20b84eee3a43038@mail.gmail.com>
	<29397D20-CF08-48DE-9942-024DB7253760@segment7.net>
	<735c8b860907230701u36de1f8akc9e710e0a5182d11@mail.gmail.com>
	<F839CC1C-6D7A-41AD-8500-8437584ADBF0@segment7.net>
Message-ID: <735c8b860907231511n33bbbe48v1d54ac19aa8873e3@mail.gmail.com>

Yes, adding Errno::EPIPE seems to have completely solved the problem!(barring
very unlikely coincidences)

Thank you !

For reference, the line # was correct for my "remote_fetcher.rb" file from
June 3, 2009 in rubygems 1.3.5
My lines 337 - 340 are now:

    # HACK work around EOFError bug in Net::HTTP
    # NOTE Errno::ECONNABORTED raised a lot on Windows, and make impossible
    # to install gems.
    rescue EOFError, Errno::ECONNABORTED, Errno::ECONNRESET, Errno::EPIPE

- Randy

On Thu, Jul 23, 2009 at 6:00 PM, Eric Hodel <drbrain at segment7.net> wrote:

> On Jul 23, 2009, at 07:01, Randy Parker wrote:
>
>  Eric wrote:
>>> Looks like you have some kind of network issue
>>>
>> I've had the same update behavior
>> 100% of the time for almost a month using 2 different connections
>> located 10 miles apart.  One is Comcast, the other is a CBeyond
>> T1.   And don't forget that 3 out of 4 of the guys in the Atlanta Ruby
>> Users Group that responded to my IRC request for confirmation reported
>> the exact same problem.  The probability of a network problem whose
>> sole manifestation is "gem update" is very low.
>>
>
> At the same time, only four people out of thousands (or more?) are
> reporting this issue...
>
>  Can you run:  $ sudo gem update -V --debug
>>>
>>
>> ~ $ gem --version
>> 1.3.5
>>
>>
>> ~ $ sudo gem update -V --debug
>> Password:
>> Exception `NameError' at
>> /Library/Ruby/Site/1.8/rubygems/command_manager.rb:161 - uninitialized
>> constant Gem::Commands::UpdateCommand
>> Exception `Gem::LoadError' at /Library/Ruby/Site/1.8/rubygems.rb:827 -
>> Could
>> not find RubyGem test-unit (>= 0)
>>
>> Updating installed gems
>> GET 200 OK: http://gems.rubyforge.org/latest_specs.4.8.gz
>> GET 200 OK: http://gems.github.com/latest_specs.4.8.gz
>> Updating crack
>> Exception `Errno::EPIPE' at
>>
>> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/protocol.rb:175
>> - Broken pipe
>> Exception `Gem::RemoteFetcher::FetchError' at
>> /Library/Ruby/Site/1.8/rubygems/remote_fetcher.rb:172 - Errno::EPIPE:
>> Broken
>> pipe (http://gems.rubyforge.org/quick/Marshal.4.8/crack-0.1.4.gemspec.rz)
>>
>
> Does adding Errno::EPIPE to line 340 of lib/rubygems/remote_fetcher.rb in
> #request help?  Looks like somebody is closing the connection on you
> early...
>
> _______________________________________________
> Rubygems-developers mailing list
> http://rubyforge.org/projects/rubygems
> Rubygems-developers at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubygems-developers
>



-- 
http://mobiledyne.com

From devnull+rubygems-ci at pivotallabs.com  Thu Jul 23 18:42:37 2009
From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com)
Date: Thu, 23 Jul 2009 22:42:37 +0000
Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2280 fixed
Message-ID: <4a68e75db3ad7_6358..fdbdd5b8410a8@ci.pivotallabs.com.tmail>

The build has been fixed.

CHANGES
-------
New revision 2280 detected
Revision 2280 committed by thewoolleyman on 2009-07-23 22:34:24
fix broken test
  M /trunk/test/test_gem_indexer.rb



See http://ci.pivotallabs.com:3333/builds/RubyGems/2280 for details.

From noreply at rubyforge.org  Fri Jul 24 03:44:54 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 24 Jul 2009 03:44:54 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26740 ] outdated
	rubygems/rubygems_version.rb still exists on Leopard default
	ruby install even though it was removed in 1.3.5
Message-ID: <20090724074454.A9B7C18581E5@rubyforge.org>

Bugs item #26740, was opened at 2009-07-24 00:44
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26740&group_id=126

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Chad Woolley (thewoolleyman)
Assigned to: Nobody (None)
Summary: outdated rubygems/rubygems_version.rb still exists on Leopard default ruby install even though it was removed in 1.3.5

Initial Comment:
Does system installer not delete old files?  If someone happens to load this file, they get a warning, then get the wrong version.

Can't we just move the version back into this file and avoid the issue altogether?

chadmac:1.8 woolley$ pwd
/Library/Ruby/Site/1.8
chadmac:1.8 woolley$ grep RubyGemsVersion rubygems.rb 
  RubyGemsVersion = VERSION = '1.3.5'
chadmac:1.8 woolley$ ls rubygems/rubygems_version.rb 
rubygems/rubygems_version.rb


chadmac:~ woolley$ irb
>> Gem::RubyGemsVersion
=> "1.3.5"
>> require 'rubygems/rubygems_version'
/Library/Ruby/Site/1.8/rubygems/rubygems_version.rb:12: warning: already initialized constant RubyGemsVersion
/Library/Ruby/Site/1.8/rubygems/rubygems_version.rb:17: warning: already initialized constant VERSION
=> true
>> Gem::RubyGemsVersion
=> "1.3.4"


chadmac:~ woolley$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.5
  - RUBY VERSION: 1.8.6 (2008-08-11 patchlevel 287) [universal-darwin9.0]
  - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8
  - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - universal-darwin-9
  - GEM PATHS:
     - /Library/Ruby/Gems/1.8
     - /Users/woolley/.gem/ruby/1.8
     - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://gems.rubyforge.org", "http://gems.github.com"]
  - REMOTE SOURCES:
     - http://gems.rubyforge.org
     - http://gems.github.com




----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26740&group_id=126

From thewoolleyman at gmail.com  Fri Jul 24 03:48:04 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Fri, 24 Jul 2009 00:48:04 -0700
Subject: [Rubygems-developers] Hoe'ify broke Gem::RubyGemsVersion for me
In-Reply-To: <4D2D0870-A20F-4C32-A637-326BACD77F07@segment7.net>
References: <e3af97510906121748s1e53a74l90cdb2d633f5c226@mail.gmail.com> 
	<e3af97510906142030k5ac459c8v3264fd1e2d6bd07b@mail.gmail.com> 
	<FCA3A605-436F-46A9-A77F-DE3BE7BB39F4@segment7.net>
	<4D2D0870-A20F-4C32-A637-326BACD77F07@segment7.net>
Message-ID: <e3af97510907240048l672d2344n7bd5098a31ab0f4@mail.gmail.com>

On Fri, Jun 19, 2009 at 3:24 PM, Eric Hodel <drbrain at segment7.net> wrote:

> On Jun 19, 2009, at 15:02, Eric Hodel wrote:
>
>> On Jun 14, 2009, at 20:30, Chad Woolley wrote:
>>
>>> On Fri, Jun 12, 2009 at 5:48 PM, Chad Woolley<thewoolleyman at gmail.com>
>>> wrote:
>>>
>>>> Any reason we can't put the version back in
>>>> rubygems/rubygems_version.rb?
>>>>
>>>
>>> Assuming not, I fixed this too...
>>>
>>
>> The streamlined Rakefile doesn't need this extra file.
>>
>
> I reverted this change.  I don't see why RubyGems needs to require an extra
> file.  If you need to extract a version without require 'rubygems' you can
> use standard tools like grep.
>

Here's one reason why it needs this file:

http://rubyforge.org/tracker/index.php?func=detail&aid=26740&group_id=126&atid=575

From noreply at rubyforge.org  Fri Jul 24 14:23:12 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 24 Jul 2009 14:23:12 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26740 ] outdated
	rubygems/rubygems_version.rb still exists on Leopard default
	ruby install even though it was removed in 1.3.5
Message-ID: <20090724182312.C8C33185811A@rubyforge.org>

Bugs item #26740, was opened at 2009-07-24 00:44
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26740&group_id=126

Category: None
Group: None
>Status: Closed
>Resolution: Rejected
Priority: 3
Submitted By: Chad Woolley (thewoolleyman)
Assigned to: Nobody (None)
Summary: outdated rubygems/rubygems_version.rb still exists on Leopard default ruby install even though it was removed in 1.3.5

Initial Comment:
Does system installer not delete old files?  If someone happens to load this file, they get a warning, then get the wrong version.

Can't we just move the version back into this file and avoid the issue altogether?

chadmac:1.8 woolley$ pwd
/Library/Ruby/Site/1.8
chadmac:1.8 woolley$ grep RubyGemsVersion rubygems.rb 
  RubyGemsVersion = VERSION = '1.3.5'
chadmac:1.8 woolley$ ls rubygems/rubygems_version.rb 
rubygems/rubygems_version.rb


chadmac:~ woolley$ irb
>> Gem::RubyGemsVersion
=> "1.3.5"
>> require 'rubygems/rubygems_version'
/Library/Ruby/Site/1.8/rubygems/rubygems_version.rb:12: warning: already initialized constant RubyGemsVersion
/Library/Ruby/Site/1.8/rubygems/rubygems_version.rb:17: warning: already initialized constant VERSION
=> true
>> Gem::RubyGemsVersion
=> "1.3.4"


chadmac:~ woolley$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.5
  - RUBY VERSION: 1.8.6 (2008-08-11 patchlevel 287) [universal-darwin9.0]
  - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8
  - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - universal-darwin-9
  - GEM PATHS:
     - /Library/Ruby/Gems/1.8
     - /Users/woolley/.gem/ruby/1.8
     - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://gems.rubyforge.org", "http://gems.github.com"]
  - REMOTE SOURCES:
     - http://gems.rubyforge.org
     - http://gems.github.com




----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26740&group_id=126

From noreply at rubyforge.org  Fri Jul 24 15:01:06 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 24 Jul 2009 15:01:06 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26740 ] outdated
	rubygems/rubygems_version.rb still exists on Leopard default
	ruby install even though it was removed in 1.3.5
Message-ID: <20090724190106.C29A11D787F1@rubyforge.org>

Bugs item #26740, was opened at 2009-07-24 00:44
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26740&group_id=126

Category: None
Group: None
>Status: Open
Resolution: Rejected
Priority: 3
Submitted By: Chad Woolley (thewoolleyman)
Assigned to: Nobody (None)
Summary: outdated rubygems/rubygems_version.rb still exists on Leopard default ruby install even though it was removed in 1.3.5

Initial Comment:
Does system installer not delete old files?  If someone happens to load this file, they get a warning, then get the wrong version.

Can't we just move the version back into this file and avoid the issue altogether?

chadmac:1.8 woolley$ pwd
/Library/Ruby/Site/1.8
chadmac:1.8 woolley$ grep RubyGemsVersion rubygems.rb 
  RubyGemsVersion = VERSION = '1.3.5'
chadmac:1.8 woolley$ ls rubygems/rubygems_version.rb 
rubygems/rubygems_version.rb


chadmac:~ woolley$ irb
>> Gem::RubyGemsVersion
=> "1.3.5"
>> require 'rubygems/rubygems_version'
/Library/Ruby/Site/1.8/rubygems/rubygems_version.rb:12: warning: already initialized constant RubyGemsVersion
/Library/Ruby/Site/1.8/rubygems/rubygems_version.rb:17: warning: already initialized constant VERSION
=> true
>> Gem::RubyGemsVersion
=> "1.3.4"


chadmac:~ woolley$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.5
  - RUBY VERSION: 1.8.6 (2008-08-11 patchlevel 287) [universal-darwin9.0]
  - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8
  - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - universal-darwin-9
  - GEM PATHS:
     - /Library/Ruby/Gems/1.8
     - /Users/woolley/.gem/ruby/1.8
     - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://gems.rubyforge.org", "http://gems.github.com"]
  - REMOTE SOURCES:
     - http://gems.rubyforge.org
     - http://gems.github.com




----------------------------------------------------------------------

>Comment By: Chad Woolley (thewoolleyman)
Date: 2009-07-24 12:01

Message:
Rejected with no comment, huh?  Classy.

You ignore the fact that there are actual bugs:  

* RubyGems 1.3.5 introduced an obsolete file on the Leopard distribution
* This file contains an outdated and conflicting RubyGems version number
* If any existing rubygems API clients happen to still load this file, they will get a warning, and rubygems will subsequently report the incorrect and outdated version.
* There is a bug with the system update command that does not delete old files, at least on the default Leopard install.


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26740&group_id=126

From thewoolleyman at gmail.com  Fri Jul 24 15:02:06 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Fri, 24 Jul 2009 12:02:06 -0700
Subject: [Rubygems-developers] Please do not reject valid bugs
Message-ID: <e3af97510907241202x65fbc478rd2df0f22851df2c4@mail.gmail.com>

Ryan, please do not reject valid bugs without comment:


http://rubyforge.org/tracker/index.php?func=detail&aid=26740&group_id=126&atid=575

From noreply at rubyforge.org  Fri Jul 24 15:16:26 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 24 Jul 2009 15:16:26 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26740 ] outdated
	rubygems/rubygems_version.rb still exists on Leopard default
	ruby install even though it was removed in 1.3.5
Message-ID: <20090724191627.104371858121@rubyforge.org>

Bugs item #26740, was opened at 2009-07-24 00:44
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26740&group_id=126

Category: None
Group: None
Status: Open
Resolution: Rejected
Priority: 3
Submitted By: Chad Woolley (thewoolleyman)
Assigned to: Nobody (None)
Summary: outdated rubygems/rubygems_version.rb still exists on Leopard default ruby install even though it was removed in 1.3.5

Initial Comment:
Does system installer not delete old files?  If someone happens to load this file, they get a warning, then get the wrong version.

Can't we just move the version back into this file and avoid the issue altogether?

chadmac:1.8 woolley$ pwd
/Library/Ruby/Site/1.8
chadmac:1.8 woolley$ grep RubyGemsVersion rubygems.rb 
  RubyGemsVersion = VERSION = '1.3.5'
chadmac:1.8 woolley$ ls rubygems/rubygems_version.rb 
rubygems/rubygems_version.rb


chadmac:~ woolley$ irb
>> Gem::RubyGemsVersion
=> "1.3.5"
>> require 'rubygems/rubygems_version'
/Library/Ruby/Site/1.8/rubygems/rubygems_version.rb:12: warning: already initialized constant RubyGemsVersion
/Library/Ruby/Site/1.8/rubygems/rubygems_version.rb:17: warning: already initialized constant VERSION
=> true
>> Gem::RubyGemsVersion
=> "1.3.4"


chadmac:~ woolley$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.5
  - RUBY VERSION: 1.8.6 (2008-08-11 patchlevel 287) [universal-darwin9.0]
  - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8
  - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - universal-darwin-9
  - GEM PATHS:
     - /Library/Ruby/Gems/1.8
     - /Users/woolley/.gem/ruby/1.8
     - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://gems.rubyforge.org", "http://gems.github.com"]
  - REMOTE SOURCES:
     - http://gems.rubyforge.org
     - http://gems.github.com




----------------------------------------------------------------------

>Comment By: Daniel Berger (djberg96)
Date: 2009-07-24 12:16

Message:
I agree, the rubygems_version.rb file should be deleted on update if possible. Mind you, I've never heard of anyone explicitly require'ing that file, so it strikes me as a very low priority item, but it's still something we could fix.

Regards,

Dan

----------------------------------------------------------------------

Comment By: Chad Woolley (thewoolleyman)
Date: 2009-07-24 12:01

Message:
Rejected with no comment, huh?  Classy.

You ignore the fact that there are actual bugs:  

* RubyGems 1.3.5 introduced an obsolete file on the Leopard distribution
* This file contains an outdated and conflicting RubyGems version number
* If any existing rubygems API clients happen to still load this file, they will get a warning, and rubygems will subsequently report the incorrect and outdated version.
* There is a bug with the system update command that does not delete old files, at least on the default Leopard install.


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26740&group_id=126

From noreply at rubyforge.org  Fri Jul 24 16:51:03 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 24 Jul 2009 16:51:03 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26740 ] outdated
	rubygems/rubygems_version.rb still exists on Leopard default
	ruby install even though it was removed in 1.3.5
Message-ID: <20090724205103.543DD1858133@rubyforge.org>

Bugs item #26740, was opened at 2009-07-24 03:44
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26740&group_id=126

Category: None
Group: None
Status: Open
Resolution: Rejected
Priority: 3
Submitted By: Chad Woolley (thewoolleyman)
Assigned to: Nobody (None)
Summary: outdated rubygems/rubygems_version.rb still exists on Leopard default ruby install even though it was removed in 1.3.5

Initial Comment:
Does system installer not delete old files?  If someone happens to load this file, they get a warning, then get the wrong version.

Can't we just move the version back into this file and avoid the issue altogether?

chadmac:1.8 woolley$ pwd
/Library/Ruby/Site/1.8
chadmac:1.8 woolley$ grep RubyGemsVersion rubygems.rb 
  RubyGemsVersion = VERSION = '1.3.5'
chadmac:1.8 woolley$ ls rubygems/rubygems_version.rb 
rubygems/rubygems_version.rb


chadmac:~ woolley$ irb
>> Gem::RubyGemsVersion
=> "1.3.5"
>> require 'rubygems/rubygems_version'
/Library/Ruby/Site/1.8/rubygems/rubygems_version.rb:12: warning: already initialized constant RubyGemsVersion
/Library/Ruby/Site/1.8/rubygems/rubygems_version.rb:17: warning: already initialized constant VERSION
=> true
>> Gem::RubyGemsVersion
=> "1.3.4"


chadmac:~ woolley$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.5
  - RUBY VERSION: 1.8.6 (2008-08-11 patchlevel 287) [universal-darwin9.0]
  - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8
  - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - universal-darwin-9
  - GEM PATHS:
     - /Library/Ruby/Gems/1.8
     - /Users/woolley/.gem/ruby/1.8
     - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://gems.rubyforge.org", "http://gems.github.com"]
  - REMOTE SOURCES:
     - http://gems.rubyforge.org
     - http://gems.github.com




----------------------------------------------------------------------

Comment By: John Trupiano (jtrupiano)
Date: 2009-07-24 16:51

Message:
I can confirm the odd behavior on a default Leopard install:

john-mbp:1.8 john$ irb
irb(main):001:0> Gem::RubyGemsVersion
=> "1.3.5"
irb(main):002:0> require 'rubygems/rubygems_version'
/Library/Ruby/Site/1.8/rubygems/rubygems_version.rb:12: warning: already initialized constant RubyGemsVersion
/Library/Ruby/Site/1.8/rubygems/rubygems_version.rb:17: warning: already initialized constant VERSION
=> true
irb(main):003:0> Gem::RubyGemsVersion
=> "1.3.4"

-John

----------------------------------------------------------------------

Comment By: Daniel Berger (djberg96)
Date: 2009-07-24 15:16

Message:
I agree, the rubygems_version.rb file should be deleted on update if possible. Mind you, I've never heard of anyone explicitly require'ing that file, so it strikes me as a very low priority item, but it's still something we could fix.

Regards,

Dan

----------------------------------------------------------------------

Comment By: Chad Woolley (thewoolleyman)
Date: 2009-07-24 15:01

Message:
Rejected with no comment, huh?  Classy.

You ignore the fact that there are actual bugs:  

* RubyGems 1.3.5 introduced an obsolete file on the Leopard distribution
* This file contains an outdated and conflicting RubyGems version number
* If any existing rubygems API clients happen to still load this file, they will get a warning, and rubygems will subsequently report the incorrect and outdated version.
* There is a bug with the system update command that does not delete old files, at least on the default Leopard install.


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26740&group_id=126

From noreply at rubyforge.org  Fri Jul 24 16:53:36 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 24 Jul 2009 16:53:36 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26740 ] outdated
	rubygems/rubygems_version.rb still exists on Leopard default
	ruby install even though it was removed in 1.3.5
Message-ID: <20090724205336.84980185812F@rubyforge.org>

Bugs item #26740, was opened at 2009-07-24 00:44
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26740&group_id=126

Category: None
Group: None
Status: Open
Resolution: Rejected
Priority: 3
Submitted By: Chad Woolley (thewoolleyman)
Assigned to: Nobody (None)
Summary: outdated rubygems/rubygems_version.rb still exists on Leopard default ruby install even though it was removed in 1.3.5

Initial Comment:
Does system installer not delete old files?  If someone happens to load this file, they get a warning, then get the wrong version.

Can't we just move the version back into this file and avoid the issue altogether?

chadmac:1.8 woolley$ pwd
/Library/Ruby/Site/1.8
chadmac:1.8 woolley$ grep RubyGemsVersion rubygems.rb 
  RubyGemsVersion = VERSION = '1.3.5'
chadmac:1.8 woolley$ ls rubygems/rubygems_version.rb 
rubygems/rubygems_version.rb


chadmac:~ woolley$ irb
>> Gem::RubyGemsVersion
=> "1.3.5"
>> require 'rubygems/rubygems_version'
/Library/Ruby/Site/1.8/rubygems/rubygems_version.rb:12: warning: already initialized constant RubyGemsVersion
/Library/Ruby/Site/1.8/rubygems/rubygems_version.rb:17: warning: already initialized constant VERSION
=> true
>> Gem::RubyGemsVersion
=> "1.3.4"


chadmac:~ woolley$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.5
  - RUBY VERSION: 1.8.6 (2008-08-11 patchlevel 287) [universal-darwin9.0]
  - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8
  - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - universal-darwin-9
  - GEM PATHS:
     - /Library/Ruby/Gems/1.8
     - /Users/woolley/.gem/ruby/1.8
     - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://gems.rubyforge.org", "http://gems.github.com"]
  - REMOTE SOURCES:
     - http://gems.rubyforge.org
     - http://gems.github.com




----------------------------------------------------------------------

>Comment By: Chad Woolley (thewoolleyman)
Date: 2009-07-24 13:53

Message:
Agreed, a very low priority.  I was only requiring explicitly as a side effect of my regression tests - normally you should rely on rubygems to require what it needs.

However, this should probably get turned into a bug with the system install command, because it isn't deleting old files.  This could come back to bite us in a more serious way in the future.

----------------------------------------------------------------------

Comment By: John Trupiano (jtrupiano)
Date: 2009-07-24 13:51

Message:
I can confirm the odd behavior on a default Leopard install:

john-mbp:1.8 john$ irb
irb(main):001:0> Gem::RubyGemsVersion
=> "1.3.5"
irb(main):002:0> require 'rubygems/rubygems_version'
/Library/Ruby/Site/1.8/rubygems/rubygems_version.rb:12: warning: already initialized constant RubyGemsVersion
/Library/Ruby/Site/1.8/rubygems/rubygems_version.rb:17: warning: already initialized constant VERSION
=> true
irb(main):003:0> Gem::RubyGemsVersion
=> "1.3.4"

-John

----------------------------------------------------------------------

Comment By: Daniel Berger (djberg96)
Date: 2009-07-24 12:16

Message:
I agree, the rubygems_version.rb file should be deleted on update if possible. Mind you, I've never heard of anyone explicitly require'ing that file, so it strikes me as a very low priority item, but it's still something we could fix.

Regards,

Dan

----------------------------------------------------------------------

Comment By: Chad Woolley (thewoolleyman)
Date: 2009-07-24 12:01

Message:
Rejected with no comment, huh?  Classy.

You ignore the fact that there are actual bugs:  

* RubyGems 1.3.5 introduced an obsolete file on the Leopard distribution
* This file contains an outdated and conflicting RubyGems version number
* If any existing rubygems API clients happen to still load this file, they will get a warning, and rubygems will subsequently report the incorrect and outdated version.
* There is a bug with the system update command that does not delete old files, at least on the default Leopard install.


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26740&group_id=126

From drbrain at segment7.net  Fri Jul 24 16:58:16 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Fri, 24 Jul 2009 13:58:16 -0700
Subject: [Rubygems-developers] --format-executable should be the default
In-Reply-To: <e3af97510907230315i7d4eaadbr4e9729b860136ca5@mail.gmail.com>
References: <1095EA03-2A0C-451F-84FF-1A9B024687A6@gmail.com>
	<90681D1F-18E7-469C-81C7-D880C113E616@segment7.net>
	<e3af97510907230315i7d4eaadbr4e9729b860136ca5@mail.gmail.com>
Message-ID: <88D81C45-8C7F-4A69-9BD6-CFEDB0DA2FC2@segment7.net>

On Jul 23, 2009, at 03:15, Chad Woolley wrote:

> On Wed, Jul 22, 2009 at 2:52 PM, Eric Hodel <drbrain at segment7.net>  
> wrote:
>
>> I would like to make --format-executable the default for 1.4+.  It  
>> seems
>> many more people are running multiple versions of ruby these days.
>>
>
> I've committed this to trunk in rev 2278.  Didn't write any new  
> tests, but I
> tried it out and it worked for me.  Please test and report any  
> problems.

Please revert this change.  There wasn't even 24 hours of discussion  
on this before you made it.

When the feature was introduced there was a fairly lengthy discussion  
with the JRuby folks.  I doubt they've even had a change to check this  
list.

While this is a low-traffic list, not everybody can read it every  
minute of the day.  I'd rather wait a week to ensure that any  
objections can be met, especially when the default change affects  
multiple ruby implementations.

From drbrain at segment7.net  Fri Jul 24 16:58:21 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Fri, 24 Jul 2009 13:58:21 -0700
Subject: [Rubygems-developers] Please do not reject valid bugs
In-Reply-To: <e3af97510907241202x65fbc478rd2df0f22851df2c4@mail.gmail.com>
References: <e3af97510907241202x65fbc478rd2df0f22851df2c4@mail.gmail.com>
Message-ID: <FD6B2214-A18A-4571-B0DD-365FC2E16EE1@segment7.net>

On Jul 24, 2009, at 12:02, Chad Woolley wrote:

> Ryan, please do not reject valid bugs without comment:
>
> http://rubyforge.org/tracker/index.php?func=detail&aid=26740&group_id=126&atid=575

It's not a valid bug.  RubyGems required this file as an  
implementation detail. If you're requiring this file you're doing it  
wrong.

RubyGems probably should delete files that no longer exist, but I  
don't see that as any priority.

From luislavena at gmail.com  Fri Jul 24 17:08:29 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Fri, 24 Jul 2009 18:08:29 -0300
Subject: [Rubygems-developers] Please do not reject valid bugs
In-Reply-To: <FD6B2214-A18A-4571-B0DD-365FC2E16EE1@segment7.net>
References: <e3af97510907241202x65fbc478rd2df0f22851df2c4@mail.gmail.com> 
	<FD6B2214-A18A-4571-B0DD-365FC2E16EE1@segment7.net>
Message-ID: <71166b3b0907241408t6c09389am226daf78a240806c@mail.gmail.com>

On Fri, Jul 24, 2009 at 5:58 PM, Eric Hodel<drbrain at segment7.net> wrote:
> On Jul 24, 2009, at 12:02, Chad Woolley wrote:
>
>> Ryan, please do not reject valid bugs without comment:
>>
>>
>> http://rubyforge.org/tracker/index.php?func=detail&aid=26740&group_id=126&atid=575
>
> It's not a valid bug. ?RubyGems required this file as an implementation
> detail. If you're requiring this file you're doing it wrong.
>
> RubyGems probably should delete files that no longer exist, but I don't see
> that as any priority.

For the record, even old setup.rb left files as left overs when
installed using ruby setup.rb install

Removal of old scripts like gem_server required manual patching of the
setup.rb file.

-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

From noreply at rubyforge.org  Sat Jul 25 18:10:48 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sat, 25 Jul 2009 18:10:48 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26752 ] system update should
	delete obsolete files
Message-ID: <20090725221048.7AF6118581EF@rubyforge.org>

Bugs item #26752, was opened at 2009-07-25 15:10
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26752&group_id=126

Category: RubyGems installer (setup.rb)
Group: None
Status: Open
Resolution: None
Priority: 1
Submitted By: Chad Woolley (thewoolleyman)
Assigned to: Chad Woolley (thewoolleyman)
Summary: system update should delete obsolete files

Initial Comment:
For example, rubygems/rubygems_version.rb

See: http://rubyforge.org/tracker/index.php?func=detail&aid=26740&group_id=126&atid=575

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26752&group_id=126

From thewoolleyman at gmail.com  Sat Jul 25 18:11:27 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Sat, 25 Jul 2009 15:11:27 -0700
Subject: [Rubygems-developers] Please do not reject valid bugs
In-Reply-To: <71166b3b0907241408t6c09389am226daf78a240806c@mail.gmail.com>
References: <e3af97510907241202x65fbc478rd2df0f22851df2c4@mail.gmail.com> 
	<FD6B2214-A18A-4571-B0DD-365FC2E16EE1@segment7.net>
	<71166b3b0907241408t6c09389am226daf78a240806c@mail.gmail.com>
Message-ID: <e3af97510907251511r47be58b7oc42451160fe35838@mail.gmail.com>

On Fri, Jul 24, 2009 at 2:08 PM, Luis Lavena <luislavena at gmail.com> wrote:

> On Fri, Jul 24, 2009 at 5:58 PM, Eric Hodel<drbrain at segment7.net> wrote:
> > It's not a valid bug.  RubyGems required this file as an implementation
> > detail. If you're requiring this file you're doing it wrong.
>

To be clear, I had already fixed my code.  This was merely reporting a bug
in the rubygems update --system command.  Yes, I was doing it wrong (lazily
putting the require in app rather than test code), and I originally
identified an incorrect solution (putting the file back), but this
*discussion* has resulted in a correct low-priority ticket, assigned to me,
to track the specific issue (a bug is a bug):

http://rubyforge.org/tracker/index.php?func=detail&aid=26752&group_id=126&atid=575

For the record, even old setup.rb left files as left overs when
> installed using ruby setup.rb install
>
> Removal of old scripts like gem_server required manual patching of the
> setup.rb file.
>

OK.  Now I understand.  Fixable, but low-priority.

Thanks...
-- Chad

From noreply at rubyforge.org  Sat Jul 25 18:22:56 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sat, 25 Jul 2009 18:22:56 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Patches-26754 ] Make
	--format-executable the default
Message-ID: <20090725222256.F043C18581EC@rubyforge.org>

Patches item #26754, was opened at 2009-07-25 15:22
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=577&aid=26754&group_id=126

Category: `gem install`
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Chad Woolley (thewoolleyman)
Assigned to: Chad Woolley (thewoolleyman)
Summary: Make --format-executable the default

Initial Comment:
See thread:  http://rubyforge.org/pipermail/rubygems-developers/2009-July/004803.html

Patch attached.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=577&aid=26754&group_id=126

From thewoolleyman at gmail.com  Sat Jul 25 18:32:51 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Sat, 25 Jul 2009 15:32:51 -0700
Subject: [Rubygems-developers] --format-executable should be the default
In-Reply-To: <88D81C45-8C7F-4A69-9BD6-CFEDB0DA2FC2@segment7.net>
References: <1095EA03-2A0C-451F-84FF-1A9B024687A6@gmail.com> 
	<90681D1F-18E7-469C-81C7-D880C113E616@segment7.net>
	<e3af97510907230315i7d4eaadbr4e9729b860136ca5@mail.gmail.com> 
	<88D81C45-8C7F-4A69-9BD6-CFEDB0DA2FC2@segment7.net>
Message-ID: <e3af97510907251532o77c8b166n93f984046e00105a@mail.gmail.com>

On Fri, Jul 24, 2009 at 1:58 PM, Eric Hodel <drbrain at segment7.net> wrote:

> On Jul 23, 2009, at 03:15, Chad Woolley wrote:
>
>> On Wed, Jul 22, 2009 at 2:52 PM, Eric Hodel <drbrain at segment7.net> wrote:
>>
>>> I would like to make --format-executable the default for 1.4+.  It seems
>>> many more people are running multiple versions of ruby these days.
>>>
>> I've committed this to trunk in rev 2278.  Didn't write any new tests, but
>> I
>> tried it out and it worked for me.  Please test and report any problems.
>>
>  Please revert this change.  There wasn't even 24 hours of discussion on
> this before you made it.
>
> When the feature was introduced there was a fairly lengthy discussion with
> the JRuby folks.  I doubt they've even had a change to check this list.
>
> While this is a low-traffic list, not everybody can read it every minute of
> the day.  I'd rather wait a week to ensure that any objections can be met,
> especially when the default change affects multiple ruby implementations.
>

OK.  Reverted and made a patch:
http://rubyforge.org/tracker/index.php?func=detail&aid=26754&group_id=126&atid=577
- I thought when you said "I would like" it meant "make it so".

I'd like to get feedback from JRuby or anyone else about required changes to
this, because this is a blocker to multiple MRI interpreters coexisting
[1].  Also, I'm pretty sure there's a bug in the existing code [2]

Thanks,
-- Chad

[1] http://github.com/thewoolleyman/bootstrap-ruby
[2] incorrect symbol name :no_format_executable in
Gem::Commands::UpdateCommand#do_rubygems_update line 142.

From noreply at rubyforge.org  Mon Jul 27 19:34:56 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Mon, 27 Jul 2009 19:34:56 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Patches-26769 ] Refactor
	Gem::Version to remove Part and reduce object allocations
	from 35 to 5
Message-ID: <20090727233457.12B481D780F2@rubyforge.org>

Patches item #26769, was opened at 2009-07-27 19:34
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=577&aid=26769&group_id=126

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Yehuda Katz (wycats)
Assigned to: Nobody (None)
Summary: Refactor Gem::Version to remove Part and reduce object allocations from 35 to 5

Initial Comment:
This patch simplifies the creation of Gem::Version objects by removing the need for Gem::Part (and storing the parts in an Array), lazy-evaluating details as needed, storing the release parts in a separate Array calculated at initialization time, and using a backing Array for Gem::Version instead of a String (so unmarshalling is faster, since it doesn't need to parse the parts again).

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=577&aid=26769&group_id=126

From noreply at rubyforge.org  Wed Jul 29 17:20:45 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Wed, 29 Jul 2009 17:20:45 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Patches-26790 ] Patch to support
	MagLev
Message-ID: <20090729212045.DD83D1858125@rubyforge.org>

Patches item #26790, was opened at 2009-07-29 14:20
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=577&aid=26790&group_id=126

Category: other
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Peter McLain (pbm)
Assigned to: Nobody (None)
Summary: Patch to support MagLev

Initial Comment:
Hi,

  I'm working on the MagLev project at GemStone, and am currently trying to get RubyGems working under MagLev.  Apparently, MagLev processes zip streams the same way Rubinius does.  The following one-line patch (also attached) allows RubyGems 1.3.5 to work under MagLev.

Thanks,


diff --git a/src/external/rubygems-1.3.5/lib/rubygems/package/tar_input.rb b/src/external/rubygems-1.3.5/lib/rubygems/package/tar_input.rb
index 9f90102..cb1bbe7 100644
--- a/src/external/rubygems-1.3.5/lib/rubygems/package/tar_input.rb
+++ b/src/external/rubygems-1.3.5/lib/rubygems/package/tar_input.rb
@@ -199,7 +199,7 @@ class Gem::Package::TarInput
   # times.  And that's the way it is.
 
   def zipped_stream(entry)
-    if defined? Rubinius then
+    if defined? Rubinius or defined? Maglev then
       zis = Zlib::GzipReader.new entry
       dis = zis.read
       is = StringIO.new(dis)





----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=577&aid=26790&group_id=126

From noreply at rubyforge.org  Wed Jul 29 19:59:57 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Wed, 29 Jul 2009 19:59:57 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26792 ] uses gem even when an
	install fails
Message-ID: <20090729235957.A73D018581DE@rubyforge.org>

Bugs item #26792, was opened at 2009-07-29 23:59
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26792&group_id=126

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Roger Pack (rogerdpack)
Assigned to: Nobody (None)
Summary: uses gem even when an install fails

Initial Comment:
Appears that in 1.9, at least

if you install a gem, and the installation fails

then you run 
require 'gemname'
it still loads it--in its very broken state.

At least that's about what I figure from scratching my head at this circumstance:

C:\dev\ruby\downloads\ruby-debug\pkg>gem search linecache -b

*** LOCAL GEMS ***

mark-moseley-linecache (0.5.2)
# note the lack of linecache -- removing mark-moseley-linecache seems to not affect the results, either

*** REMOTE GEMS ***

linecache (0.43)
mark-moseley-linecache (0.5.2)

C:\dev\ruby\downloads\ruby-debug\pkg>gem install linecache
Building native extensions.  This could take a while...
ERROR:  Error installing linecache:
        ERROR: Failed to build gem native extension.

c:/installs/ruby_trunk_installed/bin/ruby.exe extconf.rb
Can't handle 1.9.x yet
*** extconf.rb failed ***
...

C:\dev\ruby\downloads\ruby-debug\pkg>gem search linecache

*** LOCAL GEMS ***

mark-moseley-linecache (0.5.2)

C:\dev\ruby\downloads\ruby-debug\pkg>irb
irb(main):001:0> require 'ruby-debug'
LoadError: no such file to load -- c:/installs/ruby_trunk_installed/lib/ruby/gems/1.9.1/gems/linecache-0.43/lib/../lib/trace_nums # note that it's using the linecache-0.43 that just failed
        from c:/installs/ruby_trunk_installed/lib/ruby/gems/1.9.1/gems/linecache-0.43/lib/tracelines.rb:12:in `require'
        from c:/installs/ruby_trunk_installed/lib/ruby/gems/1.9.1/gems/linecache-0.43/lib/tracelines.rb:12:in `rescue in <module:TraceLineNumbers>'
        from c:/installs/ruby_trunk_installed/lib/ruby/gems/1.9.1/gems/linecache-0.43/lib/tracelines.rb:8:in `<module:TraceLineNumbers>'
        from c:/installs/ruby_trunk_installed/lib/ruby/gems/1.9.1/gems/linecache-0.43/lib/tracelines.rb:6:in `<top (required)>'
        from c:/installs/ruby_trunk_installed/lib/ruby/gems/1.9.1/gems/linecache-0.43/lib/linecache.rb:63:in `require'
        from c:/installs/ruby_trunk_installed/lib/ruby/gems/1.9.1/gems/linecache-0.43/lib/linecache.rb:63:in `<top (required)>'
        from c:/installs/ruby_trunk_installed/lib/ruby/gems/1.9.1/gems/mark-moseley-ruby-debug-base-0.11.6/lib/ruby-debug-base.rb:3:in `require'
        from c:/installs/ruby_trunk_installed/lib/ruby/gems/1.9.1/gems/mark-moseley-ruby-debug-base-0.11.6/lib/ruby-debug-base.rb:3:in `<top (required)>'
        from c:/installs/ruby_trunk_installed/lib/ruby/gems/1.9.1/gems/ruby-debug-0.11/cli/ruby-debug.rb:5:in `require'
        from c:/installs/ruby_trunk_installed/lib/ruby/gems/1.9.1/gems/ruby-debug-0.11/cli/ruby-debug.rb:5:in `<top (required)>'
        from (irb):1:in `require'
        from (irb):1
        from c:/installs/ruby_trunk_installed/bin/irb.bat:20:in `<main>'

Thanks!

[gem v 1.3.5, ruby 1.9.2 trunk]

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26792&group_id=126

From noreply at rubyforge.org  Thu Jul 30 10:27:37 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 30 Jul 2009 10:27:37 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26801 ] "gem update --system"
	breaks rubygems under Windows XP using
	"mingw32-ruby-1.9.1-wxruby-2.0.0-setup.exe"
Message-ID: <20090730142738.0F97C18581E1@rubyforge.org>

Bugs item #26801, was opened at 2009-07-30 16:27
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26801&group_id=126

Category: `gem` commands (other)
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Rainer Wolf (rainer42)
Assigned to: Nobody (None)
Summary: "gem update --system" breaks rubygems under Windows XP using "mingw32-ruby-1.9.1-wxruby-2.0.0-setup.exe"

Initial Comment:
I have a Ruby installation with wxRuby on Windows XP using this installer:

  mingw32-ruby-1.9.1-wxruby-2.0.0-setup.exe 

I typed 

 gem -v 

and found out that I was rubygems 1.3.1. So I typed: 

 gem update --system 

This was the result: 

---begin--- 
Updating RubyGems 
Updating rubygems-update 
Successfully installed rubygems-update-1.3.5 
:0:Warning: Gem::SourceIndex#search support for String patterns is 
deprecated 
Updating RubyGems to 1.3.5 
Installing RubyGems 1.3.5 
c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/ 
config_file. 
rb:39:in `new': wrong number of arguments (5 for 4) (ArgumentError) 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/config_file.rb:39:in `<class:ConfigFile>' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/config_file.rb:12:in `<top (required)>' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/gem_runner.rb:8:in `require' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/gem_runner.rb:8:in `<top (required)>' 
        from setup.rb:25:in `require' 
        from setup.rb:25:in `<main>' 
RubyGems system software updated 
--end-- 

Now, when I type 

  gem -v 

I get this: 

---begin--- 
c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/ 
config_file. 
rb:39:in `new': wrong number of arguments (5 for 4) (ArgumentError) 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/config_file.rb:39:in `<class:ConfigFile>' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/config_file.rb:12:in `<top (required)>' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/gem_runner.rb:8:in `require' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/gem_runner.rb:8:in `<top (required)>' 
        from c:/ruby/bin/gem.bat:17:in `require' 
        from c:/ruby/bin/gem.bat:17:in `<main>' 
---end--- 

Does this mean I have broken rubygems on mingw32 by typing "gem update 
--system"? Typing 

  "gem search wxruby-ruby19 --remote" 

or trying to install a gem - any gem - gives me the same argument 
error.

Since rubygems was unusable, I uninstalled and reinstalled Ruby, using rubygems 1.3.1 for the time being. So this bug is not "lethal".

Kind regards,

Rainer

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26801&group_id=126

From noreply at rubyforge.org  Thu Jul 30 10:40:53 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 30 Jul 2009 10:40:53 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26801 ] "gem update --system"
	breaks rubygems under Windows XP using
	"mingw32-ruby-1.9.1-wxruby-2.0.0-setup.exe"
Message-ID: <20090730144053.499CF1D780E7@rubyforge.org>

Bugs item #26801, was opened at 2009-07-30 11:27
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26801&group_id=126

Category: `gem` commands (other)
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Rainer Wolf (rainer42)
Assigned to: Nobody (None)
>Summary: "gem update --system" breaks rubygems under Windows XP using "mingw32-ruby-1.9.1-wxruby-2.0.0-setup.exe"

Initial Comment:
I have a Ruby installation with wxRuby on Windows XP using this installer:

  mingw32-ruby-1.9.1-wxruby-2.0.0-setup.exe 

I typed 

 gem -v 

and found out that I was rubygems 1.3.1. So I typed: 

 gem update --system 

This was the result: 

---begin--- 
Updating RubyGems 
Updating rubygems-update 
Successfully installed rubygems-update-1.3.5 
:0:Warning: Gem::SourceIndex#search support for String patterns is 
deprecated 
Updating RubyGems to 1.3.5 
Installing RubyGems 1.3.5 
c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/ 
config_file. 
rb:39:in `new': wrong number of arguments (5 for 4) (ArgumentError) 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/config_file.rb:39:in `<class:ConfigFile>' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/config_file.rb:12:in `<top (required)>' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/gem_runner.rb:8:in `require' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/gem_runner.rb:8:in `<top (required)>' 
        from setup.rb:25:in `require' 
        from setup.rb:25:in `<main>' 
RubyGems system software updated 
--end-- 

Now, when I type 

  gem -v 

I get this: 

---begin--- 
c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/ 
config_file. 
rb:39:in `new': wrong number of arguments (5 for 4) (ArgumentError) 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/config_file.rb:39:in `<class:ConfigFile>' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/config_file.rb:12:in `<top (required)>' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/gem_runner.rb:8:in `require' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/gem_runner.rb:8:in `<top (required)>' 
        from c:/ruby/bin/gem.bat:17:in `require' 
        from c:/ruby/bin/gem.bat:17:in `<main>' 
---end--- 

Does this mean I have broken rubygems on mingw32 by typing "gem update 
--system"? Typing 

  "gem search wxruby-ruby19 --remote" 

or trying to install a gem - any gem - gives me the same argument 
error.

Since rubygems was unusable, I uninstalled and reinstalled Ruby, using rubygems 1.3.1 for the time being. So this bug is not "lethal".

Kind regards,

Rainer

----------------------------------------------------------------------

>Comment By: Luis Lavena (luislavena)
Date: 2009-07-30 11:40

Message:
When automatic installation fails, you can fall back to manual installation.

http://blog.mmediasys.com/2008/08/04/problems-with-rubygems-find-here-some-handy-tips/

Keep in mind that Ruby version built by wxRuby team is not supported and is an old patchlevel (not latest stable).

Please use proper new One-Click Ruby Installers for 1.9.1:

http://blog.mmediasys.com/2009/06/28/rubyinstaller-preview1-released/


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26801&group_id=126

From noreply at rubyforge.org  Thu Jul 30 11:09:01 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 30 Jul 2009 11:09:01 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26801 ] &quot;
	gem update --system&quot;
	breaks rubygems under Windows XP using &quot;
	mingw32-ruby-1.9.1-wxruby-2.0.0-setup.exe&quot; 
Message-ID: <20090730150901.350B81D780E7@rubyforge.org>

Bugs item #26801, was opened at 2009-07-30 16:27
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26801&group_id=126

Category: `gem` commands (other)
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Rainer Wolf (rainer42)
Assigned to: Nobody (None)
>Summary: &quot;gem update --system&quot; breaks rubygems under Windows XP using &quot;mingw32-ruby-1.9.1-wxruby-2.0.0-setup.exe&quot;

Initial Comment:
I have a Ruby installation with wxRuby on Windows XP using this installer:

  mingw32-ruby-1.9.1-wxruby-2.0.0-setup.exe 

I typed 

 gem -v 

and found out that I was rubygems 1.3.1. So I typed: 

 gem update --system 

This was the result: 

---begin--- 
Updating RubyGems 
Updating rubygems-update 
Successfully installed rubygems-update-1.3.5 
:0:Warning: Gem::SourceIndex#search support for String patterns is 
deprecated 
Updating RubyGems to 1.3.5 
Installing RubyGems 1.3.5 
c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/ 
config_file. 
rb:39:in `new': wrong number of arguments (5 for 4) (ArgumentError) 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/config_file.rb:39:in `<class:ConfigFile>' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/config_file.rb:12:in `<top (required)>' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/gem_runner.rb:8:in `require' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/gem_runner.rb:8:in `<top (required)>' 
        from setup.rb:25:in `require' 
        from setup.rb:25:in `<main>' 
RubyGems system software updated 
--end-- 

Now, when I type 

  gem -v 

I get this: 

---begin--- 
c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/ 
config_file. 
rb:39:in `new': wrong number of arguments (5 for 4) (ArgumentError) 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/config_file.rb:39:in `<class:ConfigFile>' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/config_file.rb:12:in `<top (required)>' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/gem_runner.rb:8:in `require' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/gem_runner.rb:8:in `<top (required)>' 
        from c:/ruby/bin/gem.bat:17:in `require' 
        from c:/ruby/bin/gem.bat:17:in `<main>' 
---end--- 

Does this mean I have broken rubygems on mingw32 by typing "gem update 
--system"? Typing 

  "gem search wxruby-ruby19 --remote" 

or trying to install a gem - any gem - gives me the same argument 
error.

Since rubygems was unusable, I uninstalled and reinstalled Ruby, using rubygems 1.3.1 for the time being. So this bug is not "lethal".

Kind regards,

Rainer

----------------------------------------------------------------------

>Comment By: Rainer Wolf (rainer42)
Date: 2009-07-30 17:09

Message:
Hello Luis,

thanks for the quick reply. Two questions about this:

Up until now, I never ever had a problem with updating 
rubygems. In your opinion, is it wise to do a manual 
installation of rubygems as described in your first link?

Second: Thanks for the link to the proper installer, but I 
have used p129 before. Couldn't get the wxRuby gem to work 
with that under Windows XP:

http://www.ruby-forum.com/topic/187872#new

So I switched to p0 with the unsupported installer mentioned 
above. Is your installer of p129 known to work with the 
wxRuby gem? 

----------------------------------------------------------------------

Comment By: Luis Lavena (luislavena)
Date: 2009-07-30 16:40

Message:
When automatic installation fails, you can fall back to manual installation.

http://blog.mmediasys.com/2008/08/04/problems-with-rubygems-find-here-some-handy-tips/

Keep in mind that Ruby version built by wxRuby team is not supported and is an old patchlevel (not latest stable).

Please use proper new One-Click Ruby Installers for 1.9.1:

http://blog.mmediasys.com/2009/06/28/rubyinstaller-preview1-released/


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26801&group_id=126

From noreply at rubyforge.org  Thu Jul 30 11:13:33 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 30 Jul 2009 11:13:33 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26801 ] &quot;
	gem update --system&quot;
	breaks rubygems under Windows XP using &quot;
	mingw32-ruby-1.9.1-wxruby-2.0.0-setup.exe&quot; 
Message-ID: <20090730151333.985561D780E7@rubyforge.org>

Bugs item #26801, was opened at 2009-07-30 11:27
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26801&group_id=126

Category: `gem` commands (other)
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Rainer Wolf (rainer42)
Assigned to: Nobody (None)
Summary: &quot;gem update --system&quot; breaks rubygems under Windows XP using &quot;mingw32-ruby-1.9.1-wxruby-2.0.0-setup.exe&quot;

Initial Comment:
I have a Ruby installation with wxRuby on Windows XP using this installer:

  mingw32-ruby-1.9.1-wxruby-2.0.0-setup.exe 

I typed 

 gem -v 

and found out that I was rubygems 1.3.1. So I typed: 

 gem update --system 

This was the result: 

---begin--- 
Updating RubyGems 
Updating rubygems-update 
Successfully installed rubygems-update-1.3.5 
:0:Warning: Gem::SourceIndex#search support for String patterns is 
deprecated 
Updating RubyGems to 1.3.5 
Installing RubyGems 1.3.5 
c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/ 
config_file. 
rb:39:in `new': wrong number of arguments (5 for 4) (ArgumentError) 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/config_file.rb:39:in `<class:ConfigFile>' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/config_file.rb:12:in `<top (required)>' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/gem_runner.rb:8:in `require' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/gem_runner.rb:8:in `<top (required)>' 
        from setup.rb:25:in `require' 
        from setup.rb:25:in `<main>' 
RubyGems system software updated 
--end-- 

Now, when I type 

  gem -v 

I get this: 

---begin--- 
c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/ 
config_file. 
rb:39:in `new': wrong number of arguments (5 for 4) (ArgumentError) 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/config_file.rb:39:in `<class:ConfigFile>' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/config_file.rb:12:in `<top (required)>' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/gem_runner.rb:8:in `require' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/gem_runner.rb:8:in `<top (required)>' 
        from c:/ruby/bin/gem.bat:17:in `require' 
        from c:/ruby/bin/gem.bat:17:in `<main>' 
---end--- 

Does this mean I have broken rubygems on mingw32 by typing "gem update 
--system"? Typing 

  "gem search wxruby-ruby19 --remote" 

or trying to install a gem - any gem - gives me the same argument 
error.

Since rubygems was unusable, I uninstalled and reinstalled Ruby, using rubygems 1.3.1 for the time being. So this bug is not "lethal".

Kind regards,

Rainer

----------------------------------------------------------------------

>Comment By: Luis Lavena (luislavena)
Date: 2009-07-30 12:13

Message:
As stated by wxRuby developers, there were some C API changes or similar that made things not to work between patchlevels (in similar fashion with 1.8.7).

Is safe to manually install RubyGems on top of 1.9.1. In my experience RubyGems never installed properly on 1.9 using gem update --system.

For The official One-Click Installer we update it using ruby setup.rb and works, so should work over wxRuby installer too.

Cheers.


----------------------------------------------------------------------

Comment By: Rainer Wolf (rainer42)
Date: 2009-07-30 12:09

Message:
Hello Luis,

thanks for the quick reply. Two questions about this:

Up until now, I never ever had a problem with updating 
rubygems. In your opinion, is it wise to do a manual 
installation of rubygems as described in your first link?

Second: Thanks for the link to the proper installer, but I 
have used p129 before. Couldn't get the wxRuby gem to work 
with that under Windows XP:

http://www.ruby-forum.com/topic/187872#new

So I switched to p0 with the unsupported installer mentioned 
above. Is your installer of p129 known to work with the 
wxRuby gem? 

----------------------------------------------------------------------

Comment By: Luis Lavena (luislavena)
Date: 2009-07-30 11:40

Message:
When automatic installation fails, you can fall back to manual installation.

http://blog.mmediasys.com/2008/08/04/problems-with-rubygems-find-here-some-handy-tips/

Keep in mind that Ruby version built by wxRuby team is not supported and is an old patchlevel (not latest stable).

Please use proper new One-Click Ruby Installers for 1.9.1:

http://blog.mmediasys.com/2009/06/28/rubyinstaller-preview1-released/


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26801&group_id=126

From noreply at rubyforge.org  Thu Jul 30 15:22:21 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 30 Jul 2009 15:22:21 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26801 ] &amp; quot;
	gem update --system&amp; quot;
	breaks rubygems under Windows XP using &amp; quot;
	mingw32-ruby-1.9.1-wxruby-2.0.0-setup.exe&amp; quot; 
Message-ID: <20090730192221.C7CD618581F6@rubyforge.org>

Bugs item #26801, was opened at 2009-07-30 16:27
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26801&group_id=126

Category: `gem` commands (other)
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Rainer Wolf (rainer42)
Assigned to: Nobody (None)
>Summary: &amp;quot;gem update --system&amp;quot; breaks rubygems under Windows XP using &amp;quot;mingw32-ruby-1.9.1-wxruby-2.0.0-setup.exe&amp;quot;

Initial Comment:
I have a Ruby installation with wxRuby on Windows XP using this installer:

  mingw32-ruby-1.9.1-wxruby-2.0.0-setup.exe 

I typed 

 gem -v 

and found out that I was rubygems 1.3.1. So I typed: 

 gem update --system 

This was the result: 

---begin--- 
Updating RubyGems 
Updating rubygems-update 
Successfully installed rubygems-update-1.3.5 
:0:Warning: Gem::SourceIndex#search support for String patterns is 
deprecated 
Updating RubyGems to 1.3.5 
Installing RubyGems 1.3.5 
c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/ 
config_file. 
rb:39:in `new': wrong number of arguments (5 for 4) (ArgumentError) 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/config_file.rb:39:in `<class:ConfigFile>' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/config_file.rb:12:in `<top (required)>' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/gem_runner.rb:8:in `require' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/gem_runner.rb:8:in `<top (required)>' 
        from setup.rb:25:in `require' 
        from setup.rb:25:in `<main>' 
RubyGems system software updated 
--end-- 

Now, when I type 

  gem -v 

I get this: 

---begin--- 
c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/ 
config_file. 
rb:39:in `new': wrong number of arguments (5 for 4) (ArgumentError) 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/config_file.rb:39:in `<class:ConfigFile>' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/config_file.rb:12:in `<top (required)>' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/gem_runner.rb:8:in `require' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/gem_runner.rb:8:in `<top (required)>' 
        from c:/ruby/bin/gem.bat:17:in `require' 
        from c:/ruby/bin/gem.bat:17:in `<main>' 
---end--- 

Does this mean I have broken rubygems on mingw32 by typing "gem update 
--system"? Typing 

  "gem search wxruby-ruby19 --remote" 

or trying to install a gem - any gem - gives me the same argument 
error.

Since rubygems was unusable, I uninstalled and reinstalled Ruby, using rubygems 1.3.1 for the time being. So this bug is not "lethal".

Kind regards,

Rainer

----------------------------------------------------------------------

>Comment By: Rainer Wolf (rainer42)
Date: 2009-07-30 21:22

Message:
Thanks for the answer, Luis. You're really fast!

----------------------------------------------------------------------

Comment By: Luis Lavena (luislavena)
Date: 2009-07-30 17:13

Message:
As stated by wxRuby developers, there were some C API changes or similar that made things not to work between patchlevels (in similar fashion with 1.8.7).

Is safe to manually install RubyGems on top of 1.9.1. In my experience RubyGems never installed properly on 1.9 using gem update --system.

For The official One-Click Installer we update it using ruby setup.rb and works, so should work over wxRuby installer too.

Cheers.


----------------------------------------------------------------------

Comment By: Rainer Wolf (rainer42)
Date: 2009-07-30 17:09

Message:
Hello Luis,

thanks for the quick reply. Two questions about this:

Up until now, I never ever had a problem with updating 
rubygems. In your opinion, is it wise to do a manual 
installation of rubygems as described in your first link?

Second: Thanks for the link to the proper installer, but I 
have used p129 before. Couldn't get the wxRuby gem to work 
with that under Windows XP:

http://www.ruby-forum.com/topic/187872#new

So I switched to p0 with the unsupported installer mentioned 
above. Is your installer of p129 known to work with the 
wxRuby gem? 

----------------------------------------------------------------------

Comment By: Luis Lavena (luislavena)
Date: 2009-07-30 16:40

Message:
When automatic installation fails, you can fall back to manual installation.

http://blog.mmediasys.com/2008/08/04/problems-with-rubygems-find-here-some-handy-tips/

Keep in mind that Ruby version built by wxRuby team is not supported and is an old patchlevel (not latest stable).

Please use proper new One-Click Ruby Installers for 1.9.1:

http://blog.mmediasys.com/2009/06/28/rubyinstaller-preview1-released/


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26801&group_id=126

From noreply at rubyforge.org  Thu Jul 30 20:41:40 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 30 Jul 2009 20:41:40 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26801 ] gem update --system:
	breaks rubygems under Windows XP using &amp; quot;
	mingw32-ruby-1.9.1-wxruby-2.0.0-setup.exe&amp; quot; 
Message-ID: <20090731004140.9CAC71858120@rubyforge.org>

Bugs item #26801, was opened at 2009-07-30 07:27
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26801&group_id=126

Category: `gem` commands (other)
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Rainer Wolf (rainer42)
Assigned to: Nobody (None)
>Summary: gem update --system: breaks rubygems under Windows XP using &amp;quot;mingw32-ruby-1.9.1-wxruby-2.0.0-setup.exe&amp;quot;

Initial Comment:
I have a Ruby installation with wxRuby on Windows XP using this installer:

  mingw32-ruby-1.9.1-wxruby-2.0.0-setup.exe 

I typed 

 gem -v 

and found out that I was rubygems 1.3.1. So I typed: 

 gem update --system 

This was the result: 

---begin--- 
Updating RubyGems 
Updating rubygems-update 
Successfully installed rubygems-update-1.3.5 
:0:Warning: Gem::SourceIndex#search support for String patterns is 
deprecated 
Updating RubyGems to 1.3.5 
Installing RubyGems 1.3.5 
c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/ 
config_file. 
rb:39:in `new': wrong number of arguments (5 for 4) (ArgumentError) 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/config_file.rb:39:in `<class:ConfigFile>' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/config_file.rb:12:in `<top (required)>' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/gem_runner.rb:8:in `require' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/gem_runner.rb:8:in `<top (required)>' 
        from setup.rb:25:in `require' 
        from setup.rb:25:in `<main>' 
RubyGems system software updated 
--end-- 

Now, when I type 

  gem -v 

I get this: 

---begin--- 
c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/ 
config_file. 
rb:39:in `new': wrong number of arguments (5 for 4) (ArgumentError) 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/config_file.rb:39:in `<class:ConfigFile>' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/config_file.rb:12:in `<top (required)>' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/gem_runner.rb:8:in `require' 
        from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/ 
lib/rubygems 
/gem_runner.rb:8:in `<top (required)>' 
        from c:/ruby/bin/gem.bat:17:in `require' 
        from c:/ruby/bin/gem.bat:17:in `<main>' 
---end--- 

Does this mean I have broken rubygems on mingw32 by typing "gem update 
--system"? Typing 

  "gem search wxruby-ruby19 --remote" 

or trying to install a gem - any gem - gives me the same argument 
error.

Since rubygems was unusable, I uninstalled and reinstalled Ruby, using rubygems 1.3.1 for the time being. So this bug is not "lethal".

Kind regards,

Rainer

----------------------------------------------------------------------

Comment By: Rainer Wolf (rainer42)
Date: 2009-07-30 12:22

Message:
Thanks for the answer, Luis. You're really fast!

----------------------------------------------------------------------

Comment By: Luis Lavena (luislavena)
Date: 2009-07-30 08:13

Message:
As stated by wxRuby developers, there were some C API changes or similar that made things not to work between patchlevels (in similar fashion with 1.8.7).

Is safe to manually install RubyGems on top of 1.9.1. In my experience RubyGems never installed properly on 1.9 using gem update --system.

For The official One-Click Installer we update it using ruby setup.rb and works, so should work over wxRuby installer too.

Cheers.


----------------------------------------------------------------------

Comment By: Rainer Wolf (rainer42)
Date: 2009-07-30 08:09

Message:
Hello Luis,

thanks for the quick reply. Two questions about this:

Up until now, I never ever had a problem with updating 
rubygems. In your opinion, is it wise to do a manual 
installation of rubygems as described in your first link?

Second: Thanks for the link to the proper installer, but I 
have used p129 before. Couldn't get the wxRuby gem to work 
with that under Windows XP:

http://www.ruby-forum.com/topic/187872#new

So I switched to p0 with the unsupported installer mentioned 
above. Is your installer of p129 known to work with the 
wxRuby gem? 

----------------------------------------------------------------------

Comment By: Luis Lavena (luislavena)
Date: 2009-07-30 07:40

Message:
When automatic installation fails, you can fall back to manual installation.

http://blog.mmediasys.com/2008/08/04/problems-with-rubygems-find-here-some-handy-tips/

Keep in mind that Ruby version built by wxRuby team is not supported and is an old patchlevel (not latest stable).

Please use proper new One-Click Ruby Installers for 1.9.1:

http://blog.mmediasys.com/2009/06/28/rubyinstaller-preview1-released/


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26801&group_id=126

From noreply at rubyforge.org  Fri Jul 31 17:13:17 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 31 Jul 2009 17:13:17 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Feature Requests-26811 ] Consider
	collecting and publishing DOAP information
Message-ID: <20090731211318.0AF0B1858109@rubyforge.org>

Feature Requests item #26811, was opened at 2009-07-31 14:13
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=578&aid=26811&group_id=126

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Rich Morin (rdm)
Assigned to: Nobody (None)
Summary: Consider collecting and publishing DOAP information

Initial Comment:
[I didn't realize that there was a group for RubyGems, so I posted this
 to group_id 5.  I see no way to simply move the bug report, so I'm
 reposting it here.  -r]

DOAP (Description of a Project; http://trac.usefulinc.com/doap) is a
project to create an XML/RDF vocabulary to describe software projects,
and in particular open source.  In many cases, the information is
equivalent to that stored in the RubyGems metadata.

I'd like to see RubyGems:

  *  publish equivalent metadata in DOAP format

  *  investigate the collection and publication of fields that
     are currently missing from the RubyGems metadata

  *  work with DOAP to investigate adding fields that are currently
     missing from DOAP

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=578&aid=26811&group_id=126

From noreply at rubyforge.org  Fri Jul 31 17:13:23 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 31 Jul 2009 17:13:23 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Feature Requests-26812 ] add error
	handling for RubyGems metadata
Message-ID: <20090731211323.62A611D787E9@rubyforge.org>

Feature Requests item #26812, was opened at 2009-07-31 14:13
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=578&aid=26812&group_id=126

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Rich Morin (rdm)
Assigned to: Nobody (None)
Summary: add error handling for RubyGems metadata

Initial Comment:
[I didn't realize that there was a group for RubyGems, so I posted this
 to group_id 5.  I see no way to simply move the bug report, so I'm
 reposting it here.  -r]

As discussed in Bug #26667 [in group_id 5], I have found some problems
in the RubyGems metadata.  For example, some of the version numbers
are encoded as strings, rather than numbers.  Also, names may be encoded
as either strings or symbols. Finally, in the entry for oauth-simple-0.0.2,
the name listed in the first dependencies entry is a list.

These problems show up in both the YAML and marshalled versions of the
metadata, so I assume that they are input errors which are not being
handled by the RubyGems build system.  My suggestion would be to add
some error handling, as:

  *  Create a documentation page (ie, HowTo) that specifies the
     acceptable format for each piece of metadata.

  *  If the input format can be coerced to the proper form, do so,
     but send a "warning" note to the developer.

  *  If the input format cannot be coerced, fill in the field with
     a placeholder and send an "error" note to the developer.

In other words, document the desired format, encourage developers to use
it, and set things up so that the published metadata is always compliant.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=578&aid=26812&group_id=126