From ryand-ruby at zenspider.com  Sun Mar  1 23:37:19 2009
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Sun, 1 Mar 2009 20:37:19 -0800
Subject: [Rubygems-developers] [Fwd: Re: Question about gems,
	platform and win32-api]
In-Reply-To: <49A6EA20.4010109@gmail.com>
References: <49A6EA20.4010109@gmail.com>
Message-ID: <905CC816-19FA-4919-B41E-FED032A549F4@zenspider.com>


On Feb 26, 2009, at 11:14 , Daniel Berger wrote:

> Forwarding from Charley. Looks like there's some sort of gems/hoe  
> interaction bug happening.

I'd try to help, but you windoze bastards top-post everything to the  
point of unreadability.

--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?




From djberg96 at gmail.com  Mon Mar  2 00:05:04 2009
From: djberg96 at gmail.com (Daniel Berger)
Date: Sun, 01 Mar 2009 22:05:04 -0700
Subject: [Rubygems-developers] [Fwd: Re: Question about gems,
 platform and win32-api]
In-Reply-To: <905CC816-19FA-4919-B41E-FED032A549F4@zenspider.com>
References: <49A6EA20.4010109@gmail.com>
	<905CC816-19FA-4919-B41E-FED032A549F4@zenspider.com>
Message-ID: <49AB6900.9010404@gmail.com>

Ryan Davis wrote:
> 
> On Feb 26, 2009, at 11:14 , Daniel Berger wrote:
> 
>> Forwarding from Charley. Looks like there's some sort of gems/hoe 
>> interaction bug happening.
> 
> I'd try to help, but you windoze bastards top-post everything to the 
> point of unreadability.

Synopsis: I had two binary gems for win32-api. One for mswin32_60 and 
one for mswin32_80. The '60' gem is the one compatible with the 
one-click installer. However, if another gem generated by Hoe was added 
as a dependency first, it would grab the wrong windows binary gem.

In Charley's example, he had this:

Gem::Specification.new do |s|
    ...
    s.add_dependency('user_choices')
    s.add_dependency('win32-process')
end

But, if you reversed the dependencies, it would work.

I haven't verified this myself, I'm just passing along what I was told.

Regards,

Dan


From luislavena at gmail.com  Mon Mar  2 09:01:21 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Mon, 2 Mar 2009 09:01:21 -0500
Subject: [Rubygems-developers] [Fwd: Re: Question about gems,
	platform and 	win32-api]
In-Reply-To: <905CC816-19FA-4919-B41E-FED032A549F4@zenspider.com>
References: <49A6EA20.4010109@gmail.com>
	<905CC816-19FA-4919-B41E-FED032A549F4@zenspider.com>
Message-ID: <71166b3b0903020601q1f63566fn2f85ae74d922d1b@mail.gmail.com>

On Sun, Mar 1, 2009 at 11:37 PM, Ryan Davis <ryand-ruby at zenspider.com> wrote:
>
> On Feb 26, 2009, at 11:14 , Daniel Berger wrote:
>
>> Forwarding from Charley. Looks like there's some sort of gems/hoe
>> interaction bug happening.
>
> I'd try to help, but you windoze bastards top-post everything to the point
> of unreadability.
>

C'mon, I know some Solaris and some Slackware dudes that top post too,
and I'm not messing with their mothers ;-)

-- 
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 jftucker at gmail.com  Mon Mar  2 08:56:11 2009
From: jftucker at gmail.com (James Tucker)
Date: Mon, 2 Mar 2009 13:56:11 +0000
Subject: [Rubygems-developers] Gem.bin_path for gem binaries
Message-ID: <218BD2D2-9006-4891-8100-D11CD04B55FD@gmail.com>

Good day folks,

I've placed a patch in the tracker:

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

It provides a simple interface to look up a full and accurate path to  
a gem binary.

Along with the problems described on the ticket, from what I hear this  
also solved addressing issues for a lot of general purpose rake tasks  
for JRuby users who don't keep jruby high in their path.

Any input welcome,

Kind regards,

James Tucker

From rick.denatale at gmail.com  Tue Mar  3 10:17:15 2009
From: rick.denatale at gmail.com (Rick DeNatale)
Date: Tue, 3 Mar 2009 10:17:15 -0500
Subject: [Rubygems-developers] [Fwd: Re: Question about gems,
	platform and 	win32-api]
In-Reply-To: <905CC816-19FA-4919-B41E-FED032A549F4@zenspider.com>
References: <49A6EA20.4010109@gmail.com>
	<905CC816-19FA-4919-B41E-FED032A549F4@zenspider.com>
Message-ID: <deb2337a0903030717w86ff2a8m4bb0ad98cd9e5d47@mail.gmail.com>

On Sun, Mar 1, 2009 at 11:37 PM, Ryan Davis <ryand-ruby at zenspider.com>wrote:

>
> On Feb 26, 2009, at 11:14 , Daniel Berger wrote:
>
>  Forwarding from Charley. Looks like there's some sort of gems/hoe
>> interaction bug happening.
>>
>
> I'd try to help, but you windoze bastards top-post everything to the point
> of unreadability.
>

And here I thought that it was the Forth programmers and users of old HP
calculators! <G>
-- 
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rubygems-developers/attachments/20090303/70515c6c/attachment.html>

From jtrupiano at gmail.com  Fri Mar  6 01:17:18 2009
From: jtrupiano at gmail.com (John Trupiano)
Date: Fri, 6 Mar 2009 01:17:18 -0500
Subject: [Rubygems-developers] gem() command caches gem list upon first
	invocation
Message-ID: <2847174d0903052217x545b489dka4a39ddd93ee3183@mail.gmail.com>

Hey guys, see my message below regarding a caching issue with the gem()
function.  At this point, I just want to report the information I've
gathered regarding the specifics of the bug.  I am willing to troubleshoot
this further, but to be honest, I'm not sure how to go about modifying the
rubygems library itself.  Are there instructions for how to maintain your
own fork/branch of the library so that I can continue to troubleshoot the
issue?

-John\

---------- Forwarded message ----------
From: John Trupiano <jtrupiano at gmail.com>
Date: Thu, Mar 5, 2009 at 8:06 PM
Subject: Re: GemInstaller --- #install then #autogem
To: Chad Woolley <thewoolleyman at gmail.com>


Hey Chad, it looks to me like it's a problem in the rubygems API.  The
Gem::SourceIndex class properly picks up on the newly installed gem, but the
call to gem() does not.  But, there's a wrinkle.  This only happens if a
call to gem for that gem previously failed.

*Scenario 1: Install gem before trying to activate it, then activate it with
success
*john-mbp:trunk john$ irb
>> Gem::SourceIndex.from_installed_gems.search("jtrupiano-sanitize_email")
:0:Warning: Gem::SourceIndex#search support for String patterns is
deprecated
=> []
>> `sudo gem install jtrupiano-sanitize_email`
=> "Successfully installed jtrupiano-sanitize_email-0.1.0\n1 gem
installed\nInstalling ri documentation for
jtrupiano-sanitize_email-0.1.0...\nInstalling RDoc documentation for
jtrupiano-sanitize_email-0.1.0...\n"
>> Gem::SourceIndex.from_installed_gems.search("jtrupiano-sanitize_email")
:0:Warning: Gem::SourceIndex#search support for String patterns is
deprecated
=> [#<Gem::Specification:0x112374c ........>]
>> gem 'jtrupiano-sanitize_email', '= 0.1.0'
=> true

*Scenario 2: Try to activate the gem before it's installed, then install it,
then try to activate again, and fail.
*john-mbp:trunk john$ sudo gem uninstall jtrupiano-sanitize_email
Successfully uninstalled jtrupiano-sanitize_email-0.1.0
john-mbp:trunk john$ irb
>> Gem::SourceIndex.from_installed_gems.search("jtrupiano-sanitize_email")
:0:Warning: Gem::SourceIndex#search support for String patterns is
deprecated
=> []
>> gem 'jtrupiano-sanitize_email', '= 0.1.0'
Gem::LoadError: Could not find RubyGem jtrupiano-sanitize_email (= 0.1.0)

    from /Library/Ruby/Site/1.8/rubygems.rb:636:in `report_activate_error'
    from /Library/Ruby/Site/1.8/rubygems.rb:141:in `activate'
    from /Library/Ruby/Site/1.8/rubygems.rb:49:in `gem'
    from (irb):2
>> `sudo gem install jtrupiano-sanitize_email`
=> "Successfully installed jtrupiano-sanitize_email-0.1.0\n1 gem
installed\nInstalling ri documentation for
jtrupiano-sanitize_email-0.1.0...\nInstalling RDoc documentation for
jtrupiano-sanitize_email-0.1.0...\n"
>> Gem::SourceIndex.from_installed_gems.search("jtrupiano-sanitize_email")
:0:Warning: Gem::SourceIndex#search support for String patterns is
deprecated
=> [#<Gem::Specification:0x183d62c ....>]
>> gem 'jtrupiano-sanitize_email', '= 0.1.0'
Gem::LoadError: Could not find RubyGem jtrupiano-sanitize_email (= 0.1.0)

    from /Library/Ruby/Site/1.8/rubygems.rb:636:in `report_activate_error'
    from /Library/Ruby/Site/1.8/rubygems.rb:141:in `activate'
    from /Library/Ruby/Site/1.8/rubygems.rb:49:in `gem'
    from (irb):5



So the caching issue appears to be further up the stack, specifically in the
rubygems library itself.  I'm done looking into this for the evening, but
wanted to pass along my findings in the interim.  I'm going to continue
working on this over the weekend.

-John


On Tue, Mar 3, 2009 at 11:08 AM, Chad Woolley <thewoolleyman at gmail.com>wrote:

> That would be great.  I've only ever looked at this briefly.
> - Show quoted text -
> - Show quoted text -
>
> On Tue, Mar 3, 2009 at 7:07 AM, John Trupiano <jtrupiano at gmail.com> wrote:
> > Hey Chad, thanks for the response.  I was poking a bit around the
> > geminstaller code before I reached out to you.  I do think that I can
> give
> > you a hand on this one.  Schedule's a little tight today/tomorrow, but I
> > have gobs of time available this weekend.  I'll follow up.
> >
> > -John
> >
> > On Mon, Mar 2, 2009 at 9:44 PM, Chad Woolley <thewoolleyman at gmail.com>
> > wrote:
> >>
> >> Yep, that has been a bug forever:
> >>
> >>
> >>
> http://thewoolleyweb.lighthouseapp.com/projects/11580/tickets/3-autogem-fails-when-run-for-newly-installed-gem
> >>
> >> I think it is a problem with rubygems caching, but I've never looked
> >> into it.  It bites us all the time.  You're welcome to take a look :)
> >> I'm trying to make a priority to fix all these and get GemInstaller to
> >> 1.0 release - especially since more and more people become convinced
> >> config.gems is broken.
> >>
> >> -- Chad
> >> - Show quoted text -
> >> On Mon, Mar 2, 2009 at 3:11 PM, John Trupiano <jtrupiano at gmail.com>
> wrote:
> >> > Hey Chad,
> >> >
> >> > It appears that I cannot run an install immediately followed by an
> >> > autogem:
> >> >
> >> > john-mbp:trunk john$ irb
> >> >>> gem 'geminstaller', '=0.5.1'
> >> > => true
> >> >>> require 'geminstaller'
> >> > => true
> >> >>> GemInstaller.install('--sudo --config=config/geminstaller.yml')
> >> > Invoking gem install for jtrupiano-sanitize_email, version 0.1.0.
> >> > => 0
> >> >>> require 'sanitize_email'
> >> > LoadError: no such file to load -- sanitize_email
> >> >     from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in
> >> > `gem_original_require'
> >> >     from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in
> >> > `require'
> >> >     from (irb):4
> >> >>> GemInstaller.autogem('--config=config/geminstaller.yml')
> >> > Error: GemInstaller attempted to load gem 'jtrupiano-sanitize_email',
> >> > version '= 0.1.0', but that version is not installed.  Use
> GemInstaller
> >> > to
> >> > install the gem.  Original Gem::LoadError was: 'Could not find RubyGem
> >> > jtrupiano-sanitize_email (= 0.1.0)'
> >> > => 1
> >> >
> >> > What you'll see is that I can install the gem just fine, but I cannot
> >> > subsequently activate/load it.  If I exit and reload irb, it will
> >> > activate
> >> > the newly-installed gem just fine.
> >> >
> >> > I'm trying to set it up so that the gems auto-install in my automated
> >> > and
> >> > development environments.  What technique do you use to accomplish
> this?
> >> > This seems to be following the same convention you used in the sample
> >> > (geminstaller_rails_preinitializer.rb).  Do you notice anything that
> I'm
> >> > doing incorrectly here?
> >> >
> >> > Thanks, and no worries if you're unable to help.
> >> >
> >> > -John
> >> >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rubygems-developers/attachments/20090306/847da49f/attachment.html>

From thewoolleyman at gmail.com  Fri Mar  6 03:24:59 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Fri, 6 Mar 2009 01:24:59 -0700
Subject: [Rubygems-developers] gem() command caches gem list upon first
	invocation
In-Reply-To: <2847174d0903052217x545b489dka4a39ddd93ee3183@mail.gmail.com>
References: <2847174d0903052217x545b489dka4a39ddd93ee3183@mail.gmail.com>
Message-ID: <e3af97510903060024h16bffd12s742643b86b086d8e@mail.gmail.com>

On Thu, Mar 5, 2009 at 11:17 PM, John Trupiano <jtrupiano at gmail.com> wrote:
> I am willing to troubleshoot
> this further, but to be honest, I'm not sure how to go about modifying the
> rubygems library itself.? Are there instructions for how to maintain your
> own fork/branch of the library so that I can continue to troubleshoot the
> issue?

RubyGems is on SVN.  Just check out a read-only copy, make changes,
and submit a bug + patch:

svn checkout http://rubygems.rubyforge.org/svn/

http://rubyforge.org/tracker/?atid=575&group_id=126&func=browse

When you finish, post to this thread (or go ahead and create the bug
and assign to me), then I can test and apply your patch to trunk.

Thanks for your help.

-- Chad

From drbrain at segment7.net  Sat Mar  7 14:10:01 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Sat, 7 Mar 2009 11:10:01 -0800
Subject: [Rubygems-developers] conflict when rubygems generated wrapper
	tries to load autotest executable on ruby 1.9
In-Reply-To: <7FDBEE9C-5A89-4B5D-BDD7-97DAB008193C@gmail.com>
References: <268f428a0902201250u6f8e9495ja51ea0bfd08a14b1@mail.gmail.com>
	<268f428a0902250451j8d1755bv7457e29e3c080f84@mail.gmail.com>
	<7FDBEE9C-5A89-4B5D-BDD7-97DAB008193C@gmail.com>
Message-ID: <3C6F193D-47A6-4E0D-B04C-89B47214B7BF@segment7.net>

On Feb 26, 2009, at 03:41, James Tucker wrote:
>> That would be enough to get autotest working on ruby 1.9.
>> Any downsides?
>
> See Gem.bin_path patch here: http://rubyforge.org/tracker/index.php?func=detail&aid=24114&group_id=126&atid=577

I've applied this patch and made the Gem::Installer modification to  
use it.

From lasitha.ranatunga at gmail.com  Sat Mar  7 16:16:46 2009
From: lasitha.ranatunga at gmail.com (lasitha)
Date: Sun, 8 Mar 2009 02:46:46 +0530
Subject: [Rubygems-developers] conflict when rubygems generated wrapper
	tries to load autotest executable on ruby 1.9
In-Reply-To: <3C6F193D-47A6-4E0D-B04C-89B47214B7BF@segment7.net>
References: <268f428a0902201250u6f8e9495ja51ea0bfd08a14b1@mail.gmail.com>
	<268f428a0902250451j8d1755bv7457e29e3c080f84@mail.gmail.com>
	<7FDBEE9C-5A89-4B5D-BDD7-97DAB008193C@gmail.com>
	<3C6F193D-47A6-4E0D-B04C-89B47214B7BF@segment7.net>
Message-ID: <268f428a0903071316j632418f6n749ea9c1cd89214e@mail.gmail.com>

On Sun, Mar 8, 2009 at 12:40 AM, Eric Hodel <drbrain at segment7.net> wrote:
> On Feb 26, 2009, at 03:41, James Tucker wrote:
>>>
>>> That would be enough to get autotest working on ruby 1.9.
>>> Any downsides?
>>
>> See Gem.bin_path patch here:
>> http://rubyforge.org/tracker/index.php?func=detail&aid=24114&group_id=126&atid=577
>
> I've applied this patch and made the Gem::Installer modification to use it.

Tested with latest source by installing ZenTest-4.0.0 on ruby 1.9.1-p0
and works fine.
Thanks!
lasitha.

From jftucker at gmail.com  Sun Mar  8 12:27:10 2009
From: jftucker at gmail.com (James Tucker)
Date: Sun, 8 Mar 2009 16:27:10 +0000
Subject: [Rubygems-developers] conflict when rubygems generated wrapper
	tries to load autotest executable on ruby 1.9
In-Reply-To: <3C6F193D-47A6-4E0D-B04C-89B47214B7BF@segment7.net>
References: <268f428a0902201250u6f8e9495ja51ea0bfd08a14b1@mail.gmail.com>
	<268f428a0902250451j8d1755bv7457e29e3c080f84@mail.gmail.com>
	<7FDBEE9C-5A89-4B5D-BDD7-97DAB008193C@gmail.com>
	<3C6F193D-47A6-4E0D-B04C-89B47214B7BF@segment7.net>
Message-ID: <744D8A82-F548-4430-9614-B335D69E2545@gmail.com>


On 7 Mar 2009, at 19:10, Eric Hodel wrote:

> On Feb 26, 2009, at 03:41, James Tucker wrote:
>>> That would be enough to get autotest working on ruby 1.9.
>>> Any downsides?
>>
>> See Gem.bin_path patch here: http://rubyforge.org/tracker/index.php?func=detail&aid=24114&group_id=126&atid=577
>
> I've applied this patch and made the Gem::Installer modification to  
> use it.

Thank you, as always sir! :-)


