From jtrupiano at gmail.com  Mon Jun  1 10:32:16 2009
From: jtrupiano at gmail.com (John Trupiano)
Date: Mon, 1 Jun 2009 10:32:16 -0400
Subject: [Rubygems-developers] [ANN] RubyGems 1.3.4
In-Reply-To: <8F5BC8B8-8312-4A63-A17A-82976E1FC10A@segment7.net>
References: <8F5BC8B8-8312-4A63-A17A-82976E1FC10A@segment7.net>
Message-ID: <2847174d0906010732x161b977bw8b70d5261c302cd6@mail.gmail.com>

fyi, upon upgrading from 1.3.3 to 1.3.4, I received a message saying 'no
release notes found.'

-John

john-mbp:trunk john$ sudo gem update --system
Updating RubyGems
Updating rubygems-update
Successfully installed rubygems-update-1.3.4
/Library/Ruby/Site/1.8/rubygems/commands/update_command.rb:103:Warning:
Gem::SourceIndex#search support for String patterns is deprecated
Updating RubyGems to 1.3.4
Installing RubyGems 1.3.4
Installing RubyGems
Installing gem executable
Removing old source_cache files
Removing old RubyGems RDoc and ri
Installing rubygems-1.3.4 ri into
/Library/Ruby/Gems/1.8/doc/rubygems-1.3.4/ri
Installing rubygems-1.3.4 rdoc into
/Library/Ruby/Gems/1.8/doc/rubygems-1.3.4/rdoc

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

Oh-no! Unable to find release notes!

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

RubyGems installed the following executables:
    /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/gem


On Sat, May 30, 2009 at 10:22 AM, Eric Hodel <drbrain at segment7.net> wrote:

> 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.4 fixes some bugs and adds some features.
>
> Bug Fixes:
>
> * Fixed various warnings
> * Gem::ruby_version works correctly for 1.8 branch and trunk
> * Prerelease gems now show up in `gem list` and can be used
> * Fixed option name for `gem setup --format-executable`
> * RubyGems now matches Ruby > 1.9.1 gem paths
> * Gem::RemoteFetcher#download now works for explicit Windows paths across
>  drives.  Bug #25882 by Lars Christensen
> * Fix typo in Gem::Requirement#parse.  Bug #26000 by Mike Gunderloy.
>
> 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.
>
> For a full list of changes to RubyGems and the contributor for each change,
> see
> the ChangeLog file.
>
> == 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!
>
> -- The RubyGems team
>
>
> _______________________________________________
> Rubygems-developers mailing list
> http://rubyforge.org/projects/rubygems
> Rubygems-developers at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubygems-developers
>

From noreply at rubyforge.org  Mon Jun  1 14:20:01 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Mon,  1 Jun 2009 14:20:01 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Feature Requests-26090 ] Gem
	activation errors should be more informative.
Message-ID: <20090601182001.73B3318581E9@rubyforge.org>

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

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Bob Aman (sporkmonger)
Assigned to: Nobody (None)
Summary: Gem activation errors should be more informative.

Initial Comment:
In some cases, especially with closely related projects like rspec and rspec-rails, it's easy for gems to get out-of-sync.  When a file is required without a version, the latest version gets loaded.  So if rspec gets loaded first, rspec 1.2.6 gets activated.  The only copy of rspec-rails on the machine requires 1.2.4, and when you run your specs, rake fails with:

Can't activate rspec (= 1.2.4), already activated rspec (= 1.2.6).

The problem is, in a large project with lots of dependencies, it's nearly impossible to determine what exactly is doing the require of the old version based on this error message.  None of the rspec-rails code appears in the exception backtrace, so you may even be forced to add debug code to RubyGems itself in order to actually find the offending gem.

I'd like to see the error message read:

Gem rspec-rails couldn't activate rspec (= 1.2.4), already activated rspec (= 1.2.6).

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

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

From rick.denatale at gmail.com  Mon Jun  1 16:42:21 2009
From: rick.denatale at gmail.com (Rick DeNatale)
Date: Mon, 1 Jun 2009 16:42:21 -0400
Subject: [Rubygems-developers] Hoe, Rubyforge, and name confusion
In-Reply-To: <C7D36F2E-4C35-4AFF-83CF-E39E4DF70020@zenspider.com>
References: <deb2337a0905280910ubfa92f2ifa988ab2ba9ef5fb@mail.gmail.com>
	<C7D36F2E-4C35-4AFF-83CF-E39E4DF70020@zenspider.com>
Message-ID: <deb2337a0906011342y1b20ef15m2288d91012c87987@mail.gmail.com>

On Fri, May 29, 2009 at 3:07 PM, Ryan Davis <ryand-ruby at zenspider.com> wrote:


>
>> Hoe.new('ri_cal', RiCal::VERSION) do |p|
>> ?p.rubyforge_name = 'ri-cal'
>>
>> ?p.developer('Rick DeNatale', 'rick.denatale at gmail.com')
>> end
>
> isn't that prettier?
>
> this means: the gem name is "ri_cal" and it is published under the "ri-cal"
> rubyforge project. This appears to be the case:

Thanks, using "ri_cal" as the first arg to Hoe.new, and 'ri-cal' as
the project name does seem to be correct.

It finally worked but only after I'd manually added
processor_ids:
  IA64: 6000
  Any: 8000
  AMD-64: 1500
  PPC: 2000
  Sparc: 4000
  Other: 9999
  i386: 1000
  Alpha: 7000
  MIPS: 3000
  UltraSparc: 5000

To ~/.rubyforge/auto-config.yml  should this not have been put there
by rubyforge config ?

I'm still a bit confused by the package concept. I now seem to have
the following packages in the ri-cal rubyforge project:

ri-cal
  0.5.2	  2009-05-28 15:54
        ri_cal-0.5.2.gem     371 KB    2  Any            .gem (RubyGem)
  0.5.1	  2009-05-26 16:06
        ri_cal-0.5.1.gem     370 KB    2  Universal     .gem (RubyGem)
  0.5.0	  2009-05-26 14:38
        ri_cal-0.5.0.gem     371 KB    2  Any             .gem (RubyGem)

ri_cal
  0.5.3	  2009-06-01 10:46
        ri_cal-0.5.3.gem     406 KB    1  Any             .gem (RubyGem)
        ri_cal-0.5.3.tgz      407 KB     0 Any              Source .zip

The first three in the ri-cal package were uploaded when I manually
uploaded before I got hoe to do it for me.

I can't seem to find a way to move files between packages.  Does it matter?

-- 
Rick DeNatale

Blog: http://talklikeaduck.denhaven2.com/
Twitter: http://twitter.com/RickDeNatale
WWR: http://www.workingwithrails.com/person/9021-rick-denatale
LinkedIn: http://www.linkedin.com/in/rickdenatale

From noreply at rubyforge.org  Tue Jun  2 18:03:17 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  2 Jun 2009 18:03:17 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26109 ] gem install gemname
	--remote will fail if gemname is in current directory
Message-ID: <20090602220317.2C296185810C@rubyforge.org>

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

Category: `gem install` command
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: ara howard (ahoward)
Assigned to: Nobody (None)
Summary: gem install gemname --remote will fail if gemname is in current directory

Initial Comment:
gem install gemname --remote  will prefer a gem in the current directory.  seems like --remote should *never* do *anything* local?

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

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

From noreply at rubyforge.org  Tue Jun  2 20:14:13 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  2 Jun 2009 20:14:13 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26110 ] Binary files in RDoc
	file list causes gem to hang during RDoc generation
Message-ID: <20090603001413.E9B6A1598077@rubyforge.org>

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

Category: `gem install` command
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Logan Barnett (logan_barnett)
Assigned to: Nobody (None)
Summary: Binary files in RDoc file list causes gem to hang during RDoc generation

Initial Comment:
This is the output I get:
$ sudo gem install pkg/rawr-1.3.4.gem 
Password:
Successfully installed rubyzip-0.9.1
Successfully installed rawr-1.3.4
2 gems installed
Installing ri documentation for rawr-1.3.4...
Installing RDoc documentation for rawr-1.3.4...

At this point the processor is pegged and the task never ends (I've left my machine to do this for hours and have seen no result). If I rerun the task with --no-rdoc, it works just fine. Also, if I run the rdoc command from Rawr's source the command completes just fine.

I understand that we shouldn't have binary files on the list (I've fixed Rawr on head to no longer do this), but having gem hang seems buggy to me because there's little indication of what went wrong.

When I put on the verbose flag this is what I get for output (it also hangs):

gem install -V pkg/rawr-1.3.4.gem 
GET 304 Not Modified: http://gems.rubyforge.org/latest_specs.4.8.gz
Installing gem rawr-1.3.4
Using local gem /Users/logan/dev/jruby/lib/ruby/gems/1.8/cache/rawr-1.3.4.gem
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/History.txt
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/Manifest.txt
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/README.txt
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/Rakefile
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/bin/rawr
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/data/GenericJavaApp.icns
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/data/JavaApplicationStub
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/data/Rawr logo 1 large.png
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/data/Rawr logo 2 large.png
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/data/Rawr logo2.png
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/data/website/_notes/dwsync.xml
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/data/website/css/1.css
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/data/website/css/_notes/dwsync.xml
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/data/website/images/_notes/dwsync.xml
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/data/website/images/body_bg.jpg
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/data/website/images/bullet.gif
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/data/website/images/content.jpg
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/data/website/images/content_h2.gif
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/data/website/images/details.gif
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/data/website/images/details.jpg
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/data/website/images/header_bg.jpg
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/data/website/images/nav_a_hover.gif
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/data/website/images/rawr_logo.png
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/data/website/index.html
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/app_bundler.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/command.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/bundler.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/exe_bundler.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/generator.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/jar_builder.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/jruby_release.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/jruby_batch_compiler.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/LICENSE.txt
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/bin-mac/COPYING
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/bin-mac/ld
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/bin-mac/readme.txt
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/bin-mac/windres
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/build.xml
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/demo/ConsoleApp/ConsoleApp.jar
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/demo/ConsoleApp/build.xml
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/demo/ConsoleApp/l4j/ConsoleApp.ico
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/demo/ConsoleApp/lib/readme.txt
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/demo/ConsoleApp/readme.txt
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/demo/ConsoleApp/src/net/sf/launch4j/example/ConsoleApp.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/demo/LICENSE.txt
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/demo/SimpleApp/SimpleApp.jar
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/demo/SimpleApp/build.xml
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/demo/SimpleApp/l4j/SimpleApp.ico
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/demo/SimpleApp/l4j/SimpleApp.xml
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/demo/SimpleApp/l4j/splash.bmp
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/demo/SimpleApp/lib/readme.txt
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/demo/SimpleApp/readme.txt
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/demo/SimpleApp/src/net/sf/launch4j/example/SimpleApp.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/demo/readme.txt
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/head/LICENSE.txt
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/head/consolehead.o
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/head/guihead.o
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/head/head.o
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/head_src/LICENSE.txt
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/head_src/consolehead/Makefile.win
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/head_src/consolehead/consolehead.c
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/head_src/consolehead/consolehead.dev
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/head_src/guihead/Makefile.win
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/head_src/guihead/guihead.c
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/head_src/guihead/guihead.dev
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/head_src/guihead/guihead.h
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/head_src/head.c
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/head_src/head.h
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/head_src/resource.h
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/launch4j
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/launch4j.jar
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/launch4j.jfpr
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/lib/JGoodies.Forms.LICENSE.txt
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/lib/JGoodies.Looks.LICENSE.txt
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/lib/Nuvola.Icon.Theme.LICENSE.txt
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/lib/XStream.LICENSE.txt
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/lib/commons-beanutils.jar
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/lib/commons-logging.jar
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/lib/commons.LICENSE.txt
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/lib/forms.jar
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/lib/formsrt.jar
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/lib/foxtrot.LICENSE.txt
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/lib/foxtrot.jar
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/lib/looks.jar
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/lib/xstream.jar
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/manifest/uac.exe.manifest
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/manifest/xp-themes.exe.manifest
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/images/asterix-o.gif
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/images/asterix.gif
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/images/build.png
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/images/button_ok.png
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/images/cancel16.png
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/images/down16.png
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/images/edit_add16.png
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/images/info.png
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/images/new.png
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/images/new16.png
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/images/ok16.png
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/images/open.png
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/images/open16.png
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/images/run.png
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/images/save.png
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/images/up16.png
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/launch4j.properties
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/Builder.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/BuilderException.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/ExecException.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/FileChooserFilter.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/Log.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/Main.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/Messages.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/OptionParser.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/RcBuilder.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/Util.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/ant/AntClassPath.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/ant/AntConfig.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/ant/AntJre.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/ant/Launch4jTask.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/ant/Messages.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/ant/StringWrapper.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/ant/messages.properties
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/ant/messages_es.properties
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/binding/Binding.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/binding/BindingException.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/binding/Bindings.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/binding/IValidatable.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/binding/InvariantViolationException.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/binding/JComboBoxBinding.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/binding/JListBinding.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/binding/JRadioButtonBinding.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/binding/JTextAreaBinding.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/binding/JTextComponentBinding.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/binding/JToggleButtonBinding.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/binding/Messages.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/binding/OptComponentBinding.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/binding/OptJTextAreaBinding.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/binding/Validator.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/binding/messages.properties
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/binding/messages_es.properties
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/config/ClassPath.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/config/Config.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/config/ConfigPersister.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/config/ConfigPersisterException.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/config/Jre.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/config/LdDefaults.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/config/Messages.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/config/Msg.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/config/SingleInstance.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/config/Splash.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/config/VersionInfo.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/config/messages.properties
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/config/messages_es.properties
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/form/BasicForm.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/form/BasicForm.jfrm
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/form/ClassPathForm.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/form/ClassPathForm.jfrm
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/form/ConfigForm.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/form/ConfigForm.jfrm
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/form/EnvironmentVarsForm.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/form/EnvironmentVarsForm.jfrm
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/form/HeaderForm.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/form/HeaderForm.jfrm
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/form/JreForm.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/form/JreForm.jfrm
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/form/Messages.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/form/MessagesForm.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/form/MessagesForm.jfrm
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/form/SingleInstanceForm.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/form/SingleInstanceForm.jfrm
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/form/SplashForm.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/form/SplashForm.jfrm
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/form/VersionInfoForm.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/form/VersionInfoForm.jfrm
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/form/messages.properties
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/form/messages_es.properties
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/formimpl/AbstractAcceptListener.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/formimpl/BasicFormImpl.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/formimpl/BrowseActionListener.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/formimpl/ClassPathFormImpl.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/formimpl/ConfigFormImpl.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/formimpl/EnvironmentVarsFormImpl.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/formimpl/FileChooser.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/formimpl/GlassPane.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/formimpl/HeaderFormImpl.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/formimpl/JreFormImpl.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/formimpl/MainFrame.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/formimpl/Messages.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/formimpl/MessagesFormImpl.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/formimpl/SingleInstanceFormImpl.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/formimpl/SplashFormImpl.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/formimpl/VersionInfoFormImpl.java
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/formimpl/messages.properties
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/formimpl/messages_es.properties
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/messages.properties
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/src/net/sf/launch4j/messages_es.properties
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/w32api/MinGW.LICENSE.txt
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/w32api/crt2.o
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/w32api/libadvapi32.a
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/w32api/libgcc.a
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/w32api/libkernel32.a
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/w32api/libmingw32.a
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/w32api/libmsvcrt.a
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/w32api/libshell32.a
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/w32api/libuser32.a
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/web/bullet.gif
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/web/changelog.html
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/web/docs.html
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/web/index.html
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/web/launch4j-use.gif
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/web/launch4j.gif
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/web/links.html
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/web/style.css
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/bin-linux/COPYING
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/bin-linux/ld
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/bin-linux/windres
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/bin-win/COPYING
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/bin-win/ld.exe
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/launch4j/bin-win/windres.exe
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/options.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/platform.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/rawr.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/rawr_bundle.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/rawr_version.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/web_bundler.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/zip/ioextras.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/zip/stdrubyext.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/zip/tempfile_bugfixed.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/zip/zip.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/zip/zipfilesystem.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/lib/zip/ziprequire.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/tasks/ann.rake
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/tasks/bones.rake
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/tasks/gem.rake
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/tasks/manifest.rake
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/tasks/notes.rake
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/tasks/post_load.rake
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/tasks/rdoc.rake
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/tasks/rubyforge.rake
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/tasks/setup.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/tasks/spec.rake
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/tasks/svn.rake
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/tasks/test.rake
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/test/unit/app_bundler_spec.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/test/unit/bundler_spec.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/test/unit/generator_spec.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/test/unit/jar_builder_spec.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/test/unit/options_spec.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/test/unit/platform_spec.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/test/spec_helpers.rb
/Users/logan/dev/jruby/lib/ruby/gems/1.8/gems/rawr-1.3.4/test/unit/web_bundler_spec.rb
/Users/logan/dev/jruby/bin/rawr
Successfully installed rawr-1.3.4
1 gem installed
Installing ri documentation for rawr-1.3.4...
Updating ri class cache with 3956 classes...
Installing RDoc documentation for rawr-1.3.4...



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

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