From drbrain at segment7.net  Mon Mar  9 18:01:06 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Mon, 9 Mar 2009 15:01:06 -0700
Subject: [Rubygems-developers] RubyGems setup.rb --destdir patch
Message-ID: <1DBC9C7C-7C98-4DF6-9A4C-317B8A2C1ECA@segment7.net>

Can someone tell me if this patch for --destdir behavior is correct?

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

I don't use --destdir, so I don't know the desired behavior.

Thanks!

From rbrown at exherbo.org  Mon Mar  9 18:13:52 2009
From: rbrown at exherbo.org (Richard Brown)
Date: Mon, 9 Mar 2009 22:13:52 +0000
Subject: [Rubygems-developers] RubyGems setup.rb --destdir patch
In-Reply-To: <1DBC9C7C-7C98-4DF6-9A4C-317B8A2C1ECA@segment7.net>
References: <1DBC9C7C-7C98-4DF6-9A4C-317B8A2C1ECA@segment7.net>
Message-ID: <df1735a20903091513j5edadcabr353471ea0d4f45ce@mail.gmail.com>

On Mon, Mar 9, 2009 at 22:01, Eric Hodel <drbrain at segment7.net> wrote:
>
> Can someone tell me if this patch for --destdir behavior is correct?
>
> http://rubyforge.org/tracker/index.php?func=detail&aid=23964&group_id=126&atid=577
>
> I don't use --destdir, so I don't know the desired behavior.
>

Luis changed the behaviour of --destdir shortly after I wrote the
original patch to add it, we never agreed on restoring it, I think the
thread on-list fizzled out. The patch you linked to is similar to
http://tinyurl.com/aslo8n, which is the patch I use in exherbo to make
setup.rb do what I want. I haven't thought about how it affects
windows, so I haven't submitted it.

Regards,

--
Richard Brown

From luislavena at gmail.com  Mon Mar  9 18:31:35 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Mon, 9 Mar 2009 18:31:35 -0400
Subject: [Rubygems-developers] RubyGems setup.rb --destdir patch
In-Reply-To: <df1735a20903091513j5edadcabr353471ea0d4f45ce@mail.gmail.com>
References: <1DBC9C7C-7C98-4DF6-9A4C-317B8A2C1ECA@segment7.net>
	<df1735a20903091513j5edadcabr353471ea0d4f45ce@mail.gmail.com>
Message-ID: <71166b3b0903091531u74e72a39md94389ecae21b198@mail.gmail.com>

On Mon, Mar 9, 2009 at 6:13 PM, Richard Brown <rbrown at exherbo.org> wrote:
> On Mon, Mar 9, 2009 at 22:01, Eric Hodel <drbrain at segment7.net> wrote:
>>
>> Can someone tell me if this patch for --destdir behavior is correct?
>>
>> http://rubyforge.org/tracker/index.php?func=detail&aid=23964&group_id=126&atid=577
>>
>> I don't use --destdir, so I don't know the desired behavior.
>>
>
> Luis changed the behaviour of --destdir shortly after I wrote the
> original patch to add it, we never agreed on restoring it, I think the
> thread on-list fizzled out. The patch you linked to is similar to
> http://tinyurl.com/aslo8n, which is the patch I use in exherbo to make
> setup.rb do what I want. I haven't thought about how it affects
> windows, so I haven't submitted it.
>

I was going to chime in and accept the guilt on this.

I now realized that my destdir patches, which affected other users,
didn't help us (One-Click Installer developers) in the long run.

The thing is that prefix on Windows should be /, so next build of OCI
is going to use that and destdir properly.

I assume --destdir will use prefix on which ruby was built, and not
imposing /usr somehow, correct?

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

From luislavena at gmail.com  Mon Mar  9 18:33:12 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Mon, 9 Mar 2009 18:33:12 -0400
Subject: [Rubygems-developers] RubyGems setup.rb --destdir patch
In-Reply-To: <71166b3b0903091531u74e72a39md94389ecae21b198@mail.gmail.com>
References: <1DBC9C7C-7C98-4DF6-9A4C-317B8A2C1ECA@segment7.net>
	<df1735a20903091513j5edadcabr353471ea0d4f45ce@mail.gmail.com>
	<71166b3b0903091531u74e72a39md94389ecae21b198@mail.gmail.com>
Message-ID: <71166b3b0903091533g68ca29ees3e0df0e2771f2b9@mail.gmail.com>

On Mon, Mar 9, 2009 at 6:31 PM, Luis Lavena <luislavena at gmail.com> wrote:
> On Mon, Mar 9, 2009 at 6:13 PM, Richard Brown <rbrown at exherbo.org> wrote:
>> On Mon, Mar 9, 2009 at 22:01, Eric Hodel <drbrain at segment7.net> wrote:
>>>
>>> Can someone tell me if this patch for --destdir behavior is correct?
>>>
>>> http://rubyforge.org/tracker/index.php?func=detail&aid=23964&group_id=126&atid=577
>>>
>>> I don't use --destdir, so I don't know the desired behavior.
>>>
>>
>> Luis changed the behaviour of --destdir shortly after I wrote the
>> original patch to add it, we never agreed on restoring it, I think the
>> thread on-list fizzled out. The patch you linked to is similar to
>> http://tinyurl.com/aslo8n, which is the patch I use in exherbo to make
>> setup.rb do what I want. I haven't thought about how it affects
>> windows, so I haven't submitted it.
>>
>
> I was going to chime in and accept the guilt on this.
>
> I now realized that my destdir patches, which affected other users,
> didn't help us (One-Click Installer developers) in the long run.
>
> The thing is that prefix on Windows should be /, so next build of OCI
> is going to use that and destdir properly.
>
> I assume --destdir will use prefix on which ruby was built, and not
> imposing /usr somehow, correct?
>

Forgot to mention if those patches do not clash on Windows drive
letters, I'm cool with them

Previous implementation break those.

-- 
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 rbrown at exherbo.org  Mon Mar  9 18:38:58 2009
From: rbrown at exherbo.org (Richard Brown)
Date: Mon, 9 Mar 2009 22:38:58 +0000
Subject: [Rubygems-developers] RubyGems setup.rb --destdir patch
In-Reply-To: <71166b3b0903091531u74e72a39md94389ecae21b198@mail.gmail.com>
References: <1DBC9C7C-7C98-4DF6-9A4C-317B8A2C1ECA@segment7.net>
	<df1735a20903091513j5edadcabr353471ea0d4f45ce@mail.gmail.com>
	<71166b3b0903091531u74e72a39md94389ecae21b198@mail.gmail.com>
Message-ID: <df1735a20903091538wc2ff258r64dedc2d845486d8@mail.gmail.com>

On Mon, Mar 9, 2009 at 22:31, Luis Lavena <luislavena at gmail.com> wrote:
> On Mon, Mar 9, 2009 at 6:13 PM, Richard Brown <rbrown at exherbo.org> wrote:
>
> I was going to chime in and accept the guilt on this.

I didn't test it on Windows when I wrote it.

> I now realized that my destdir patches, which affected other users,
> didn't help us (One-Click Installer developers) in the long run.
>
> The thing is that prefix on Windows should be /, so next build of OCI
> is going to use that and destdir properly.
>
> I assume --destdir will use prefix on which ruby was built, and not
> imposing /usr somehow, correct?

The intended behaviour of --destdir should have nothing to do with
prefix. The destdir is prepended to the install path. This lets me say
that libdir should be /usr/lib64, bindir should be /usr/bin, and then
it's installed to $destdir not to "/". I know you had trouble with
paths on Windows so I hadn't pushed this patch. I think I took out the
RbConfig::TOPDIR part because that is calculated wrong by ruby to
always include lib, even if libdir is something else.

-- 
Richard Brown

From rbrown at exherbo.org  Thu Mar 12 03:51:02 2009
From: rbrown at exherbo.org (Richard Brown)
Date: Thu, 12 Mar 2009 07:51:02 +0000
Subject: [Rubygems-developers] RubyGems setup.rb --destdir patch
In-Reply-To: <71166b3b0903091533g68ca29ees3e0df0e2771f2b9@mail.gmail.com>
References: <1DBC9C7C-7C98-4DF6-9A4C-317B8A2C1ECA@segment7.net>
	<df1735a20903091513j5edadcabr353471ea0d4f45ce@mail.gmail.com>
	<71166b3b0903091531u74e72a39md94389ecae21b198@mail.gmail.com>
	<71166b3b0903091533g68ca29ees3e0df0e2771f2b9@mail.gmail.com>
Message-ID: <df1735a20903120051y7699f4f4h59d1f721bde37499@mail.gmail.com>

On Mon, Mar 9, 2009 at 22:33, Luis Lavena <luislavena at gmail.com> wrote:
>
> Forgot to mention if those patches do not clash on Windows drive
> letters, I'm cool with them
>

This gist contains two patches against trunk. The first patch fixes
some option names that I think got mangled in the refactoring of
setup.rb. The second patch makes destdir to what I think it should do,
and to make it work on windows, I've just called
.gsub(/^[a-zA-Z]:/,'') on paths being joined to destdir to remove a
drive letter if present. Is this too hacky?

http://gist.github.com/77950




-- 
Richard Brown

From djberg96 at gmail.com  Thu Mar 12 07:20:50 2009
From: djberg96 at gmail.com (Daniel Berger)
Date: Thu, 12 Mar 2009 05:20:50 -0600
Subject: [Rubygems-developers] 1.3.2?
Message-ID: <49B8F012.4000704@gmail.com>

Hi,

I think we have enough patches in place that we ought to consider a 
1.3.2 release soon.

Is there anything in limbo that needs fixing first besides --destdir?

Regards,

Dan

From luislavena at gmail.com  Thu Mar 12 09:20:37 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Thu, 12 Mar 2009 09:20:37 -0400
Subject: [Rubygems-developers] 1.3.2?
In-Reply-To: <49B8F012.4000704@gmail.com>
References: <49B8F012.4000704@gmail.com>
Message-ID: <71166b3b0903120620j3c13ca32qbbbc389c5263dc6b@mail.gmail.com>

On Thu, Mar 12, 2009 at 7:20 AM, Daniel Berger <djberg96 at gmail.com> wrote:
> Hi,
>
> I think we have enough patches in place that we ought to consider a 1.3.2
> release soon.
>
> Is there anything in limbo that needs fixing first besides --destdir?
>

Yeah, the new =~ comparison implemented is not passing test under MinGW:

http://rubyforge.org/pipermail/rubygems-developers/2009-January/004346.html

Didn't had time to check those.

I can provide MinGW binaries if you want.
-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

From luislavena at gmail.com  Thu Mar 12 09:26:02 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Thu, 12 Mar 2009 09:26:02 -0400
Subject: [Rubygems-developers] RubyGems setup.rb --destdir patch
In-Reply-To: <df1735a20903120051y7699f4f4h59d1f721bde37499@mail.gmail.com>
References: <1DBC9C7C-7C98-4DF6-9A4C-317B8A2C1ECA@segment7.net>
	<df1735a20903091513j5edadcabr353471ea0d4f45ce@mail.gmail.com>
	<71166b3b0903091531u74e72a39md94389ecae21b198@mail.gmail.com>
	<71166b3b0903091533g68ca29ees3e0df0e2771f2b9@mail.gmail.com>
	<df1735a20903120051y7699f4f4h59d1f721bde37499@mail.gmail.com>
Message-ID: <71166b3b0903120626s56338a5pce1bda32149b3426@mail.gmail.com>