From thewoolleyman at gmail.com  Thu Jun  4 05:25:14 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Thu, 4 Jun 2009 02:25:14 -0700
Subject: [Rubygems-developers] Commit 2221 broke uninstall on OSX (not linux)
Message-ID: <e3af97510906040225n3c177e06m3ab12c6013e6ffd8@mail.gmail.com>

My uninstall regression tests started failing on default OSX Leopard
Ruby (not linux) as of commit 2221.  This is with Ruby 1.8.6.  Test is
functional/install_processor_spec.rb in GemInstaller.

Just a heads up for now.  Sorry, didn't dig deeper yet, this is a very
coarse "make sure it is not still installed after uninstall"
functional test, so not much info provided.

-- Chad

From thewoolleyman at gmail.com  Thu Jun  4 05:29:01 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Thu, 4 Jun 2009 02:29:01 -0700
Subject: [Rubygems-developers] Commit 2221 broke uninstall on OSX (not
	linux)
In-Reply-To: <e3af97510906040225n3c177e06m3ab12c6013e6ffd8@mail.gmail.com>
References: <e3af97510906040225n3c177e06m3ab12c6013e6ffd8@mail.gmail.com>
Message-ID: <e3af97510906040229w2a7148d2g220b1e022a4e6713@mail.gmail.com>

On Thu, Jun 4, 2009 at 2:25 AM, Chad Woolley<thewoolleyman at gmail.com> wrote:
> My uninstall regression tests started failing on default OSX Leopard
> Ruby (not linux) as of commit 2221.

On second thought, it could well have been an earlier commit, since I
only run my CI on linux, not Leopard.  I believe they were passing on
OSX in the last month or so.

Maybe the same bug as this:

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

From drbrain at segment7.net  Fri Jun  5 17:33:01 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Fri, 5 Jun 2009 14:33:01 -0700
Subject: [Rubygems-developers] [ANN] RubyGems 1.3.4
In-Reply-To: <2847174d0906010732x161b977bw8b70d5261c302cd6@mail.gmail.com>
References: <8F5BC8B8-8312-4A63-A17A-82976E1FC10A@segment7.net>
	<2847174d0906010732x161b977bw8b70d5261c302cd6@mail.gmail.com>
Message-ID: <03DACB23-8ADE-4B90-8FC9-6DB7439D0B83@segment7.net>

On Jun 1, 2009, at 07:32, John Trupiano wrote:

> fyi, upon upgrading from 1.3.3 to 1.3.4, I received a message saying  
> 'no
> release notes found.'

Fixed that, need to finish converting the Rakefile to Hoe.

From noreply at rubyforge.org  Tue Jun  9 18:47:13 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  9 Jun 2009 18:47:13 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Patches-26180 ] Simplify and speed
	up Gem::Version::Part
Message-ID: <20090609224713.B827218580F5@rubyforge.org>

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

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Aaron Patterson (aaronp)
Assigned to: Nobody (None)
Summary: Simplify and speed up Gem::Version::Part

Initial Comment:
This patch will simplify and speed up Gem::Version::Part.  A version part can be determined whether it is an alpha? or a numeric? upon initialization and can cache that fact.

This patch determines the type of version on initialization, caches the values, and also defines attributes with attr_reader for increased speed.

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

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

From noreply at rubyforge.org  Tue Jun  9 22:54:27 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  9 Jun 2009 22:54:27 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26069 ] Error uninstalling
	pre-release gem
Message-ID: <20090610025427.D674418580F4@rubyforge.org>

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

Category: `gem` commands (other)
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: David Chelimsky (dchelimsky)
>Assigned to: Phil Hagelberg (technomancy)
Summary: Error uninstalling pre-release gem

Initial Comment:
$ gem list rspec

*** LOCAL GEMS ***

rspec (1.2.7.a)
$ sudo gem uninstall rspec
Remove executables:
	autospec, spec

in addition to the gem? [Yn]  y
Removing autospec
Removing spec
ERROR:  While executing gem ... (NoMethodError)
    undefined method `name' for nil:NilClass
$ gem list rspec

*** LOCAL GEMS ***

rspec (1.2.7.a)


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

Comment By: David Chelimsky (dchelimsky)
Date: 2009-05-30 09:53

Message:
$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.4
  - RUBY VERSION: 1.8.6 (2008-03-03 patchlevel 114) [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/david/.gem/ruby/1.8
     - 
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/ge
ms/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/"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/
     - http://gems.github.com/


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

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

From noreply at rubyforge.org  Wed Jun 10 12:35:19 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Wed, 10 Jun 2009 12:35:19 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26069 ] Error uninstalling
	pre-release gem
Message-ID: <20090610171138.B0A551598030@rubyforge.org>

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

Category: `gem` commands (other)
Group: v1.3.x
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: David Chelimsky (dchelimsky)
Assigned to: Phil Hagelberg (technomancy)
Summary: Error uninstalling pre-release gem

Initial Comment:
$ gem list rspec

*** LOCAL GEMS ***

rspec (1.2.7.a)
$ sudo gem uninstall rspec
Remove executables:
	autospec, spec

in addition to the gem? [Yn]  y
Removing autospec
Removing spec
ERROR:  While executing gem ... (NoMethodError)
    undefined method `name' for nil:NilClass
$ gem list rspec

*** LOCAL GEMS ***

rspec (1.2.7.a)


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

>Comment By: Phil Hagelberg (technomancy)
Date: 2009-06-10 09:35

Message:
Just fixed this last night. r2229 and up should be good.

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

Comment By: David Chelimsky (dchelimsky)
Date: 2009-05-30 09:53

Message:
$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.4
  - RUBY VERSION: 1.8.6 (2008-03-03 patchlevel 114) [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/david/.gem/ruby/1.8
     - 
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/ge
ms/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/"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/
     - http://gems.github.com/


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

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

From noreply at rubyforge.org  Wed Jun 10 13:14:44 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Wed, 10 Jun 2009 13:14:44 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26069 ] Error uninstalling
	pre-release gem
Message-ID: <20090610171444.33BC718580ED@rubyforge.org>

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

Category: `gem` commands (other)
Group: v1.3.x
Status: Closed
Resolution: Accepted
Priority: 3
Submitted By: David Chelimsky (dchelimsky)
Assigned to: Phil Hagelberg (technomancy)
Summary: Error uninstalling pre-release gem

Initial Comment:
$ gem list rspec

*** LOCAL GEMS ***

rspec (1.2.7.a)
$ sudo gem uninstall rspec
Remove executables:
	autospec, spec

in addition to the gem? [Yn]  y
Removing autospec
Removing spec
ERROR:  While executing gem ... (NoMethodError)
    undefined method `name' for nil:NilClass
$ gem list rspec

*** LOCAL GEMS ***

rspec (1.2.7.a)


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

>Comment By: David Chelimsky (dchelimsky)
Date: 2009-06-10 17:14

Message:
Thanks Phil!

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

Comment By: Phil Hagelberg (technomancy)
Date: 2009-06-10 16:35

Message:
Just fixed this last night. r2229 and up should be good.

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

Comment By: David Chelimsky (dchelimsky)
Date: 2009-05-30 16:53

Message:
$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.4
  - RUBY VERSION: 1.8.6 (2008-03-03 patchlevel 114) [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/david/.gem/ruby/1.8
     - 
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/ge
ms/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/"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/
     - http://gems.github.com/


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

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

From devnull+rubygems-ci at pivotallabs.com  Wed Jun 10 12:10:07 2009
From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com)
Date: Wed, 10 Jun 2009 16:10:07 +0000
Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2226 failed
Message-ID: <4a2fdadfd4223_6358..fdbdd5b841c9@ci.pivotallabs.com.tmail>

The build failed.

CHANGES
-------
New revision 2225 detected
Revision 2225 committed by technomancy on 2009-06-10 16:06:43
Merge @gems and @prerelease_gems in SourceIndex. Search methods should make distinction.

Still need to fix test cases.
  M /trunk/lib/rubygems/source_index.rb
Revision 2224 committed by technomancy on 2009-06-10 16:06:39
Added failing test case for bug #26069.
  M /trunk/test/test_gem_commands_uninstall_command.rb



TEST FAILURES AND ERRORS
-----------------------
Name: test_execute_regexp(TestGemCommandsDependencyCommand)
Type: Failure
Message: Expected "Gem a-1\n\nGem a-2\n\nGem a_evil-9\n\nGem b-2\n\n", not "Gem a-1\n\nGem a-2\n\nGem a-3.a\n\nGem a_evil-9\n\nGem b-2\n\n".

./test/test_gem_commands_dependency_command.rb:109


Name: test_execute_no_args(TestGemCommandsDependencyCommand)
Type: Failure
Message: Expected "Gem a-1\n\nGem a-2\n\nGem a_evil-9\n\nGem b-2\n\nGem c-1.2\n\nGem pl-1-x86-linux\n\n", not "Gem a-1\n\nGem a-2\n\nGem a-3.a\n\nGem a_evil-9\n\nGem b-2\n\nGem c-1.2\n\nGem pl-1-x86-linux\n\n".

./test/test_gem_commands_dependency_command.rb:56


Name: test_execute_prerelease(TestGemCommandsUninstallCommand)
Type: Failure
Message: Expected /Successfully uninstalled/ to match "  Successfully built RubyGem".

./test/test_gem_commands_uninstall_command.rb:80


Name: test_prerelease_specs_kept_in_right_place(TestGemSourceIndex)
Type: Failure
Message: Expected Gem::Specification.new do |s|
  s.authors = ["A User"]
  s.date = Time.utc(2009, 6, 10)
  s.description = "This is a test description"
  s.email = "example at example.com"
  s.homepage = "http://example.com"
  s.name = "abba"
  s.require_paths = ["lib"]
  s.required_rubygems_version = Gem::Requirement.new(["> 1.3.1"])
  s.rubygems_version = "1.3.4"
  s.specification_version = 3
  s.summary = "this is a summary"
  s.version = Gem::Version.new("1.a")
  end to be nil.

./test/test_gem_source_index.rb:338




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

From devnull+rubygems-ci at pivotallabs.com  Wed Jun 10 12:10:39 2009
From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com)
Date: Wed, 10 Jun 2009 16:10:39 +0000
Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2229 fixed
Message-ID: <4a2fdaff5f85d_6358..fdbdd5b8425f@ci.pivotallabs.com.tmail>

The build has been fixed.

CHANGES
-------
New revision 2229 detected
Revision 2229 committed by technomancy on 2009-06-10 16:06:52
Fix dependency command test.
  M /trunk/test/test_gem_commands_dependency_command.rb
Revision 2228 committed by technomancy on 2009-06-10 16:06:50
Fix uninstall command test.
  M /trunk/test/test_gem_commands_uninstall_command.rb
Revision 2227 committed by technomancy on 2009-06-10 16:06:48
Fixed indexer to use released_gems instead of all gems when building indices.
  M /trunk/test/test_gem_source_index.rb
  M /trunk/lib/rubygems/indexer.rb
  M /trunk/test/test_gem_indexer.rb
  M /trunk/lib/rubygems/source_index.rb



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

From thewoolleyman at gmail.com  Wed Jun 10 16:21:17 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Wed, 10 Jun 2009 13:21:17 -0700
Subject: [Rubygems-developers] Commit 2221 broke uninstall on OSX (not
	linux)
In-Reply-To: <e3af97510906040225n3c177e06m3ab12c6013e6ffd8@mail.gmail.com>
References: <e3af97510906040225n3c177e06m3ab12c6013e6ffd8@mail.gmail.com>
Message-ID: <e3af97510906101321y56687843j53c3ad0cd7bbeebe@mail.gmail.com>

On Thu, Jun 4, 2009 at 2:25 AM, Chad Woolley<thewoolleyman at gmail.com> wrote:
> My uninstall regression tests started failing on default OSX Leopard
> Ruby (not linux) as of commit 2221. ?This is with Ruby 1.8.6. ?Test is
> functional/install_processor_spec.rb in GemInstaller.
>
> Just a heads up for now. ?Sorry, didn't dig deeper yet, this is a very
> coarse "make sure it is not still installed after uninstall"
> functional test, so not much info provided.

Update on this - don't have time to investigate further right now...

The test mysteriously started passing again when I uninstalled a local
copy of my test stub gem from ~/.gems.

This is concerning, because my test suite is set up to override
GEM_HOME and GEM_PATH to a freshly-created directory on each run, and
the tests use a local, never-changing stub gem for testing.

So, there theoretically shouldn't be any bleed-over from any locally
installed gems, and there never has been in the past.  This failure
could indicate a bug where GEM_HOME and GEM_PATH overrides are not
being properly observed, or are not handled the same way they were in
previous releases.

I'll look into it more when I get time, or if it occurs again.

-- Chad

From noreply at rubyforge.org  Thu Jun 11 07:19:23 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 11 Jun 2009 07:19:23 -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: <20090611111925.963661858185@rubyforge.org>

Bugs item #26199, was opened at 2009-06-11 07: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: Open
Resolution: None
Priority: 3
Submitted By: Robert Holt (bobholt)
Assigned to: Nobody (None)
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/

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

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

From noreply at rubyforge.org  Thu Jun 11 07:38:24 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 11 Jun 2009 07:38:24 -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: <20090611113824.9469A159802F@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: Open
Resolution: None
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-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  Thu Jun 11 07:58:26 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 11 Jun 2009 07:58:26 -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: <20090611115826.B673F1858136@rubyforge.org>

Bugs item #26199, was opened at 2009-06-11 07: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: Open
Resolution: None
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: Bob Holt (bobholt)
Date: 2009-06-11 07: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 07: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  Thu Jun 11 08:09:49 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 11 Jun 2009 08:09:49 -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: <20090611120950.8E028159802F@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: Open
Resolution: None
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-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  Thu Jun 11 08:18:07 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 11 Jun 2009 08:18:07 -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: <20090611121807.EB5A2159802F@rubyforge.org>

Bugs item #26199, was opened at 2009-06-11 07: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: Open
Resolution: None
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: Bob Holt (bobholt)
Date: 2009-06-11 08: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 08: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 07: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 07: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  Thu Jun 11 17:37:07 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 11 Jun 2009 17:37:07 -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: <20090611213707.868FE1858112@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: Open
Resolution: None
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-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 devnull+rubygems-ci at pivotallabs.com  Fri Jun 12 19:19:03 2009
From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com)
Date: Fri, 12 Jun 2009 23:19:03 +0000
Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2232 failed
Message-ID: <4a32e2675a134_6358..fdbdd5b84329@ci.pivotallabs.com.tmail>

The build failed.

CHANGES
-------
New revision 2232 detected
Revision 2232 committed by zenspider on 2009-06-12 23:12:38
hoe'd the rakefile
  M /trunk/README
  M /trunk/Rakefile
  M /trunk/Manifest.txt
  M /trunk/lib/rubygems/commands/setup_command.rb
  D /trunk/doc
  M /trunk/lib/rubygems.rb
  D /trunk/lib/rubygems/rubygems_version.rb
  D /trunk/scripts
  A /trunk/release_notes
  D /trunk/redist



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

From thewoolleyman at gmail.com  Fri Jun 12 19:55:19 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Fri, 12 Jun 2009 16:55:19 -0700
Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2232 failed
In-Reply-To: <4a32e2675a134_6358..fdbdd5b84329@ci.pivotallabs.com.tmail>
References: <4a32e2675a134_6358..fdbdd5b84329@ci.pivotallabs.com.tmail>
Message-ID: <e3af97510906121655r43557d44oda63aed1ecc9923b@mail.gmail.com>

On Fri, Jun 12, 2009 at 4:19 PM, <devnull+rubygems-ci at pivotallabs.com> wrote:
> The build failed.
>
> CHANGES
> -------
> New revision 2232 detected
> Revision 2232 committed by zenspider on 2009-06-12 23:12:38
> hoe'd the rakefile
> ...
> See http://ci.pivotallabs.com:3333/builds/RubyGems/2232 for details.

Is this because of a downlevel Hoe version on our CI server?  If so,
we can set up a wrapper build script to run GemInstaller (or anything
you want to accomplish same thing) and also print out env stats.  This
is what we do on the Rails build:

http://github.com/rails/rails/blob/master/ci/ci_build.rb

I DON'T want to manually install a required version of Hoe, even
though I could - it is better to have the build completely specify its
required dependencies (this is a shared server CI anyway, but it's the
principle).

Let me know how I can help.

-- Chad
-- Chad

From thewoolleyman at gmail.com  Fri Jun 12 20:48:09 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Fri, 12 Jun 2009 17:48:09 -0700
Subject: [Rubygems-developers] Hoe'ify broke Gem::RubyGemsVersion for me
Message-ID: <e3af97510906121748s1e53a74l90cdb2d633f5c226@mail.gmail.com>

The last commit 2232 broke Gem::RubyGemsVersion for me by moving it
from rubygems/rubygems_version.rb to rubygems.rb.

GemInstaller runs unit tests (and useful functional tests for Rubygems
itself) via CI against the trunk version of RubyGems via an svn
external.  Before, I could force the RubyGems version to come from the
svn external by forcing a load of the trunk rubygems_version.rb before
the system version of rubygems got activated.

Now that it was moved into rubygems.rb, I cannot do that anymore.  I
also cannot just force a load of the trunk rubygems.rb, because that
causes other problems (including breaking my ability to run regression
tests against older versions of rubygems).

Any reason we can't put the version back in rubygems/rubygems_version.rb?

Thanks,
-- Chad

From noreply at rubyforge.org  Sat Jun 13 18:23:20 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sat, 13 Jun 2009 18:23:20 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Feature Requests-26223 ] slightly
	more verbose --help output
Message-ID: <20090613222320.C75651858112@rubyforge.org>

Feature Requests item #26223, was opened at 2009-06-13 22:23
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=578&aid=26223&group_id=126

Category: `gem` commands
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Roger Pack (rogerdpack)
Assigned to: Nobody (None)
Summary: slightly more verbose --help output

Initial Comment:
Twould be nice if it showed all commands when you did --help [but very tersely, I realize it shouldn't be verbose]

like perhaps

   gem help commands            list all 'gem' commands
     [build, cert, contents, query, rdoc, search]

or so.
Much thanks.
-=r

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

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

From devnull+rubygems-ci at pivotallabs.com  Sun Jun 14 21:59:15 2009
From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com)
Date: Mon, 15 Jun 2009 01:59:15 +0000
Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2233 fixed
Message-ID: <4a35aaf31f261_6358..fdbdd5b844a@ci.pivotallabs.com.tmail>

The build has been fixed.

CHANGES
-------
Build was manually requested


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

From thewoolleyman at gmail.com  Sun Jun 14 22:34:30 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Sun, 14 Jun 2009 19:34:30 -0700
Subject: [Rubygems-developers] Fixed CI build
Message-ID: <e3af97510906141934s7af8aadpc0483165a3113371@mail.gmail.com>

RubyGems has a Continuous Integration build [1].  A commit on Friday
broke it [2], which I triaged with a suggested fix [3] even though I
didn't break it.  It is good to fix builds as soon as they break [4],
especially if your commit broke it.  It was still broken after three
days [5], so I fixed it.

As a nice side benefit, RubyGems now also has an
'install_build_dependencies.rb', just in case people trying to hack on
rubygems are unaware that "undefined method `plugin' for Hoe:Class"
really means "install latest hoe and hoe-seattlerb gems"...

Thanks,
-- Chad

[1] http://ci.pivotallabs.com:3333/builds/RubyGems
[2] http://rubyforge.org/pipermail/rubygems-developers/2009-June/004712.html
[3] http://rubyforge.org/pipermail/rubygems-developers/2009-June/004713.html
[4] http://www.pragprog.com/the-pragmatic-programmer/extracts/software-entropy
[5] http://www.box.net/shared/ebaco1347v

From thewoolleyman at gmail.com  Sun Jun 14 23:30:10 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Sun, 14 Jun 2009 20:30:10 -0700
Subject: [Rubygems-developers] Hoe'ify broke Gem::RubyGemsVersion for me
In-Reply-To: <e3af97510906121748s1e53a74l90cdb2d633f5c226@mail.gmail.com>
References: <e3af97510906121748s1e53a74l90cdb2d633f5c226@mail.gmail.com>
Message-ID: <e3af97510906142030k5ac459c8v3264fd1e2d6bd07b@mail.gmail.com>

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

From thewoolleyman at gmail.com  Sun Jun 14 23:50:30 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Sun, 14 Jun 2009 20:50:30 -0700
Subject: [Rubygems-developers] Trunk version of rubygems should always be >
	released version
Message-ID: <e3af97510906142050i7e77c0f3k76bdf89cda83280e@mail.gmail.com>

I bumped the trunk version of RubyGems to 1.3.4.1.  I previously
discussed [1] why this makes sense.

To summarize, this makes it much easier for people writing and testing
with CI against the RubyGems API, especially if they have embedded
version checks to support backward- and forward-compatibility with
older or unreleased versions of RubyGems.

The version should be changed to something appropriate before the next
release.  1.3.4.1 is arbitrary and interim, I don't care what it is,
as long as it is > 1.3.4.  As soon as the 1.3.4 gem was released,
trunk was NOT version 1.3.4 anymore.

Thanks,
-- Chad

[1] http://rubyforge.org/pipermail/rubygems-developers/2008-September/004070.html

From technomancy at gmail.com  Mon Jun 15 12:16:02 2009
From: technomancy at gmail.com (Phil Hagelberg)
Date: Mon, 15 Jun 2009 09:16:02 -0700
Subject: [Rubygems-developers] Trunk version of rubygems should always
	be > released version