On Thu, Mar 12, 2009 at 3:51 AM, Richard Brown <rbrown at exherbo.org> wrote:
> On Mon, Mar 9, 2009 at 22:33, Luis Lavena <luislavena at gmail.com> wrote:
>>
>> Forgot to mention if those patches do not clash on Windows drive
>> letters, I'm cool with them
>>
>
> This gist contains two patches against trunk. The first patch fixes
> some option names that I think got mangled in the refactoring of
> setup.rb. The second patch makes destdir to what I think it should do,
> and to make it work on windows, I've just called
> .gsub(/^[a-zA-Z]:/,'') on paths being joined to destdir to remove a
> drive letter if present. Is this too hacky?
>
> http://gist.github.com/77950
>

Hmn, that smells pretty aggressive patch, at least in relation to Windows paths.

I'll check this later and see what are the outcome on Windows.

-- 
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 Daniel.Berger at qwest.com  Thu Mar 12 11:23:36 2009
From: Daniel.Berger at qwest.com (Berger, Daniel)
Date: Thu, 12 Mar 2009 10:23:36 -0500
Subject: [Rubygems-developers] 1.3.2?
In-Reply-To: <71166b3b0903120620j3c13ca32qbbbc389c5263dc6b@mail.gmail.com>
References: <49B8F012.4000704@gmail.com>
	<71166b3b0903120620j3c13ca32qbbbc389c5263dc6b@mail.gmail.com>
Message-ID: <E1331D75B8E8DA46B15CDEA9BC46FA270D75EA3300@qtomaexmbm25.AD.QINTRA.COM>

> -----Original Message-----
> From: rubygems-developers-bounces at rubyforge.org 
> [mailto:rubygems-developers-bounces at rubyforge.org] On Behalf 
> Of Luis Lavena
> Sent: Thursday, March 12, 2009 7:21 AM
> To: rubygems-developers at rubyforge.org
> Subject: Re: [Rubygems-developers] 1.3.2?
> 
> On Thu, Mar 12, 2009 at 7:20 AM, Daniel Berger 
> <djberg96 at gmail.com> wrote:
> > Hi,
> >
> > I think we have enough patches in place that we ought to consider a 
> > 1.3.2 release soon.
> >
> > Is there anything in limbo that needs fixing first besides 
> --destdir?
> >
> 
> Yeah, the new =~ comparison implemented is not passing test 
> under MinGW:
> 
> http://rubyforge.org/pipermail/rubygems-developers/2009-Januar
> y/004346.html
> 
> Didn't had time to check those.
> 
> I can provide MinGW binaries if you want.

Ok, it also looks like we have some new test failures on Windows. This is Ruby 1.8.6-p114 on Windows XP Pro.

C:\Documents and Settings\djberge\workspace\rubygems>rake test
(in C:/Documents and Settings/djberge/workspace/rubygems)
Loaded suite C:/ruby/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake/rake_test_loader
Started
.............................................................................C:/ruby/lib/ruby/site_r
uby/1.8/openssl/x509.rb:24: warning: instance variable @config not initialized
C:/ruby/lib/ruby/site_ruby/1.8/openssl/x509.rb:24: warning: instance variable @config not initialize
d
C:/ruby/lib/ruby/site_ruby/1.8/openssl/x509.rb:24: warning: instance variable @config not initialize
d
...............................................C:/ruby/lib/ruby/1.8/rdoc/parsers/parse_c.rb:204: war
ning: method redefined; discarding old progress
.F..................................................................................E..F..F....F....
................................................S.............................F........S............
...S...................................S............................................................
....E...............................................................................................
....................................................................................................
....................................................................................................
.............................
Finished in 475.747000 seconds.

  1) Failure:
test_no_user_install(TestGemCommandsInstallCommand) [./test/test_gem_commands_install_command.rb:122
]:
<[Gem::FilePermissionError]> exception expected, not
Class: <Gem::SystemExitException>
Message: <"Exiting RubyGems with exit_code 0">
---Backtrace---
C:/Documents and Settings/djberge/workspace/rubygems/test/../lib/rubygems/commands/install_command.r
b:124:in `execute'
./test/test_gem_commands_install_command.rb:123:in `test_no_user_install'
C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:133:in `assert_raises'
./test/test_gem_commands_install_command.rb:122:in `test_no_user_install'
C:/Documents and Settings/djberge/workspace/rubygems/lib/rubygems/user_interaction.rb:42:in `use_ui'

C:/Documents and Settings/djberge/workspace/rubygems/lib/rubygems/user_interaction.rb:65:in `use_ui'

./test/test_gem_commands_install_command.rb:115:in `test_no_user_install'
C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:421:in `__send__'
C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:421:in `run'
C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:400:in `run_test_suites'
C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:394:in `each'
C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:394:in `run_test_suites'
C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:393:in `each'
C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:393:in `run_test_suites'
C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:373:in `run'
C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:317:in `autorun'
C:/ruby/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake/rake_test_loader.rb:5
---------------.
Expected [Gem::FilePermissionError] to include Gem::SystemExitException.

  2) Error:
test_equals_tilde_escape(TestGemDependency):
TypeError: can't convert Regexp into String
    C:/Documents and Settings/djberge/workspace/rubygems/lib/rubygems/dependency.rb:124:in `=~'
    C:/Documents and Settings/djberge/workspace/rubygems/lib/rubygems/dependency.rb:124:in `=~'
    C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:116:in `assert_match'
    ./test/test_gem_dependency.rb:128:in `test_equals_tilde_escape'
    C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:421:in `__send__'
    C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:421:in `run'
    C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:400:in `run_test_suites'
    C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:394:in `each'
    C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:394:in `run_test_suites'
    C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:393:in `each'
    C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:393:in `run_test_suites'
    C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:373:in `run'
    C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:317:in `autorun'
    C:/ruby/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake/rake_test_loader.rb:5

  3) Failure:
test_equals_tilde_object(TestGemDependency) [./test/test_gem_dependency.rb:139]:
match version exact.
Expected #<Object:0x2db8d58> to match Gem::Dependency.new("a", Gem::Requirement.new([">= 0"]), :runt
ime).

  4) Failure:
test_equals_tilde_spec(TestGemDependency) [./test/test_gem_dependency.rb:158]:
match version exact.
Expected Gem::Specification.new do |s|
  s.date = Time.utc(2009, 3, 12)
  s.name = "a"
  s.require_paths = ["lib"]
  s.rubygems_version = "1.3.1.2403"
  s.specification_version = 3
  s.summary = nil
  s.version = Gem::Version.new("0")
  end to match Gem::Dependency.new("a", Gem::Requirement.new([">= 0"]), :runtime).

  5) Failure:
test_equals_tilde(TestGemDependency) [./test/test_gem_dependency.rb:112]:
match version exact.
Expected Gem::Dependency.new("a", Gem::Requirement.new(["= 0"]), :runtime) to match Gem::Dependency.
new("a", Gem::Requirement.new([">= 0"]), :runtime).

  7) Failure:
test_generate_index(TestGemIndexer) [./test/test_gem_indexer.rb:241]:
Expected "<?xml version=\"1.0\"?>\n<rss version=\"2.0\">\n  <channel>\n    <title>ExampleForge gems<
/title>\n    <link>http://example.com</link>\n    <description>Recently released gems from http://ex
ample.com</description>\n    <generator>RubyGems v1.3.1.2403</generator>\n    <docs>http://cyber.law
.harvard.edu/rss/rss.html</docs>\n    <item>\n      <title>a-2</title>\n      <description>This is a
 test description</description>\n      <author>example at example.com (A User)</author>\n      <guid>a-
2</guid>\n      <enclosure url=\"http://gems.example.com/gems/a-2.gem\"\n                 length=\"3
072\" type=\"application/octet-stream\" />\n      <pubDate>Thu, 12 Mar 2009 06:00:00 -0000</pubDate>
\n      <link>http://example.com</link>\n    </item>\n    <item>\n      <title>a_evil-9</title>\n
   <description>This is a test description</description>\n      <author>example at example.com (A User)
</author>\n      <guid>a_evil-9</guid>\n      <enclosure url=\"http://gems.example.com/gems/a_evil-9
.gem\"\n                 length=\"3072\" type=\"application/octet-stream\" />\n      <pubDate>Thu, 1
2 Mar 2009 06:00:00 -0000</pubDate>\n      <link>http://example.com</link>\n    </item>\n    <item>\
n      <title>b-2</title>\n      <description>This is a test description</description>\n      <autho
r>example at example.com (A User)</author>\n      <guid>b-2</guid>\n      <enclosure url=\"http://gems.
example.com/gems/b-2.gem\"\n                 length=\"3072\" type=\"application/octet-stream\" />\n
     <pubDate>Thu, 12 Mar 2009 06:00:00 -0000</pubDate>\n      <link>http://example.com</link>\n
</item>\n    <item>\n      <title>c-1.2</title>\n      <description>This is a test description</desc
ription>\n      <author>example at example.com (A User)</author>\n      <guid>c-1.2</guid>\n      <encl
osure url=\"http://gems.example.com/gems/c-1.2.gem\"\n                 length=\"3072\" type=\"applic
ation/octet-stream\" />\n      <pubDate>Thu, 12 Mar 2009 06:00:00 -0000</pubDate>\n      <link>http:
//example.com</link>\n    </item>\n    <item>\n      <title>pl-1-x86-linux</title>\n      <descripti
on>This is a test description</description>\n      <author>example at example.com (A User)</author>\n
    <guid>pl-1-x86-linux</guid>\n      <enclosure url=\"http://gems.example.com/gems/pl-1-x86-linux.
gem\"\n                 length=\"3072\" type=\"application/octet-stream\" />\n      <pubDate>Thu, 12
 Mar 2009 06:00:00 -0000</pubDate>\n      <link>http://example.com</link>\n    </item>\n    <item>\n
      <title>a-1</title>\n      <description>This is a test description</description>\n      <author
>example at example.com (Example), example2 at example.com (Example2)</author>\n      <guid>a-1</guid>\n
    <enclosure url=\"http://gems.example.com/gems/a-1.gem\"\n                 length=\"3072\" type=\
"application/octet-stream\" />\n      <pubDate>Wed, 11 Mar 2009 06:00:00 -0000</pubDate>\n      <lin
k>http://a.example.com</link>\n    </item>\n  </channel>\n</rss>\n", not "<?xml version=\"1.0\"?>\n<
rss version=\"2.0\">\n  <channel>\n    <title>ExampleForge gems</title>\n    <link>http://example.co
m</link>\n    <description>Recently released gems from http://example.com</description>\n    <genera
tor>RubyGems v1.3.1.2403</generator>\n    <docs>http://cyber.law.harvard.edu/rss/rss.html</docs>\n
  <item>\n      <title>a-2</title>\n      <description>This is a test description</description>\n
   <author>example at example.com (A User)</author>\n      <guid>a-2</guid>\n      <enclosure url=\"htt
p://gems.example.com/gems/a-2.gem\"\n                 length=\"3072\" type=\"application/octet-strea
m\" />\n      <pubDate>Thu, 12 Mar 2009 06:00:00 -0000</pubDate>\n      <link>http://example.com</li
nk>\n    </item>\n    <item>\n      <title>a_evil-9</title>\n      <description>This is a test descr
iption</description>\n      <author>example at example.com (A User)</author>\n      <guid>a_evil-9</gui
d>\n      <enclosure url=\"http://gems.example.com/gems/a_evil-9.gem\"\n                 length=\"30
72\" type=\"application/octet-stream\" />\n      <pubDate>Thu, 12 Mar 2009 06:00:00 -0000</pubDate>\
n      <link>http://example.com</link>\n    </item>\n    <item>\n      <title>b-2</title>\n      <de
scription>This is a test description</description>\n      <author>example at example.com (A User)</auth
or>\n      <guid>b-2</guid>\n      <enclosure url=\"http://gems.example.com/gems/b-2.gem\"\n
         length=\"3072\" type=\"application/octet-stream\" />\n      <pubDate>Thu, 12 Mar 2009 06:00
:00 -0000</pubDate>\n      <link>http://example.com</link>\n    </item>\n    <item>\n      <title>c-
1.2</title>\n      <description>This is a test description</description>\n      <author>example at exam
ple.com (A User)</author>\n      <guid>c-1.2</guid>\n      <enclosure url=\"http://gems.example.com/
gems/c-1.2.gem\"\n                 length=\"3072\" type=\"application/octet-stream\" />\n      <pubD
ate>Thu, 12 Mar 2009 06:00:00 -0000</pubDate>\n      <link>http://example.com</link>\n    </item>\n
   <item>\n      <title>pl-1-x86-linux</title>\n      <description>This is a test description</descr
iption>\n      <author>example at example.com (A User)</author>\n      <guid>pl-1-x86-linux</guid>\n
   <enclosure url=\"http://gems.example.com/gems/pl-1-x86-linux.gem\"\n                 length=\"307
2\" type=\"application/octet-stream\" />\n      <pubDate>Thu, 12 Mar 2009 06:00:00 -0000</pubDate>\n
      <link>http://example.com</link>\n    </item>\n    <item>\n      <title>a-1</title>\n      <des
cription>This is a test description</description>\n      <author>example at example.com (Example), exam
ple2 at example.com (Example2)</author>\n      <guid>a-1</guid>\n      <enclosure url=\"http://gems.exa
mple.com/gems/a-1.gem\"\n                 length=\"3072\" type=\"application/octet-stream\" />\n
  <pubDate>Wed, 11 Mar 2009 00:00:00 -0600</pubDate>\n      <link>http://a.example.com</link>\n    <
/item>\n  </channel>\n</rss>\n".

 11) Error:
test_download_local_space(TestGemRemoteFetcher):
URI::InvalidURIError: bad URI(is not URI?): C:/DOCUME~1/djberge/LOCALS~1/Temp/test_rubygems_5196/spa
ce path/a-1.gem
    C:/ruby/lib/ruby/1.8/uri/common.rb:436:in `split'
    C:/ruby/lib/ruby/1.8/uri/common.rb:485:in `parse'
    C:/Documents and Settings/djberge/workspace/rubygems/test/../lib/rubygems/remote_fetcher.rb:90:i
n `download'
    ./test/test_gem_remote_fetcher.rb:252:in `test_download_local_space'
    C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:421:in `__send__'
    C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:421:in `run'
    C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:400:in `run_test_suites'
    C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:394:in `each'
    C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:394:in `run_test_suites'
    C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:393:in `each'
    C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:393:in `run_test_suites'
    C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:373:in `run'
    C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:317:in `autorun'
    C:/ruby/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake/rake_test_loader.rb:5