In-Reply-To: <e3af97510906142050i7e77c0f3k76bdf89cda83280e@mail.gmail.com>
	(Chad Woolley's message of "Sun, 14 Jun 2009 20:50:30 -0700")
References: <e3af97510906142050i7e77c0f3k76bdf89cda83280e@mail.gmail.com>
Message-ID: <87zlc9v5fh.fsf@hagelb.org>

Chad Woolley <thewoolleyman at gmail.com> writes:

> I bumped the trunk version of RubyGems to 1.3.4.1.  I previously
> discussed [1] why this makes sense.
>
> To summarize, this makes it much easier for people writing and testing
> with CI against the RubyGems API, especially if they have embedded
> version checks to support backward- and forward-compatibility with
> older or unreleased versions of RubyGems.
>
> The version should be changed to something appropriate before the next
> release.  1.3.4.1 is arbitrary and interim, I don't care what it is,
> as long as it is > 1.3.4.  As soon as the 1.3.4 gem was released,
> trunk was NOT version 1.3.4 anymore.

We've got all the logic for prerelease versions in the Gem::Version
class. We could use it for RubyGems' version itself rather than just
versions of gems, since 1.3.4.1 is not actually accurate either without
moving to an "odd for development, even for release" scheme.

-Phil

From thewoolleyman at gmail.com  Mon Jun 15 13:03:16 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Mon, 15 Jun 2009 10:03:16 -0700
Subject: [Rubygems-developers] Trunk version of rubygems should always
	be > released version
In-Reply-To: <87zlc9v5fh.fsf@hagelb.org>
References: <e3af97510906142050i7e77c0f3k76bdf89cda83280e@mail.gmail.com> 
	<87zlc9v5fh.fsf@hagelb.org>
Message-ID: <e3af97510906151003p404e317ev6c9f5efa99b37b52@mail.gmail.com>

On Mon, Jun 15, 2009 at 9:16 AM, Phil Hagelberg<technomancy at gmail.com> wrote:
> We've got all the logic for prerelease versions in the Gem::Version
> class. We could use it for RubyGems' version itself rather than just
> versions of gems,

Sure, if it works. I haven't used the prerelease support yet, so I
didn't think of that.  I assume this works with Hoe too, which wants
to parse "VERSION = 'x..'" out of some file in the manifest?

> since 1.3.4.1 is not actually accurate either without
> moving to an "odd for development, even for release" scheme.

Yeah, we could make it 1.3.5.  I was just going with the smallest
possible increment in lieu of anything better.  Doesn't really matter
that much since it should be replaced before the next release, and
this version will only ever be seen by people hacking on rubygems.
The important thing is that apps using the rubygems API can check >
1.3.4 (for supporting unreleased version) or <= 1.3.4 (for backward
compatibility).

-- Chad

From noreply at rubyforge.org  Mon Jun 15 15:02:58 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Mon, 15 Jun 2009 15:02:58 -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: <20090615190258.4AD3218580F6@rubyforge.org>

Bugs item #26199, was opened at 2009-06-11 07: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: Open
Resolution: None
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: Bob Holt (bobholt)
Date: 2009-06-15 15: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 17: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 08: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 08: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 07: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 07: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 sevak001 at gmail.com  Thu Jun 18 16:25:15 2009
From: sevak001 at gmail.com (Sevada Abraamyan)
Date: Thu, 18 Jun 2009 13:25:15 -0700
Subject: [Rubygems-developers] Can I use RubyGems to package java, c++ code?
Message-ID: <f07d16140906181325x4847222cx3f8c46cadaecee86@mail.gmail.com>

I need to be able to package Java, C++, and Ruby code in a uniform format. I
was hoping to do this with RubyGems. Is this possible? If so can anyone
point to some documentation or info on how to do this? Thank you.

-- 
Sevada Abraamyan

From jftucker at gmail.com  Thu Jun 18 16:54:20 2009
From: jftucker at gmail.com (James Tucker)
Date: Thu, 18 Jun 2009 21:54:20 +0100
Subject: [Rubygems-developers] Can I use RubyGems to package java,
	c++ code?
In-Reply-To: <f07d16140906181325x4847222cx3f8c46cadaecee86@mail.gmail.com>
References: <f07d16140906181325x4847222cx3f8c46cadaecee86@mail.gmail.com>
Message-ID: <B35EF2B7-7A19-4BEA-8117-A1126245B6B0@gmail.com>


On 18 Jun 2009, at 21:25, Sevada Abraamyan wrote:

> I need to be able to package Java, C++, and Ruby code in a uniform  
> format. I
> was hoping to do this with RubyGems. Is this possible? If so can  
> anyone
> point to some documentation or info on how to do this? Thank you.

Just like you would install a ruby extension. You'd traditionally make  
a directory called ext/ and use an extconf.rb to create a makefile  
(using mkmf for configuration). For your specific needs, you could  
skip that and just store a makefile in the dir, system('./configure'),  
etc in extconf.rb.

There are also other external builders, but they're not so often used.

>
> -- 
> Sevada Abraamyan
> _______________________________________________
> Rubygems-developers mailing list
> http://rubyforge.org/projects/rubygems
> Rubygems-developers at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubygems-developers


From drbrain at segment7.net  Fri Jun 19 16:59:15 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Fri, 19 Jun 2009 13:59:15 -0700
Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2232 failed
In-Reply-To: <e3af97510906121655r43557d44oda63aed1ecc9923b@mail.gmail.com>
References: <4a32e2675a134_6358..fdbdd5b84329@ci.pivotallabs.com.tmail>
	<e3af97510906121655r43557d44oda63aed1ecc9923b@mail.gmail.com>
Message-ID: <F4DD77BC-8B31-4A8F-9199-5DBE7F269935@segment7.net>

On Jun 12, 2009, at 16:55, Chad Woolley wrote:

> On Fri, Jun 12, 2009 at 4:19 PM, <devnull+rubygems- 
> ci at pivotallabs.com> wrote:
>> The build failed.
>>
>> CHANGES
>> -------
>> New revision 2232 detected
>> Revision 2232 committed by zenspider on 2009-06-12 23:12:38
>> hoe'd the rakefile
>> ...
>> See http://ci.pivotallabs.com:3333/builds/RubyGems/2232 for details.
>
> Is this because of a downlevel Hoe version on our CI server?  If so,
> we can set up a wrapper build script to run GemInstaller (or anything
> you want to accomplish same thing) and also print out env stats.  This
> is what we do on the Rails build:
>
> http://github.com/rails/rails/blob/master/ci/ci_build.rb
>
> I DON'T want to manually install a required version of Hoe, even
> though I could - it is better to have the build completely specify its
> required dependencies (this is a shared server CI anyway, but it's the
> principle).

Yes, you need Hoe 2, which is backwards compatible with 1.x.

From drbrain at segment7.net  Fri Jun 19 18:02:49 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Fri, 19 Jun 2009 15:02:49 -0700
Subject: [Rubygems-developers] Hoe'ify broke Gem::RubyGemsVersion for me
In-Reply-To: <e3af97510906142030k5ac459c8v3264fd1e2d6bd07b@mail.gmail.com>
References: <e3af97510906121748s1e53a74l90cdb2d633f5c226@mail.gmail.com>
	<e3af97510906142030k5ac459c8v3264fd1e2d6bd07b@mail.gmail.com>
Message-ID: <FCA3A605-436F-46A9-A77F-DE3BE7BB39F4@segment7.net>

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.

From drbrain at segment7.net  Fri Jun 19 18:14:07 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Fri, 19 Jun 2009 15:14:07 -0700
Subject: [Rubygems-developers] Trunk version of rubygems should always
	be > released version
In-Reply-To: <e3af97510906142050i7e77c0f3k76bdf89cda83280e@mail.gmail.com>
References: <e3af97510906142050i7e77c0f3k76bdf89cda83280e@mail.gmail.com>
Message-ID: <DA1C7FCD-E66D-4051-9D2D-48E1965F9EA3@segment7.net>

On Jun 14, 2009, at 20:50, Chad Woolley wrote:

> I bumped the trunk version of RubyGems to 1.3.4.1.  I previously
> discussed [1] why this makes sense.

No.

We've been over this, and the answer is no.

Don't make the change unless you're making a release.

From drbrain at segment7.net  Fri Jun 19 18:24:07 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Fri, 19 Jun 2009 15:24:07 -0700
Subject: [Rubygems-developers] Hoe'ify broke Gem::RubyGemsVersion for me
In-Reply-To: <FCA3A605-436F-46A9-A77F-DE3BE7BB39F4@segment7.net>
References: <e3af97510906121748s1e53a74l90cdb2d633f5c226@mail.gmail.com>
	<e3af97510906142030k5ac459c8v3264fd1e2d6bd07b@mail.gmail.com>
	<FCA3A605-436F-46A9-A77F-DE3BE7BB39F4@segment7.net>
Message-ID: <4D2D0870-A20F-4C32-A637-326BACD77F07@segment7.net>

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.

From drbrain at segment7.net  Fri Jun 19 18:26:44 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Fri, 19 Jun 2009 15:26:44 -0700
Subject: [Rubygems-developers] Hoe'ify broke Gem::RubyGemsVersion for me
In-Reply-To: <e3af97510906121748s1e53a74l90cdb2d633f5c226@mail.gmail.com>
References: <e3af97510906121748s1e53a74l90cdb2d633f5c226@mail.gmail.com>
Message-ID: <59D8F622-9FD4-4BBA-AFF9-DF6ACBF18F7F@segment7.net>

On Jun 12, 2009, at 17:48, Chad Woolley wrote:
> The last commit 2232 broke Gem::RubyGemsVersion for me by moving it
> from rubygems/rubygems_version.rb to rubygems.rb.
>
> GemInstaller runs unit tests (and useful functional tests for Rubygems
> itself) via CI against the trunk version of RubyGems via an svn
> external.  Before, I could force the RubyGems version to come from the
> svn external by forcing a load of the trunk rubygems_version.rb before
> the system version of rubygems got activated.

This does not make sense to me.  Why would you use a system version of  
RubyGems but with a different version number?  It sounds like you're  
mixing and matching RubyGems code.

From drbrain at segment7.net  Fri Jun 19 18:27:21 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Fri, 19 Jun 2009 15:27:21 -0700
Subject: [Rubygems-developers] Fixed CI build
In-Reply-To: <e3af97510906141934s7af8aadpc0483165a3113371@mail.gmail.com>
References: <e3af97510906141934s7af8aadpc0483165a3113371@mail.gmail.com>
Message-ID: <66537CC9-936E-42FA-AF48-BE8984003153@segment7.net>

On Jun 14, 2009, at 19:34, Chad Woolley wrote:

> RubyGems has a Continuous Integration build [1].  A commit on Friday
> broke it [2], which I triaged with a suggested fix [3] even though I
> didn't break it.  It is good to fix builds as soon as they break [4],
> especially if your commit broke it.  It was still broken after three
> days [5], so I fixed it.
>
> As a nice side benefit, RubyGems now also has an
> 'install_build_dependencies.rb', just in case people trying to hack on
> rubygems are unaware that "undefined method `plugin' for Hoe:Class"
> really means "install latest hoe and hoe-seattlerb gems"...

I reverted this in favor of rake check_extra_deps.

From thewoolleyman at gmail.com  Sat Jun 20 05:11:05 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Sat, 20 Jun 2009 02:11:05 -0700
Subject: [Rubygems-developers] Fixed CI build
In-Reply-To: <66537CC9-936E-42FA-AF48-BE8984003153@segment7.net>
References: <e3af97510906141934s7af8aadpc0483165a3113371@mail.gmail.com> 
	<66537CC9-936E-42FA-AF48-BE8984003153@segment7.net>
Message-ID: <e3af97510906200211l33c90ad6ob10cb11db8504417@mail.gmail.com>

On Fri, Jun 19, 2009 at 3:27 PM, Eric Hodel<drbrain at segment7.net> wrote:
> I reverted this in favor of rake check_extra_deps.

Thanks, didn't know about that.

However, the original build error was because of an outdated version
of hoe which didn't have a 'plugin' method.  The
'install_development_dependencies.rb' approach I had ensures that hoe
> 2.0 is installed (and caused the CI server to update hoe and fix
itself without manual intervention)...

check_extra_deps wouldn't have fixed that, right?

From noreply at rubyforge.org  Sat Jun 20 14:50:28 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sat, 20 Jun 2009 14:50:28 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26299 ] undefined method
	`each' for #<String:0xcb6e3e4>
Message-ID: <20090620185028.8EB5D15B8020@rubyforge.org>

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

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Thomas Preymesser (thopre)
Assigned to: Nobody (None)
Summary: undefined method `each' for #<String:0xcb6e3e4>

Initial Comment:
i get the following message at the installation of each gem with Ruby 1.9