753 tests, 2560 assertions, 5 failures, 2 errors, 4 skips
rake aborted!
Command failed with status (1): [C:/ruby/bin/ruby -w -I"C:/Documents and Se...]

Regards,

Dan

From thewoolleyman at gmail.com  Fri Mar 13 15:54:10 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Fri, 13 Mar 2009 12:54:10 -0700
Subject: [Rubygems-developers] 1.3.2?
In-Reply-To: <49B8F012.4000704@gmail.com>
References: <49B8F012.4000704@gmail.com>
Message-ID: <e3af97510903131254j73f2364dq66ed20fd32e9d15d@mail.gmail.com>

On Thu, Mar 12, 2009 at 4:20 AM, Daniel Berger <djberg96 at gmail.com> wrote:
> Is there anything in limbo that needs fixing first besides --destdir?

What is the status of autoinstalling to ~/.gem if there is no root
permission?  Eric said this might be removed because it cannot be
supported under Ruby 1.9.

If we are going to keep it, we should fix "uninstall" to look here as
well - currently, if a gem gets autoinstalled in ~/.gem, there's no
way to uninstall it without manually specifying GEM_HOME, e.g.:
GEM_HOME=~/.gem/ruby/1.8 gem uninstall json

-- Chad

From drbrain at segment7.net  Fri Mar 13 20:03:47 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Fri, 13 Mar 2009 17:03:47 -0700
Subject: [Rubygems-developers] Need help with some mswin bugs
Message-ID: <B224C181-8547-4DF8-8A62-8B3130A4BFA0@segment7.net>

gem cache goes to wrong drive in windows if ruby is run from non C  
drive:
http://rubyforge.org/tracker/index.php?func=detail&aid=23429&group_id=126&atid=575

on windows platform, RubyGems generates a gem.bat that can't execute:
http://rubyforge.org/tracker/index.php?func=detail&aid=24039&group_id=126&atid=575

From luislavena at gmail.com  Sat Mar 14 12:23:23 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Sat, 14 Mar 2009 12:23:23 -0400
Subject: [Rubygems-developers] Need help with some mswin bugs
In-Reply-To: <B224C181-8547-4DF8-8A62-8B3130A4BFA0@segment7.net>
References: <B224C181-8547-4DF8-8A62-8B3130A4BFA0@segment7.net>
Message-ID: <71166b3b0903140923v185c8445sa7aea5f748382af0@mail.gmail.com>

On Fri, Mar 13, 2009 at 8:03 PM, Eric Hodel <drbrain at segment7.net> wrote:
> gem cache goes to wrong drive in windows if ruby is run from non C drive:
> http://rubyforge.org/tracker/index.php?func=detail&aid=23429&group_id=126&atid=575

I have Ruby and RubyGems installed in D drive, never had a problem with that.

Commented there and waiting for answers.

> on windows platform, RubyGems generates a gem.bat that can't execute:
> http://rubyforge.org/tracker/index.php?func=detail&aid=24039&group_id=126&atid=575

This is fixed now in trunk. The problem is when people install Ruby in
locations with spaces and Gem::ruby quoting it.
-- 
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  Sat Mar 14 21:33:37 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Sat, 14 Mar 2009 18:33:37 -0700
Subject: [Rubygems-developers] 1.3.2?
In-Reply-To: <49B8F012.4000704@gmail.com>
References: <49B8F012.4000704@gmail.com>
Message-ID: <B8C7DF17-D70B-4948-B015-B4C0436354A4@segment7.net>

On Mar 12, 2009, at 04:20, Daniel Berger wrote:
> I think we have enough patches in place that we ought to consider a  
> 1.3.2 release soon.

I think so too.

There's a few 1.9 issues in the bugs list, and a few patches that  
should be closed out in the patch tracker.

From drbrain at segment7.net  Sat Mar 14 21:34:15 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Sat, 14 Mar 2009 18:34:15 -0700
Subject: [Rubygems-developers] 1.3.2?
In-Reply-To: <E1331D75B8E8DA46B15CDEA9BC46FA270D75EA3300@qtomaexmbm25.AD.QINTRA.COM>
References: <49B8F012.4000704@gmail.com>
	<71166b3b0903120620j3c13ca32qbbbc389c5263dc6b@mail.gmail.com>
	<E1331D75B8E8DA46B15CDEA9BC46FA270D75EA3300@qtomaexmbm25.AD.QINTRA.COM>
Message-ID: <3D937CDF-3586-4732-B006-6BCD7B50BDBC@segment7.net>

On Mar 12, 2009, at 08:23, Berger, Daniel wrote:

>> -----Original Message-----
>> From: rubygems-developers-bounces at rubyforge.org
>> [mailto:rubygems-developers-bounces at rubyforge.org] On Behalf
>> Of Luis Lavena
>> Sent: Thursday, March 12, 2009 7:21 AM
>> To: rubygems-developers at rubyforge.org
>> Subject: Re: [Rubygems-developers] 1.3.2?
>>
>> On Thu, Mar 12, 2009 at 7:20 AM, Daniel Berger
>> <djberg96 at gmail.com> wrote:
>>> Hi,
>>>
>>> I think we have enough patches in place that we ought to consider a
>>> 1.3.2 release soon.
>>>
>>> Is there anything in limbo that needs fixing first besides
>> --destdir?
>>>
>>
>> Yeah, the new =~ comparison implemented is not passing test
>> under MinGW:
>>
>> http://rubyforge.org/pipermail/rubygems-developers/2009-Januar
>> y/004346.html
>>
>> Didn't had time to check those.
>>
>> I can provide MinGW binaries if you want.
>
> Ok, it also looks like we have some new test failures on Windows.  
> This is Ruby 1.8.6-p114 on Windows XP Pro.
>
> C:\Documents and Settings\djberge\workspace\rubygems>rake test

Can you run this piped through unit_diff -u?  It's in the ZenTest gem.

From luislavena at gmail.com  Sat Mar 14 21:52:38 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Sat, 14 Mar 2009 21:52:38 -0400
Subject: [Rubygems-developers] 1.3.2?
In-Reply-To: <3D937CDF-3586-4732-B006-6BCD7B50BDBC@segment7.net>
References: <49B8F012.4000704@gmail.com>
	<71166b3b0903120620j3c13ca32qbbbc389c5263dc6b@mail.gmail.com>
	<E1331D75B8E8DA46B15CDEA9BC46FA270D75EA3300@qtomaexmbm25.AD.QINTRA.COM>
	<3D937CDF-3586-4732-B006-6BCD7B50BDBC@segment7.net>
Message-ID: <71166b3b0903141852t6c1175acxea381bce73a5a8cf@mail.gmail.com>

On Sat, Mar 14, 2009 at 9:34 PM, Eric Hodel <drbrain at segment7.net> wrote:
> On Mar 12, 2009, at 08:23, Berger, Daniel wrote:
> [...]
>
>>>
>>> Yeah, the new =~ comparison implemented is not passing test
>>> under MinGW:
>>>
>>> http://rubyforge.org/pipermail/rubygems-developers/2009-Januar
>>> y/004346.html
>>>
>>> Didn't had time to check those.
>>>
>>> I can provide MinGW binaries if you want.
>>
>> Ok, it also looks like we have some new test failures on Windows. This is
>> Ruby 1.8.6-p114 on Windows XP Pro.
>>
>> C:\Documents and Settings\djberge\workspace\rubygems>rake test
>
> Can you run this piped through unit_diff -u? ?It's in the ZenTest gem.

revision 2085, after my last commit:

MinGW results:

http://pastie.org/416563

VC6 results:

http://pastie.org/416566

-- 
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 djberg96 at gmail.com  Sun Mar 15 00:18:50 2009
From: djberg96 at gmail.com (Daniel Berger)
Date: Sat, 14 Mar 2009 22:18:50 -0600
Subject: [Rubygems-developers] 1.3.2?
In-Reply-To: <E1331D75B8E8DA46B15CDEA9BC46FA270D75EA3300@qtomaexmbm25.AD.QINTRA.COM>
References: <49B8F012.4000704@gmail.com>	<71166b3b0903120620j3c13ca32qbbbc389c5263dc6b@mail.gmail.com>
	<E1331D75B8E8DA46B15CDEA9BC46FA270D75EA3300@qtomaexmbm25.AD.QINTRA.COM>
Message-ID: <49BC81AA.6070305@gmail.com>

Berger, Daniel wrote:

<snip>

>   2) Error:
> test_equals_tilde_escape(TestGemDependency):
> TypeError: can't convert Regexp into String
>     C:/Documents and Settings/djberge/workspace/rubygems/lib/rubygems/dependency.rb:124:in `=~'
>     C:/Documents and Settings/djberge/workspace/rubygems/lib/rubygems/dependency.rb:124:in `=~'
>     C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:116:in `assert_match'
>     ./test/test_gem_dependency.rb:128:in `test_equals_tilde_escape'
>     C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:421:in `__send__'
>     C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:421:in `run'
>     C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:400:in `run_test_suites'
>     C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:394:in `each'
>     C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:394:in `run_test_suites'
>     C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:393:in `each'
>     C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:393:in `run_test_suites'
>     C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:373:in `run'
>     C:/ruby/lib/ruby/gems/1.8/gems/minitest-1.3.0/lib/minitest/unit.rb:317:in `autorun'
>     C:/ruby/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake/rake_test_loader.rb:5

I traced this one down (and it's not Windows specific). It looks like 
it's trying to compare a Regexp to a Regexp with the =~ method, which is 
illegal. This is what that particular test to doing:

irb(main):001:0> /\Aa\Z/ =~ /a|b/
TypeError: can't convert Regexp into String
         from (irb):1

I'm not sure what the proper behavior is for Gem::Dependency because it 
is poorly documented. So, I don't know if the behavior is wrong or the 
test itself is bad.

Regards,

Dan

From thewoolleyman at gmail.com  Sun Mar 15 00:48:55 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Sat, 14 Mar 2009 21:48:55 -0700
Subject: [Rubygems-developers] 1.3.2?
In-Reply-To: <49B8F012.4000704@gmail.com>
References: <49B8F012.4000704@gmail.com>
Message-ID: <e3af97510903142148o57bf9d7bg8adaaff71eac7fb5@mail.gmail.com>

On Thu, Mar 12, 2009 at 4:20 AM, Daniel Berger <djberg96 at gmail.com> wrote:
> I think we have enough patches in place that we ought to consider a 1.3.2
> release soon.

FYI, my integration tests are all green:

http://ci.thewoolleyweb.com:3333/builds/geminstaller_trunk_using_rubygems_9-9-9

From drbrain at segment7.net  Mon Mar 16 14:47:59 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Mon, 16 Mar 2009 11:47:59 -0700
Subject: [Rubygems-developers] 1.3.2?
In-Reply-To: <49BC81AA.6070305@gmail.com>
References: <49B8F012.4000704@gmail.com>	<71166b3b0903120620j3c13ca32qbbbc389c5263dc6b@mail.gmail.com>
	<E1331D75B8E8DA46B15CDEA9BC46FA270D75EA3300@qtomaexmbm25.AD.QINTRA.COM>
	<49BC81AA.6070305@gmail.com>
Message-ID: <1612C58D-2E47-4F1E-B9DC-67390E51B77E@segment7.net>

On Mar 14, 2009, at 21:18, Daniel Berger wrote:
> I traced this one down (and it's not Windows specific). It looks  
> like it's trying to compare a Regexp to a Regexp with the =~ method,  
> which is illegal. This is what that particular test to doing:
>
> irb(main):001:0> /\Aa\Z/ =~ /a|b/
> TypeError: can't convert Regexp into String
>        from (irb):1
>
> I'm not sure what the proper behavior is for Gem::Dependency because  
> it is poorly documented. So, I don't know if the behavior is wrong  
> or the test itself is bad.

Newer minitest fixes some assert_match issues, so I've added a version  
check to the Rakefile.  Give it a whirl now.

From luislavena at gmail.com  Tue Mar 17 12:07:24 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Tue, 17 Mar 2009 12:07:24 -0400
Subject: [Rubygems-developers] 1.3.2?
In-Reply-To: <1612C58D-2E47-4F1E-B9DC-67390E51B77E@segment7.net>
References: <49B8F012.4000704@gmail.com>
	<71166b3b0903120620j3c13ca32qbbbc389c5263dc6b@mail.gmail.com>
	<E1331D75B8E8DA46B15CDEA9BC46FA270D75EA3300@qtomaexmbm25.AD.QINTRA.COM>
	<49BC81AA.6070305@gmail.com>
	<1612C58D-2E47-4F1E-B9DC-67390E51B77E@segment7.net>
Message-ID: <71166b3b0903170907r258d0e89rb7387cc84a3e0924@mail.gmail.com>

On Mon, Mar 16, 2009 at 2:47 PM, Eric Hodel <drbrain at segment7.net> wrote:
> On Mar 14, 2009, at 21:18, Daniel Berger wrote:
>>
>> I traced this one down (and it's not Windows specific). It looks like it's
>> trying to compare a Regexp to a Regexp with the =~ method, which is illegal.
>> This is what that particular test to doing:
>>
>> irb(main):001:0> /\Aa\Z/ =~ /a|b/
>> TypeError: can't convert Regexp into String
>> ? ? ? from (irb):1
>>
>> I'm not sure what the proper behavior is for Gem::Dependency because it is
>> poorly documented. So, I don't know if the behavior is wrong or the test
>> itself is bad.
>
> Newer minitest fixes some assert_match issues, so I've added a version check
> to the Rakefile. ?Give it a whirl now.

I had installed 1.3.1 at the time of my test, however, the following
are the results:

MinGW:
http://pastie.org/418794

VC6:
http://pastie.org/418805

Looks much better, but it seems that test_download_local_space still fails.

The idea was test path with spaces, like Windows paths? because Ruby
URI is not recognizing it as a file source URI.

Or I'm missing something?
-- 
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 Mar 17 21:53:49 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Tue, 17 Mar 2009 18:53:49 -0700
Subject: [Rubygems-developers] 1.3.2?
In-Reply-To: <71166b3b0903170907r258d0e89rb7387cc84a3e0924@mail.gmail.com>
References: <49B8F012.4000704@gmail.com>
	<71166b3b0903120620j3c13ca32qbbbc389c5263dc6b@mail.gmail.com>
	<E1331D75B8E8DA46B15CDEA9BC46FA270D75EA3300@qtomaexmbm25.AD.QINTRA.COM>
	<49BC81AA.6070305@gmail.com>
	<1612C58D-2E47-4F1E-B9DC-67390E51B77E@segment7.net>
	<71166b3b0903170907r258d0e89rb7387cc84a3e0924@mail.gmail.com>
Message-ID: <226B9DD5-BDE7-460A-A7F5-7E3C6DF95079@segment7.net>

On Mar 17, 2009, at 09:07, Luis Lavena wrote:
> On Mon, Mar 16, 2009 at 2:47 PM, Eric Hodel <drbrain at segment7.net>  
> wrote:
>> On Mar 14, 2009, at 21:18, Daniel Berger wrote:
>>> I traced this one down (and it's not Windows specific). It looks  
>>> like it's
>>> trying to compare a Regexp to a Regexp with the =~ method, which  
>>> is illegal.
>>> This is what that particular test to doing:
>>>
>>> irb(main):001:0> /\Aa\Z/ =~ /a|b/
>>> TypeError: can't convert Regexp into String
>>>       from (irb):1
>>>
>>> I'm not sure what the proper behavior is for Gem::Dependency  
>>> because it is
>>> poorly documented. So, I don't know if the behavior is wrong or  
>>> the test
>>> itself is bad.
>>
>> Newer minitest fixes some assert_match issues, so I've added a  
>> version check
>> to the Rakefile.  Give it a whirl now.
>
> I had installed 1.3.1 at the time of my test, however, the following
> are the results:
>
> MinGW:
> http://pastie.org/418794
>
> VC6:
> http://pastie.org/418805
>
> Looks much better, but it seems that test_download_local_space still  
> fails.
>
> The idea was test path with spaces, like Windows paths? because Ruby
> URI is not recognizing it as a file source URI.
>
> Or I'm missing something?

The idea was to test (at least) installing from a space path.  My idea  
was to URI encode the path first to make the spaces palatable.  This  
at least works for OS X, maybe the drive letter is confusing it and it  
needs extra escaping?

From djberg96 at gmail.com  Tue Mar 17 22:59:48 2009
From: djberg96 at gmail.com (Daniel Berger)
Date: Tue, 17 Mar 2009 20:59:48 -0600
Subject: [Rubygems-developers] 1.3.2?
In-Reply-To: <226B9DD5-BDE7-460A-A7F5-7E3C6DF95079@segment7.net>
References: <49B8F012.4000704@gmail.com>	<71166b3b0903120620j3c13ca32qbbbc389c5263dc6b@mail.gmail.com>	<E1331D75B8E8DA46B15CDEA9BC46FA270D75EA3300@qtomaexmbm25.AD.QINTRA.COM>	<49BC81AA.6070305@gmail.com>	<1612C58D-2E47-4F1E-B9DC-67390E51B77E@segment7.net>	<71166b3b0903170907r258d0e89rb7387cc84a3e0924@mail.gmail.com>
	<226B9DD5-BDE7-460A-A7F5-7E3C6DF95079@segment7.net>
Message-ID: <49C063A4.80200@gmail.com>

Eric Hodel wrote:
> On Mar 17, 2009, at 09:07, Luis Lavena wrote:
>> On Mon, Mar 16, 2009 at 2:47 PM, Eric Hodel <drbrain at segment7.net> wrote:
>>> On Mar 14, 2009, at 21:18, Daniel Berger wrote:
>>>> I traced this one down (and it's not Windows specific). It looks 
>>>> like it's
>>>> trying to compare a Regexp to a Regexp with the =~ method, which is 
>>>> illegal.
>>>> This is what that particular test to doing:
>>>>
>>>> irb(main):001:0> /\Aa\Z/ =~ /a|b/
>>>> TypeError: can't convert Regexp into String
>>>>       from (irb):1
>>>>
>>>> I'm not sure what the proper behavior is for Gem::Dependency because 
>>>> it is
>>>> poorly documented. So, I don't know if the behavior is wrong or the 
>>>> test
>>>> itself is bad.
>>>
>>> Newer minitest fixes some assert_match issues, so I've added a 
>>> version check
>>> to the Rakefile.  Give it a whirl now.
>>
>> I had installed 1.3.1 at the time of my test, however, the following
>> are the results:
>>
>> MinGW:
>> http://pastie.org/418794
>>
>> VC6:
>> http://pastie.org/418805
>>
>> Looks much better, but it seems that test_download_local_space still 
>> fails.
>>
>> The idea was test path with spaces, like Windows paths? because Ruby
>> URI is not recognizing it as a file source URI.
>>
>> Or I'm missing something?

A valid URI can't contain a space can it?

irb(main):005:0> URI.parse('/foo/test_rubygems/space path/a-1.gem')
URI::InvalidURIError: bad URI(is not URI?): /foo/test_rubygems/space 
path/a-1.gem
         from /usr/local/lib/ruby/1.8/uri/common.rb:436:in `split'
         from /usr/local/lib/ruby/1.8/uri/common.rb:485:in `parse'
         from (irb):5

Dan

From drbrain at segment7.net  Wed Mar 18 00:58:55 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Tue, 17 Mar 2009 21:58:55 -0700
Subject: [Rubygems-developers] 1.3.2?
In-Reply-To: <49C063A4.80200@gmail.com>
References: <49B8F012.4000704@gmail.com>	<71166b3b0903120620j3c13ca32qbbbc389c5263dc6b@mail.gmail.com>	<E1331D75B8E8DA46B15CDEA9BC46FA270D75EA3300@qtomaexmbm25.AD.QINTRA.COM>	<49BC81AA.6070305@gmail.com>	<1612C58D-2E47-4F1E-B9DC-67390E51B77E@segment7.net>	<71166b3b0903170907r258d0e89rb7387cc84a3e0924@mail.gmail.com>
	<226B9DD5-BDE7-460A-A7F5-7E3C6DF95079@segment7.net>
	<49C063A4.80200@gmail.com>
Message-ID: <B71E5C44-A1D8-46D6-B9DC-B0CD25413604@segment7.net>

On Mar 17, 2009, at 19:59, Daniel Berger wrote:
> Eric Hodel wrote:
>> On Mar 17, 2009, at 09:07, Luis Lavena wrote:
>>> On Mon, Mar 16, 2009 at 2:47 PM, Eric Hodel <drbrain at segment7.net>  
>>> wrote:
>>>> On Mar 14, 2009, at 21:18, Daniel Berger wrote:
>>>>> I traced this one down (and it's not Windows specific). It looks  
>>>>> like it's
>>>>> trying to compare a Regexp to a Regexp with the =~ method, which  
>>>>> is illegal.
>>>>> This is what that particular test to doing:
>>>>>
>>>>> irb(main):001:0> /\Aa\Z/ =~ /a|b/
>>>>> TypeError: can't convert Regexp into String
>>>>>      from (irb):1
>>>>>
>>>>> I'm not sure what the proper behavior is for Gem::Dependency  
>>>>> because it is
>>>>> poorly documented. So, I don't know if the behavior is wrong or  
>>>>> the test
>>>>> itself is bad.
>>>>
>>>> Newer minitest fixes some assert_match issues, so I've added a  
>>>> version check
>>>> to the Rakefile.  Give it a whirl now.
>>>
>>> I had installed 1.3.1 at the time of my test, however, the following
>>> are the results:
>>>
>>> MinGW:
>>> http://pastie.org/418794
>>>
>>> VC6:
>>> http://pastie.org/418805
>>>
>>> Looks much better, but it seems that test_download_local_space  
>>> still fails.
>>>
>>> The idea was test path with spaces, like Windows paths? because Ruby
>>> URI is not recognizing it as a file source URI.
>>>
>>> Or I'm missing something?
>
> A valid URI can't contain a space can it?
>
> irb(main):005:0> URI.parse('/foo/test_rubygems/space path/a-1.gem')
> URI::InvalidURIError: bad URI(is not URI?): /foo/test_rubygems/space  
> path/a-1.gem
>        from /usr/local/lib/ruby/1.8/uri/common.rb:436:in `split'
>        from /usr/local/lib/ruby/1.8/uri/common.rb:485:in `parse'
>        from (irb):5

No, it needs to be encoded:

irb(main):003:0> URI.parse '/space%20path/file.txt'
=> #<URI::Generic:0x2cb19a URL:/space%20path/file.txt>


From luislavena at gmail.com  Wed Mar 18 11:22:01 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Wed, 18 Mar 2009 12:22:01 -0300
Subject: [Rubygems-developers] 1.3.2?
In-Reply-To: <226B9DD5-BDE7-460A-A7F5-7E3C6DF95079@segment7.net>
References: <49B8F012.4000704@gmail.com>
	<71166b3b0903120620j3c13ca32qbbbc389c5263dc6b@mail.gmail.com>
	<E1331D75B8E8DA46B15CDEA9BC46FA270D75EA3300@qtomaexmbm25.AD.QINTRA.COM>
	<49BC81AA.6070305@gmail.com>
	<1612C58D-2E47-4F1E-B9DC-67390E51B77E@segment7.net>
	<71166b3b0903170907r258d0e89rb7387cc84a3e0924@mail.gmail.com>
	<226B9DD5-BDE7-460A-A7F5-7E3C6DF95079@segment7.net>
Message-ID: <71166b3b0903180822y550913f2kdcb56315929ccf13@mail.gmail.com>

On Tue, Mar 17, 2009 at 10:53 PM, Eric Hodel <drbrain at segment7.net> wrote:
> On Mar 17, 2009, at 09:07, Luis Lavena wrote:
>>
>> On Mon, Mar 16, 2009 at 2:47 PM, Eric Hodel <drbrain at segment7.net> wrote:
>>>
>>> On Mar 14, 2009, at 21:18, Daniel Berger wrote:
>>>>
>>>> I traced this one down (and it's not Windows specific). It looks like
>>>> it's
>>>> trying to compare a Regexp to a Regexp with the =~ method, which is
>>>> illegal.
>>>> This is what that particular test to doing:
>>>>
>>>> irb(main):001:0> /\Aa\Z/ =~ /a|b/
>>>> TypeError: can't convert Regexp into String
>>>> ? ? ?from (irb):1
>>>>
>>>> I'm not sure what the proper behavior is for Gem::Dependency because it
>>>> is
>>>> poorly documented. So, I don't know if the behavior is wrong or the test
>>>> itself is bad.
>>>
>>> Newer minitest fixes some assert_match issues, so I've added a version
>>> check
>>> to the Rakefile. ?Give it a whirl now.
>>
>> I had installed 1.3.1 at the time of my test, however, the following
>> are the results:
>>
>> MinGW:
>> http://pastie.org/418794
>>
>> VC6:
>> http://pastie.org/418805
>>
>> Looks much better, but it seems that test_download_local_space still
>> fails.
>>
>> The idea was test path with spaces, like Windows paths? because Ruby
>> URI is not recognizing it as a file source URI.
>>
>> Or I'm missing something?
>
> The idea was to test (at least) installing from a space path. ?My idea was
> to URI encode the path first to make the spaces palatable. ?This at least
> works for OS X, maybe the drive letter is confusing it and it needs extra
> escaping?

I think for D:/Some/Path/with spaces/ requires to be prepend with
file:// protocol :-D

Something like this:

file:///D:/Some/path/with%20spaces/

-- 
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 djberg96 at gmail.com  Fri Mar 20 23:52:07 2009
From: djberg96 at gmail.com (Daniel Berger)
Date: Fri, 20 Mar 2009 21:52:07 -0600
Subject: [Rubygems-developers] 1.3.2?
In-Reply-To: <71166b3b0903180822y550913f2kdcb56315929ccf13@mail.gmail.com>
References: <49B8F012.4000704@gmail.com>	<71166b3b0903120620j3c13ca32qbbbc389c5263dc6b@mail.gmail.com>	<E1331D75B8E8DA46B15CDEA9BC46FA270D75EA3300@qtomaexmbm25.AD.QINTRA.COM>	<49BC81AA.6070305@gmail.com>	<1612C58D-2E47-4F1E-B9DC-67390E51B77E@segment7.net>	<71166b3b0903170907r258d0e89rb7387cc84a3e0924@mail.gmail.com>	<226B9DD5-BDE7-460A-A7F5-7E3C6DF95079@segment7.net>
	<71166b3b0903180822y550913f2kdcb56315929ccf13@mail.gmail.com>
Message-ID: <49C46467.3020700@gmail.com>

Luis Lavena wrote:

<snip>

>>>
>>> The idea was test path with spaces, like Windows paths? because Ruby
>>> URI is not recognizing it as a file source URI.
>>>
>>> Or I'm missing something?
>> The idea was to test (at least) installing from a space path.  My idea was
>> to URI encode the path first to make the spaces palatable.  This at least
>> works for OS X, maybe the drive letter is confusing it and it needs extra
>> escaping?
> 
> I think for D:/Some/Path/with spaces/ requires to be prepend with
> file:// protocol :-D
> 
> Something like this:
> 
> file:///D:/Some/path/with%20spaces/

I think always escaping the URI is the better solution:

--- remote_fetcher.old  Fri Mar 20 21:37:44 2009
+++ remote_fetcher.rb   Fri Mar 20 21:38:30 2009
@@ -85,17 +85,12 @@
     local_gem_path = File.join cache_dir, gem_file_name

     FileUtils.mkdir_p cache_dir rescue nil unless File.exist? cache_dir
+
+    # Always escape URI's to deal with potential spaces and such
     unless URI::Generic === source_uri
-      begin
-        source_uri = URI.parse source_uri
-      rescue URI::InvalidURIError
-        if source_uri =~ /\A#{File::SEPARATOR}/o then # HACK mswin
-          source_uri = URI.parse URI.escape(source_uri)
-        else
-          raise
-        end
-      end
+      source_uri = URI.parse(URI.escape(source_uri))
     end
+
     scheme = source_uri.scheme

     # URI.parse gets confused by MS Windows paths with forward slashes.

All tests pass.

Unless anyone has any objections, I'm going to commit this at some point 
this weekend.

Regards,

Dan


From luislavena at gmail.com  Sat Mar 21 09:17:26 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Sat, 21 Mar 2009 10:17:26 -0300
Subject: [Rubygems-developers] 1.3.2?
In-Reply-To: <49C46467.3020700@gmail.com>
References: <49B8F012.4000704@gmail.com>
	<71166b3b0903120620j3c13ca32qbbbc389c5263dc6b@mail.gmail.com>
	<E1331D75B8E8DA46B15CDEA9BC46FA270D75EA3300@qtomaexmbm25.AD.QINTRA.COM>
	<49BC81AA.6070305@gmail.com>
	<1612C58D-2E47-4F1E-B9DC-67390E51B77E@segment7.net>
	<71166b3b0903170907r258d0e89rb7387cc84a3e0924@mail.gmail.com>
	<226B9DD5-BDE7-460A-A7F5-7E3C6DF95079@segment7.net>
	<71166b3b0903180822y550913f2kdcb56315929ccf13@mail.gmail.com>
	<49C46467.3020700@gmail.com>
Message-ID: <71166b3b0903210617l313503c1ie70b8d215d5acdfa@mail.gmail.com>

On Sat, Mar 21, 2009 at 12:52 AM, Daniel Berger <djberg96 at gmail.com> wrote:
> [snip]
>
> I think always escaping the URI is the better solution:
>
> --- remote_fetcher.old ?Fri Mar 20 21:37:44 2009
> +++ remote_fetcher.rb ? Fri Mar 20 21:38:30 2009
> @@ -85,17 +85,12 @@
> ? ?local_gem_path = File.join cache_dir, gem_file_name
>
> ? ?FileUtils.mkdir_p cache_dir rescue nil unless File.exist? cache_dir
> +
> + ? ?# Always escape URI's to deal with potential spaces and such
> ? ?unless URI::Generic === source_uri
> - ? ? ?begin
> - ? ? ? ?source_uri = URI.parse source_uri
> - ? ? ?rescue URI::InvalidURIError
> - ? ? ? ?if source_uri =~ /\A#{File::SEPARATOR}/o then # HACK mswin
> - ? ? ? ? ?source_uri = URI.parse URI.escape(source_uri)
> - ? ? ? ?else
> - ? ? ? ? ?raise
> - ? ? ? ?end
> - ? ? ?end
> + ? ? ?source_uri = URI.parse(URI.escape(source_uri))
> ? ?end
> +
> ? ?scheme = source_uri.scheme
>
> ? ?# URI.parse gets confused by MS Windows paths with forward slashes.
>
> All tests pass.
>

But remote fetcher works? I mean, can we point to a local rubygems
repository using a PATH instead of a URL with file:// ?

Last time I've tried that (back in 2007) that didn't work on Windows.

> Unless anyone has any objections, I'm going to commit this at some point
> this weekend.
>

Except for the above note, everything looks good from my side :-)

> Regards,
>
> Dan
>

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

From djberg96 at gmail.com  Sat Mar 21 09:53:27 2009
From: djberg96 at gmail.com (Daniel Berger)
Date: Sat, 21 Mar 2009 07:53:27 -0600
Subject: [Rubygems-developers] 1.3.2?
In-Reply-To: <71166b3b0903210617l313503c1ie70b8d215d5acdfa@mail.gmail.com>
References: <49B8F012.4000704@gmail.com>
	<71166b3b0903120620j3c13ca32qbbbc389c5263dc6b@mail.gmail.com>
	<E1331D75B8E8DA46B15CDEA9BC46FA270D75EA3300@qtomaexmbm25.AD.QINTRA.COM>
	<49BC81AA.6070305@gmail.com>
	<1612C58D-2E47-4F1E-B9DC-67390E51B77E@segment7.net>
	<71166b3b0903170907r258d0e89rb7387cc84a3e0924@mail.gmail.com>
	<226B9DD5-BDE7-460A-A7F5-7E3C6DF95079@segment7.net>
	<71166b3b0903180822y550913f2kdcb56315929ccf13@mail.gmail.com>
	<49C46467.3020700@gmail.com>
	<71166b3b0903210617l313503c1ie70b8d215d5acdfa@mail.gmail.com>
Message-ID: <6037b70c0903210653k21049f73v9f91486fdf68972c@mail.gmail.com>

On Sat, Mar 21, 2009 at 7:17 AM, Luis Lavena <luislavena at gmail.com> wrote:
> On Sat, Mar 21, 2009 at 12:52 AM, Daniel Berger <djberg96 at gmail.com> wrote:
>> [snip]
>>
>> I think always escaping the URI is the better solution:
>>
>> --- remote_fetcher.old ?Fri Mar 20 21:37:44 2009
>> +++ remote_fetcher.rb ? Fri Mar 20 21:38:30 2009
>> @@ -85,17 +85,12 @@
>> ? ?local_gem_path = File.join cache_dir, gem_file_name
>>
>> ? ?FileUtils.mkdir_p cache_dir rescue nil unless File.exist? cache_dir
>> +
>> + ? ?# Always escape URI's to deal with potential spaces and such
>> ? ?unless URI::Generic === source_uri
>> - ? ? ?begin
>> - ? ? ? ?source_uri = URI.parse source_uri
>> - ? ? ?rescue URI::InvalidURIError
>> - ? ? ? ?if source_uri =~ /\A#{File::SEPARATOR}/o then # HACK mswin
>> - ? ? ? ? ?source_uri = URI.parse URI.escape(source_uri)
>> - ? ? ? ?else
>> - ? ? ? ? ?raise
>> - ? ? ? ?end
>> - ? ? ?end
>> + ? ? ?source_uri = URI.parse(URI.escape(source_uri))
>> ? ?end
>> +
>> ? ?scheme = source_uri.scheme
>>
>> ? ?# URI.parse gets confused by MS Windows paths with forward slashes.
>>
>> All tests pass.
>>
>
> But remote fetcher works? I mean, can we point to a local rubygems
> repository using a PATH instead of a URL with file:// ?

Yep, should work. That's one of the changes I've made in the last few months.

See RF bug #16495.

Regards,

Dan

From djberg96 at gmail.com  Sat Mar 21 12:29:38 2009
From: djberg96 at gmail.com (Daniel Berger)
Date: Sat, 21 Mar 2009 10:29:38 -0600
Subject: [Rubygems-developers] Gem::SourceIndex#search deprecation?
Message-ID: <49C515F2.3060008@gmail.com>

Hi,

I installed the latest from svn, and ran a "gem clean ptools". I got 
this warning:

/usr/local/lib/ruby/site_ruby/1.8/rubygems/commands/cleanup_command.rb:45:Warning: 
Gem::SourceIndex#search support for Regexp patterns is deprecated

Why is regex search deprecated?

Regards,

Dan

From drbrain at segment7.net  Mon Mar 23 17:52:52 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Mon, 23 Mar 2009 14:52:52 -0700
Subject: [Rubygems-developers] Gem::SourceIndex#search deprecation?
In-Reply-To: <49C515F2.3060008@gmail.com>
References: <49C515F2.3060008@gmail.com>
Message-ID: <D9244A1B-30E5-4A12-971E-0AC150565ECB@segment7.net>

On Mar 21, 2009, at 09:29, Daniel Berger wrote:
> I installed the latest from svn, and ran a "gem clean ptools". I got  
> this warning:
>
> /usr/local/lib/ruby/site_ruby/1.8/rubygems/commands/ 
> cleanup_command.rb:45:Warning: Gem::SourceIndex#search support for  
> Regexp patterns is deprecated
>
> Why is regex search deprecated?

I'm trying to reduce code duplication.  Both Gem::SourceIndex and  
Gem::Dependency had code to turn a Regexp into a Gem::Dependency.  I'd  
rather have just Gem::Dependency have that code.

From drbrain at segment7.net  Mon Mar 23 17:59:59 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Mon, 23 Mar 2009 14:59:59 -0700
Subject: [Rubygems-developers] Gem::SourceIndex#search deprecation?
In-Reply-To: <49C515F2.3060008@gmail.com>
References: <49C515F2.3060008@gmail.com>
Message-ID: <5DC448BE-B86C-4F67-99F2-567E069B54FA@segment7.net>

On Mar 21, 2009, at 09:29, Daniel Berger wrote:

> I installed the latest from svn, and ran a "gem clean ptools". I got  
> this warning:

Ok, I've also fixed this warning.

From drbrain at segment7.net  Fri Mar 27 18:13:29 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Fri, 27 Mar 2009 15:13:29 -0700
Subject: [Rubygems-developers] RubyGems 1.3.2 RSN
Message-ID: <526388EE-66CC-4D38-826C-CC05286E46C8@segment7.net>

I think it's about time to release 1.3.2.

Here's what's left that's candidates for fixing:

#23964 setup command --destdir handling:

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

Was this patch committed, should I commit it?

#23429 gem cache goes to wrong drive

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

#24770 RubyGems 1.3.1 doesn't install on Vista Business

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

Delayed Issues:

#22965 gem activation failures

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

There's a patch, but it's relatively large and has no tests.

#22617 Gem.loaded_specs on 1.9

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

I think this will require gem_prelude.rb changes.


From rbrown at exherbo.org  Fri Mar 27 18:35:06 2009
From: rbrown at exherbo.org (Richard Brown)
Date: Fri, 27 Mar 2009 22:35:06 +0000
Subject: [Rubygems-developers] RubyGems 1.3.2 RSN
In-Reply-To: <526388EE-66CC-4D38-826C-CC05286E46C8@segment7.net>
References: <526388EE-66CC-4D38-826C-CC05286E46C8@segment7.net>
Message-ID: <df1735a20903271535o49839314u55b2588b54df2fb2@mail.gmail.com>

2009/3/27 Eric Hodel <drbrain at segment7.net>:
> I think it's about time to release 1.3.2.
>
> Here's what's left that's candidates for fixing:
>
> #23964 setup command --destdir handling:
>
> http://rubyforge.org/tracker/index.php?func=detail&aid=23964&group_id=126&atid=577
>
> Was this patch committed, should I commit it?

No, and No. There's two patches on http://gist.github.com/77950 that I
can submit to the bug if you want. The first you can probably just
apply, it fixes some variable names in the install file that got
confused when setup_command.rb was created. The second fixes
--destdir, but it waiting for Luis to say whether it works on windows.


-- 
Richard Brown

From luislavena at gmail.com  Fri Mar 27 20:28:01 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Fri, 27 Mar 2009 21:28:01 -0300
Subject: [Rubygems-developers] RubyGems 1.3.2 RSN
In-Reply-To: <df1735a20903271535o49839314u55b2588b54df2fb2@mail.gmail.com>
References: <526388EE-66CC-4D38-826C-CC05286E46C8@segment7.net>
	<df1735a20903271535o49839314u55b2588b54df2fb2@mail.gmail.com>
Message-ID: <71166b3b0903271728x141996adj278a831a876ebc77@mail.gmail.com>

On Fri, Mar 27, 2009 at 7:35 PM, Richard Brown <rbrown at exherbo.org> wrote:
> 2009/3/27 Eric Hodel <drbrain at segment7.net>:
>> I think it's about time to release 1.3.2.
>>
>> Here's what's left that's candidates for fixing:
>>
>> #23964 setup command --destdir handling:
>>
>> http://rubyforge.org/tracker/index.php?func=detail&aid=23964&group_id=126&atid=577
>>
>> Was this patch committed, should I commit it?
>
> No, and No. There's two patches on http://gist.github.com/77950 that I
> can submit to the bug if you want. The first you can probably just
> apply, it fixes some variable names in the install file that got
> confused when setup_command.rb was created. The second fixes
> --destdir, but it waiting for Luis to say whether it works on windows.
>

I'll confirm this tomorrow, when I work on One-Click Installer.

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

From luislavena at gmail.com  Fri Mar 27 20:29:39 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Fri, 27 Mar 2009 21:29:39 -0300
Subject: [Rubygems-developers] RubyGems 1.3.2 RSN
In-Reply-To: <526388EE-66CC-4D38-826C-CC05286E46C8@segment7.net>
References: <526388EE-66CC-4D38-826C-CC05286E46C8@segment7.net>
Message-ID: <71166b3b0903271729n10318007y5b4f1269cc0c4971@mail.gmail.com>

2009/3/27 Eric Hodel <drbrain at segment7.net>:
> [...]
>
> #23429 gem cache goes to wrong drive
>
> http://rubyforge.org/tracker/index.php?func=detail&aid=23429&group_id=126&atid=575
>

Cannot reproduce this. Added my comments to the ticket.

> #24770 RubyGems 1.3.1 doesn't install on Vista Business
>
> http://rubyforge.org/tracker/index.php?func=detail&aid=24770&group_id=126&atid=575

I'm not a Vista user and without the exact error messages, cannot do
too much to help out fixing it.

-- 
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 technomancy at gmail.com  Fri Mar 27 21:09:01 2009
From: technomancy at gmail.com (Phil Hagelberg)
Date: Fri, 27 Mar 2009 18:09:01 -0700
Subject: [Rubygems-developers] RubyGems 1.3.2 RSN
In-Reply-To: <526388EE-66CC-4D38-826C-CC05286E46C8@segment7.net> (Eric Hodel's
	message of "Fri, 27 Mar 2009 15:13:29 -0700")
References: <526388EE-66CC-4D38-826C-CC05286E46C8@segment7.net>
Message-ID: <87iqlu78sy.fsf@hagelb.org>

Eric Hodel <drbrain at segment7.net> writes:

> I think it's about time to release 1.3.2.

I've got some documentation to do for the new prerelease logic that
should make it in before the release. I will try to do this soon.

-Phil

From drbrain at segment7.net  Sat Mar 28 00:17:49 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Fri, 27 Mar 2009 21:17:49 -0700
Subject: [Rubygems-developers] RubyGems 1.3.2 RSN
Message-ID: <4D1D143A-9FE6-4720-9DFD-886270A94A8C@segment7.net>

I think it's about time to release 1.3.2.

Here's what's left that's candidates for fixing:

#23964 setup command --destdir handling:

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

Was this patch committed, should I commit it?

#23429 gem cache goes to wrong drive

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

#24770 RubyGems 1.3.1 doesn't install on Vista Business

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

Delayed Issues:

#22965 gem activation failures

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

There's a patch, but it's relatively large and has no tests.

#22617 Gem.loaded_specs on 1.9

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

I think this will require gem_prelude.rb changes.


From drbrain at segment7.net  Sat Mar 28 00:36:17 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Fri, 27 Mar 2009 21:36:17 -0700
Subject: [Rubygems-developers] RubyGems 1.3.2 RSN
In-Reply-To: <4D1D143A-9FE6-4720-9DFD-886270A94A8C@segment7.net>
References: <4D1D143A-9FE6-4720-9DFD-886270A94A8C@segment7.net>
Message-ID: <E9E4C5C3-FA9A-45B4-BAEB-CFB9C47793FA@segment7.net>

On Mar 27, 2009, at 21:17, Eric Hodel wrote:

> I think it's about time to release 1.3.2.

Oops, Mail.app wasn't being friendly with me, so I sent it twice :(

From drbrain at segment7.net  Sat Mar 28 05:55:40 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Sat, 28 Mar 2009 02:55:40 -0700
Subject: [Rubygems-developers] RubyGems 1.3.2 RSN
In-Reply-To: <df1735a20903271535o49839314u55b2588b54df2fb2@mail.gmail.com>
References: <526388EE-66CC-4D38-826C-CC05286E46C8@segment7.net>
	<df1735a20903271535o49839314u55b2588b54df2fb2@mail.gmail.com>
Message-ID: <A1CEA049-D41A-4FAC-AC29-019764029A22@segment7.net>

On Mar 27, 2009, at 15:35, Richard Brown wrote:
> 2009/3/27 Eric Hodel <drbrain at segment7.net>:
>> I think it's about time to release 1.3.2.
>>
>> Here's what's left that's candidates for fixing:
>>
>> #23964 setup command --destdir handling:
>>
>> http://rubyforge.org/tracker/index.php?func=detail&aid=23964&group_id=126&atid=577
>>
>> Was this patch committed, should I commit it?
>
> No, and No. There's two patches on http://gist.github.com/77950 that I
> can submit to the bug if you want.

Yes, please submit them, it'll make them easier to track.

> The first you can probably just apply, it fixes some variable names  
> in the install file that got confused when setup_command.rb was  
> created.

Sorry, it was one small step towards getting the setup command tested  
so that hopefully things won't break in the future.

> The second fixes --destdir, but it waiting for Luis to say whether  
> it works on windows.


From drbrain at segment7.net  Sat Mar 28 05:57:18 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Sat, 28 Mar 2009 02:57:18 -0700
Subject: [Rubygems-developers] RubyGems 1.3.2 RSN
In-Reply-To: <71166b3b0903271729n10318007y5b4f1269cc0c4971@mail.gmail.com>
References: <526388EE-66CC-4D38-826C-CC05286E46C8@segment7.net>
	<71166b3b0903271729n10318007y5b4f1269cc0c4971@mail.gmail.com>
Message-ID: <6CBE2D72-34FC-4549-B462-BB6CA419F836@segment7.net>

On Mar 27, 2009, at 17:29, Luis Lavena wrote:

>> #24770 RubyGems 1.3.1 doesn't install on Vista Business
>>
>> http://rubyforge.org/tracker/index.php?func=detail&aid=24770&group_id=126&atid=575
>
> I'm not a Vista user and without the exact error messages, cannot do
> too much to help out fixing it.

I don't know if the reporter will give the exact error message to us :(

From dsisnero at gmail.com  Tue Mar 31 03:11:29 2009
From: dsisnero at gmail.com (Dominic Sisneros)
Date: Tue, 31 Mar 2009 01:11:29 -0600
Subject: [Rubygems-developers] gem problem
Message-ID: <c429d15e0903310011r12b88155rbaf26ad8ece962d0@mail.gmail.com>

I did a gem cleanup and since then I have been getting the following error
whenever I try to use a gem

irb(main):002:0> require 'systemu'
NoMethodError: undefined method `join' for nil:NilClass
        from
c:/ruby/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:96:in
`lib_dirs_for'
        from
c:/ruby/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:26:in
`initialize'
        from
c:/ruby/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:25:in `each'
        from
c:/ruby/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:25:in
`initialize'
        from c:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:684:in `new'
        from c:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:684:in `searcher'
        from c:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:683:in `synchronize'
        from c:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:683:in `searcher'
        from c:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:34:in
`require'
        from (irb):2
irb(main):003:0> require 'rails'
NoMethodError: undefined method `join' for nil:NilClass
        from
c:/ruby/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:96:in
`lib_dirs_for'
        from
c:/ruby/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:26:in
`initialize'
        from
c:/ruby/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:25:in `each'
        from
c:/ruby/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:25:in
`initialize'


Heres my gem env

$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.1
  - RUBY VERSION: 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32]
  - INSTALLATION DIRECTORY: c:/ruby/lib/ruby/gems/1.8
  - RUBY EXECUTABLE: c:/ruby/bin/ruby.exe
  - EXECUTABLE DIRECTORY: c:/ruby/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mswin32-60
  - GEM PATHS:
     - c:/ruby/lib/ruby/gems/1.8
     - c:/Documents and Settings/dominic e sisneros/My
Documents/.gem/ruby/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://gems.rubyforge.org", "
http://gems.rubyonrails.org", "http://gems.github.com/"]
  - REMOTE SOURCES:
     - http://gems.rubyforge.org
     - http://gems.rubyonrails.org
     - http://gems.github.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rubygems-developers/attachments/20090331/7b5753fd/attachment-0001.html>