Updating ri class cache with 7980 classes...
ERROR:  While executing gem ... (NoMethodError)
    undefined method `each' for #<String:0xcb6e3e4>


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

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

From thewoolleyman at gmail.com  Sun Jun 21 15:44:58 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Sun, 21 Jun 2009 12:44:58 -0700
Subject: [Rubygems-developers] Trunk version of rubygems should always
	be > released version
In-Reply-To: <DA1C7FCD-E66D-4051-9D2D-48E1965F9EA3@segment7.net>
References: <e3af97510906142050i7e77c0f3k76bdf89cda83280e@mail.gmail.com> 
	<DA1C7FCD-E66D-4051-9D2D-48E1965F9EA3@segment7.net>
Message-ID: <e3af97510906211244h67603ad0t3ef258863015618a@mail.gmail.com>

On Fri, Jun 19, 2009 at 3:14 PM, Eric Hodel<drbrain at segment7.net> wrote:
> We've been over this, and the answer is no.
>
> Don't make the change unless you're making a release.

Why?  I've described valid and useful reasons to do this.  I don't
remember your reasons against it, can you repeat them?

Thanks,
-- Chad

From hgs at dmu.ac.uk  Sun Jun 21 17:04:31 2009
From: hgs at dmu.ac.uk (Hugh Sasse)
Date: Sun, 21 Jun 2009 22:04:31 +0100 (BST)
Subject: [Rubygems-developers] Trunk version of rubygems should always
 be > released version
In-Reply-To: <e3af97510906211244h67603ad0t3ef258863015618a@mail.gmail.com>
References: <e3af97510906142050i7e77c0f3k76bdf89cda83280e@mail.gmail.com>
	<DA1C7FCD-E66D-4051-9D2D-48E1965F9EA3@segment7.net>
	<e3af97510906211244h67603ad0t3ef258863015618a@mail.gmail.com>
Message-ID: <alpine.LFD.2.00.0906212158440.21466@trueman.cs.cse.dmu.ac.uk>

On Sun, 21 Jun 2009, Chad Woolley wrote:

> On Fri, Jun 19, 2009 at 3:14 PM, Eric Hodel<drbrain at segment7.net> wrote:
> > We've been over this, and the answer is no.
> >
> > Don't make the change unless you're making a release.
> 
> Why?  I've described valid and useful reasons to do this.  I don't
> remember your reasons against it, can you repeat them?

Off the top of my head I can't remember either, but it looks like it
might be time to compile a FAQ for things like this and other coding
standards, whether people should be expecting to be keel-hauled for
top posting, and so on.

The archive is pointed to in the message headers, no time for me to
search for you now.
> 
> Thanks,
> -- Chad

        Hugh

From djberg96 at gmail.com  Mon Jun 22 01:04:59 2009
From: djberg96 at gmail.com (Daniel Berger)
Date: Sun, 21 Jun 2009 23:04:59 -0600
Subject: [Rubygems-developers] Is zlib an official dependency?
Message-ID: <015501c9f2f6$ffbd4340$ff37c9c0$@com>

Hi,

Is it really necessary to have this many require's spread throughout the
rubygems source?

lib\rubygems\commands\mirror_command.rb:2:require 'zlib'
lib\rubygems\indexer.rb:3:require 'zlib'
lib\rubygems\old_format.rb:10:require 'zlib'
lib\rubygems\package.rb:10:require 'zlib'
lib\rubygems\server.rb:3:require 'zlib'
lib\rubygems\source_index.rb:527:    require 'zlib'
lib\rubygems\spec_fetcher.rb:1:require 'zlib'
lib\rubygems.rb:456:    require 'zlib'
lib\rubygems.rb:572:    require 'zlib'
lib\rubygems.rb:583:    require 'zlib'
lib\rubygems.rb:595:    require 'zlib'
test\gemutilities.rb:386:    require 'zlib'
test\test_gem_remote_fetcher.rb:9:require 'zlib'

I ask because I'd like to default to pr/zlib if zlib isn't found. If we can
limit it to a single require near the top of rubygems.rb, it would simplify
the process drastically. :)

Regards,

Dan




From noreply at rubyforge.org  Mon Jun 22 11:05:22 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Mon, 22 Jun 2009 11:05:22 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Patches-26394 ] Easier working on
	a fork of a gem
Message-ID: <20090622150522.6E244159807A@rubyforge.org>

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

Category: #gem and #require methods
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Vladimir Dobriakov (geekq)
Assigned to: Nobody (None)
Summary: Easier working on a fork of a gem

Initial Comment:
Hi,

I already asked about the issue on a mailing list
http://rubyforge.org/pipermail/rubygems-developers/2009-May/004665.html

Now I have a concrete suggestion (patch).

BTW, thanks for all the responses, I tried all the suggested
workarounds in addition to workarounds that already came
into my mind. Unfortunately they do not make my life less
miserable.

* editing source files to unshift $: can not be really used
with a long chain of dependent gems where I would like to
work on the gem in the middle of that chain - it would require 
editing the source code of other (depending) gems

* 'ruby -I' can not be universally used if you do not call
ruby directly; think of 'rake', 'script/server', ruby
scripts called from shell scripts

But after some research it seams, that there is a perfect
solution only one step away. And it probably even already
worked in the past. The documentation and implementation of
Kernel#gem underwent lot of changes in the past and the
documentation and the behavior seem not to match anymore.

= Suggestion 1

My suggestion is to make the work on a private fork of a gem
easy through environment variables by:

1. giving the developer version of a gem higher priority
with RUBYLIB (already works as desired) 

2. instructing rubygems through GEM_SKIP to ignore the
version requirements in the Kernel#gem statements for
particular gem (s. patch)


= Alternative 2

Alternatively, if -I switch really works as promized in rdoc

  # In older RubyGems versions, the environment variable GEM_SKIP could be
  # used to skip activation of specified gems, for example to test out changes
  # that haven't been installed yet.  Now RubyGems defers to -I and the
  # RUBYLIB environment variable to skip activation of a gem.

and RUBYLIB does not work due a bug, then we should fix this
bug.  Or is that behaviour a feature and the
documentation needs to be fixed? For me RUBYLIB does not
skip the activation - I get "RubyGem version error:".



I'm sure, I'm not the only one having big problems, other
developers are also forced to do all possible sorts of dirty
tricks to somehow help themselves [1]

if respond_to? :gem
  begin
    begin
      gem 'locale', '>=2.0'
    rescue Gem::LoadError
    end
  rescue NoMethodError
  else LoadError
  end
end

Unfortunately, this particular one by my friend Masao does not work well.

I would be glad to provide any clarification about usage
scenarios bugging me so much and the motivation behind the
patch.

Best Regards,

Vladimir

[1] http://github.com/mutoh/gettext/blob/ee09a33de94a2699fb5d8b6894cb16a383a2963a/lib/gettext.rb#L16


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

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

From thewoolleyman at gmail.com  Tue Jun 23 03:01:36 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Tue, 23 Jun 2009 00:01:36 -0700
Subject: [Rubygems-developers] Trunk version of rubygems should always
	be > released version
In-Reply-To: <alpine.LFD.2.00.0906212158440.21466@trueman.cs.cse.dmu.ac.uk>
References: <e3af97510906142050i7e77c0f3k76bdf89cda83280e@mail.gmail.com> 
	<DA1C7FCD-E66D-4051-9D2D-48E1965F9EA3@segment7.net>
	<e3af97510906211244h67603ad0t3ef258863015618a@mail.gmail.com> 
	<alpine.LFD.2.00.0906212158440.21466@trueman.cs.cse.dmu.ac.uk>
Message-ID: <e3af97510906230001h2d28f345vb601479225082c40@mail.gmail.com>

On Sun, Jun 21, 2009 at 2:04 PM, Hugh Sasse<hgs at dmu.ac.uk> wrote:
> On Sun, 21 Jun 2009, Chad Woolley wrote:
>> On Fri, Jun 19, 2009 at 3:14 PM, Eric Hodel<drbrain at segment7.net> wrote:
>> > We've been over this, and the answer is no.
>> Why? ?I've described valid and useful reasons to do this. ?I don't
>> remember your reasons against it, can you repeat them?
> The archive is pointed to in the message headers, no time for me to
> search for you now.

You don't need to search the archives for me, I already did - my first
post in this thread contains a link to the original unanswered
question.  I have followed every message on this list since I joined
in Feb. 06, and don't recall seeing it ever addressed elsewhere, nor
did I find it browsing my chat logs with Eric.

This is just usage of a prerelease version in trunk.  It is a trivial
(two character) change which makes it easier for RubyGems API users to
maintain version checks and automated tests for forward and backward
compatibility.  Right now I have to fake the trunk version to be 9.9.9
for version comparisons to work against unreleased code, which is
silly.  If there is legitimate reason to not bump to a prerelease
version in trunk, or problems it would cause, I'd like to know,
because I can't think of any.

Thanks,
-- Chad

From thewoolleyman at gmail.com  Tue Jun 23 15:57:26 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Tue, 23 Jun 2009 12:57:26 -0700
Subject: [Rubygems-developers] Trunk version of rubygems should always
	be > released version
In-Reply-To: <alpine.LFD.2.00.0906231330540.1748@trueman.cs.cse.dmu.ac.uk>
References: <e3af97510906142050i7e77c0f3k76bdf89cda83280e@mail.gmail.com> 
	<DA1C7FCD-E66D-4051-9D2D-48E1965F9EA3@segment7.net>
	<e3af97510906211244h67603ad0t3ef258863015618a@mail.gmail.com> 
	<alpine.LFD.2.00.0906212158440.21466@trueman.cs.cse.dmu.ac.uk> 
	<e3af97510906230001h2d28f345vb601479225082c40@mail.gmail.com> 
	<alpine.LFD.2.00.0906231330540.1748@trueman.cs.cse.dmu.ac.uk>
Message-ID: <e3af97510906231257u7e5da155sbd319896767f464a@mail.gmail.com>

On Tue, Jun 23, 2009 at 5:32 AM, Hugh Sasse<hgs at dmu.ac.uk> wrote:
> Sorry if that came across as criticism, I was trying to provide the
> only help I could at the time. ?I'll leave the other points to Eric.

Yeah sorry too for being inflammatory and wasting group bandwidth
harping on a minor issue.  However, I try to contribute to RubyGems by
using the API and doing automated functional testing.  This is AFAIK a
trivial innocuous change that makes it much easier for me to do that,
and I'd just like an objective response or counterpoint other than
"no".

From drbrain at segment7.net  Tue Jun 23 16:50:34 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Tue, 23 Jun 2009 13:50:34 -0700
Subject: [Rubygems-developers] Is zlib an official dependency?
In-Reply-To: <015501c9f2f6$ffbd4340$ff37c9c0$@com>
References: <015501c9f2f6$ffbd4340$ff37c9c0$@com>
Message-ID: <8D0694AE-A434-4659-871D-3C6A7AE527A5@segment7.net>

On Jun 21, 2009, at 22:04, Daniel Berger wrote:
> Is it really necessary to have this many require's spread throughout  
> the
> rubygems source?
>
> lib\rubygems\commands\mirror_command.rb:2:require 'zlib'
> lib\rubygems\indexer.rb:3:require 'zlib'
> lib\rubygems\old_format.rb:10:require 'zlib'
> lib\rubygems\package.rb:10:require 'zlib'
> lib\rubygems\server.rb:3:require 'zlib'
> lib\rubygems\source_index.rb:527:    require 'zlib'
> lib\rubygems\spec_fetcher.rb:1:require 'zlib'
> lib\rubygems.rb:456:    require 'zlib'
> lib\rubygems.rb:572:    require 'zlib'
> lib\rubygems.rb:583:    require 'zlib'
> lib\rubygems.rb:595:    require 'zlib'
> test\gemutilities.rb:386:    require 'zlib'
> test\test_gem_remote_fetcher.rb:9:require 'zlib'
>
> I ask because I'd like to default to pr/zlib if zlib isn't found. If  
> we can
> limit it to a single require near the top of rubygems.rb, it would  
> simplify
> the process drastically. :)

I'd be happy to see if they were all pushed down into lib/ 
rubygems.rb.  zlib shouldn't be required for the runtime, the runtime  
should only load what it needs (smaller is better).

From drbrain at segment7.net  Tue Jun 23 16:53:58 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Tue, 23 Jun 2009 13:53:58 -0700
Subject: [Rubygems-developers] Trunk version of rubygems should always
	be > released version
In-Reply-To: <e3af97510906231257u7e5da155sbd319896767f464a@mail.gmail.com>
References: <e3af97510906142050i7e77c0f3k76bdf89cda83280e@mail.gmail.com>
	<DA1C7FCD-E66D-4051-9D2D-48E1965F9EA3@segment7.net>
	<e3af97510906211244h67603ad0t3ef258863015618a@mail.gmail.com>
	<alpine.LFD.2.00.0906212158440.21466@trueman.cs.cse.dmu.ac.uk>
	<e3af97510906230001h2d28f345vb601479225082c40@mail.gmail.com>
	<alpine.LFD.2.00.0906231330540.1748@trueman.cs.cse.dmu.ac.uk>
	<e3af97510906231257u7e5da155sbd319896767f464a@mail.gmail.com>
Message-ID: <42DB12F6-5D0B-469C-969F-CED31F80B0F9@segment7.net>

On Jun 23, 2009, at 12:57, Chad Woolley wrote:
> On Tue, Jun 23, 2009 at 5:32 AM, Hugh Sasse<hgs at dmu.ac.uk> wrote:
>> Sorry if that came across as criticism, I was trying to provide the
>> only help I could at the time.  I'll leave the other points to Eric.
>
> Yeah sorry too for being inflammatory and wasting group bandwidth
> harping on a minor issue.  However, I try to contribute to RubyGems by
> using the API and doing automated functional testing.  This is AFAIK a
> trivial innocuous change that makes it much easier for me to do that,
> and I'd just like an objective response or counterpoint other than
> "no".

I think multiruby does something similar to what you do with gem  
versions, but multiruby doesn't use the ruby version as the  
discriminator, it uses the directory name instead.  In this way  
multiruby allows for multiple installs of the same version (i.e.  
different compile flags) without having to change the version around.

From devnull+rubygems-ci at pivotallabs.com  Tue Jun 23 20:36:29 2009
From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com)
Date: Wed, 24 Jun 2009 00:36:29 +0000
Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2255 failed
Message-ID: <4a41750dd9178_6358..fdbdd5b84587@ci.pivotallabs.com.tmail>

The build failed.

CHANGES
-------
New revision 2255 detected
Revision 2255 committed by drbrain on 2009-06-24 00:27:41
Only print to stdout during gem building when verbose
  M /trunk/lib/rubygems/package_task.rb
  M /trunk/ChangeLog
  M /trunk/lib/rubygems/builder.rb



TEST FAILURES AND ERRORS
-----------------------
Name: test_gem_package(TestGemPackageTask)
Type: Error
Message: NoMethodError: undefined method `gem_file' for #<Gem::PackageTask:0xb7802d90>

    ./test/test_gem_package_task.rb:38:in `test_gem_package'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:434:in `__send__'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:434:in `run'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:413:in `run_test_suites'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:407:in `each'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:407:in `run_test_suites'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:406:in `each'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:406:in `run_test_suites'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:386:in `run'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:327:in `autorun'


Name: test_gem_package_with_current_platform(TestGemPackageTask)
Type: Error
Message: NoMethodError: undefined method `gem_file' for #<Gem::PackageTask:0xb77eec78>

    ./test/test_gem_package_task.rb:52:in `test_gem_package_with_current_platform'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:434:in `__send__'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:434:in `run'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:413:in `run_test_suites'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:407:in `each'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:407:in `run_test_suites'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:406:in `each'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:406:in `run_test_suites'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:386:in `run'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:327:in `autorun'


Name: test_gem_package_with_ruby_platform(TestGemPackageTask)
Type: Error
Message: NoMethodError: undefined method `gem_file' for #<Gem::PackageTask:0xb77d8f18>

    ./test/test_gem_package_task.rb:66:in `test_gem_package_with_ruby_platform'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:434:in `__send__'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:434:in `run'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:413:in `run_test_suites'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:407:in `each'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:407:in `run_test_suites'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:406:in `each'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:406:in `run_test_suites'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:386:in `run'
    /usr/local/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:327:in `autorun'




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

From devnull+rubygems-ci at pivotallabs.com  Tue Jun 23 21:02:25 2009
From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com)
Date: Wed, 24 Jun 2009 01:02:25 +0000
Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2256 fixed
Message-ID: <4a417b21ec753_6358..fdbdd5b846ee@ci.pivotallabs.com.tmail>

The build has been fixed.

CHANGES
-------
New revision 2256 detected
Revision 2256 committed by drbrain on 2009-06-24 00:53:33
Fix test
  M /trunk/test/test_gem_package_task.rb



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

From drbrain at segment7.net  Tue Jun 23 23:15:54 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Tue, 23 Jun 2009 20:15:54 -0700
Subject: [Rubygems-developers] 1.3.5 soon
In-Reply-To: <e3af97510906231954i370dd3cfs9aba58cc3ae84d80@mail.gmail.com>
References: <6D0B5E11-1149-4898-8FF6-C5727D7491BC@segment7.net>
	<e3af97510906231954i370dd3cfs9aba58cc3ae84d80@mail.gmail.com>
Message-ID: <31BC61BD-10C6-4724-B860-2E2B50A61C56@segment7.net>

On Jun 23, 2009, at 19:54, Chad Woolley wrote:
> On Tue, Jun 23, 2009 at 4:45 PM, Eric Hodel<drbrain at segment7.net>  
> wrote:
>> I've made a 1_3 branch from the REL_1_3_4 tag and merged over the  
>> prerelease
>> gems fixes from it.  I'd like to do a 1.3.5 soon.
>>
>> Bug fixes:
>>
>> * Fix use of prerelease gems.
>>
>> Here's a tarball for testing:
>
> Attachment?  I would have sent it, but wasn't sure how you generated.
> What's the right package task?

Damn you mailing list software!

Try:

http://segment7.net/temp/rubygems-1.3.4.tgz

From transfire at gmail.com  Wed Jun 24 07:36:12 2009
From: transfire at gmail.com (Trans)
Date: Wed, 24 Jun 2009 04:36:12 -0700 (PDT)
Subject: [Rubygems-developers] Gem.active?, Gem.gemspec and Gem.gempath
Message-ID: <be2da6a4-05e0-46f7-99c5-96f9f49e878c@n4g2000vba.googlegroups.com>

Hi--

I have these extensions I've used on a couple of occasions. I just
tested them out again and they still seem to be working fine. Maybe
other's are interested. Or perhaps there are other better ways to do
these things?

  module Gem

    def self.active?(gemname)
      @loaded_specs ||= Hash.new
      @loaded_specs.key? gemname
    end

    def self.gemspec(gemname)
      @loaded_specs[gemname] if active?(gemname)
    end

    def self.gempath(gemname, subdir=nil)
      if active?(gemname)
        if subdir
          File.join( @loaded_specs[gemname].full_gem_path, subdir )
        else
          @loaded_specs[gemname].full_gem_path
        end
      end
    end

  end

Thanks,
Trans.

From luislavena at gmail.com  Wed Jun 24 19:28:00 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Wed, 24 Jun 2009 20:28:00 -0300
Subject: [Rubygems-developers] 1.3.5 soon
In-Reply-To: <6D0B5E11-1149-4898-8FF6-C5727D7491BC@segment7.net>
References: <6D0B5E11-1149-4898-8FF6-C5727D7491BC@segment7.net>
Message-ID: <71166b3b0906241628t477ad6cdud030599a43e4003@mail.gmail.com>

On Tue, Jun 23, 2009 at 8:45 PM, Eric Hodel<drbrain at segment7.net> wrote:
> I've made a 1_3 branch from the REL_1_3_4 tag and merged over the prerelease
> gems fixes from it. ?I'd like to do a 1.3.5 soon.
>
> Bug fixes:
>
> * Fix use of prerelease gems.
>

What about trunk? right now trunk just generate errors:

./lib/rubygems/config_file.rb:38:in `initialize': wrong number of
arguments (5 for 4) (ArgumentError)
        from ./lib/rubygems/config_file.rb:38:in `new'
        from ./lib/rubygems/config_file.rb:38
        from ./lib/rubygems.rb:1104:in `require'
        from ./lib/rubygems.rb:1104
        from -e:1:in `require'
        from -e:1
rake aborted!

as for 1_3 branch, we started pretty good:

Started
C:/Users/Luis/.gem/ruby/1.8/gems/minitest-1.4.1/lib/minitest/unit.rb:440:in
`trap': unsupported signal SIGINFO (ArgumentError)
        from C:/Users/Luis/.gem/ruby/1.8/gems/minitest-1.4.1/lib/minitest/unit.rb:440:in
`run'
        from C:/Users/Luis/.gem/ruby/1.8/gems/minitest-1.4.1/lib/minitest/unit.rb:420:in
`run_test_suites'
        from C:/Users/Luis/.gem/ruby/1.8/gems/minitest-1.4.1/lib/minitest/unit.rb:414:in
`each'
        from C:/Users/Luis/.gem/ruby/1.8/gems/minitest-1.4.1/lib/minitest/unit.rb:414:in
`run_test_suites'
        from C:/Users/Luis/.gem/ruby/1.8/gems/minitest-1.4.1/lib/minitest/unit.rb:413:in
`each'
        from C:/Users/Luis/.gem/ruby/1.8/gems/minitest-1.4.1/lib/minitest/unit.rb:413:in
`run_test_suites'
        from C:/Users/Luis/.gem/ruby/1.8/gems/minitest-1.4.1/lib/minitest/unit.rb:387:in
`run'
        from C:/Users/Luis/.gem/ruby/1.8/gems/minitest-1.4.1/lib/minitest/unit.rb:328:in
`autorun'
rake aborted!
Command failed with status (1): [C:/Users/Luis/Tools/Ruby/ruby-1.8.6-p368-i...]

(me being sarcastic)

-- 
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  Wed Jun 24 20:27:26 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Wed, 24 Jun 2009 17:27:26 -0700
Subject: [Rubygems-developers] 1.3.5 soon
In-Reply-To: <71166b3b0906241628t477ad6cdud030599a43e4003@mail.gmail.com>
References: <6D0B5E11-1149-4898-8FF6-C5727D7491BC@segment7.net>
	<71166b3b0906241628t477ad6cdud030599a43e4003@mail.gmail.com>
Message-ID: <FA9FBE95-B973-47E9-A906-A3D0E4C4E946@segment7.net>