From aslak.hellesoy at gmail.com  Tue Mar 31 04:10:55 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Tue, 31 Mar 2009 10:10:55 +0200
Subject: [Rubygems-developers] gem problem
In-Reply-To: <c429d15e0903310011r12b88155rbaf26ad8ece962d0@mail.gmail.com>
References: <c429d15e0903310011r12b88155rbaf26ad8ece962d0@mail.gmail.com>
Message-ID: <8d961d900903310110t7cb1a254n6603eb5b851bce61@mail.gmail.com>

2009/3/31 Dominic Sisneros <dsisnero at gmail.com>

> I did a gem cleanup and since then I have been getting the following error
> whenever I try to use a gem
>

I had the same problem yesterday, when I upgraded all my gems. It turns out,
this error occurs if you have one broken gem.
My solution: Add a puts statement inside gem_path_searcher.rb to find out
what gem is broken. Then uninstall it. (For me it was the latest
mojombo-grit).

A better solution would be to patch Rubygems so it doesn't choke just
because you have a broken gem - or at least tell you which one it is.


> irb(main):002:0> require 'systemu'
> NoMethodError: undefined method `join' for nil:NilClass
>         from
> c:/ruby/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:96:in
> `lib_dirs_for'
>         from
> c:/ruby/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:26:in
> `initialize'
>         from
> c:/ruby/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:25:in `each'
>         from
> c:/ruby/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:25:in
> `initialize'
>         from c:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:684:in `new'
>         from c:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:684:in `searcher'
>         from c:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:683:in
> `synchronize'
>         from c:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:683:in `searcher'
>         from
> c:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:34:in `require'
>         from (irb):2
> irb(main):003:0> require 'rails'
> NoMethodError: undefined method `join' for nil:NilClass
>         from
> c:/ruby/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:96:in
> `lib_dirs_for'
>         from
> c:/ruby/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:26:in
> `initialize'
>         from
> c:/ruby/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:25:in `each'
>         from
> c:/ruby/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:25:in
> `initialize'
>
>
> Heres my gem env
>
> $ gem env
> RubyGems Environment:
>   - RUBYGEMS VERSION: 1.3.1
>   - RUBY VERSION: 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32]
>   - INSTALLATION DIRECTORY: c:/ruby/lib/ruby/gems/1.8
>   - RUBY EXECUTABLE: c:/ruby/bin/ruby.exe
>   - EXECUTABLE DIRECTORY: c:/ruby/bin
>   - RUBYGEMS PLATFORMS:
>     - ruby
>     - x86-mswin32-60
>   - GEM PATHS:
>      - c:/ruby/lib/ruby/gems/1.8
>      - c:/Documents and Settings/dominic e sisneros/My
> Documents/.gem/ruby/1.8
>   - GEM CONFIGURATION:
>      - :update_sources => true
>      - :verbose => true
>      - :benchmark => false
>      - :backtrace => false
>      - :bulk_threshold => 1000
>      - :sources => ["http://gems.rubyforge.org", "
> http://gems.rubyonrails.org", "http://gems.github.com/"]
>   - REMOTE SOURCES:
>      - http://gems.rubyforge.org
>      - http://gems.rubyonrails.org
>      - http://gems.github.com/
>
>
> _______________________________________________
> Rubygems-developers mailing list
> Rubygems-developers at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubygems-developers
>



-- 
Aslak (::)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rubygems-developers/attachments/20090331/efa65087/attachment.html>

From jftucker at gmail.com  Tue Mar 31 08:53:43 2009
From: jftucker at gmail.com (James Tucker)
Date: Tue, 31 Mar 2009 13:53:43 +0100
Subject: [Rubygems-developers] gem problem
In-Reply-To: <8d961d900903310110t7cb1a254n6603eb5b851bce61@mail.gmail.com>
References: <c429d15e0903310011r12b88155rbaf26ad8ece962d0@mail.gmail.com>
	<8d961d900903310110t7cb1a254n6603eb5b851bce61@mail.gmail.com>
Message-ID: <405B53B0-8125-4F1A-A93A-9F86BBE5F337@gmail.com>

This should probably be made to result in a LoadError. Thoughts?

On 31 Mar 2009, at 09:10, aslak hellesoy wrote:

>
>
> 2009/3/31 Dominic Sisneros <dsisnero at gmail.com>
> I did a gem cleanup and since then I have been getting the following  
> error whenever I try to use a gem
>
> I had the same problem yesterday, when I upgraded all my gems. It  
> turns out, this error occurs if you have one broken gem.
> My solution: Add a puts statement inside gem_path_searcher.rb to  
> find out what gem is broken. Then uninstall it. (For me it was the  
> latest mojombo-grit).
>
> A better solution would be to patch Rubygems so it doesn't choke  
> just because you have a broken gem - or at least tell you which one  
> it is.
>
>
> irb(main):002:0> require 'systemu'
> NoMethodError: undefined method `join' for nil:NilClass
>         from c:/ruby/lib/ruby/site_ruby/1.8/rubygems/ 
> gem_path_searcher.rb:96:in `lib_dirs_for'
>         from c:/ruby/lib/ruby/site_ruby/1.8/rubygems/ 
> gem_path_searcher.rb:26:in `initialize'
>         from c:/ruby/lib/ruby/site_ruby/1.8/rubygems/ 
> gem_path_searcher.rb:25:in `each'
>         from c:/ruby/lib/ruby/site_ruby/1.8/rubygems/ 
> gem_path_searcher.rb:25:in `initialize'
>         from c:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:684:in `new'
>         from c:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:684:in  
> `searcher'
>         from c:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:683:in  
> `synchronize'
>         from c:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:683:in  
> `searcher'
>         from c:/ruby/lib/ruby/site_ruby/1.8/rubygems/ 
> custom_require.rb:34:in `require'
>         from (irb):2
> irb(main):003:0> require 'rails'
> NoMethodError: undefined method `join' for nil:NilClass
>         from c:/ruby/lib/ruby/site_ruby/1.8/rubygems/ 
> gem_path_searcher.rb:96:in `lib_dirs_for'
>         from c:/ruby/lib/ruby/site_ruby/1.8/rubygems/ 
> gem_path_searcher.rb:26:in `initialize'
>         from c:/ruby/lib/ruby/site_ruby/1.8/rubygems/ 
> gem_path_searcher.rb:25:in `each'
>         from c:/ruby/lib/ruby/site_ruby/1.8/rubygems/ 
> gem_path_searcher.rb:25:in `initialize'
>
>
> Heres my gem env
>
> $ gem env
> RubyGems Environment:
>   - RUBYGEMS VERSION: 1.3.1
>   - RUBY VERSION: 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32]
>   - INSTALLATION DIRECTORY: c:/ruby/lib/ruby/gems/1.8
>   - RUBY EXECUTABLE: c:/ruby/bin/ruby.exe
>   - EXECUTABLE DIRECTORY: c:/ruby/bin
>   - RUBYGEMS PLATFORMS:
>     - ruby
>     - x86-mswin32-60
>   - GEM PATHS:
>      - c:/ruby/lib/ruby/gems/1.8
>      - c:/Documents and Settings/dominic e sisneros/My  
> Documents/.gem/ruby/1.8
>   - GEM CONFIGURATION:
>      - :update_sources => true
>      - :verbose => true
>      - :benchmark => false
>      - :backtrace => false
>      - :bulk_threshold => 1000
>      - :sources => ["http://gems.rubyforge.org", "http://gems.rubyonrails.org 
> ", "http://gems.github.com/"]
>   - REMOTE SOURCES:
>      - http://gems.rubyforge.org
>      - http://gems.rubyonrails.org
>      - http://gems.github.com/
>
>
> _______________________________________________
> Rubygems-developers mailing list
> Rubygems-developers at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubygems-developers
>
>
>
> -- 
> Aslak (::)
> _______________________________________________
> Rubygems-developers mailing list
> Rubygems-developers at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubygems-developers

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rubygems-developers/attachments/20090331/cfc68281/attachment.html>

From aslak.hellesoy at gmail.com  Tue Mar 31 10:08:54 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Tue, 31 Mar 2009 16:08:54 +0200
Subject: [Rubygems-developers] gem problem
In-Reply-To: <405B53B0-8125-4F1A-A93A-9F86BBE5F337@gmail.com>
References: <c429d15e0903310011r12b88155rbaf26ad8ece962d0@mail.gmail.com>
	<8d961d900903310110t7cb1a254n6603eb5b851bce61@mail.gmail.com>
	<405B53B0-8125-4F1A-A93A-9F86BBE5F337@gmail.com>
Message-ID: <8d961d900903310708x7fd080ces2f854ad1d3dfa06d@mail.gmail.com>

This should probably be made to result in a LoadError. Thoughts?
>

In my case I wasn't trying to load the mojombo-grit gem. The error happened
while scanning all the gems. I don't think scanning a broken gem should
result in a LoadError.

Aslak


>
> On 31 Mar 2009, at 09:10, aslak hellesoy wrote:
>
>
>
> 2009/3/31 Dominic Sisneros <dsisnero at gmail.com>
>
>> I did a gem cleanup and since then I have been getting the following error
>> whenever I try to use a gem
>>
>
> I had the same problem yesterday, when I upgraded all my gems. It turns
> out, this error occurs if you have one broken gem.
> My solution: Add a puts statement inside gem_path_searcher.rb to find out
> what gem is broken. Then uninstall it. (For me it was the latest
> mojombo-grit).
>
> A better solution would be to patch Rubygems so it doesn't choke just
> because you have a broken gem - or at least tell you which one it is.
>
>
>> irb(main):002:0> require 'systemu'
>> NoMethodError: undefined method `join' for nil:NilClass
>>         from
>> c:/ruby/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:96:in
>> `lib_dirs_for'
>>         from
>> c:/ruby/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:26:in
>> `initialize'
>>         from
>> c:/ruby/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:25:in `each'
>>         from
>> c:/ruby/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:25:in
>> `initialize'
>>         from c:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:684:in `new'
>>         from c:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:684:in `searcher'
>>         from c:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:683:in
>> `synchronize'
>>         from c:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:683:in `searcher'
>>         from
>> c:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:34:in `require'
>>         from (irb):2
>> irb(main):003:0> require 'rails'
>> NoMethodError: undefined method `join' for nil:NilClass
>>         from
>> c:/ruby/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:96:in
>> `lib_dirs_for'
>>         from
>> c:/ruby/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:26:in
>> `initialize'
>>         from
>> c:/ruby/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:25:in `each'
>>         from
>> c:/ruby/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:25:in
>> `initialize'
>>
>>
>> Heres my gem env
>>
>> $ gem env
>> RubyGems Environment:
>>   - RUBYGEMS VERSION: 1.3.1
>>   - RUBY VERSION: 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32]
>>   - INSTALLATION DIRECTORY: c:/ruby/lib/ruby/gems/1.8
>>   - RUBY EXECUTABLE: c:/ruby/bin/ruby.exe
>>   - EXECUTABLE DIRECTORY: c:/ruby/bin
>>   - RUBYGEMS PLATFORMS:
>>     - ruby
>>     - x86-mswin32-60
>>   - GEM PATHS:
>>      - c:/ruby/lib/ruby/gems/1.8
>>      - c:/Documents and Settings/dominic e sisneros/My
>> Documents/.gem/ruby/1.8
>>   - GEM CONFIGURATION:
>>      - :update_sources => true
>>      - :verbose => true
>>      - :benchmark => false
>>      - :backtrace => false
>>      - :bulk_threshold => 1000
>>      - :sources => ["http://gems.rubyforge.org", "
>> http://gems.rubyonrails.org", "http://gems.github.com/"]
>>   - REMOTE SOURCES:
>>      - http://gems.rubyforge.org
>>      - http://gems.rubyonrails.org
>>      - http://gems.github.com/
>>
>>
>> _______________________________________________
>> Rubygems-developers mailing list
>> Rubygems-developers at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rubygems-developers
>>
>
>
>
> --
> Aslak (::)
> _______________________________________________
> Rubygems-developers mailing list
> Rubygems-developers at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubygems-developers
>
>
>
> _______________________________________________
> Rubygems-developers mailing list
> Rubygems-developers at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubygems-developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rubygems-developers/attachments/20090331/5302dd92/attachment-0001.html>

From dsisnero at gmail.com  Tue Mar 31 10:51:19 2009
From: dsisnero at gmail.com (Dominic Sisneros)
Date: Tue, 31 Mar 2009 08:51:19 -0600
Subject: [Rubygems-developers] gem problem
In-Reply-To: <8d961d900903310110t7cb1a254n6603eb5b851bce61@mail.gmail.com>
References: <c429d15e0903310011r12b88155rbaf26ad8ece962d0@mail.gmail.com>
	<8d961d900903310110t7cb1a254n6603eb5b851bce61@mail.gmail.com>
Message-ID: <c429d15e0903310751h411e56dclc85c5d57b13bf9b7@mail.gmail.com>

thanks so much!

It was the latest mojombo-grit!



> My solution: Add a puts statement inside gem_path_searcher.rb to find out
> what gem is broken. Then uninstall it. (For me it was the latest
> mojombo-grit).
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rubygems-developers/attachments/20090331/277fb4b2/attachment.html>

From dsisnero at gmail.com  Tue Mar 31 11:12:36 2009
From: dsisnero at gmail.com (Dominic Sisneros)
Date: Tue, 31 Mar 2009 09:12:36 -0600
Subject: [Rubygems-developers] gem problem
In-Reply-To: <8d961d900903310708x7fd080ces2f854ad1d3dfa06d@mail.gmail.com>
References: <c429d15e0903310011r12b88155rbaf26ad8ece962d0@mail.gmail.com>
	<8d961d900903310110t7cb1a254n6603eb5b851bce61@mail.gmail.com>
	<405B53B0-8125-4F1A-A93A-9F86BBE5F337@gmail.com>
	<8d961d900903310708x7fd080ces2f854ad1d3dfa06d@mail.gmail.com>
Message-ID: <c429d15e0903310812t2b779264m8b247c042ef417e7@mail.gmail.com>

>
> In my case I wasn't trying to load the mojombo-grit gem. The error happened
> while scanning all the gems. I don't think scanning a broken gem should
> result in a LoadError.
>
>

That was the case for me also.  I was just scanning the gems not loading or
requiring.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rubygems-developers/attachments/20090331/6def5fa8/attachment.html>

From Daniel.Berger at qwest.com  Tue Mar 31 11:03:33 2009
From: Daniel.Berger at qwest.com (Berger, Daniel)
Date: Tue, 31 Mar 2009 10:03:33 -0500
Subject: [Rubygems-developers] #rubygems channel?
Message-ID: <E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D460F@qtomaexmbm25.AD.QINTRA.COM>

Hi,

How does everyone feel about a #rubygems irc channel where we could congregate to discuss rubygems development issues? Good idea or not worth the effort?

Regards,

Dan

From jftucker at gmail.com  Tue Mar 31 11:49:59 2009
From: jftucker at gmail.com (James Tucker)
Date: Tue, 31 Mar 2009 16:49:59 +0100
Subject: [Rubygems-developers] #rubygems channel?
In-Reply-To: <E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D460F@qtomaexmbm25.AD.QINTRA.COM>
References: <E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D460F@qtomaexmbm25.AD.QINTRA.COM>
Message-ID: <C496C3A1-CF1C-4787-879B-A74E726FF7CA@gmail.com>


On 31 Mar 2009, at 16:03, Berger, Daniel wrote:

> Hi,
>
> How does everyone feel about a #rubygems irc channel where we could  
> congregate to discuss rubygems development issues? Good idea or not  
> worth the effort?

i'll see you there..

>
> Regards,
>
> Dan
> _______________________________________________
> Rubygems-developers mailing list
> Rubygems-developers at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubygems-developers


From aslak.hellesoy at gmail.com  Tue Mar 31 11:57:40 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Tue, 31 Mar 2009 17:57:40 +0200
Subject: [Rubygems-developers] #rubygems channel?
In-Reply-To: <E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D460F@qtomaexmbm25.AD.QINTRA.COM>
References: <E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D460F@qtomaexmbm25.AD.QINTRA.COM>
Message-ID: <8d961d900903310857m26cffd9agd4fb78240174c69@mail.gmail.com>

On Tue, Mar 31, 2009 at 5:03 PM, Berger, Daniel <Daniel.Berger at qwest.com>wrote:

> Hi,
>
> How does everyone feel about a #rubygems irc channel where we could
> congregate to discuss rubygems development issues? Good idea or not worth
> the effort?
>

I didn't know "/join #rubygems" required effort ;-)

Aslak


>
> Regards,
>
> Dan
> _______________________________________________
> Rubygems-developers mailing list
> Rubygems-developers at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubygems-developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rubygems-developers/attachments/20090331/518cf39f/attachment.html>

From Amanda.Waite at Sun.COM  Tue Mar 31 12:34:46 2009
From: Amanda.Waite at Sun.COM (Amanda Waite)
Date: Tue, 31 Mar 2009 17:34:46 +0100
Subject: [Rubygems-developers] #rubygems channel?
In-Reply-To: <E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D460F@qtomaexmbm25.AD.QINTRA.COM>
References: <E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D460F@qtomaexmbm25.AD.QINTRA.COM>
Message-ID: <49D24626.6010701@sun.com>

Berger, Daniel wrote:
> Hi,
>
> How does everyone feel about a #rubygems irc channel where we could congregate to discuss rubygems development issues? Good idea or not worth the effort?
>   

I think it's a great idea, although I might ask questions on IRC earlier 
than I would on email. Not sure if that's a good thing or a bad thing :o)

Amanda

> Regards,
>
> Dan
> _______________________________________________
> Rubygems-developers mailing list
> Rubygems-developers at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubygems-developers
>   


From thewoolleyman at gmail.com  Tue Mar 31 12:52:36 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Tue, 31 Mar 2009 09:52:36 -0700
Subject: [Rubygems-developers] #rubygems channel?
In-Reply-To: <E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D460F@qtomaexmbm25.AD.QINTRA.COM>
References: <E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D460F@qtomaexmbm25.AD.QINTRA.COM>
Message-ID: <e3af97510903310952gf8ef6bi344b649847fe00fc@mail.gmail.com>

On Tue, Mar 31, 2009 at 8:03 AM, Berger, Daniel <Daniel.Berger at qwest.com> wrote:
> How does everyone feel about a #rubygems irc channel where we could congregate to discuss rubygems development issues? Good idea or not worth the effort?

+1

Added to my favorites.

From luislavena at gmail.com  Tue Mar 31 13:01:03 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Tue, 31 Mar 2009 14:01:03 -0300
Subject: [Rubygems-developers] #rubygems channel?
In-Reply-To: <E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D460F@qtomaexmbm25.AD.QINTRA.COM>
References: <E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D460F@qtomaexmbm25.AD.QINTRA.COM>
Message-ID: <71166b3b0903311001o39cd6993s52efa1bbfbd46686@mail.gmail.com>

On Tue, Mar 31, 2009 at 12:03 PM, Berger, Daniel
<Daniel.Berger at qwest.com> wrote:
> Hi,
>
> How does everyone feel about a #rubygems irc channel where we could congregate to discuss rubygems development issues? Good idea or not worth the effort?
>

I usually don't hang out on IRC, somehow I find it distracting (maybe
is just me)

But having a channel and most of the time contributors hang out over
there and help out.

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  Tue Mar 31 13:45:46 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Tue, 31 Mar 2009 10:45:46 -0700
Subject: [Rubygems-developers] Latest and greatest instructions for setting
	up a public gem server?
Message-ID: <e3af97510903311045s1b0cc06qffb2062eefa53dfe@mail.gmail.com>

Any suggestions?  Including example scripts, cron jobs, etc?

From drbrain at segment7.net  Tue Mar 31 13:51:53 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Tue, 31 Mar 2009 10:51:53 -0700
Subject: [Rubygems-developers] gem problem
In-Reply-To: <8d961d900903310110t7cb1a254n6603eb5b851bce61@mail.gmail.com>
References: <c429d15e0903310011r12b88155rbaf26ad8ece962d0@mail.gmail.com>
	<8d961d900903310110t7cb1a254n6603eb5b851bce61@mail.gmail.com>
Message-ID: <B9962927-4B74-4DE7-8D29-2F59AA098C8C@segment7.net>

On Mar 31, 2009, at 01:10, aslak hellesoy wrote:

> 2009/3/31 Dominic Sisneros <dsisnero at gmail.com>
>> I did a gem cleanup and since then I have been getting the  
>> following error whenever I try to use a gem
>
> I had the same problem yesterday, when I upgraded all my gems. It  
> turns out, this error occurs if you have one broken gem.
> My solution: Add a puts statement inside gem_path_searcher.rb to  
> find out what gem is broken. Then uninstall it. (For me it was the  
> latest mojombo-grit).
>
> A better solution would be to patch Rubygems so it doesn't choke  
> just because you have a broken gem - or at least tell you which one  
> it is.

Without details about how your gems were broken this can't be fixed.

PS: Don't send HTML email to lists, it sucks.

From Daniel.Berger at qwest.com  Tue Mar 31 14:31:13 2009
From: Daniel.Berger at qwest.com (Berger, Daniel)
Date: Tue, 31 Mar 2009 13:31:13 -0500
Subject: [Rubygems-developers] gem problem
In-Reply-To: <B9962927-4B74-4DE7-8D29-2F59AA098C8C@segment7.net>
References: <c429d15e0903310011r12b88155rbaf26ad8ece962d0@mail.gmail.com><8d
	961d900903310110t7cb1a254n6603eb5b851bce61@mail.gmail.com>
	<B9962927-4B74-4DE7-8D29-2F59AA098C8C@segment7.net>
Message-ID: <E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D4613@qtomaexmbm25.AD.QINTRA.COM>

 

> -----Original Message-----
> From: rubygems-developers-bounces at rubyforge.org 
> [mailto:rubygems-developers-bounces at rubyforge.org] On Behalf 
> Of Eric Hodel
> Sent: Tuesday, March 31, 2009 11:52 AM
> To: rubygems-developers at rubyforge.org
> Subject: Re: [Rubygems-developers] gem problem
> 
> On Mar 31, 2009, at 01:10, aslak hellesoy wrote:
> 
> > 2009/3/31 Dominic Sisneros <dsisnero at gmail.com>
> >> I did a gem cleanup and since then I have been getting the 
> following 
> >> error whenever I try to use a gem
> >
> > I had the same problem yesterday, when I upgraded all my gems. It 
> > turns out, this error occurs if you have one broken gem.
> > My solution: Add a puts statement inside 
> gem_path_searcher.rb to find 
> > out what gem is broken. Then uninstall it. (For me it was 
> the latest 
> > mojombo-grit).
> >
> > A better solution would be to patch Rubygems so it doesn't 
> choke just 
> > because you have a broken gem - or at least tell you which 
> one it is.
> 
> Without details about how your gems were broken this can't be fixed.

I did notice something peculiar:

"load error: C:/Documents and Settings/dominic e sisneros/.irbrc"

I've responded on ruby-talk already about the possibility of spaces and/or non-ascii characters causing a problem. Might be a red-herring, though.
 
> PS: Don't send HTML email to lists, it sucks.

Out of curiosity I dug around the mailing list admin interface a bit, and it looks like you can convert html to text automatically. In the administrative interface for the mailing list, click on the "Content Filtering" option. Near the bottom of your screen is an option to convert html to plain text.

Regards,

Dan

From drbrain at segment7.net  Tue Mar 31 16:51:02 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Tue, 31 Mar 2009 13:51:02 -0700
Subject: [Rubygems-developers] Latest and greatest instructions for
	setting up a public gem server?
In-Reply-To: <e3af97510903311045s1b0cc06qffb2062eefa53dfe@mail.gmail.com>
References: <e3af97510903311045s1b0cc06qffb2062eefa53dfe@mail.gmail.com>
Message-ID: <5795D810-2914-41BA-B8A6-4C9FBB839DD1@segment7.net>

On Mar 31, 2009, at 10:45, Chad Woolley wrote:

> Any suggestions?  Including example scripts, cron jobs, etc?

gem help generate_index

From drbrain at segment7.net  Tue Mar 31 23:10:19 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Tue, 31 Mar 2009 20:10:19 -0700
Subject: [Rubygems-developers] gem problem
In-Reply-To: <E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D4613@qtomaexmbm25.AD.QINTRA.COM>
References: <c429d15e0903310011r12b88155rbaf26ad8ece962d0@mail.gmail.com><8d
	961d900903310110t7cb1a254n6603eb5b851bce61@mail.gmail.com>
	<B9962927-4B74-4DE7-8D29-2F59AA098C8C@segment7.net>
	<E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D4613@qtomaexmbm25.AD.QINTRA.COM>
Message-ID: <56BB44F4-12A3-4AFC-BA6F-227DCBFD8F5B@segment7.net>

On Mar 31, 2009, at 11:31, Berger, Daniel wrote:
>> -----Original Message-----
>> From: rubygems-developers-bounces at rubyforge.org
>> [mailto:rubygems-developers-bounces at rubyforge.org] On Behalf
>> Of Eric Hodel
>> Sent: Tuesday, March 31, 2009 11:52 AM
>> To: rubygems-developers at rubyforge.org
>> Subject: Re: [Rubygems-developers] gem problem
>>
>> On Mar 31, 2009, at 01:10, aslak hellesoy wrote:
>>
>>> 2009/3/31 Dominic Sisneros <dsisnero at gmail.com>
>>>> I did a gem cleanup and since then I have been getting the
>> following
>>>> error whenever I try to use a gem
>>>
>>> I had the same problem yesterday, when I upgraded all my gems. It
>>> turns out, this error occurs if you have one broken gem.
>>> My solution: Add a puts statement inside
>> gem_path_searcher.rb to find
>>> out what gem is broken. Then uninstall it. (For me it was
>> the latest
>>> mojombo-grit).
>>>
>>> A better solution would be to patch Rubygems so it doesn't
>> choke just
>>> because you have a broken gem - or at least tell you which
>> one it is.
>>
>> Without details about how your gems were broken this can't be fixed.
>
> I did notice something peculiar:
>
> "load error: C:/Documents and Settings/dominic e sisneros/.irbrc"
>
> I've responded on ruby-talk already about the possibility of spaces  
> and/or non-ascii characters causing a problem. Might be a red- 
> herring, though.

It seems that there was a bogus github gem floating around, mojombo- 
grit.  It was adding directories to the file list...  I'm  
investigating it.