On Jun 24, 2009, at 16:28, Luis Lavena wrote:
> On Tue, Jun 23, 2009 at 8:45 PM, Eric Hodel<drbrain at segment7.net>  
> wrote:
>> I've made a 1_3 branch from the REL_1_3_4 tag and merged over the  
>> prerelease
>> gems fixes from it.  I'd like to do a 1.3.5 soon.
>>
>> Bug fixes:
>>
>> * Fix use of prerelease gems.
>
> What about trunk? right now trunk just generate errors:
>
> ./lib/rubygems/config_file.rb:38:in `initialize': wrong number of
> arguments (5 for 4) (ArgumentError)

I guess :stdcall is only for 1.9+

> as for 1_3 branch, we started pretty good:
>
> Started
> C:/Users/Luis/.gem/ruby/1.8/gems/minitest-1.4.1/lib/minitest/unit.rb: 
> 440:in
> `trap': unsupported signal SIGINFO (ArgumentError)

Does minitest 1.4.0 work?  I will fix minitest tomorrow.

> (me being sarcastic)

:)

From luislavena at gmail.com  Wed Jun 24 20:41:58 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Wed, 24 Jun 2009 21:41:58 -0300
Subject: [Rubygems-developers] 1.3.5 soon
In-Reply-To: <FA9FBE95-B973-47E9-A906-A3D0E4C4E946@segment7.net>
References: <6D0B5E11-1149-4898-8FF6-C5727D7491BC@segment7.net> 
	<71166b3b0906241628t477ad6cdud030599a43e4003@mail.gmail.com> 
	<FA9FBE95-B973-47E9-A906-A3D0E4C4E946@segment7.net>
Message-ID: <71166b3b0906241741o29c5d7d9sd1e49fbccad84d39@mail.gmail.com>

On Wed, Jun 24, 2009 at 9:27 PM, Eric Hodel<drbrain at segment7.net> wrote:
> On Jun 24, 2009, at 16:28, Luis Lavena wrote:
>>
>> On Tue, Jun 23, 2009 at 8:45 PM, Eric Hodel<drbrain at segment7.net> wrote:
>>>
>>> I've made a 1_3 branch from the REL_1_3_4 tag and merged over the
>>> prerelease
>>> gems fixes from it. ?I'd like to do a 1.3.5 soon.
>>>
>>> Bug fixes:
>>>
>>> * Fix use of prerelease gems.
>>
>> What about trunk? right now trunk just generate errors:
>>
>> ./lib/rubygems/config_file.rb:38:in `initialize': wrong number of
>> arguments (5 for 4) (ArgumentError)
>
> I guess :stdcall is only for 1.9+
>

Afaik is only for 1.9 only.

The funniest thing is that Win32API was used to report a deprecation
warning on p0, but seems now is gone?

>> as for 1_3 branch, we started pretty good:
>>
>> Started
>>
>> C:/Users/Luis/.gem/ruby/1.8/gems/minitest-1.4.1/lib/minitest/unit.rb:440:in
>> `trap': unsupported signal SIGINFO (ArgumentError)
>
> Does minitest 1.4.0 work? ?I will fix minitest tomorrow.
>

Yup, it worked.

Now I need to install the rake gem inside the ruby installation and
not in the shared place :-P

Will keep you posted with the results.

Cheers,
-- 
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  Wed Jun 24 22:07:07 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Wed, 24 Jun 2009 19:07:07 -0700
Subject: [Rubygems-developers] Trunk version of rubygems should always
	be > released version
In-Reply-To: <42DB12F6-5D0B-469C-969F-CED31F80B0F9@segment7.net>
References: <e3af97510906142050i7e77c0f3k76bdf89cda83280e@mail.gmail.com> 
	<DA1C7FCD-E66D-4051-9D2D-48E1965F9EA3@segment7.net>
	<e3af97510906211244h67603ad0t3ef258863015618a@mail.gmail.com> 
	<alpine.LFD.2.00.0906212158440.21466@trueman.cs.cse.dmu.ac.uk> 
	<e3af97510906230001h2d28f345vb601479225082c40@mail.gmail.com> 
	<alpine.LFD.2.00.0906231330540.1748@trueman.cs.cse.dmu.ac.uk> 
	<e3af97510906231257u7e5da155sbd319896767f464a@mail.gmail.com> 
	<42DB12F6-5D0B-469C-969F-CED31F80B0F9@segment7.net>
Message-ID: <e3af97510906241907o8889e3cw9a4e7d4bac8291d@mail.gmail.com>

On Tue, Jun 23, 2009 at 1:53 PM, Eric Hodel<drbrain at segment7.net> wrote:
> I think multiruby does something similar to what you do with gem versions

No it doesn't, I looked [1].  Multiruby itself does not have automated
CI running against every commit of MRI trunk.

It DOES parse the version out of the MRI *tags* and use them, though.
This is exactly what I am asking for as well - some way to distinguish
versions - except I want to do it for every trunk commit as well as
releases/tags, so I can do conditional version checks against
unreleased breaking API changes if necessary to keep green.

However, if you keep the trunk version the same as the released
version, it is a lot more effort to fake a different version than
actually exists in the code - instead of just a simple comparison of
the actual version using Gem::Version::Requirement#satisfied_by?

Plus, to reiterate, trunk is NOT the released version.  For example,
the 1.3.5 preview tarball you just sent out as version 1.3.4 was NOT
1.3.4 code - it was 1.3.5 code.  Yes?  Yes!

Thanks,
-- Chad

[1] http://zentest.rubyforge.org/svn/ZenTest/dev/lib/multiruby.rb

From ryand-ruby at zenspider.com  Wed Jun 24 23:06:24 2009
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Wed, 24 Jun 2009 20:06:24 -0700
Subject: [Rubygems-developers] Trunk version of rubygems should always
	be > released version
In-Reply-To: <e3af97510906241907o8889e3cw9a4e7d4bac8291d@mail.gmail.com>
References: <e3af97510906142050i7e77c0f3k76bdf89cda83280e@mail.gmail.com>
	<DA1C7FCD-E66D-4051-9D2D-48E1965F9EA3@segment7.net>
	<e3af97510906211244h67603ad0t3ef258863015618a@mail.gmail.com>
	<alpine.LFD.2.00.0906212158440.21466@trueman.cs.cse.dmu.ac.uk>
	<e3af97510906230001h2d28f345vb601479225082c40@mail.gmail.com>
	<alpine.LFD.2.00.0906231330540.1748@trueman.cs.cse.dmu.ac.uk>
	<e3af97510906231257u7e5da155sbd319896767f464a@mail.gmail.com>
	<42DB12F6-5D0B-469C-969F-CED31F80B0F9@segment7.net>
	<e3af97510906241907o8889e3cw9a4e7d4bac8291d@mail.gmail.com>
Message-ID: <C4C0146B-F9D2-4759-B250-9E0D6CC716ED@zenspider.com>


On Jun 24, 2009, at 19:07 , Chad Woolley wrote:

> However, if you keep the trunk version the same as the released
> version, it is a lot more effort to fake a different version than
> actually exists in the code - instead of just a simple comparison of
> the actual version using Gem::Version::Requirement#satisfied_by?

I'm gonna wade in on this thread ONE time only...

This is a false dilemma. You're insisting on using the version to  
distinguish trunk-run-from-svn vs released versions. But you (should)  
already know you're running from trunk vs running on released  
versions. Not only that, you're also running on every commit made to  
trunk. Don't you want to distinguish them from each other?. If you do,  
use svn to your advantage and tack it onto the version:

   "#{current_version_or_trunk_or_whatever}.r#{`svnversion .`}"

Eric pointed out that multiruby uses the install directory names to  
distinguish the versions:

> % ls ~/.multiruby/install/
> 1.8.6-p287	1.8.6-p368	1.8.7-p160	1.8.7-p72	1.9.1-p129

and that is the only thing it uses to report versions on runs. It  
doesn't have to be fancier than that. If I were to extend multiruby to  
run on multiple commits on trunk, I'd use the snippet above to report  
the exact commit.

Just because something makes sense in your development model doesn't  
mean it makes sense in ours. Right before a release, we look at the  
changelog from the last release to the head of trunk and determine  
what sort of version bump it needs (major/minor/bug). Doing more than  
that is not a good use of our time. Changing the version TWICE for  
every release makes as much sense as knees on a fish to us.

Finally, I meant what I said about one time only. I'm not going to  
respond to anything else on this thread. I've been watching it go by  
and the only word that comes to mind consistently is "mentarbation".  
Please. Drop it. Let's get on to more useful things.


From thewoolleyman at gmail.com  Thu Jun 25 03:02:50 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Thu, 25 Jun 2009 00:02:50 -0700
Subject: [Rubygems-developers] Trunk version of rubygems should always
	be > released version
In-Reply-To: <C4C0146B-F9D2-4759-B250-9E0D6CC716ED@zenspider.com>
References: <e3af97510906142050i7e77c0f3k76bdf89cda83280e@mail.gmail.com> 
	<DA1C7FCD-E66D-4051-9D2D-48E1965F9EA3@segment7.net>
	<e3af97510906211244h67603ad0t3ef258863015618a@mail.gmail.com> 
	<alpine.LFD.2.00.0906212158440.21466@trueman.cs.cse.dmu.ac.uk> 
	<e3af97510906230001h2d28f345vb601479225082c40@mail.gmail.com> 
	<alpine.LFD.2.00.0906231330540.1748@trueman.cs.cse.dmu.ac.uk> 
	<e3af97510906231257u7e5da155sbd319896767f464a@mail.gmail.com> 
	<42DB12F6-5D0B-469C-969F-CED31F80B0F9@segment7.net>
	<e3af97510906241907o8889e3cw9a4e7d4bac8291d@mail.gmail.com> 
	<C4C0146B-F9D2-4759-B250-9E0D6CC716ED@zenspider.com>
Message-ID: <e3af97510906250002s4d31541gf8637d1d860f353b@mail.gmail.com>

On Wed, Jun 24, 2009 at 8:06 PM, Ryan Davis<ryand-ruby at zenspider.com> wrote:
> I've been watching it go by and the only
> word that comes to mind consistently is "mentarbation".

Cute term.  However, repeated refusal to answer a question directly
begets verbosity.  If you don't want me to keep explaining myself in
greater and greater detail, don't keep ignoring clearly stated points
and making irrelevant responses and suggestions.  Also, this thread
would not have existed past my single courtesy post if you hadn't
rolled back my two-character commit in the first place.

Other comments (verbose yet still carefully chosen after *reading*
your email - hint hint):

* You still never described any problems this would cause for your
development model, or why it matters at all to you.

* I *already* do what multiruby does - I freeze selected major
*released* versions of RubyGems in version-named directories and can
run dedicated CI projects against them.  That has nothing to do this
issue.
* No, I don't care about parsing or distinguishing different revisions
of trunk, because they are not released.  They are all the same to me
for purposes of API compatibility checks: "> last_release".  That has
nothing to do with this issue either.

* "Doing more than that is not a good use of our time."  You don't
even have to do it yourselves, Eric gave me commit rights a while back
(unless you get pissed and revoke it).  I use this to help out as I
can, running CI and (very) occasional patches, and I always try to be
very diligent with good Changelog comments, etc.  That's what I was
originally trying to do in this thread...

* "Please. Drop it. Let's get on to more useful things."  I considered
that, but then decided against it, since you still have not shown that
you understand the issue, and are telling me to go write some
unnecessary and overly complex code.  That justifies further
discussion in my book.  This is a development list, after all.  Anyone
who doesn't care about this topic should have hit mute in gmail a long
time ago.

Let me explain, verbosely, yet again:

The main point here is for an API client to be able to tell what
version of code it is running against.  That is a *requirement* for
properly managing backward and forward compatibility.   If you break
the API for me, I want my client to *conditionally* execute code to
handle that.  I want to add that client code immediately and
proactively, as soon as you break the API, so I'm ready to release my
client update as soon as (ideally before) you release the API.

I want my conditional compatibility code to only run on *future*
releases - NOT the current release, because the API is not broken in
the current release.  The logical way to do that is to have a
*different* version for the current and the future API release.  The
current and future release are not the same code; my client does not
interact with them in the same way; therefore they should not have the
same version.

Freezing old versions and parsing revisions in future release do not
solve this problem - I can't do that in my client code, and there's no
reason to do it in my test code.  What does solve these problems,
simply, and correctly, is *comparing* versions.  You can only compare
versions if they are different.  There is a simple method built into
rubygems for exactly this purpose:
Gem::Version::Requirement#satisfied_by?  I don't know how many other
different ways I can explain it, so I'll stop.

Here's my paraphrase of the tone of your note:

"We won't allow you to commit two characters after each release.
These changes don't make any difference to our "developement model",
or even matter to us at all, but we are still refusing because we are
in control.  Instead, go write some unnecessary and complex code in
your own API client and tests."

The phrase that comes consistently to MY mind is a quote I heard from
Evan Phoenix: "You are not the project, Mr. Ego!"

http://pivotallabs.com/users/chad/blog/articles/category/152-mtnwestrubyconf

Anyway, no hard feelings.  Just being an OCD programmer and trying to
get you to understand my point.  You do a lot of great stuff,
especially all the metrics tools.  I'm in awe of Eric too, the stuff
he's done for RubyGems and Ruby is huge.  Great job.

Thanks,
-- Chad

From drbrain at segment7.net  Thu Jun 25 17:40:29 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Thu, 25 Jun 2009 14:40:29 -0700
Subject: [Rubygems-developers] 1.3.5 soon
In-Reply-To: <71166b3b0906241741o29c5d7d9sd1e49fbccad84d39@mail.gmail.com>
References: <6D0B5E11-1149-4898-8FF6-C5727D7491BC@segment7.net>
	<71166b3b0906241628t477ad6cdud030599a43e4003@mail.gmail.com>
	<FA9FBE95-B973-47E9-A906-A3D0E4C4E946@segment7.net>
	<71166b3b0906241741o29c5d7d9sd1e49fbccad84d39@mail.gmail.com>
Message-ID: <3B2994FA-91EE-452F-84AD-CFB87203D0C6@segment7.net>

On Jun 24, 2009, at 17:41, Luis Lavena wrote:
> On Wed, Jun 24, 2009 at 9:27 PM, Eric Hodel<drbrain at segment7.net>  
> wrote:
>> On Jun 24, 2009, at 16:28, Luis Lavena wrote:
>>>
>>> On Tue, Jun 23, 2009 at 8:45 PM, Eric Hodel<drbrain at segment7.net>  
>>> wrote:
>>>>
>>>> I've made a 1_3 branch from the REL_1_3_4 tag and merged over the
>>>> prerelease
>>>> gems fixes from it.  I'd like to do a 1.3.5 soon.
>>>>
>>>> Bug fixes:
>>>>
>>>> * Fix use of prerelease gems.
>>>
>>> What about trunk? right now trunk just generate errors:
>>>
>>> ./lib/rubygems/config_file.rb:38:in `initialize': wrong number of
>>> arguments (5 for 4) (ArgumentError)
>>
>> I guess :stdcall is only for 1.9+
>>
>
> Afaik is only for 1.9 only.

Ok, I fixed this on trunk and merged to the branch.

You can try either updating from the branch or downloading a new  
tarball from:

http://segment7.net/temp/rubygems-1.3.4.tgz

> The funniest thing is that Win32API was used to report a deprecation
> warning on p0, but seems now is gone?
>
>>> as for 1_3 branch, we started pretty good:
>>>
>>> Started
>>>
>>> C:/Users/Luis/.gem/ruby/1.8/gems/minitest-1.4.1/lib/minitest/ 
>>> unit.rb:440:in
>>> `trap': unsupported signal SIGINFO (ArgumentError)
>>
>> Does minitest 1.4.0 work?  I will fix minitest tomorrow.
>
> Yup, it worked.

Ryan released minitest 1.4.2 which doesn't trap SIGINFO on systems  
that don't support it.

From luislavena at gmail.com  Thu Jun 25 18:20:34 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Thu, 25 Jun 2009 19:20:34 -0300
Subject: [Rubygems-developers] 1.3.5 soon
In-Reply-To: <3B2994FA-91EE-452F-84AD-CFB87203D0C6@segment7.net>
References: <6D0B5E11-1149-4898-8FF6-C5727D7491BC@segment7.net> 
	<71166b3b0906241628t477ad6cdud030599a43e4003@mail.gmail.com> 
	<FA9FBE95-B973-47E9-A906-A3D0E4C4E946@segment7.net>
	<71166b3b0906241741o29c5d7d9sd1e49fbccad84d39@mail.gmail.com> 
	<3B2994FA-91EE-452F-84AD-CFB87203D0C6@segment7.net>
Message-ID: <71166b3b0906251520j6098b698q38fa62893f79a6dc@mail.gmail.com>

On Thu, Jun 25, 2009 at 6:40 PM, Eric Hodel<drbrain at segment7.net> wrote:
>
> Ok, I fixed this on trunk and merged to the branch.
>
> You can try either updating from the branch or downloading a new tarball
> from:
>
> http://segment7.net/temp/rubygems-1.3.4.tgz
>

http://pastie.org/524829

> Ryan released minitest 1.4.2 which doesn't trap SIGINFO on systems that
> don't support it.

That worked, thank Ryan from me.

Now, 1.9 results:

http://pastie.org/524832

Looks like ChangeLog is not being parsed properly by Hoe:

Hoe installed stuff:

C:\Users\Luis\Projects\oss\rubygems-1_3>gem list hoe

*** LOCAL GEMS ***

hoe (2.3.1, 1.12.2)
hoe-seattlerb (1.2.0)

-- 
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  Thu Jun 25 21:01:24 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Thu, 25 Jun 2009 18:01:24 -0700
Subject: [Rubygems-developers] 1.3.5 soon
In-Reply-To: <71166b3b0906251520j6098b698q38fa62893f79a6dc@mail.gmail.com>
References: <6D0B5E11-1149-4898-8FF6-C5727D7491BC@segment7.net>
	<71166b3b0906241628t477ad6cdud030599a43e4003@mail.gmail.com>
	<FA9FBE95-B973-47E9-A906-A3D0E4C4E946@segment7.net>
	<71166b3b0906241741o29c5d7d9sd1e49fbccad84d39@mail.gmail.com>
	<3B2994FA-91EE-452F-84AD-CFB87203D0C6@segment7.net>
	<71166b3b0906251520j6098b698q38fa62893f79a6dc@mail.gmail.com>
Message-ID: <563E2A45-D85B-42A0-9294-B1576033C979@segment7.net>


On Jun 25, 2009, at 15:20, Luis Lavena wrote:

> On Thu, Jun 25, 2009 at 6:40 PM, Eric Hodel<drbrain at segment7.net>  
> wrote:
>>
>> Ok, I fixed this on trunk and merged to the branch.
>>
>> You can try either updating from the branch or downloading a new  
>> tarball
>> from:
>>
>> http://segment7.net/temp/rubygems-1.3.4.tgz
>>
>
> http://pastie.org/524829
>
>> Ryan released minitest 1.4.2 which doesn't trap SIGINFO on systems  
>> that
>> don't support it.
>
> That worked, thank Ryan from me.
>
> Now, 1.9 results:
>
> http://pastie.org/524832
>
> Looks like ChangeLog is not being parsed properly by Hoe

Ok, I merged release_notes/* into History.txt and updated the Rakefile  
and setup command to use it.  `ruby setup.rb` now prints the latest  
entry from History.txt.

New gem uploaded:

http://segment7.net/temp/rubygems-1.3.4.tgz


From luislavena at gmail.com  Thu Jun 25 21:27:29 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Thu, 25 Jun 2009 22:27:29 -0300
Subject: [Rubygems-developers] 1.3.5 soon
In-Reply-To: <563E2A45-D85B-42A0-9294-B1576033C979@segment7.net>
References: <6D0B5E11-1149-4898-8FF6-C5727D7491BC@segment7.net> 
	<71166b3b0906241628t477ad6cdud030599a43e4003@mail.gmail.com> 
	<FA9FBE95-B973-47E9-A906-A3D0E4C4E946@segment7.net>
	<71166b3b0906241741o29c5d7d9sd1e49fbccad84d39@mail.gmail.com> 
	<3B2994FA-91EE-452F-84AD-CFB87203D0C6@segment7.net>
	<71166b3b0906251520j6098b698q38fa62893f79a6dc@mail.gmail.com> 
	<563E2A45-D85B-42A0-9294-B1576033C979@segment7.net>
Message-ID: <71166b3b0906251827q7e6d1b6fgaff546a4499bc118@mail.gmail.com>

On Thu, Jun 25, 2009 at 10:01 PM, Eric Hodel<drbrain at segment7.net> wrote:
>
> On Jun 25, 2009, at 15:20, Luis Lavena wrote:
>>
>> Now, 1.9 results:
>>
>> http://pastie.org/524832
>>
>> Looks like ChangeLog is not being parsed properly by Hoe
>
> Ok, I merged release_notes/* into History.txt and updated the Rakefile and
> setup command to use it. ?`ruby setup.rb` now prints the latest entry from
> History.txt.
>
> New gem uploaded:
>
> http://segment7.net/temp/rubygems-1.3.4.tgz
>

Hmn, exact same result. Are those changes in the repository at 1_3
branch? If so, I can svn up and check from there instead of the
package ones.

-- 
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  Fri Jun 26 18:09:19 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Fri, 26 Jun 2009 15:09:19 -0700
Subject: [Rubygems-developers] 1.3.5 soon
In-Reply-To: <71166b3b0906251827q7e6d1b6fgaff546a4499bc118@mail.gmail.com>
References: <6D0B5E11-1149-4898-8FF6-C5727D7491BC@segment7.net>
	<71166b3b0906241628t477ad6cdud030599a43e4003@mail.gmail.com>
	<FA9FBE95-B973-47E9-A906-A3D0E4C4E946@segment7.net>
	<71166b3b0906241741o29c5d7d9sd1e49fbccad84d39@mail.gmail.com>
	<3B2994FA-91EE-452F-84AD-CFB87203D0C6@segment7.net>
	<71166b3b0906251520j6098b698q38fa62893f79a6dc@mail.gmail.com>
	<563E2A45-D85B-42A0-9294-B1576033C979@segment7.net>
	<71166b3b0906251827q7e6d1b6fgaff546a4499bc118@mail.gmail.com>
Message-ID: <A48E17B7-57F3-4C2B-9B57-38F3F1136CE1@segment7.net>

On Jun 25, 2009, at 18:27, Luis Lavena wrote:
> On Thu, Jun 25, 2009 at 10:01 PM, Eric Hodel<drbrain at segment7.net>  
> wrote:
>> On Jun 25, 2009, at 15:20, Luis Lavena wrote:
>>>
>>> Now, 1.9 results:
>>>
>>> http://pastie.org/524832
>>>
>>> Looks like ChangeLog is not being parsed properly by Hoe
>>
>> Ok, I merged release_notes/* into History.txt and updated the  
>> Rakefile and
>> setup command to use it.  `ruby setup.rb` now prints the latest  
>> entry from
>> History.txt.
>>
>> New gem uploaded:
>>
>> http://segment7.net/temp/rubygems-1.3.4.tgz
>
> Hmn, exact same result. Are those changes in the repository at 1_3
> branch? If so, I can svn up and check from there instead of the
> package ones.

Maybe I forgot to clean before packaging, should be correct now.  1_3  
has the same changes.

From drbrain at segment7.net  Fri Jun 26 19:03:45 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Fri, 26 Jun 2009 16:03:45 -0700
Subject: [Rubygems-developers] 1.3.5 soon
In-Reply-To: <A48E17B7-57F3-4C2B-9B57-38F3F1136CE1@segment7.net>
References: <6D0B5E11-1149-4898-8FF6-C5727D7491BC@segment7.net>
	<71166b3b0906241628t477ad6cdud030599a43e4003@mail.gmail.com>
	<FA9FBE95-B973-47E9-A906-A3D0E4C4E946@segment7.net>
	<71166b3b0906241741o29c5d7d9sd1e49fbccad84d39@mail.gmail.com>
	<3B2994FA-91EE-452F-84AD-CFB87203D0C6@segment7.net>
	<71166b3b0906251520j6098b698q38fa62893f79a6dc@mail.gmail.com>
	<563E2A45-D85B-42A0-9294-B1576033C979@segment7.net>
	<71166b3b0906251827q7e6d1b6fgaff546a4499bc118@mail.gmail.com>
	<A48E17B7-57F3-4C2B-9B57-38F3F1136CE1@segment7.net>
Message-ID: <2E2AF047-BBF5-4BE2-B0E4-7BA217699875@segment7.net>

On Jun 26, 2009, at 15:09, Eric Hodel wrote:
> On Jun 25, 2009, at 18:27, Luis Lavena wrote:
>> On Thu, Jun 25, 2009 at 10:01 PM, Eric Hodel<drbrain at segment7.net>  
>> wrote:
>>> On Jun 25, 2009, at 15:20, Luis Lavena wrote:
>>>>
>>>> Now, 1.9 results:
>>>>
>>>> http://pastie.org/524832
>>>>
>>>> Looks like ChangeLog is not being parsed properly by Hoe
>>>
>>> Ok, I merged release_notes/* into History.txt and updated the  
>>> Rakefile and
>>> setup command to use it.  `ruby setup.rb` now prints the latest  
>>> entry from
>>> History.txt.
>>>
>>> New gem uploaded:
>>>
>>> http://segment7.net/temp/rubygems-1.3.4.tgz
>>
>> Hmn, exact same result. Are those changes in the repository at 1_3
>> branch? If so, I can svn up and check from there instead of the
>> package ones.
>
> Maybe I forgot to clean before packaging, should be correct now.   
> 1_3 has the same changes.

And once again a new package, this one will unpack into rubygems-1.3.4  
instead of rubygems-update-1.3.4.

From luislavena at gmail.com  Sat Jun 27 01:29:29 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Sat, 27 Jun 2009 02:29:29 -0300
Subject: [Rubygems-developers] 1.3.5 soon
In-Reply-To: <2E2AF047-BBF5-4BE2-B0E4-7BA217699875@segment7.net>
References: <6D0B5E11-1149-4898-8FF6-C5727D7491BC@segment7.net> 
	<71166b3b0906241628t477ad6cdud030599a43e4003@mail.gmail.com> 
	<FA9FBE95-B973-47E9-A906-A3D0E4C4E946@segment7.net>
	<71166b3b0906241741o29c5d7d9sd1e49fbccad84d39@mail.gmail.com> 
	<3B2994FA-91EE-452F-84AD-CFB87203D0C6@segment7.net>
	<71166b3b0906251520j6098b698q38fa62893f79a6dc@mail.gmail.com> 
	<563E2A45-D85B-42A0-9294-B1576033C979@segment7.net>
	<71166b3b0906251827q7e6d1b6fgaff546a4499bc118@mail.gmail.com> 
	<A48E17B7-57F3-4C2B-9B57-38F3F1136CE1@segment7.net>
	<2E2AF047-BBF5-4BE2-B0E4-7BA217699875@segment7.net>
Message-ID: <71166b3b0906262229l216ad0aby4b3fac3891f73368@mail.gmail.com>

On Fri, Jun 26, 2009 at 8:03 PM, Eric Hodel<drbrain at segment7.net> wrote:
>>
>> Maybe I forgot to clean before packaging, should be correct now. ?1_3 has
>> the same changes.
>

Test 1_3 branch, exact same results, so decided to turn trace on for rake:

http://pastie.org/526214

Could this be related to default encoding and Hoe process the 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 gthiesfeld at gmail.com  Mon Jun 29 10:30:13 2009
From: gthiesfeld at gmail.com (Gordon Thiesfeld)
Date: Mon, 29 Jun 2009 09:30:13 -0500
Subject: [Rubygems-developers] Bug in Gem.bin_path - gem bin scripts are
	broken if there are spaces in GEM_HOME env. variable (on Windows)
Message-ID: <e9ece6840906290730s31e7fb21oa18a43697b7ec805@mail.gmail.com>

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.

Summary:
gem bin scripts are broken if there are spaces in GEM_HOME env.
variable (on Windows)

Description:

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.

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


C:\scripts\repo\rubygems>gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.4
  - RUBY VERSION: 1.8.6 (2009-03-31 patchlevel 368) [i386-mingw32]
  - INSTALLATION DIRECTORY: C:/documents and settings/gthiesfeld/.gem/ruby/1.8
  - RUBY EXECUTABLE: c:/ruby/186-p368-mingw32/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/documents and settings/gthiesfeld/.gem/ruby/1.8/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mingw32
  - GEM PATHS:
     - C:/documents and settings/gthiesfeld/.gem/ruby/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/



Thanks,

Gordon Thiesfeld

From drbrain at segment7.net  Mon Jun 29 18:27:19 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Mon, 29 Jun 2009 15:27:19 -0700
Subject: [Rubygems-developers] 1.3.5 soon
In-Reply-To: <71166b3b0906262229l216ad0aby4b3fac3891f73368@mail.gmail.com>
References: <6D0B5E11-1149-4898-8FF6-C5727D7491BC@segment7.net>
	<71166b3b0906241628t477ad6cdud030599a43e4003@mail.gmail.com>
	<FA9FBE95-B973-47E9-A906-A3D0E4C4E946@segment7.net>
	<71166b3b0906241741o29c5d7d9sd1e49fbccad84d39@mail.gmail.com>
	<3B2994FA-91EE-452F-84AD-CFB87203D0C6@segment7.net>
	<71166b3b0906251520j6098b698q38fa62893f79a6dc@mail.gmail.com>
	<563E2A45-D85B-42A0-9294-B1576033C979@segment7.net>
	<71166b3b0906251827q7e6d1b6fgaff546a4499bc118@mail.gmail.com>
	<A48E17B7-57F3-4C2B-9B57-38F3F1136CE1@segment7.net>
	<2E2AF047-BBF5-4BE2-B0E4-7BA217699875@segment7.net>
	<71166b3b0906262229l216ad0aby4b3fac3891f73368@mail.gmail.com>
Message-ID: <3D94512A-8548-46F6-98AF-0F7AE7C29862@segment7.net>

On Jun 26, 2009, at 22:29, Luis Lavena wrote:
> On Fri, Jun 26, 2009 at 8:03 PM, Eric Hodel<drbrain at segment7.net>  
> wrote:
>>>
>>> Maybe I forgot to clean before packaging, should be correct now.   
>>> 1_3 has
>>> the same changes.
>>
>
> Test 1_3 branch, exact same results, so decided to turn trace on for  
> rake:
>
> http://pastie.org/526214
>
> Could this be related to default encoding and Hoe process the file?

History.txt had non-UTF-8 characters in it, I fixed them (file said  
ISO-8859).  Other than the mail by gthiesfeld at gmail.com, I don't think  
there are any other blockers.

From devnull+rubygems-ci at pivotallabs.com  Mon Jun 29 18:34:09 2009
From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com)
Date: Mon, 29 Jun 2009 22:34:09 +0000
Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2269 failed
Message-ID: <4a494161e1b28_6358..fdbdd5b84724@ci.pivotallabs.com.tmail>

The build failed.

CHANGES
-------
New revision 2269 detected
Revision 2269 committed by drbrain on 2009-06-29 22:24:49
Convert to UTF-8
  M /trunk/History.txt



TEST FAILURES AND ERRORS
-----------------------
Name: test_self_cache_refreshes(TestGemSourceInfoCache)
Type: Failure
Message: Expected /Bulk updating/ to match "".

./test/test_gem_source_info_cache.rb:56




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

From luislavena at gmail.com  Mon Jun 29 18:33:54 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Mon, 29 Jun 2009 19:33:54 -0300
Subject: [Rubygems-developers] 1.3.5 soon
In-Reply-To: <3D94512A-8548-46F6-98AF-0F7AE7C29862@segment7.net>
References: <6D0B5E11-1149-4898-8FF6-C5727D7491BC@segment7.net> 
	<71166b3b0906241741o29c5d7d9sd1e49fbccad84d39@mail.gmail.com> 
	<3B2994FA-91EE-452F-84AD-CFB87203D0C6@segment7.net>
	<71166b3b0906251520j6098b698q38fa62893f79a6dc@mail.gmail.com> 
	<563E2A45-D85B-42A0-9294-B1576033C979@segment7.net>
	<71166b3b0906251827q7e6d1b6fgaff546a4499bc118@mail.gmail.com> 
	<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>
Message-ID: <71166b3b0906291533t414f1141sde1492336f6e8060@mail.gmail.com>

On Mon, Jun 29, 2009 at 7:27 PM, Eric Hodel<drbrain at segment7.net> wrote:
> On Jun 26, 2009, at 22:29, Luis Lavena wrote:
>>
>> On Fri, Jun 26, 2009 at 8:03 PM, Eric Hodel<drbrain at segment7.net> wrote:
>>>>
>>>> Maybe I forgot to clean before packaging, should be correct now. ?1_3
>>>> has
>>>> the same changes.
>>>
>>
>> Test 1_3 branch, exact same results, so decided to turn trace on for rake:
>>
>> http://pastie.org/526214
>>
>> Could this be related to default encoding and Hoe process the file?
>
> History.txt had non-UTF-8 characters in it, I fixed them (file said
> ISO-8859). ?Other than the mail by gthiesfeld at gmail.com, I don't think there
> are any other blockers.

Thank you, I'm going to check this against 1.8.6-p368 and 1.9.1-129
and get back to you.

In relation to Gordon's email, could you add those as a report on
RubyForge and I'll take care?

Going to invest some hours tonight so you can prepare a new release.

Cheers,
-- 
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 Jun 29 19:14:42 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Mon, 29 Jun 2009 19:14:42 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-26299 ] undefined method
	`each' for #<String:0xcb6e3e4>
Message-ID: <20090629231442.81760185811D@rubyforge.org>

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

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Thomas Preymesser (thopre)
Assigned to: Nobody (None)
Summary: undefined method `each' for #<String:0xcb6e3e4>

Initial Comment:
i get the following message at the installation of each gem with Ruby 1.9

Updating ri class cache with 7980 classes...
ERROR:  While executing gem ... (NoMethodError)
    undefined method `each' for #<String:0xcb6e3e4>


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

>Comment By: Eric Hodel (drbrain)
Date: 2009-06-29 16:14

Message:
Hi, please follow the guidelines from the top of the "submit bug" page:

Be sure to include the output of `gem env` with your bug report, and if the bug is a result of one of the `gem` commands, run with `gem -- debug thecommand` and include the full output. This will greatly help us in fixing your bug.

Thanks.

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

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

From luislavena at gmail.com  Mon Jun 29 19:14:23 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Mon, 29 Jun 2009 20:14:23 -0300
Subject: [Rubygems-developers] 1.3.5 soon
In-Reply-To: <71166b3b0906291533t414f1141sde1492336f6e8060@mail.gmail.com>
References: <6D0B5E11-1149-4898-8FF6-C5727D7491BC@segment7.net> 
	<3B2994FA-91EE-452F-84AD-CFB87203D0C6@segment7.net>
	<71166b3b0906251520j6098b698q38fa62893f79a6dc@mail.gmail.com> 
	<563E2A45-D85B-42A0-9294-B1576033C979@segment7.net>
	<71166b3b0906251827q7e6d1b6fgaff546a4499bc118@mail.gmail.com> 
	<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>
Message-ID: <71166b3b0906291614n541e7f9avd70778cbd08ab528@mail.gmail.com>

On Mon, Jun 29, 2009 at 7:33 PM, Luis Lavena<luislavena at gmail.com> wrote:
> On Mon, Jun 29, 2009 at 7:27 PM, Eric Hodel<drbrain at segment7.net> wrote:
>> On Jun 26, 2009, at 22:29, Luis Lavena wrote:
>>>
>>> On Fri, Jun 26, 2009 at 8:03 PM, Eric Hodel<drbrain at segment7.net> wrote:
>>>>>
>>>>> Maybe I forgot to clean before packaging, should be correct now. ?1_3
>>>>> has
>>>>> the same changes.
>>>>
>>>
>>> Test 1_3 branch, exact same results, so decided to turn trace on for rake:
>>>
>>> http://pastie.org/526214
>>>
>>> Could this be related to default encoding and Hoe process the file?
>>
>> History.txt had non-UTF-8 characters in it, I fixed them (file said
>> ISO-8859). ?Other than the mail by gthiesfeld at gmail.com, I don't think there
>> are any other blockers.
>
> Thank you, I'm going to check this against 1.8.6-p368 and 1.9.1-129
> and get back to you.
>

Same old problem. I believe the root of the issue is at lib/hoe.rb:360:

version = File.read(file)[/VERSION = ([\"\'])([\d][\d\w\.]+)\1/, 2]

That line is reporting issues with ChangeLog, not History.txt

After adding some debug lines, found that.

-- 
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 Jun 29 19:15:59 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Mon, 29 Jun 2009 19:15:59 -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: <20090629231559.7956B185811D@rubyforge.org>

Bugs item #26458, was opened at 2009-06-29 16: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: Open
Resolution: None
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.


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

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

From drbrain at segment7.net  Mon Jun 29 19:16:11 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Mon, 29 Jun 2009 16:16: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: <e9ece6840906290730s31e7fb21oa18a43697b7ec805@mail.gmail.com>
References: <e9ece6840906290730s31e7fb21oa18a43697b7ec805@mail.gmail.com>
Message-ID: <5A6A9553-4E01-4592-BF82-4187D1A2AA00@segment7.net>

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.

From devnull+rubygems-ci at pivotallabs.com  Mon Jun 29 19:30:35 2009
From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com)
Date: Mon, 29 Jun 2009 23:30:35 +0000
Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2271 fixed
Message-ID: <4a494e9b6658f_6358..fdbdd5b848db@ci.pivotallabs.com.tmail>

The build has been fixed.

CHANGES
-------
New revision 2271 detected
Revision 2271 committed by drbrain on 2009-06-29 23:22:48
Remove all tests for legacy remote repositories
  M /trunk/test/test_gem_commands_fetch_command.rb
  M /trunk/test/test_gem_spec_fetcher.rb
  M /trunk/test/gemutilities.rb
  M /trunk/test/test_gem_commands_dependency_command.rb
  D /trunk/test/test_gem_source_info_cache.rb
  D /trunk/test/test_gem_source_info_cache_entry.rb
  M /trunk/test/test_gem_commands_sources_command.rb
  M /trunk/test/test_gem_commands_query_command.rb



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

From drbrain at segment7.net  Mon Jun 29 19:58:38 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Mon, 29 Jun 2009 16:58:38 -0700
Subject: [Rubygems-developers] 1.3.5 soon
In-Reply-To: <71166b3b0906291614n541e7f9avd70778cbd08ab528@mail.gmail.com>
References: <6D0B5E11-1149-4898-8FF6-C5727D7491BC@segment7.net>
	<3B2994FA-91EE-452F-84AD-CFB87203D0C6@segment7.net>
	<71166b3b0906251520j6098b698q38fa62893f79a6dc@mail.gmail.com>
	<563E2A45-D85B-42A0-9294-B1576033C979@segment7.net>
	<71166b3b0906251827q7e6d1b6fgaff546a4499bc118@mail.gmail.com>
	<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>
Message-ID: <BAED9630-B211-49FE-8342-B23110ABF6DF@segment7.net>

On Jun 29, 2009, at 16:14, Luis Lavena wrote:
> On Mon, Jun 29, 2009 at 7:33 PM, Luis Lavena<luislavena at gmail.com>  
> wrote:
>> On Mon, Jun 29, 2009 at 7:27 PM, Eric Hodel<drbrain at segment7.net>  
>> wrote:
>>> On Jun 26, 2009, at 22:29, Luis Lavena wrote:
>>>> On Fri, Jun 26, 2009 at 8:03 PM, Eric Hodel<drbrain at segment7.net>  
>>>> wrote:
>>>>>> Maybe I forgot to clean before packaging, should be correct  
>>>>>> now.  1_3
>>>>>> has
>>>>>> the same changes.
>>>>>
>>>>
>>>> Test 1_3 branch, exact same results, so decided to turn trace on  
>>>> for rake:
>>>>
>>>> http://pastie.org/526214
>>>>
>>>> Could this be related to default encoding and Hoe process the file?
>>>
>>> History.txt had non-UTF-8 characters in it, I fixed them (file said
>>> ISO-8859).  Other than the mail by gthiesfeld at gmail.com, I don't  
>>> think there
>>> are any other blockers.
>>
>> Thank you, I'm going to check this against 1.8.6-p368 and 1.9.1-129
>> and get back to you.
>>
>
> Same old problem. I believe the root of the issue is at lib/hoe.rb: 
> 360:
>
> version = File.read(file)[/VERSION = ([\"\'])([\d][\d\w\.]+)\1/, 2]
>
> That line is reporting issues with ChangeLog, not History.txt
>
> After adding some debug lines, found that.

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:

$ ~/.multiruby/install/1.9.1-p129/bin/rake debug_gem | head -5
(in /Users/drbrain/Work/svn/rubygems/trunk)
** History.txt is missing or in the wrong format for auto-intuiting.
    run `sow blah` and look at its text files
# -*- encoding: utf-8 -*-

Gem::Specification.new do |s|
   s.name = %q{rubygems-update}
$ rake debug_gem | head -5
(in /Users/drbrain/Work/svn/rubygems/trunk)
# -*- encoding: utf-8 -*-

Gem::Specification.new do |s|
   s.name = %q{rubygems-update}


From drbrain at segment7.net  Mon Jun 29 19:59:01 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Mon, 29 Jun 2009 16:59:01 -0700
Subject: [Rubygems-developers] 1.3.5 soon
In-Reply-To: <71166b3b0906291533t414f1141sde1492336f6e8060@mail.gmail.com>
References: <6D0B5E11-1149-4898-8FF6-C5727D7491BC@segment7.net>
	<71166b3b0906241741o29c5d7d9sd1e49fbccad84d39@mail.gmail.com>
	<3B2994FA-91EE-452F-84AD-CFB87203D0C6@segment7.net>
	<71166b3b0906251520j6098b698q38fa62893f79a6dc@mail.gmail.com>
	<563E2A45-D85B-42A0-9294-B1576033C979@segment7.net>
	<71166b3b0906251827q7e6d1b6fgaff546a4499bc118@mail.gmail.com>
	<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>
Message-ID: <C96F6152-195C-4643-9E6D-A895EFA7B77E@segment7.net>

On Jun 29, 2009, at 15:33, Luis Lavena wrote:

> In relation to Gordon's email, could you add those as a report on
> RubyForge and I'll take care?

Done!

From luislavena at gmail.com  Mon Jun 29 23:04:30 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Tue, 30 Jun 2009 00:04:30 -0300
Subject: [Rubygems-developers] 1.3.5 soon
In-Reply-To: <BAED9630-B211-49FE-8342-B23110ABF6DF@segment7.net>
References: <6D0B5E11-1149-4898-8FF6-C5727D7491BC@segment7.net> 
	<563E2A45-D85B-42A0-9294-B1576033C979@segment7.net>
	<71166b3b0906251827q7e6d1b6fgaff546a4499bc118@mail.gmail.com> 
	<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>
Message-ID: <71166b3b0906292004i14f4e2c7p5a95708e09b73cda@mail.gmail.com>

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.

Changing the Windows codepage results in exactly the same issue.

Not enough space on STDOUT is a issue quite common with outputting
unicode on a device not supporting it (or viceversa).

Now, that happens on IRB, and I think that what it read is not
correctly interpreted by encodings on Windows when executed with
Regexp (line 360 of hoe.rb)

Should ChangeLog be bundled inside the gem? And why Hoe try to parse
every file listed in the Gem spec?

-- 
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 Jun 30 19:03:53 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Tue, 30 Jun 2009 16:03:53 -0700
Subject: [Rubygems-developers] 1.3.5 soon
In-Reply-To: <71166b3b0906292004i14f4e2c7p5a95708e09b73cda@mail.gmail.com>
References: <6D0B5E11-1149-4898-8FF6-C5727D7491BC@segment7.net>
	<563E2A45-D85B-42A0-9294-B1576033C979@segment7.net>
	<71166b3b0906251827q7e6d1b6fgaff546a4499bc118@mail.gmail.com>
	<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>
Message-ID: <10FC8EC5-899A-4C37-BE2A-C830257BDC1D@segment7.net>

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?