From thewoolleyman at gmail.com  Wed Apr  1 01:13:35 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Tue, 31 Mar 2009 22:13:35 -0700
Subject: [Rubygems-developers] gem problem
In-Reply-To: <56BB44F4-12A3-4AFC-BA6F-227DCBFD8F5B@segment7.net>
References: <c429d15e0903310011r12b88155rbaf26ad8ece962d0@mail.gmail.com> 
	<B9962927-4B74-4DE7-8D29-2F59AA098C8C@segment7.net>
	<E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D4613@qtomaexmbm25.AD.QINTRA.COM>
	<56BB44F4-12A3-4AFC-BA6F-227DCBFD8F5B@segment7.net>
Message-ID: <e3af97510903312213pa59b914lf210e7e27a4c511@mail.gmail.com>

On Tue, Mar 31, 2009 at 8:10 PM, Eric Hodel <drbrain at segment7.net> wrote:
> 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.

Hmm:  http://github.com/mojombo/grit/commit/4ac4acab7fd9c7fd4c0e0f4ff5794b0347baecde

What I'm wondering is - how easy would it be to do this maliciously
and with greater effect, if this minor snafu caused problems.

How's that circle of trust thing coming?

-- Chad

From djberg96 at gmail.com  Wed Apr  1 03:32:19 2009
From: djberg96 at gmail.com (Daniel Berger)
Date: Wed, 01 Apr 2009 01:32:19 -0600
Subject: [Rubygems-developers] gem problem
In-Reply-To: <e3af97510903312213pa59b914lf210e7e27a4c511@mail.gmail.com>
References: <c429d15e0903310011r12b88155rbaf26ad8ece962d0@mail.gmail.com>
	<B9962927-4B74-4DE7-8D29-2F59AA098C8C@segment7.net>	<E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D4613@qtomaexmbm25.AD.QINTRA.COM>	<56BB44F4-12A3-4AFC-BA6F-227DCBFD8F5B@segment7.net>
	<e3af97510903312213pa59b914lf210e7e27a4c511@mail.gmail.com>
Message-ID: <49D31883.7060506@gmail.com>

Chad Woolley wrote:
> On Tue, Mar 31, 2009 at 8:10 PM, Eric Hodel <drbrain at segment7.net> wrote:
>> 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.
> 
> Hmm:  http://github.com/mojombo/grit/commit/4ac4acab7fd9c7fd4c0e0f4ff5794b0347baecde
> 
> What I'm wondering is - how easy would it be to do this maliciously
> and with greater effect, if this minor snafu caused problems.
> 
> How's that circle of trust thing coming?

If it comes to it we'll start requiring gem signatures. :)

Dan


From ryand-ruby at zenspider.com  Wed Apr  1 04:03:12 2009
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Wed, 1 Apr 2009 01:03:12 -0700
Subject: [Rubygems-developers] gem problem
In-Reply-To: <e3af97510903312213pa59b914lf210e7e27a4c511@mail.gmail.com>
References: <c429d15e0903310011r12b88155rbaf26ad8ece962d0@mail.gmail.com>
	<B9962927-4B74-4DE7-8D29-2F59AA098C8C@segment7.net>
	<E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D4613@qtomaexmbm25.AD.QINTRA.COM>
	<56BB44F4-12A3-4AFC-BA6F-227DCBFD8F5B@segment7.net>
	<e3af97510903312213pa59b914lf210e7e27a4c511@mail.gmail.com>
Message-ID: <95660D89-CC95-4834-9967-9F24B46AF18E@zenspider.com>


On Mar 31, 2009, at 22:13 , Chad Woolley wrote:

> On Tue, Mar 31, 2009 at 8:10 PM, Eric Hodel <drbrain at segment7.net>  
> wrote:
>> 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.
>
> Hmm:  http://github.com/mojombo/grit/commit/4ac4acab7fd9c7fd4c0e0f4ff5794b0347baecde
>
> What I'm wondering is - how easy would it be to do this maliciously
> and with greater effect, if this minor snafu caused problems.

possibly pretty easily, I can't really comment on that... but not  
really with greater effect. There are benefits to having centralized  
services, and one of them is the ability to quickly deal with issues  
and limit their effect.



From jftucker at gmail.com  Wed Apr  1 06:33:36 2009
From: jftucker at gmail.com (James Tucker)
Date: Wed, 1 Apr 2009 11:33:36 +0100
Subject: [Rubygems-developers] gem problem
In-Reply-To: <e3af97510903312213pa59b914lf210e7e27a4c511@mail.gmail.com>
References: <c429d15e0903310011r12b88155rbaf26ad8ece962d0@mail.gmail.com>
	<B9962927-4B74-4DE7-8D29-2F59AA098C8C@segment7.net>
	<E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D4613@qtomaexmbm25.AD.QINTRA.COM>
	<56BB44F4-12A3-4AFC-BA6F-227DCBFD8F5B@segment7.net>
	<e3af97510903312213pa59b914lf210e7e27a4c511@mail.gmail.com>
Message-ID: <2176D717-8173-4E90-B0F7-8E1191D3160E@gmail.com>


On 1 Apr 2009, at 06:13, Chad Woolley wrote:

> On Tue, Mar 31, 2009 at 8:10 PM, Eric Hodel <drbrain at segment7.net>  
> wrote:
>> 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.
>
> Hmm:  http://github.com/mojombo/grit/commit/4ac4acab7fd9c7fd4c0e0f4ff5794b0347baecde
>
> What I'm wondering is - how easy would it be to do this maliciously
> and with greater effect, if this minor snafu caused problems.

Create a github user called ruby, now you can easily replace any of  
the ruby- projects with new counterparts from the github gem server,  
for a great many users.

1 of many

>
> How's that circle of trust thing coming?
>
> -- Chad
> _______________________________________________
> Rubygems-developers mailing list
> Rubygems-developers at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubygems-developers


From luislavena at gmail.com  Wed Apr  1 08:15:44 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Wed, 1 Apr 2009 09:15:44 -0300
Subject: [Rubygems-developers] gem problem
In-Reply-To: <2176D717-8173-4E90-B0F7-8E1191D3160E@gmail.com>
References: <c429d15e0903310011r12b88155rbaf26ad8ece962d0@mail.gmail.com>
	<B9962927-4B74-4DE7-8D29-2F59AA098C8C@segment7.net>
	<E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D4613@qtomaexmbm25.AD.QINTRA.COM>
	<56BB44F4-12A3-4AFC-BA6F-227DCBFD8F5B@segment7.net>
	<e3af97510903312213pa59b914lf210e7e27a4c511@mail.gmail.com>
	<2176D717-8173-4E90-B0F7-8E1191D3160E@gmail.com>
Message-ID: <71166b3b0904010515k40af4fbcn21f06e958e3506bb@mail.gmail.com>

On Wed, Apr 1, 2009 at 7:33 AM, James Tucker <jftucker at gmail.com> wrote:
>
> On 1 Apr 2009, at 06:13, Chad Woolley wrote:
>
>> On Tue, Mar 31, 2009 at 8:10 PM, Eric Hodel <drbrain at segment7.net> wrote:
>>>
>>> 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.
>>
>> Hmm:
>> ?http://github.com/mojombo/grit/commit/4ac4acab7fd9c7fd4c0e0f4ff5794b0347baecde
>>
>> What I'm wondering is - how easy would it be to do this maliciously
>> and with greater effect, if this minor snafu caused problems.
>
> Create a github user called ruby, now you can easily replace any of the
> ruby- projects with new counterparts from the github gem server, for a great
> many users.
>
> 1 of many
>

Well, that has already been blocked by GitHub already: ruby, net,
win32, and others I believe.

Anyhow, gems should be tested before making available to the indexer,
so that's something GitHub should be poked about.
-- 
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 aslak.hellesoy at gmail.com  Wed Apr  1 10:25:57 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Wed, 1 Apr 2009 16:25:57 +0200
Subject: [Rubygems-developers] gem problem
In-Reply-To: <49D31883.7060506@gmail.com>
References: <c429d15e0903310011r12b88155rbaf26ad8ece962d0@mail.gmail.com>
	<B9962927-4B74-4DE7-8D29-2F59AA098C8C@segment7.net>
	<E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D4613@qtomaexmbm25.AD.QINTRA.COM>
	<56BB44F4-12A3-4AFC-BA6F-227DCBFD8F5B@segment7.net>
	<e3af97510903312213pa59b914lf210e7e27a4c511@mail.gmail.com>
	<49D31883.7060506@gmail.com>
Message-ID: <8d961d900904010725s742522c1iaa7c3fd4d6b86a9@mail.gmail.com>

On Wed, Apr 1, 2009 at 9:32 AM, Daniel Berger <djberg96 at gmail.com> wrote:

> Chad Woolley wrote:
>
>> On Tue, Mar 31, 2009 at 8:10 PM, Eric Hodel <drbrain at segment7.net> wrote:
>>
>>> 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.
>>>
>>
>> Hmm:
>> http://github.com/mojombo/grit/commit/4ac4acab7fd9c7fd4c0e0f4ff5794b0347baecde
>>
>> What I'm wondering is - how easy would it be to do this maliciously
>> and with greater effect, if this minor snafu caused problems.
>>
>> How's that circle of trust thing coming?
>>
>
> If it comes to it we'll start requiring gem signatures. :)
>

Most other packaging systems use MD5 signatures by default (apt-get, pear,
maven etc)
Why isn't Rubygems doing it?

Aslak


>
> 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/20090401/9b37979f/attachment-0001.html>

From luislavena at gmail.com  Wed Apr  1 11:59:27 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Wed, 1 Apr 2009 12:59:27 -0300
Subject: [Rubygems-developers] gem problem
In-Reply-To: <8d961d900904010725s742522c1iaa7c3fd4d6b86a9@mail.gmail.com>
References: <c429d15e0903310011r12b88155rbaf26ad8ece962d0@mail.gmail.com>
	<B9962927-4B74-4DE7-8D29-2F59AA098C8C@segment7.net>
	<E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D4613@qtomaexmbm25.AD.QINTRA.COM>
	<56BB44F4-12A3-4AFC-BA6F-227DCBFD8F5B@segment7.net>
	<e3af97510903312213pa59b914lf210e7e27a4c511@mail.gmail.com>
	<49D31883.7060506@gmail.com>
	<8d961d900904010725s742522c1iaa7c3fd4d6b86a9@mail.gmail.com>
Message-ID: <71166b3b0904010859s49d6d19xf4378e5245732b55@mail.gmail.com>

2009/4/1 aslak hellesoy <aslak.hellesoy at gmail.com>:
>
>
> On Wed, Apr 1, 2009 at 9:32 AM, Daniel Berger <djberg96 at gmail.com> wrote:
>>
>> Chad Woolley wrote:
>>>
>>> On Tue, Mar 31, 2009 at 8:10 PM, Eric Hodel <drbrain at segment7.net> wrote:
>>>>
>>>> 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.
>>>
>>> Hmm:
>>> ?http://github.com/mojombo/grit/commit/4ac4acab7fd9c7fd4c0e0f4ff5794b0347baecde
>>>
>>> What I'm wondering is - how easy would it be to do this maliciously
>>> and with greater effect, if this minor snafu caused problems.
>>>
>>> How's that circle of trust thing coming?
>>
>> If it comes to it we'll start requiring gem signatures. :)
>
> Most other packaging systems use MD5 signatures by default (apt-get, pear,
> maven etc)
> Why isn't Rubygems doing it?
>

You're talking about packaged files integrity while I think Daniel and
Ryan are talking about package signatures:

Luis at KEORE (D:\Users\Luis)
$ gem help install

    -P, --trust-policy POLICY        Specify gem trust policy


gem install mongrel -P HighSecurity

==

But first you need to install the certificates.

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

From drbrain at segment7.net  Wed Apr  1 16:39:37 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Wed, 1 Apr 2009 13:39:37 -0700
Subject: [Rubygems-developers] gem problem
In-Reply-To: <8d961d900904010725s742522c1iaa7c3fd4d6b86a9@mail.gmail.com>
References: <c429d15e0903310011r12b88155rbaf26ad8ece962d0@mail.gmail.com>
	<B9962927-4B74-4DE7-8D29-2F59AA098C8C@segment7.net>
	<E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D4613@qtomaexmbm25.AD.QINTRA.COM>
	<56BB44F4-12A3-4AFC-BA6F-227DCBFD8F5B@segment7.net>
	<e3af97510903312213pa59b914lf210e7e27a4c511@mail.gmail.com>
	<49D31883.7060506@gmail.com>
	<8d961d900904010725s742522c1iaa7c3fd4d6b86a9@mail.gmail.com>
Message-ID: <A76EE28A-9A27-4F17-9732-788595EB1F1C@segment7.net>

On Apr 1, 2009, at 07:25, aslak hellesoy wrote:

> Most other packaging systems use MD5 signatures by default (apt-get,  
> pear, maven etc)
> Why isn't Rubygems doing it?

RubyGems provides it via signatures, if you want your package  
verifiable, add a signature.

From drbrain at segment7.net  Wed Apr  1 16:50:00 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Wed, 1 Apr 2009 13:50:00 -0700
Subject: [Rubygems-developers] gem problem
In-Reply-To: <e3af97510903312213pa59b914lf210e7e27a4c511@mail.gmail.com>
References: <c429d15e0903310011r12b88155rbaf26ad8ece962d0@mail.gmail.com>
	<B9962927-4B74-4DE7-8D29-2F59AA098C8C@segment7.net>
	<E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D4613@qtomaexmbm25.AD.QINTRA.COM>
	<56BB44F4-12A3-4AFC-BA6F-227DCBFD8F5B@segment7.net>
	<e3af97510903312213pa59b914lf210e7e27a4c511@mail.gmail.com>
Message-ID: <0ED45914-7DDF-476D-9780-65F178F2B4F7@segment7.net>


On Mar 31, 2009, at 22:13, Chad Woolley wrote:

> On Tue, Mar 31, 2009 at 8:10 PM, Eric Hodel <drbrain at segment7.net>  
> wrote:
>> 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.
>
> Hmm:  http://github.com/mojombo/grit/commit/4ac4acab7fd9c7fd4c0e0f4ff5794b0347baecde
>
> What I'm wondering is - how easy would it be to do this maliciously
> and with greater effect, if this minor snafu caused problems.

No matter how much I try to idiot proof things...

One of the bigger problems in packaging gems is people who use glob or  
regexp to find files instead of a manifest file.

> How's that circle of trust thing coming?

From Daniel.Berger at qwest.com  Wed Apr  1 17:42:28 2009
From: Daniel.Berger at qwest.com (Berger, Daniel)
Date: Wed, 1 Apr 2009 16:42:28 -0500
Subject: [Rubygems-developers] gem problem
In-Reply-To: <0ED45914-7DDF-476D-9780-65F178F2B4F7@segment7.net>
References: <c429d15e0903310011r12b88155rbaf26ad8ece962d0@mail.gmail.com><B9
	962927-4B74-4DE7-8D29-2F59AA098C8C@segment7.net><E1331D75B8E8DA46B15CDEA9BC
	46FA270D7A4D4613@qtomaexmbm25.AD.QINTRA.COM><56BB44F4-12A3-4AFC-BA6F-227DCB
	FD8F5B@segment7.net><e3af97510903312213pa59b914lf210e7e27a4c511@mail.gmail.com>
	<0ED45914-7DDF-476D-9780-65F178F2B4F7@segment7.net>
Message-ID: <E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D463D@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: Wednesday, April 01, 2009 2:50 PM
> To: rubygems-developers at rubyforge.org
> Subject: Re: [Rubygems-developers] gem problem
> 
> 
> On Mar 31, 2009, at 22:13, Chad Woolley wrote:
> 
> > On Tue, Mar 31, 2009 at 8:10 PM, Eric Hodel <drbrain at segment7.net>
> > wrote:
> >> 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.
> >
> > Hmm:  
> > 
> http://github.com/mojombo/grit/commit/4ac4acab7fd9c7fd4c0e0f4ff5794b03
> > 47baecde
> >
> > What I'm wondering is - how easy would it be to do this maliciously 
> > and with greater effect, if this minor snafu caused problems.
> 
> No matter how much I try to idiot proof things...
> 
> One of the bigger problems in packaging gems is people who 
> use glob or regexp to find files instead of a manifest file.

We could consider mandating that any files in the gem must also exist in a manifest file and/or capping the file limit. Just a thought.

Dan

From drbrain at segment7.net  Wed Apr  1 18:26:21 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Wed, 1 Apr 2009 15:26:21 -0700
Subject: [Rubygems-developers] gem problem
In-Reply-To: <E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D463D@qtomaexmbm25.AD.QINTRA.COM>
References: <c429d15e0903310011r12b88155rbaf26ad8ece962d0@mail.gmail.com><B9
	962927-4B74-4DE7-8D29-2F59AA098C8C@segment7.net><E1331D75B8E8DA46B15CDEA9BC
	46FA270D7A4D4613@qtomaexmbm25.AD.QINTRA.COM><56BB44F4-12A3-4AFC-BA6F-227DCB
	FD8F5B@segment7.net><e3af97510903312213pa59b914lf210e7e27a4c511@mail.gmail.com>
	<0ED45914-7DDF-476D-9780-65F178F2B4F7@segment7.net>
	<E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D463D@qtomaexmbm25.AD.QINTRA.COM>
Message-ID: <F5437088-5094-424C-A9FC-8A1FD6CB2C3E@segment7.net>

On Apr 1, 2009, at 14:42, Berger, Daniel wrote:
>> No matter how much I try to idiot proof things...
>>
>> One of the bigger problems in packaging gems is people who
>> use glob or regexp to find files instead of a manifest file.
>
> We could consider mandating that any files in the gem must also  
> exist in a manifest file and/or capping the file limit. Just a  
> thought.

It wouldn't help, people would generate their manifest file from a  
glob or regexp and not double-check, just like now.

From luislavena at gmail.com  Wed Apr  1 19:10:04 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Wed, 1 Apr 2009 20:10:04 -0300
Subject: [Rubygems-developers] gem problem
In-Reply-To: <F5437088-5094-424C-A9FC-8A1FD6CB2C3E@segment7.net>
References: <c429d15e0903310011r12b88155rbaf26ad8ece962d0@mail.gmail.com>
	<e3af97510903312213pa59b914lf210e7e27a4c511@mail.gmail.com>
	<0ED45914-7DDF-476D-9780-65F178F2B4F7@segment7.net>
	<E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D463D@qtomaexmbm25.AD.QINTRA.COM>
	<F5437088-5094-424C-A9FC-8A1FD6CB2C3E@segment7.net>
Message-ID: <71166b3b0904011610r725bf7d5s145d45f3845fce89@mail.gmail.com>

On Wed, Apr 1, 2009 at 7:26 PM, Eric Hodel <drbrain at segment7.net> wrote:
> On Apr 1, 2009, at 14:42, Berger, Daniel wrote:
>>>
>>> No matter how much I try to idiot proof things...
>>>
>>> One of the bigger problems in packaging gems is people who
>>> use glob or regexp to find files instead of a manifest file.
>>
>> We could consider mandating that any files in the gem must also exist in a
>> manifest file and/or capping the file limit. Just a thought.
>
> It wouldn't help, people would generate their manifest file from a glob or
> regexp and not double-check, just like now.

That is a human problem, not of the technology. Even on manifest files
people include files they have in their local copies that are not
committed into the repository.

I've been using glob without any issue, and also generating YAML
gemspec files, zero glitches.

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

From noreply at rubyforge.org  Wed Apr  1 19:25:04 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Wed,  1 Apr 2009 19:25:04 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25073 ] method
	output_query_results in query_command.rb should guarantee
	some order of platform
Message-ID: <20090401232504.92D93185810A@rubyforge.org>

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

>Category: `gem` commands (other)
>Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Jirapong Nanta (jirapong)
>Assigned to: Eric Hodel (drbrain)
Summary: method output_query_results in query_command.rb should guarantee some order of platform 

Initial Comment:
in following line: 

        if non_ruby then
          if platforms.length == 1 then
            title = platforms.values.length == 1 ? 'Platform' : 'Platforms'
            entry << "    #{title}: #{platforms.values.sort.join ', '}\n"
          else
            entry << "    Platforms:\n"
            platforms.each do |version, pls|
              label = "        #{version}: "
              data = format_text pls.sort.join(', '), 68, label.length
              data[0, label.length] = label
              entry << data << "\n"
            end
          end
        end

I think platforms.each should be platforms.sort.each to guarantee sort order.

I found difference in default hash.each between MRI and IronRuby, which this fix should allow RubyGems to work in multiple ruby vm.

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

>Comment By: Eric Hodel (drbrain)
Date: 2009-04-01 16:25

Message:
I don't see why this code doesn't work in multiple implementations, please explain.

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

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

From drbrain at segment7.net  Wed Apr  1 20:08:20 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Wed, 1 Apr 2009 17:08:20 -0700
Subject: [Rubygems-developers] Bugs now appearing here
Message-ID: <46BF0FD5-9342-4ABB-AAD5-7D6DE890FC95@segment7.net>

Yay!

From noreply at rubyforge.org  Wed Apr  1 22:03:48 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Wed,  1 Apr 2009 22:03:48 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-24958 ] Install replaces ruby
	interpreter with gem executable
Message-ID: <20090402020348.C989F1858113@rubyforge.org>

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

Category: RubyGems installer (setup.rb)
Group: v1.3.x
Status: Open
Resolution: Accepted
Priority: 3
Submitted By: Michael Soulier (msoulier)
Assigned to: Eric Hodel (drbrain)
Summary: Install replaces ruby interpreter with gem executable

Initial Comment:
I'm on a system where I only have write access to my own home directory. So, I built ruby with --prefix=$HOME/ruby. It installs and works fine.

Then, I installed rubygems via

ruby setup.rb

and...

RubyGems installed the following executables:
        /home/msoulier/ruby/bin/ruby

What? That's my ruby interpreter!

No surprise, but gem, irb, and nothing else work now.

msoulier at anton:~$ gem
/home/msoulier/ruby/bin/gem: line 8: require: command not found
/home/msoulier/ruby/bin/gem: line 9: require: command not found
/home/msoulier/ruby/bin/gem: line 10: require: command not found
/home/msoulier/ruby/bin/gem: line 12: required_version: command not found
/home/msoulier/ruby/bin/gem: line 14: unless: command not found
/home/msoulier/ruby/bin/gem: line 15: abort: command not found
/home/msoulier/ruby/bin/gem: line 16: end: command not found
/home/msoulier/ruby/bin/gem: line 21: syntax error near unexpected token `('
/home/msoulier/ruby/bin/gem: line 21: `args = !ARGV.include?("--") ? ARGV.clone : ARGV[0...ARGV.index("--")]'

msoulier at anton:~$ cat $HOME/ruby/bin/ruby
#!/home/msoulier/ruby/bin/ruby
#--
# Copyright 2006 by Chad Fowler, Rich Kilmer, Jim Weirich and others.
# All rights reserved.
# See LICENSE.txt for permissions.
#++

require 'rubygems'
require 'rubygems/gem_runner'
require 'rubygems/exceptions'

required_version = Gem::Requirement.new "> 1.8.3"

unless required_version.satisfied_by? Gem.ruby_version then
  abort "Expected Ruby Version #{required_version}, was #{Gem.ruby_version}"
end

# We need to preserve the original ARGV to use for passing gem options
# to source gems.  If there is a -- in the line, strip all options after
# it...its for the source building process.
args = !ARGV.include?("--") ? ARGV.clone : ARGV[0...ARGV.index("--")]

begin
  Gem::GemRunner.new.run args
rescue Gem::SystemExitException => e
  exit e.exit_code
end

I think there's a problem here. 

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

>Comment By: Michael Soulier (msoulier)
Date: 2009-04-01 22:03

Message:
I'll need to rebuild to reproduce. 

I won't be able to run that command since the ruby
interpreter is clobbered. I'll find the file. 

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

Comment By: Eric Hodel (drbrain)
Date: 2009-03-31 22:50

Message:
I've checked in a patch which should help diagnose the problem.  It appears that Gem.default_exec_format can end up without a %s in it, but I'm not sure how.

Can you send me your rbconfig.rb from 1.9?

  gem which rbconfig

Will give you the path.

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

Comment By: Michael Soulier (msoulier)
Date: 2009-03-28 09:24

Message:
I repeated the install with ruby 1.8.7 out of SVN, and it
worked fine this time. 

Could it be a problem with the changes in ruby 1.9.1?

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

Comment By: Michael Soulier (msoulier)
Date: 2009-03-27 22:14

Message:
FWIW

msoulier at anton:~/temp$ md5sum rubygems-1.3.1.tgz 
a04ee6f6897077c5b75f5fd1e134c5a9  rubygems-1.3.1.tgz


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

Comment By: Michael Soulier (msoulier)
Date: 2009-03-27 22:13

Message:
Yes, I still have it.

msoulier at anton:~$ ls temp/rubygems-1.3.1/bin
gem  update_rubygems

I went to rubygems.org and clicked download, and grabbed the
.tgz file. 

I can't seem to reach that site right now.

msoulier at anton:~$ hostx rubygems.org
rubygems.org            A       207.114.85.50

My browser is timing out on it. 

I cd'd into the unpacked tarball directory and ran ruby on
setup.rb from there, yes. 

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

Comment By: Eric Hodel (drbrain)
Date: 2009-03-27 19:25

Message:
Do you still have the RubyGems you installed with unpacked?

Can I see an ls of the bin directory?

What URL did you get RubyGems from?

What path did you run setup.rb from?  The unpacked RubyGems tarball dir?

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

Comment By: Michael Soulier (msoulier)
Date: 2009-03-27 18:32

Message:
Oh, and I installed ruby-1.9.1-p0.tar.gz from the
ruby-lang.org site. 

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

Comment By: Michael Soulier (msoulier)
Date: 2009-03-27 18:27

Message:
FWIW this is a Gentoo Linux system. ruby is not already
installed elsewhere. 

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

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

From luislavena at gmail.com  Wed Apr  1 23:13:14 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Thu, 2 Apr 2009 00:13:14 -0300
Subject: [Rubygems-developers] Bugs now appearing here
In-Reply-To: <46BF0FD5-9342-4ABB-AAD5-7D6DE890FC95@segment7.net>
References: <46BF0FD5-9342-4ABB-AAD5-7D6DE890FC95@segment7.net>
Message-ID: <71166b3b0904012013x7e4439d3rc0bd1d39e82489d9@mail.gmail.com>

2009/4/1 Eric Hodel <drbrain at segment7.net>:
> Yay!

What about here?

http://pastie.org/434553
-- 
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 devnull+rubygems-ci at pivotallabs.com  Thu Apr  2 00:20:01 2009
From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com)
Date: Thu, 2 Apr 2009 04:20:01 +0000
Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2125 failed
Message-ID: <49d43cf177984_3a7a..fdbe5137e147@ci.pivotallabs.com.tmail>

The build failed.

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


TEST FAILURES AND ERRORS
-----------------------
Name: test_self_find_files(TestGem)
Type: Failure
Message: Expected ["/home/pivotal/.cruise/projects/RubyGems/work/test/foo/discover.rb",
 "/tmp/test_rubygems_15698/gemhome/gems/foo-1/lib/foo/discover.rb",
 "/tmp/test_rubygems_15698/gemhome/gems/foo-2/lib/foo/discover.rb"], not ["/tmp/test_rubygems_15698/gemhome/gems/foo-1/lib/foo/discover.rb",
 "/tmp/test_rubygems_15698/gemhome/gems/foo-2/lib/foo/discover.rb"].

./test/test_gem.rb:302


Name: test_run_interrupt(TestGemCommandManager)
Type: Failure
Message: Expected "ERROR:  Interrupted\n", not "ERROR:  While executing gem ... (RuntimeError)\n    Unknown command interrupt\n".

./test/test_gem_command_manager.rb:24




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

From devnull+rubygems-ci at pivotallabs.com  Thu Apr  2 00:25:02 2009
From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com)
Date: Thu, 2 Apr 2009 04:25:02 +0000
Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2125.1 failed
Message-ID: <49d43e1e33b6f_3a7a..fdbe5137e28d@ci.pivotallabs.com.tmail>

The build failed.

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


TEST FAILURES AND ERRORS
-----------------------
Name: test_self_find_files(TestGem)
Type: Failure
Message: Expected ["/home/pivotal/.cruise/projects/RubyGems/work/test/foo/discover.rb",
 "/tmp/test_rubygems_15980/gemhome/gems/foo-1/lib/foo/discover.rb",
 "/tmp/test_rubygems_15980/gemhome/gems/foo-2/lib/foo/discover.rb"], not ["/tmp/test_rubygems_15980/gemhome/gems/foo-1/lib/foo/discover.rb",
 "/tmp/test_rubygems_15980/gemhome/gems/foo-2/lib/foo/discover.rb"].

./test/test_gem.rb:302


Name: test_run_interrupt(TestGemCommandManager)
Type: Failure
Message: Expected "ERROR:  Interrupted\n", not "ERROR:  While executing gem ... (RuntimeError)\n    Unknown command interrupt\n".

./test/test_gem_command_manager.rb:24




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

From devnull+rubygems-ci at pivotallabs.com  Thu Apr  2 00:54:51 2009
From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com)
Date: Thu, 2 Apr 2009 04:54:51 +0000
Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2125.2 failed
Message-ID: <49d4451b5fad6_426a..fdbde1b821c@ci.pivotallabs.com.tmail>

The build failed.

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


TEST FAILURES AND ERRORS
-----------------------
Name: test_self_find_files(TestGem)
Type: Failure
Message: Expected ["/home/pivotal/.cruise/projects/RubyGems/work/test/foo/discover.rb",
 "/tmp/test_rubygems_17100/gemhome/gems/foo-1/lib/foo/discover.rb",
 "/tmp/test_rubygems_17100/gemhome/gems/foo-2/lib/foo/discover.rb"], not ["/tmp/test_rubygems_17100/gemhome/gems/foo-1/lib/foo/discover.rb",
 "/tmp/test_rubygems_17100/gemhome/gems/foo-2/lib/foo/discover.rb"].

./test/test_gem.rb:302


Name: test_run_interrupt(TestGemCommandManager)
Type: Failure
Message: Expected "ERROR:  Interrupted\n", not "ERROR:  While executing gem ... (RuntimeError)\n    Unknown command interrupt\n".

./test/test_gem_command_manager.rb:24




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

From devnull+rubygems-ci at pivotallabs.com  Thu Apr  2 01:07:46 2009
From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com)
Date: Thu, 2 Apr 2009 05:07:46 +0000
Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2125.4 failed
Message-ID: <49d448226fc0_426a..fdbde1b823b7@ci.pivotallabs.com.tmail>

The build failed.

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


TEST FAILURES AND ERRORS
-----------------------
Name: test_self_find_files(TestGem)
Type: Failure
Message: Expected ["/home/pivotal/.cruise/projects/RubyGems/work/test/foo/discover.rb",
 "/tmp/test_rubygems_17701/gemhome/gems/foo-1/lib/foo/discover.rb",
 "/tmp/test_rubygems_17701/gemhome/gems/foo-2/lib/foo/discover.rb"], not ["/tmp/test_rubygems_17701/gemhome/gems/foo-1/lib/foo/discover.rb",
 "/tmp/test_rubygems_17701/gemhome/gems/foo-2/lib/foo/discover.rb"].

./test/test_gem.rb:302


Name: test_run_interrupt(TestGemCommandManager)
Type: Failure
Message: Expected "ERROR:  Interrupted\n", not "ERROR:  While executing gem ... (RuntimeError)\n    Unknown command interrupt\n".

./test/test_gem_command_manager.rb:24




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

From devnull+rubygems-ci at pivotallabs.com  Thu Apr  2 01:09:27 2009
From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com)
Date: Thu, 2 Apr 2009 05:09:27 +0000
Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2125.5 failed
Message-ID: <49d4488792ee6_426a..fdbde1b82494@ci.pivotallabs.com.tmail>

The build failed.

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


TEST FAILURES AND ERRORS
-----------------------
Name: test_self_find_files(TestGem)
Type: Failure
Message: Expected ["/home/pivotal/.cruise/projects/RubyGems/work/test/foo/discover.rb",
 "/tmp/test_rubygems_17926/gemhome/gems/foo-1/lib/foo/discover.rb",
 "/tmp/test_rubygems_17926/gemhome/gems/foo-2/lib/foo/discover.rb"], not ["/tmp/test_rubygems_17926/gemhome/gems/foo-1/lib/foo/discover.rb",
 "/tmp/test_rubygems_17926/gemhome/gems/foo-2/lib/foo/discover.rb"].

./test/test_gem.rb:302


Name: test_run_interrupt(TestGemCommandManager)
Type: Failure
Message: Expected "ERROR:  Interrupted\n", not "ERROR:  While executing gem ... (RuntimeError)\n    Unknown command interrupt\n".

./test/test_gem_command_manager.rb:24




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

From devnull+rubygems-ci at pivotallabs.com  Thu Apr  2 00:59:20 2009
From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com)
Date: Thu, 2 Apr 2009 04:59:20 +0000
Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2125.3 failed
Message-ID: <49d446287efa9_426a..fdbde1b822e3@ci.pivotallabs.com.tmail>

The build failed.

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


TEST FAILURES AND ERRORS
-----------------------
Name: test_self_find_files(TestGem)
Type: Failure
Message: Expected ["/home/pivotal/.cruise/projects/RubyGems/work/test/foo/discover.rb",
 "/tmp/test_rubygems_17390/gemhome/gems/foo-1/lib/foo/discover.rb",
 "/tmp/test_rubygems_17390/gemhome/gems/foo-2/lib/foo/discover.rb"], not ["/tmp/test_rubygems_17390/gemhome/gems/foo-1/lib/foo/discover.rb",
 "/tmp/test_rubygems_17390/gemhome/gems/foo-2/lib/foo/discover.rb"].

./test/test_gem.rb:302


Name: test_run_interrupt(TestGemCommandManager)
Type: Failure
Message: Expected "ERROR:  Interrupted\n", not "ERROR:  While executing gem ... (RuntimeError)\n    Unknown command interrupt\n".

./test/test_gem_command_manager.rb:24




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

From thewoolleyman at gmail.com  Thu Apr  2 01:09:24 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Wed, 1 Apr 2009 22:09:24 -0700
Subject: [Rubygems-developers] CI builds now appearing here
Message-ID: <e3af97510904012209i72791beyd315ea25a4e7518e@mail.gmail.com>

Yay!

http://ci.pivotallabs.com:3333/builds/RubyGems

http://ci.pivotallabs.com/

From devnull+rubygems-ci at pivotallabs.com  Thu Apr  2 01:14:29 2009
From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com)
Date: Thu, 2 Apr 2009 05:14:29 +0000
Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2126 fixed
Message-ID: <49d449b563f4a_426a..fdbde1b82542@ci.pivotallabs.com.tmail>

The build has been fixed.

CHANGES
-------
New revision 2126 detected
Revision 2126 committed by drbrain on 2009-04-02 05:11:48
test_units task needs to include test
  M /trunk/Rakefile



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

From drbrain at segment7.net  Thu Apr  2 02:39:37 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Wed, 1 Apr 2009 23:39:37 -0700
Subject: [Rubygems-developers] Bugs now appearing here
In-Reply-To: <71166b3b0904012013x7e4439d3rc0bd1d39e82489d9@mail.gmail.com>
References: <46BF0FD5-9342-4ABB-AAD5-7D6DE890FC95@segment7.net>
	<71166b3b0904012013x7e4439d3rc0bd1d39e82489d9@mail.gmail.com>
Message-ID: <12390FFA-BE67-4AF5-8C69-80AC064A0258@segment7.net>

On Apr 1, 2009, at 20:13, Luis Lavena wrote:
> 2009/4/1 Eric Hodel <drbrain at segment7.net>:
>> Yay!
>
> What about here?
>
> http://pastie.org/434553

Should be fixed by 2126, I the test task needed to include the test  
directory.

From luislavena at gmail.com  Thu Apr  2 10:32:19 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Thu, 2 Apr 2009 11:32:19 -0300
Subject: [Rubygems-developers] Revision 2126 on Windows - Failures
Message-ID: <71166b3b0904020732r73e512f9h3d1d7a2c95d806c1@mail.gmail.com>

Hey Guys,

Remaining failures on Windows:

## mingw32

/test/test_gem_version.rb:128: warning: instance variable @v1_4 not initialized
./test/test_gem_version.rb:132: warning: instance variable @v1_4 not initialized
.............................................
Finished in 171.531000 seconds.

  1) Failure:
test_self_find_files(TestGem) [./test/test_gem.rb:302]:
Expected ["D:/Users/Luis/projects/oss/rubygems/trunk/test/foo/discover.rb",
 "D:/Temp/test_rubygems_508/gemhome/gems/foo-1/lib/foo/discover.rb",
 "D:/Temp/test_rubygems_508/gemhome/gems/foo-2/lib/foo/discover.rb"],
not ["D:/Temp/test_rubygems_508/gemhome/gems/foo-1/lib/foo/discover.rb",
 "D:/Temp/test_rubygems_508/gemhome/gems/foo-2/lib/foo/discover.rb",
 "D:/Users/Luis/projects/oss/rubygems/trunk/test/foo/discover.rb"].

## mswin32

/test/test_gem_version.rb:128: warning: instance variable
@v1_4 not initialized
./test/test_gem_version.rb:132: warning: instance variable @v1_4 not initialized
..................................
Finished in 188.297000 seconds.

  1) Failure:
test_self_find_files(TestGem) [./test/test_gem.rb:302]:
Expected ["D:/Users/Luis/projects/oss/rubygems/trunk/test/foo/discover.rb",
 "D:/Temp/test_rubygems_1540/gemhome/gems/foo-1/lib/foo/discover.rb",
 "D:/Temp/test_rubygems_1540/gemhome/gems/foo-2/lib/foo/discover.rb"],
not ["D:/Temp/test_rubygems_1540/gemhome/gems/foo-1/lib/foo/discover.rb",
 "D:/Temp/test_rubygems_1540/gemhome/gems/foo-2/lib/foo/discover.rb",
 "D:/Users/Luis/projects/oss/rubygems/trunk/test/foo/discover.rb"].

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

From noreply at rubyforge.org  Thu Apr  2 09:23:18 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu,  2 Apr 2009 09:23:18 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-24958 ] Install replaces ruby
	interpreter with gem executable
Message-ID: <20090402132318.7D3C318580F9@rubyforge.org>

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

Category: RubyGems installer (setup.rb)
Group: v1.3.x
Status: Open
Resolution: Accepted
Priority: 3
Submitted By: Michael Soulier (msoulier)
Assigned to: Eric Hodel (drbrain)
Summary: Install replaces ruby interpreter with gem executable

Initial Comment:
I'm on a system where I only have write access to my own home directory. So, I built ruby with --prefix=$HOME/ruby. It installs and works fine.

Then, I installed rubygems via

ruby setup.rb

and...

RubyGems installed the following executables:
        /home/msoulier/ruby/bin/ruby

What? That's my ruby interpreter!

No surprise, but gem, irb, and nothing else work now.

msoulier at anton:~$ gem
/home/msoulier/ruby/bin/gem: line 8: require: command not found
/home/msoulier/ruby/bin/gem: line 9: require: command not found
/home/msoulier/ruby/bin/gem: line 10: require: command not found
/home/msoulier/ruby/bin/gem: line 12: required_version: command not found
/home/msoulier/ruby/bin/gem: line 14: unless: command not found
/home/msoulier/ruby/bin/gem: line 15: abort: command not found
/home/msoulier/ruby/bin/gem: line 16: end: command not found
/home/msoulier/ruby/bin/gem: line 21: syntax error near unexpected token `('
/home/msoulier/ruby/bin/gem: line 21: `args = !ARGV.include?("--") ? ARGV.clone : ARGV[0...ARGV.index("--")]'

msoulier at anton:~$ cat $HOME/ruby/bin/ruby
#!/home/msoulier/ruby/bin/ruby
#--
# Copyright 2006 by Chad Fowler, Rich Kilmer, Jim Weirich and others.
# All rights reserved.
# See LICENSE.txt for permissions.
#++

require 'rubygems'
require 'rubygems/gem_runner'
require 'rubygems/exceptions'

required_version = Gem::Requirement.new "> 1.8.3"

unless required_version.satisfied_by? Gem.ruby_version then
  abort "Expected Ruby Version #{required_version}, was #{Gem.ruby_version}"
end

# We need to preserve the original ARGV to use for passing gem options
# to source gems.  If there is a -- in the line, strip all options after
# it...its for the source building process.
args = !ARGV.include?("--") ? ARGV.clone : ARGV[0...ARGV.index("--")]

begin
  Gem::GemRunner.new.run args
rescue Gem::SystemExitException => e
  exit e.exit_code
end

I think there's a problem here. 

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

>Comment By: Michael Soulier (msoulier)
Date: 2009-04-02 09:23

Message:
Here you go. 

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

Comment By: Michael Soulier (msoulier)
Date: 2009-04-01 22:03

Message:
I'll need to rebuild to reproduce. 

I won't be able to run that command since the ruby
interpreter is clobbered. I'll find the file. 

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

Comment By: Eric Hodel (drbrain)
Date: 2009-03-31 22:50

Message:
I've checked in a patch which should help diagnose the problem.  It appears that Gem.default_exec_format can end up without a %s in it, but I'm not sure how.

Can you send me your rbconfig.rb from 1.9?

  gem which rbconfig

Will give you the path.

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

Comment By: Michael Soulier (msoulier)
Date: 2009-03-28 09:24

Message:
I repeated the install with ruby 1.8.7 out of SVN, and it
worked fine this time. 

Could it be a problem with the changes in ruby 1.9.1?

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

Comment By: Michael Soulier (msoulier)
Date: 2009-03-27 22:14

Message:
FWIW

msoulier at anton:~/temp$ md5sum rubygems-1.3.1.tgz 
a04ee6f6897077c5b75f5fd1e134c5a9  rubygems-1.3.1.tgz


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

Comment By: Michael Soulier (msoulier)
Date: 2009-03-27 22:13

Message:
Yes, I still have it.

msoulier at anton:~$ ls temp/rubygems-1.3.1/bin
gem  update_rubygems

I went to rubygems.org and clicked download, and grabbed the
.tgz file. 

I can't seem to reach that site right now.

msoulier at anton:~$ hostx rubygems.org
rubygems.org            A       207.114.85.50

My browser is timing out on it. 

I cd'd into the unpacked tarball directory and ran ruby on
setup.rb from there, yes. 

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

Comment By: Eric Hodel (drbrain)
Date: 2009-03-27 19:25

Message:
Do you still have the RubyGems you installed with unpacked?

Can I see an ls of the bin directory?

What URL did you get RubyGems from?

What path did you run setup.rb from?  The unpacked RubyGems tarball dir?

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

Comment By: Michael Soulier (msoulier)
Date: 2009-03-27 18:32

Message:
Oh, and I installed ruby-1.9.1-p0.tar.gz from the
ruby-lang.org site. 

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

Comment By: Michael Soulier (msoulier)
Date: 2009-03-27 18:27

Message:
FWIW this is a Gentoo Linux system. ruby is not already
installed elsewhere. 

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

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

From noreply at rubyforge.org  Thu Apr  2 19:15:09 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu,  2 Apr 2009 19:15:09 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-24958 ] Install replaces ruby
	interpreter with gem executable
Message-ID: <20090402231509.1BEA41978589@rubyforge.org>

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

Category: RubyGems installer (setup.rb)
Group: v1.3.x
Status: Open
Resolution: Accepted
Priority: 3
Submitted By: Michael Soulier (msoulier)
Assigned to: Eric Hodel (drbrain)
Summary: Install replaces ruby interpreter with gem executable

Initial Comment:
I'm on a system where I only have write access to my own home directory. So, I built ruby with --prefix=$HOME/ruby. It installs and works fine.

Then, I installed rubygems via

ruby setup.rb

and...

RubyGems installed the following executables:
        /home/msoulier/ruby/bin/ruby

What? That's my ruby interpreter!

No surprise, but gem, irb, and nothing else work now.

msoulier at anton:~$ gem
/home/msoulier/ruby/bin/gem: line 8: require: command not found
/home/msoulier/ruby/bin/gem: line 9: require: command not found
/home/msoulier/ruby/bin/gem: line 10: require: command not found
/home/msoulier/ruby/bin/gem: line 12: required_version: command not found
/home/msoulier/ruby/bin/gem: line 14: unless: command not found
/home/msoulier/ruby/bin/gem: line 15: abort: command not found
/home/msoulier/ruby/bin/gem: line 16: end: command not found
/home/msoulier/ruby/bin/gem: line 21: syntax error near unexpected token `('
/home/msoulier/ruby/bin/gem: line 21: `args = !ARGV.include?("--") ? ARGV.clone : ARGV[0...ARGV.index("--")]'

msoulier at anton:~$ cat $HOME/ruby/bin/ruby
#!/home/msoulier/ruby/bin/ruby
#--
# Copyright 2006 by Chad Fowler, Rich Kilmer, Jim Weirich and others.
# All rights reserved.
# See LICENSE.txt for permissions.
#++

require 'rubygems'
require 'rubygems/gem_runner'
require 'rubygems/exceptions'

required_version = Gem::Requirement.new "> 1.8.3"

unless required_version.satisfied_by? Gem.ruby_version then
  abort "Expected Ruby Version #{required_version}, was #{Gem.ruby_version}"
end

# We need to preserve the original ARGV to use for passing gem options
# to source gems.  If there is a -- in the line, strip all options after
# it...its for the source building process.
args = !ARGV.include?("--") ? ARGV.clone : ARGV[0...ARGV.index("--")]

begin
  Gem::GemRunner.new.run args
rescue Gem::SystemExitException => e
  exit e.exit_code
end

I think there's a problem here. 

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

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

Message:
Yup, your BASERUBY is incorrect on line 27:

  CONFIG["BASERUBY"] = "echo executable host ruby is required.  use --with-baseruby option.; false"

I'll see what I can do...

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

Comment By: Michael Soulier (msoulier)
Date: 2009-04-02 06:23

Message:
Here you go. 

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

Comment By: Michael Soulier (msoulier)
Date: 2009-04-01 19:03

Message:
I'll need to rebuild to reproduce. 

I won't be able to run that command since the ruby
interpreter is clobbered. I'll find the file. 

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

Comment By: Eric Hodel (drbrain)
Date: 2009-03-31 19:50

Message:
I've checked in a patch which should help diagnose the problem.  It appears that Gem.default_exec_format can end up without a %s in it, but I'm not sure how.

Can you send me your rbconfig.rb from 1.9?

  gem which rbconfig

Will give you the path.

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

Comment By: Michael Soulier (msoulier)
Date: 2009-03-28 06:24

Message:
I repeated the install with ruby 1.8.7 out of SVN, and it
worked fine this time. 

Could it be a problem with the changes in ruby 1.9.1?

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

Comment By: Michael Soulier (msoulier)
Date: 2009-03-27 19:14

Message:
FWIW

msoulier at anton:~/temp$ md5sum rubygems-1.3.1.tgz 
a04ee6f6897077c5b75f5fd1e134c5a9  rubygems-1.3.1.tgz


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

Comment By: Michael Soulier (msoulier)
Date: 2009-03-27 19:13

Message:
Yes, I still have it.

msoulier at anton:~$ ls temp/rubygems-1.3.1/bin
gem  update_rubygems

I went to rubygems.org and clicked download, and grabbed the
.tgz file. 

I can't seem to reach that site right now.

msoulier at anton:~$ hostx rubygems.org
rubygems.org            A       207.114.85.50

My browser is timing out on it. 

I cd'd into the unpacked tarball directory and ran ruby on
setup.rb from there, yes. 

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

Comment By: Eric Hodel (drbrain)
Date: 2009-03-27 16:25

Message:
Do you still have the RubyGems you installed with unpacked?

Can I see an ls of the bin directory?

What URL did you get RubyGems from?

What path did you run setup.rb from?  The unpacked RubyGems tarball dir?

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

Comment By: Michael Soulier (msoulier)
Date: 2009-03-27 15:32

Message:
Oh, and I installed ruby-1.9.1-p0.tar.gz from the
ruby-lang.org site. 

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

Comment By: Michael Soulier (msoulier)
Date: 2009-03-27 15:27

Message:
FWIW this is a Gentoo Linux system. ruby is not already
installed elsewhere. 

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

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

From devnull+rubygems-ci at pivotallabs.com  Thu Apr  2 19:25:59 2009
From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com)
Date: Thu, 2 Apr 2009 23:25:59 +0000
Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2127 failed
Message-ID: <49d54987d1087_4bc3..fdbddbb7e151@ci.pivotallabs.com.tmail>

The build failed.

CHANGES
-------
New revision 2127 detected
Revision 2127 committed by drbrain on 2009-04-02 23:23:10
Fix tests
  M /trunk/test/test_gem_version.rb



TEST FAILURES AND ERRORS
-----------------------
Name: test_hash(TestGemVersion)
Type: Failure
Message: Expected -101520814 to not be equal to -101520814.

./test/test_gem_version.rb:128




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

From devnull+rubygems-ci at pivotallabs.com  Thu Apr  2 19:36:38 2009
From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com)
Date: Thu, 2 Apr 2009 23:36:38 +0000
Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2128 fixed
Message-ID: <49d54c0658d5c_4bc3..fdbddbb7e2e4@ci.pivotallabs.com.tmail>

The build has been fixed.

CHANGES
-------
New revision 2128 detected
Revision 2128 committed by drbrain on 2009-04-02 23:34:15
Oops, #hash should be equal for @v1_4_0
  M /trunk/test/test_gem_version.rb



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

From devnull+rubygems-ci at pivotallabs.com  Fri Apr  3 20:22:51 2009
From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com)
Date: Sat, 4 Apr 2009 00:22:51 +0000
Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2140 failed
Message-ID: <49d6a85b8b78d_4bc3..fdbddbb7e3bc@ci.pivotallabs.com.tmail>

The build failed.

CHANGES
-------
New revision 2140 detected
Revision 2140 committed by drbrain on 2009-04-04 00:20:44
Undent
  M /trunk/lib/rubygems/format.rb
  M /trunk/lib/rubygems/user_interaction.rb
  M /trunk/lib/rubygems/gem_runner.rb
  M /trunk/lib/rubygems/require_paths_builder.rb
  M /trunk/lib/rubygems/builder.rb
  M /trunk/lib/rubygems/old_format.rb
  M /trunk/lib/rubygems/source_index.rb



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

./test/test_gem_source_info_cache.rb:56




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

From devnull+rubygems-ci at pivotallabs.com  Mon Apr  6 15:59:57 2009
From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com)
Date: Mon, 6 Apr 2009 19:59:57 +0000
Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2142 fixed
Message-ID: <49da5f3db068c_4bc3..fdbddbb7e49c@ci.pivotallabs.com.tmail>

The build has been fixed.

CHANGES
-------
New revision 2142 detected
Revision 2142 committed by djberg96 on 2009-04-06 19:58:13
Added changes for test_gem_ext_configure_builder.rb
  M /trunk/ChangeLog
Revision 2141 committed by djberg96 on 2009-04-06 19:56:18
Replaced explicit returns with skip messages
The test_self_build_has_makefile test now checks for the presence of nmake first on Windows, and skips the test if it isn't found
  M /trunk/test/test_gem_ext_configure_builder.rb



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

From luislavena at gmail.com  Mon Apr  6 17:02:14 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Mon, 6 Apr 2009 18:02:14 -0300
Subject: [Rubygems-developers] Revision 2142, checking for nmake
Message-ID: <71166b3b0904061402s3b8ca538r5d3dada3a3893cfb@mail.gmail.com>

Hey Guys,

While the change implemented in revision 2142 may sounds good in
theory, is incorrect.

I'm running all the tests of RubyGems and other using MinGW, not
VC6/8/9 build of Ruby.

Because of that, I don't have nmake but make instead.

Skipping those test due the availability of the compiler toolset need
to take those in consideration.

Keep in mind that win_platform? will return true if your platform is
one of the Gem::WIN_PLATFORMS:

  ##
  # An Array of Regexps that match windows ruby platforms.

  WIN_PATTERNS = [
    /bccwin/i,
    /cygwin/i,
    /djgpp/i,
    /mingw/i,
    /mswin/i,
    /wince/i,
  ]


Which consider bccwin (no nmake over there), cygwin (uses make), djgpp
(who cares about DOS anymore), and wince (which should be VS based
one).

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 Daniel.Berger at qwest.com  Mon Apr  6 17:54:46 2009
From: Daniel.Berger at qwest.com (Berger, Daniel)
Date: Mon, 6 Apr 2009 16:54:46 -0500
Subject: [Rubygems-developers] Revision 2142, checking for nmake
In-Reply-To: <71166b3b0904061402s3b8ca538r5d3dada3a3893cfb@mail.gmail.com>
References: <71166b3b0904061402s3b8ca538r5d3dada3a3893cfb@mail.gmail.com>
Message-ID: <E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D469B@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: Monday, April 06, 2009 3:02 PM
> To: RubyGems Developers (ML)
> Subject: [Rubygems-developers] Revision 2142, checking for nmake
> 
> Hey Guys,
> 
> While the change implemented in revision 2142 may sounds good 
> in theory, is incorrect.
> 
> I'm running all the tests of RubyGems and other using MinGW, not
> VC6/8/9 build of Ruby.
> 
> Because of that, I don't have nmake but make instead.
> 
> Skipping those test due the availability of the compiler 
> toolset need to take those in consideration.
> 
> Keep in mind that win_platform? will return true if your 
> platform is one of the Gem::WIN_PLATFORMS:
> 
>   ##
>   # An Array of Regexps that match windows ruby platforms.
> 
>   WIN_PATTERNS = [
>     /bccwin/i,
>     /cygwin/i,
>     /djgpp/i,
>     /mingw/i,
>     /mswin/i,
>     /wince/i,
>   ]
> 
> 
> Which consider bccwin (no nmake over there), cygwin (uses 
> make), djgpp (who cares about DOS anymore), and wince (which 
> should be VS based one).

Should I just stick to RUBY_PLATFORM.match('mswin') then?

Regards,

Dan

From luislavena at gmail.com  Mon Apr  6 17:56:33 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Mon, 6 Apr 2009 18:56:33 -0300
Subject: [Rubygems-developers] Revision 2142, checking for nmake
In-Reply-To: <E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D469B@qtomaexmbm25.AD.QINTRA.COM>
References: <71166b3b0904061402s3b8ca538r5d3dada3a3893cfb@mail.gmail.com>
	<E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D469B@qtomaexmbm25.AD.QINTRA.COM>
Message-ID: <71166b3b0904061456x6a974419i52dea6ca0a051a5@mail.gmail.com>

On Mon, Apr 6, 2009 at 6:54 PM, Berger, Daniel <Daniel.Berger at qwest.com> wrote:
>
>
>> -----Original Message-----
>> From: rubygems-developers-bounces at rubyforge.org
>> [mailto:rubygems-developers-bounces at rubyforge.org] On Behalf
>> Of Luis Lavena
>> Sent: Monday, April 06, 2009 3:02 PM
>> To: RubyGems Developers (ML)
>> Subject: [Rubygems-developers] Revision 2142, checking for nmake
>>
>> Hey Guys,
>>
>> While the change implemented in revision 2142 may sounds good
>> in theory, is incorrect.
>>
>> I'm running all the tests of RubyGems and other using MinGW, not
>> VC6/8/9 build of Ruby.
>>
>> Because of that, I don't have nmake but make instead.
>>
>> Skipping those test due the availability of the compiler
>> toolset need to take those in consideration.
>>
>> Keep in mind that win_platform? will return true if your
>> platform is one of the Gem::WIN_PLATFORMS:
>>
>> ? ##
>> ? # An Array of Regexps that match windows ruby platforms.
>>
>> ? WIN_PATTERNS = [
>> ? ? /bccwin/i,
>> ? ? /cygwin/i,
>> ? ? /djgpp/i,
>> ? ? /mingw/i,
>> ? ? /mswin/i,
>> ? ? /wince/i,
>> ? ]
>>
>>
>> Which consider bccwin (no nmake over there), cygwin (uses
>> make), djgpp (who cares about DOS anymore), and wince (which
>> should be VS based one).
>
> Should I just stick to RUBY_PLATFORM.match('mswin') then?
>

RUBY_PLATFORM =~ /mswin/

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

From noreply at rubyforge.org  Mon Apr  6 19:02:07 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Mon,  6 Apr 2009 19:02:07 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25208 ] Files in the bin
	directory shouldn't be put in LOAD_PATH
Message-ID: <20090406230207.3C4D21858118@rubyforge.org>

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

Category: other
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Jeremy Lawler (jlawler)
Assigned to: Nobody (None)
Summary: Files in the bin directory shouldn't be put in LOAD_PATH

Initial Comment:
If a file is intended to be loaded by a running ruby process (not exec'd), it shouldn't be in bin.  You've created a system that uses a standard unix naming scheme that you don't implement.  Outside of rubygems, no one add bin directories to the load/include paths.  Calling it bin would be like if python had all their files end in ".rb" 



>From #rubygems on 2009-04-06:
(04:15:15 PM) drbrain: the executable stubs should probably be updated to use Gem.bin_path, now that it exists
(04:16:03 PM) drbrain: until all the bin stubs are migrated on a system, though, it has to work this way for backwards compatibility


(More context, if you'd like)
(01:46:34 PM) jlawler: This is what happened to me:  someone puts extensions on all their scripts.  I had a gem called Foo.  There was a foo.rb in the lib directory that was the app.  But there was driver called foo.rb
(01:47:15 PM) jlawler: because there was a foo.rb in the bin and the lib directory, and because the bin directory has higher priority (?!), I got exceedingly unexpected results.
(04:01:41 PM) drbrain: jlawler: you should file a bug with whoever added .rb to those files
(04:04:07 PM) jlawler: drbrain:  Agreed.  But I still don't understand wtf the point of the bin directory is.  If it gets put in LOAD_PATH, it's not a bin directory.  I'm trying to understand if there's a reason you guys don't consider that a bug...
(04:04:39 PM) drbrain: jlawler: how would "load 'rake'" work otherwise?
(04:08:38 PM) drbrain: it's not a bug because this is how load works
(04:10:17 PM) drbrain: if the exact file name is not on the load path it can't be loaded
(04:10:25 PM) jlawler: drbrain: as it exists, you're right, it wouldn't.  If a file is intended to be loaded by a running ruby process (not exec'd), it shouldn't be in bin.  The "right" way to do that IMO is to have a "rake_runner.rb" (or something like that) that you can load, which would live in the lib directory.  Hell, they can even do it exactly how they do it now, just move the rake file to the lib directory.
(04:12:16 PM) jlawler: You've created a system that uses a standard unix naming scheme that you don't implement.  Outside of rubygems, no one add bin directories to the load/include paths.  Calling it bin would be like if python had all their files end in ".rb" 
(04:14:14 PM) drbrain: jlawler: like I said before, it's done this way for historical reasons, largely
(04:15:15 PM) drbrain: the executable stubs should probably be updated to use Gem.bin_path, now that it exists
(04:16:03 PM) drbrain: until all the bin stubs are migrated on a system, though, it has to work this way for backwards compatibility
(04:16:18 PM) jlawler: drbrain:  I do understand that.  God knows I've maintained things I didn't like for historical reasons.  I'd like there to be a migration away from that, not that an alternative does exist.  I'm not asking you to deprecate it tomorrow, but I think it's a reasonable thing to try to deprecate.
(04:16:59 PM) jlawler: I absolutely refuse to believe I'm the only person who has had to track down the strange behavior caused by the fact that the same file name existed in the bin and lib directories.
(04:17:41 PM) drbrain: you're probably not
(04:34:58 PM) imperator2: jlawler, yes, please file a bug

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

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

From noreply at rubyforge.org  Mon Apr  6 20:12:12 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Mon,  6 Apr 2009 20:12:12 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-24958 ] Install replaces ruby
	interpreter with gem executable
Message-ID: <20090407001212.813BA1858108@rubyforge.org>

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

Category: RubyGems installer (setup.rb)
Group: v1.3.x
>Status: Closed
Resolution: Accepted
Priority: 3
Submitted By: Michael Soulier (msoulier)
Assigned to: Eric Hodel (drbrain)
Summary: Install replaces ruby interpreter with gem executable

Initial Comment:
I'm on a system where I only have write access to my own home directory. So, I built ruby with --prefix=$HOME/ruby. It installs and works fine.

Then, I installed rubygems via

ruby setup.rb

and...

RubyGems installed the following executables:
        /home/msoulier/ruby/bin/ruby

What? That's my ruby interpreter!

No surprise, but gem, irb, and nothing else work now.

msoulier at anton:~$ gem
/home/msoulier/ruby/bin/gem: line 8: require: command not found
/home/msoulier/ruby/bin/gem: line 9: require: command not found
/home/msoulier/ruby/bin/gem: line 10: require: command not found
/home/msoulier/ruby/bin/gem: line 12: required_version: command not found
/home/msoulier/ruby/bin/gem: line 14: unless: command not found
/home/msoulier/ruby/bin/gem: line 15: abort: command not found
/home/msoulier/ruby/bin/gem: line 16: end: command not found
/home/msoulier/ruby/bin/gem: line 21: syntax error near unexpected token `('
/home/msoulier/ruby/bin/gem: line 21: `args = !ARGV.include?("--") ? ARGV.clone : ARGV[0...ARGV.index("--")]'

msoulier at anton:~$ cat $HOME/ruby/bin/ruby
#!/home/msoulier/ruby/bin/ruby
#--
# Copyright 2006 by Chad Fowler, Rich Kilmer, Jim Weirich and others.
# All rights reserved.
# See LICENSE.txt for permissions.
#++

require 'rubygems'
require 'rubygems/gem_runner'
require 'rubygems/exceptions'

required_version = Gem::Requirement.new "> 1.8.3"

unless required_version.satisfied_by? Gem.ruby_version then
  abort "Expected Ruby Version #{required_version}, was #{Gem.ruby_version}"
end

# We need to preserve the original ARGV to use for passing gem options
# to source gems.  If there is a -- in the line, strip all options after
# it...its for the source building process.
args = !ARGV.include?("--") ? ARGV.clone : ARGV[0...ARGV.index("--")]

begin
  Gem::GemRunner.new.run args
rescue Gem::SystemExitException => e
  exit e.exit_code
end

I think there's a problem here. 

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

>Comment By: Eric Hodel (drbrain)
Date: 2009-04-06 17:12

Message:
This should be fixed now.

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

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

Message:
Yup, your BASERUBY is incorrect on line 27:

  CONFIG["BASERUBY"] = "echo executable host ruby is required.  use --with-baseruby option.; false"

I'll see what I can do...

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

Comment By: Michael Soulier (msoulier)
Date: 2009-04-02 06:23

Message:
Here you go. 

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

Comment By: Michael Soulier (msoulier)
Date: 2009-04-01 19:03

Message:
I'll need to rebuild to reproduce. 

I won't be able to run that command since the ruby
interpreter is clobbered. I'll find the file. 

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

Comment By: Eric Hodel (drbrain)
Date: 2009-03-31 19:50

Message:
I've checked in a patch which should help diagnose the problem.  It appears that Gem.default_exec_format can end up without a %s in it, but I'm not sure how.

Can you send me your rbconfig.rb from 1.9?

  gem which rbconfig

Will give you the path.

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

Comment By: Michael Soulier (msoulier)
Date: 2009-03-28 06:24

Message:
I repeated the install with ruby 1.8.7 out of SVN, and it
worked fine this time. 

Could it be a problem with the changes in ruby 1.9.1?

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

Comment By: Michael Soulier (msoulier)
Date: 2009-03-27 19:14

Message:
FWIW

msoulier at anton:~/temp$ md5sum rubygems-1.3.1.tgz 
a04ee6f6897077c5b75f5fd1e134c5a9  rubygems-1.3.1.tgz


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

Comment By: Michael Soulier (msoulier)
Date: 2009-03-27 19:13

Message:
Yes, I still have it.

msoulier at anton:~$ ls temp/rubygems-1.3.1/bin
gem  update_rubygems

I went to rubygems.org and clicked download, and grabbed the
.tgz file. 

I can't seem to reach that site right now.

msoulier at anton:~$ hostx rubygems.org
rubygems.org            A       207.114.85.50

My browser is timing out on it. 

I cd'd into the unpacked tarball directory and ran ruby on
setup.rb from there, yes. 

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

Comment By: Eric Hodel (drbrain)
Date: 2009-03-27 16:25

Message:
Do you still have the RubyGems you installed with unpacked?

Can I see an ls of the bin directory?

What URL did you get RubyGems from?

What path did you run setup.rb from?  The unpacked RubyGems tarball dir?

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

Comment By: Michael Soulier (msoulier)
Date: 2009-03-27 15:32

Message:
Oh, and I installed ruby-1.9.1-p0.tar.gz from the
ruby-lang.org site. 

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

Comment By: Michael Soulier (msoulier)
Date: 2009-03-27 15:27

Message:
FWIW this is a Gentoo Linux system. ruby is not already
installed elsewhere. 

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

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

From devnull+rubygems-ci at pivotallabs.com  Mon Apr  6 21:53:23 2009
From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com)
Date: Tue, 7 Apr 2009 01:53:23 +0000
Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2151 failed
Message-ID: <49dab21379619_4bc3..fdbddbb7e553@ci.pivotallabs.com.tmail>

The build failed.

CHANGES
-------
New revision 2151 detected
Revision 2151 committed by drbrain on 2009-04-07 01:51:43
Release notes for 1.3.2
  M /trunk/ChangeLog
  A /trunk/doc/release_notes/rel_1_3_2.rdoc
Revision 2150 committed by drbrain on 2009-04-07 01:49:40
Allow version specification
  M /trunk/Rakefile
  M /trunk/lib/rubygems/specification.rb
  M /trunk/lib/rubygems.rb
  M /trunk/util/CL2notes
  M /trunk/ChangeLog



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

From drbrain at segment7.net  Mon Apr  6 21:55:11 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Mon, 6 Apr 2009 18:55:11 -0700
Subject: [Rubygems-developers] 1.3.2 release notes
Message-ID: <555195D0-06C6-4129-8505-726DFD2B0A6B@segment7.net>

Here's what I've selected for the 1.3.2 release notes.  Let me know if  
I left out something important.  (I'm still doing some work on  
documentation here and there.)

I may be out of town over the coming weekend, so I expect I'd do a  
release Monday 4/13 or Tuesday 4/14.

Release 1.3.2 fixes some bugs and adds some features.

Select New Features:

* RubyGems now loads plugins from rubygems_plugin.rb in installed gems.
   This can be used to add commands (See Gem::CommandManager) or add
   install/uninstall hooks (See Gem::Installer and Gem::Uninstaller).
* Gem::Version now understands prerelease versions using letters. (eg.
   '1.2.1.b')  Thanks to Josh Susser, Alex Vollmer and Phil Hagelberg.
* RubyGems now includes a Rake task for creating gems which replaces  
rake's
   Rake::GemPackageTask.  See Gem::PackageTask.
* Gem::find_files now returns paths in $LOAD_PATH.
* Added Gem::promote_load_path for use with Gem::find_files
* Added Gem::bin_path to make finding executables easier.  Patch  
#24114 by
   James Tucker.
* Various improvements to build arguments for installing gems.
* Gem::Specification
   * #validate complains about not-files.
   * #description no longer removes newlines.
   * #name must be a String.
   * FIXME is no longer allowed in various fields.
   * Added support for a license attribute.  Feature #11041 (partial).
   * Removed Gem::Specification::list, too much process growth.  Bug  
#23668 by
     Steve Purcell.
* `gem generate_index`
   * Can now generate an RSS feed.
   * Modern indicies can now be updated incrementally.
   * Legacy indicies can be updated separately from modern.

Select Bugs Fixed:

* Better gem activation error message. Patch #23082.
* Kernel methods are now private.  Patch #20801 by James M. Lawrence.
* Fixed various usability issues with `gem check`.
* `gem update` now rescues InstallError and continues.  Bug #19268 by  
Gabriel
   Wilkins.
* Allow 'https', 'file' as a valid schemes for --source.  Patch #22485.
* `gem install`
   * Now removes existing path before installing.  Bug #22837.
   * Uses Gem::bin_path in executable stubs to work around Kernel#load  
bug in
     1.9.
* --user-install
   * `gem install --no-user-install` now works.  Patch #23573 by Alf  
Mikula.
   * `gem uninstall` can now uninstall from ~/.gem.  Bug #23760 by  
Roger Pack.
* setup.rb
   * Clarify RubyGems RDoc installation location.  Bug #22656 by Gian  
Marco
     Gherardi.
   * Allow setup to run from read-only location.  Patch #21862 by Luis  
Herrera.
   * Fixed overwriting ruby executable when BASERUBY was not set.  Bug  
#24958
     by Michael Soulier.
   * Ensure we're in a RubyGems dir when installing.
   * Deal with extraneous quotation mark when autogenerating .bat file  
on MS
     Windows.  Bug #22712.

Deprecation Notices:

* Gem::manage_gems has been removed.
* Time::today will be removed in RubyGems 1.4.

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


From devnull+rubygems-ci at pivotallabs.com  Mon Apr  6 21:58:28 2009
From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com)
Date: Tue, 7 Apr 2009 01:58:28 +0000
Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2152 failed
Message-ID: <49dab3446ab90_4bc3..fdbddbb7e6fd@ci.pivotallabs.com.tmail>

The build failed.

CHANGES
-------
New revision 2152 detected
Revision 2152 committed by drbrain on 2009-04-07 01:54:43
Contents is better
  M /trunk/lib/rubygems/command.rb



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

From devnull+rubygems-ci at pivotallabs.com  Mon Apr  6 22:44:43 2009
From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com)
Date: Tue, 7 Apr 2009 02:44:43 +0000
Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2153 fixed
Message-ID: <49dabe1ba44b2_4bc3..fdbddbb7e764@ci.pivotallabs.com.tmail>

The build has been fixed.

CHANGES
-------
New revision 2153 detected
Revision 2153 committed by drbrain on 2009-04-07 02:39:44
Trim off some stale code, switch to Manifest.txt
  D /trunk/scripts/runtest.rb
  M /trunk/Rakefile
  A /trunk/Manifest.txt
  M /trunk/ChangeLog
  D /trunk/scripts/buildtests.rb
  D /trunk/test/rubygems
  M /trunk/.document



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

From luislavena at gmail.com  Mon Apr  6 23:32:37 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Tue, 7 Apr 2009 00:32:37 -0300
Subject: [Rubygems-developers] 1.3.2 release notes
In-Reply-To: <555195D0-06C6-4129-8505-726DFD2B0A6B@segment7.net>
References: <555195D0-06C6-4129-8505-726DFD2B0A6B@segment7.net>
Message-ID: <71166b3b0904062032o77abb753j4eed525d37cded61@mail.gmail.com>

On Mon, Apr 6, 2009 at 10:55 PM, Eric Hodel <drbrain at segment7.net> wrote:
> Here's what I've selected for the 1.3.2 release notes. ?Let me know if I
> left out something important. ?(I'm still doing some work on documentation
> here and there.)
>

I have some questions...

> I may be out of town over the coming weekend, so I expect I'd do a release
> Monday 4/13 or Tuesday 4/14.
>
> Release 1.3.2 fixes some bugs and adds some features.
>
> [...]
>
> * RubyGems now includes a Rake task for creating gems which replaces rake's
> ?Rake::GemPackageTask. ?See Gem::PackageTask.

What is the advantage of this? Asking this since rake-compiler tool
uses Rake::GemPackageTask to build the native versions, and in case of
an advantage, will be great to know.

> * Gem::Specification
> ?* #validate complains about not-files.
> ?* #description no longer removes newlines.
> ?* #name must be a String.
> [...]

I required #dup in Gem::Specification for rake-compiler:

http://github.com/luislavena/rake-compiler/blob/master/lib/rake/extensiontask.rb#L168-170

Due the lack of it, I just dump and loaded the generated YAML, which
was suboptimal.

> * `gem install`
> ?* Uses Gem::bin_path in executable stubs to work around Kernel#load bug in
> ? ?1.9.
> * setup.rb
> [...]

Does the installation update the existing stub scripts?

Thank you again everybody for working on this and keep improving
RubyGems functionality!

Looking forward for the final release. I'm going to start using this
now locally and see if something happens in the middle ;-)

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 luislavena at gmail.com  Mon Apr  6 23:54:04 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Tue, 7 Apr 2009 00:54:04 -0300
Subject: [Rubygems-developers] Revision 2154 Results on Windows (mingw32 and
	mswin32)
Message-ID: <71166b3b0904062054l4e595e54p1155a2f26c110124@mail.gmail.com>

The Following are the pasties containing different versions of Ruby
1.8.6 (from p114 to p368 silently released last week).

mingw32:
http://pastie.org/439209

mswin32
http://pastie.org/439212

-- 
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 Apr  7 02:13:54 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Mon, 6 Apr 2009 23:13:54 -0700
Subject: [Rubygems-developers] 1.3.2 release notes
In-Reply-To: <555195D0-06C6-4129-8505-726DFD2B0A6B@segment7.net>
References: <555195D0-06C6-4129-8505-726DFD2B0A6B@segment7.net>
Message-ID: <e3af97510904062313g285a3d2s454c68b3d661e827@mail.gmail.com>

On Mon, Apr 6, 2009 at 6:55 PM, Eric Hodel <drbrain at segment7.net> wrote:
> Here's what I've selected for the 1.3.2 release notes. ?Let me know if I
> left out something important. ?(I'm still doing some work on documentation
> here and there.)

Correctly handle build args (--) via the API. RubyForge: bug #23210

From noreply at rubyforge.org  Tue Apr  7 14:16:47 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  7 Apr 2009 14:16:47 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Feature Requests-25232 ] Native
	gems
Message-ID: <20090407181647.B1C591858108@rubyforge.org>

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

Category: `gem install` command
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Jirapong Nanta (jirapong)
Assigned to: Nobody (None)
Summary: Native gems

Initial Comment:
It would be nice if rubygems support a native gems (http://www.ironruby.net/index.php?title=Documentation/How_do_I_install_additional_gems%3F)  because it allows other Ruby Virtual Machine; JRuby and/or IronRuby to call gems in a native mode.

so, platform="win32" should be ignored, but instead have user to configure a platform=="ruby" or platform=="ironruby"  in gemrc. 

or when> gem install, have a prompt the user that there are multiple platforms and will require them to chose one.

Is it something we can add to rubygems?

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

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

From drbrain at segment7.net  Tue Apr  7 17:25:22 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Tue, 7 Apr 2009 14:25:22 -0700
Subject: [Rubygems-developers] 1.3.2 release notes
In-Reply-To: <71166b3b0904062032o77abb753j4eed525d37cded61@mail.gmail.com>
References: <555195D0-06C6-4129-8505-726DFD2B0A6B@segment7.net>
	<71166b3b0904062032o77abb753j4eed525d37cded61@mail.gmail.com>
Message-ID: <694A26F5-2454-41CD-A59B-E8C232B3133D@segment7.net>

On Apr 6, 2009, at 20:32, Luis Lavena wrote:
> On Mon, Apr 6, 2009 at 10:55 PM, Eric Hodel <drbrain at segment7.net>  
> wrote:
>> Here's what I've selected for the 1.3.2 release notes.  Let me know  
>> if I
>> left out something important.  (I'm still doing some work on  
>> documentation
>> here and there.)
>
> I have some questions...
>
>> I may be out of town over the coming weekend, so I expect I'd do a  
>> release
>> Monday 4/13 or Tuesday 4/14.
>>
>> Release 1.3.2 fixes some bugs and adds some features.
>>
>> [...]
>>
>> * RubyGems now includes a Rake task for creating gems which  
>> replaces rake's
>>  Rake::GemPackageTask.  See Gem::PackageTask.
>
> What is the advantage of this? Asking this since rake-compiler tool
> uses Rake::GemPackageTask to build the native versions, and in case of
> an advantage, will be great to know.

If there needs to be any bug fixes or changes to the gem package task  
we don't have to wait for a rake release.

>> * Gem::Specification
>>  * #validate complains about not-files.
>>  * #description no longer removes newlines.
>>  * #name must be a String.
>> [...]
>
> I required #dup in Gem::Specification for rake-compiler:
>
> http://github.com/luislavena/rake-compiler/blob/master/lib/rake/extensiontask.rb#L168-170
>
> Due the lack of it, I just dump and loaded the generated YAML, which
> was suboptimal.

I implemented Gem::Specification#initialize_copy, which should take  
care of your problem.

>> * `gem install`
>>  * Uses Gem::bin_path in executable stubs to work around  
>> Kernel#load bug in
>>    1.9.
>> * setup.rb
>> [...]
>
> Does the installation update the existing stub scripts?

No, but `gem pristine --all` should do that.


From drbrain at segment7.net  Tue Apr  7 18:47:04 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Tue, 7 Apr 2009 15:47:04 -0700
Subject: [Rubygems-developers] 1.3.2 release notes
In-Reply-To: <e3af97510904062313g285a3d2s454c68b3d661e827@mail.gmail.com>
References: <555195D0-06C6-4129-8505-726DFD2B0A6B@segment7.net>
	<e3af97510904062313g285a3d2s454c68b3d661e827@mail.gmail.com>
Message-ID: <79CF3395-F46C-406E-ABCF-414225CFC665@segment7.net>

On Apr 6, 2009, at 23:13, Chad Woolley wrote:
> On Mon, Apr 6, 2009 at 6:55 PM, Eric Hodel <drbrain at segment7.net>  
> wrote:
>> Here's what I've selected for the 1.3.2 release notes.  Let me know  
>> if I
>> left out something important.  (I'm still doing some work on  
>> documentation
>> here and there.)
>
> Correctly handle build args (--) via the API. RubyForge: bug #23210

Added!

From drbrain at segment7.net  Tue Apr  7 23:22:32 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Tue, 7 Apr 2009 20:22:32 -0700
Subject: [Rubygems-developers] Revision 2154 Results on Windows (mingw32
	and mswin32)
In-Reply-To: <71166b3b0904062054l4e595e54p1155a2f26c110124@mail.gmail.com>
References: <71166b3b0904062054l4e595e54p1155a2f26c110124@mail.gmail.com>
Message-ID: <C6D17490-F4A2-4898-8295-E5BBCE82F66D@segment7.net>


On Apr 6, 2009, at 20:54, Luis Lavena wrote:

> The Following are the pasties containing different versions of Ruby
> 1.8.6 (from p114 to p368 silently released last week).
>
> mingw32:
> http://pastie.org/439209

There have been some changes to optparse, I see the  
test_add_option_overlapping_common_and_local_options failure with:

ruby 1.8.8dev (2009-04-06 revision 23143) [i386-darwin9.6.0]

and see some diffs from apple ruby (1.8.6) too.

From Daniel.Berger at qwest.com  Wed Apr  8 10:10:11 2009
From: Daniel.Berger at qwest.com (Berger, Daniel)
Date: Wed, 8 Apr 2009 09:10:11 -0500
Subject: [Rubygems-developers] Revision 2154 Results on Windows
 (mingw32and mswin32)
In-Reply-To: <C6D17490-F4A2-4898-8295-E5BBCE82F66D@segment7.net>
References: <71166b3b0904062054l4e595e54p1155a2f26c110124@mail.gmail.com>
	<C6D17490-F4A2-4898-8295-E5BBCE82F66D@segment7.net>
Message-ID: <E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D46BF@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, April 07, 2009 9:23 PM
> To: RubyGems developers mailing list
> Subject: Re: [Rubygems-developers] Revision 2154 Results on 
> Windows (mingw32and mswin32)
> 
> 
> On Apr 6, 2009, at 20:54, Luis Lavena wrote:
> 
> > The Following are the pasties containing different versions of Ruby
> > 1.8.6 (from p114 to p368 silently released last week).
> >
> > mingw32:
> > http://pastie.org/439209
> 
> There have been some changes to optparse, I see the 
> test_add_option_overlapping_common_and_local_options failure with:
> 
> ruby 1.8.8dev (2009-04-06 revision 23143) [i386-darwin9.6.0]
> 
> and see some diffs from apple ruby (1.8.6) too.

Oh, for the love of...

So, now're we're going to start having to check the version of Ruby, even within the 1.8.x branch? Or is there a more generic approach we can take?

Dan 

From luislavena at gmail.com  Wed Apr  8 10:56:09 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Wed, 8 Apr 2009 11:56:09 -0300
Subject: [Rubygems-developers] Revision 2154 Results on Windows
	(mingw32and mswin32)
In-Reply-To: <E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D46BF@qtomaexmbm25.AD.QINTRA.COM>
References: <71166b3b0904062054l4e595e54p1155a2f26c110124@mail.gmail.com>
	<C6D17490-F4A2-4898-8295-E5BBCE82F66D@segment7.net>
	<E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D46BF@qtomaexmbm25.AD.QINTRA.COM>
Message-ID: <71166b3b0904080756x3bb25983of6aa9cf89e47983c@mail.gmail.com>

On Wed, Apr 8, 2009 at 11:10 AM, Berger, Daniel <Daniel.Berger at qwest.com> wrote:
>
>
>> -----Original Message-----
>> From: rubygems-developers-bounces at rubyforge.org
>> [mailto:rubygems-developers-bounces at rubyforge.org] On Behalf
>> Of Eric Hodel
>> Sent: Tuesday, April 07, 2009 9:23 PM
>> To: RubyGems developers mailing list
>> Subject: Re: [Rubygems-developers] Revision 2154 Results on
>> Windows (mingw32and mswin32)
>>
>>
>> On Apr 6, 2009, at 20:54, Luis Lavena wrote:
>>
>> > The Following are the pasties containing different versions of Ruby
>> > 1.8.6 (from p114 to p368 silently released last week).
>> >
>> > mingw32:
>> > http://pastie.org/439209
>>
>> There have been some changes to optparse, I see the
>> test_add_option_overlapping_common_and_local_options failure with:
>>
>> ruby 1.8.8dev (2009-04-06 revision 23143) [i386-darwin9.6.0]
>>
>> and see some diffs from apple ruby (1.8.6) too.
>
> Oh, for the love of...
>

I said exactly the same.

That's why I'm sticking to 1.8.6, but it seems they backported some
weird stuff even to that.

> So, now're we're going to start having to check the version of Ruby, even within the 1.8.x branch? Or is there a more generic approach we can take?

I really don't know, and basically we will end being a huge mess of
code to workaround all those issues between versions.

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

From drbrain at segment7.net  Wed Apr  8 14:28:44 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Wed, 8 Apr 2009 11:28:44 -0700
Subject: [Rubygems-developers] Revision 2154 Results on Windows
	(mingw32and mswin32)
In-Reply-To: <E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D46BF@qtomaexmbm25.AD.QINTRA.COM>
References: <71166b3b0904062054l4e595e54p1155a2f26c110124@mail.gmail.com>
	<C6D17490-F4A2-4898-8295-E5BBCE82F66D@segment7.net>
	<E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D46BF@qtomaexmbm25.AD.QINTRA.COM>
Message-ID: <4C714AAF-A1AE-46F6-9E88-1C0C17234DBC@segment7.net>

On Apr 8, 2009, at 07:10, 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, April 07, 2009 9:23 PM
>> To: RubyGems developers mailing list
>> Subject: Re: [Rubygems-developers] Revision 2154 Results on
>> Windows (mingw32and mswin32)
>>
>>
>> On Apr 6, 2009, at 20:54, Luis Lavena wrote:
>>
>>> The Following are the pasties containing different versions of Ruby
>>> 1.8.6 (from p114 to p368 silently released last week).
>>>
>>> mingw32:
>>> http://pastie.org/439209
>>
>> There have been some changes to optparse, I see the
>> test_add_option_overlapping_common_and_local_options failure with:
>>
>> ruby 1.8.8dev (2009-04-06 revision 23143) [i386-darwin9.6.0]
>>
>> and see some diffs from apple ruby (1.8.6) too.
>
> Oh, for the love of...
>
> So, now're we're going to start having to check the version of Ruby,  
> even within the 1.8.x branch? Or is there a more generic approach we  
> can take?

The test seemed to have been determining that optparse behaved a  
certain way if it was used it wrong (specifying the same option  
twice).  I decided to just remove the test.

From luislavena at gmail.com  Wed Apr  8 14:30:30 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Wed, 8 Apr 2009 15:30:30 -0300
Subject: [Rubygems-developers] Revision 2154 Results on Windows
	(mingw32and mswin32)
In-Reply-To: <4C714AAF-A1AE-46F6-9E88-1C0C17234DBC@segment7.net>
References: <71166b3b0904062054l4e595e54p1155a2f26c110124@mail.gmail.com>
	<C6D17490-F4A2-4898-8295-E5BBCE82F66D@segment7.net>
	<E1331D75B8E8DA46B15CDEA9BC46FA270D7A4D46BF@qtomaexmbm25.AD.QINTRA.COM>
	<4C714AAF-A1AE-46F6-9E88-1C0C17234DBC@segment7.net>
Message-ID: <71166b3b0904081130n38cc56f5ld9356895bef1ecc8@mail.gmail.com>

On Wed, Apr 8, 2009 at 3:28 PM, Eric Hodel <drbrain at segment7.net> wrote:
> On Apr 8, 2009, at 07:10, 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, April 07, 2009 9:23 PM
>>> To: RubyGems developers mailing list
>>> Subject: Re: [Rubygems-developers] Revision 2154 Results on
>>> Windows (mingw32and mswin32)
>>>
>>>
>>> On Apr 6, 2009, at 20:54, Luis Lavena wrote:
>>>
>>>> The Following are the pasties containing different versions of Ruby
>>>> 1.8.6 (from p114 to p368 silently released last week).
>>>>
>>>> mingw32:
>>>> http://pastie.org/439209
>>>
>>> There have been some changes to optparse, I see the
>>> test_add_option_overlapping_common_and_local_options failure with:
>>>
>>> ruby 1.8.8dev (2009-04-06 revision 23143) [i386-darwin9.6.0]
>>>
>>> and see some diffs from apple ruby (1.8.6) too.
>>
>> Oh, for the love of...
>>
>> So, now're we're going to start having to check the version of Ruby, even
>> within the 1.8.x branch? Or is there a more generic approach we can take?
>
> The test seemed to have been determining that optparse behaved a certain way
> if it was used it wrong (specifying the same option twice). ?I decided to
> just remove the test.

So was bogus?

That make me feel better :-D

-- 
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 Apr 10 10:22:18 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Fri, 10 Apr 2009 11:22:18 -0300
Subject: [Rubygems-developers] Question: rake test requires rake outside
	GEM_PATH
Message-ID: <71166b3b0904100722v72c3aa01ved5139d54a996985@mail.gmail.com>

Hello Guys,

I have multiple versions of ruby installed, ranging from 1.8.5 to
1.8.6, p114 and p368.

To reduce duplication of common used gems, I set both GEM_HOME and
GEM_PATH to my user folder:

D:/Users/Luis/.gem/ruby/1.8

I can run rake or any other gem without any kind of issue.

I've noticed that when running some RubyGems test, rake is invoked,
and is failing:

 18) Error:
test_path_ok_eh_legacy(TestGemUninstaller):
Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native
extension.

D:/Users/Luis/ruby/ruby-1.8.6-p368-i386-mingw32/bin/ruby.exe
mkrf_conf.rb --build_arg1 --build_arg2

rake RUBYARCHDIR=D:/Temp/test_rubygems_2712/gemhome/gems/a-2/lib
RUBYLIBDIR=D:/Temp/test_rubygems_2712/gemhome/gems/a-2/lib
D:/Users/Luis/ruby/ruby-1.8.6-p368-i386-mingw32/lib/ruby/site_ruby/1.8/rubygems.rb:636:in
`report_activate_error': Could not find RubyGem rake (>= 0)
(Gem::LoadError)
        from D:/Users/Luis/ruby/ruby-1.8.6-p368-i386-mingw32/lib/ruby/site_ruby/1.8/rubygems.rb:141:in
`activate'
        from D:/Users/Luis/ruby/ruby-1.8.6-p368-i386-mingw32/lib/ruby/site_ruby/1.8/rubygems.rb:49:in
`gem'
        from D:/Users/Luis/.gem/ruby/1.8/bin/rake:18

The rake from my GEM_HOME is invoked, but looks like ENV['GEM_HOME']
and 'GEM_PATH' were tweaked, so it can no longer find that gem, thus
failing.

I wonder if this could affect other applications too, and what could
ge the workaround besides .gemrc, since I've also 1.9.1 and want to
avoid mixing the gem repositories between the two.

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 jirapong.nanta at gmail.com  Fri Apr 10 14:40:44 2009
From: jirapong.nanta at gmail.com (jirapong.nanta at gmail.com)
Date: Sat, 11 Apr 2009 01:40:44 +0700
Subject: [Rubygems-developers] Question: rake test requires rake outside
	GEM_PATH
In-Reply-To: <71166b3b0904100722v72c3aa01ved5139d54a996985@mail.gmail.com>
References: <71166b3b0904100722v72c3aa01ved5139d54a996985@mail.gmail.com>
Message-ID: <441C452C-46EF-4F87-AFD5-DC0D8F143AB8@gmail.com>

+1 vote for this feature.

On Apr 10, 2009, at 9:22 PM, Luis Lavena wrote:

> Hello Guys,
>
> I have multiple versions of ruby installed, ranging from 1.8.5 to
> 1.8.6, p114 and p368.
>
> To reduce duplication of common used gems, I set both GEM_HOME and
> GEM_PATH to my user folder:
>
> D:/Users/Luis/.gem/ruby/1.8
>
> I can run rake or any other gem without any kind of issue.
>
> I've noticed that when running some RubyGems test, rake is invoked,
> and is failing:
>
> 18) Error:
> test_path_ok_eh_legacy(TestGemUninstaller):
> Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native
> extension.
>
> D:/Users/Luis/ruby/ruby-1.8.6-p368-i386-mingw32/bin/ruby.exe
> mkrf_conf.rb --build_arg1 --build_arg2
>
> rake RUBYARCHDIR=D:/Temp/test_rubygems_2712/gemhome/gems/a-2/lib
> RUBYLIBDIR=D:/Temp/test_rubygems_2712/gemhome/gems/a-2/lib
> D:/Users/Luis/ruby/ruby-1.8.6-p368-i386-mingw32/lib/ruby/site_ruby/ 
> 1.8/rubygems.rb:636:in
> `report_activate_error': Could not find RubyGem rake (>= 0)
> (Gem::LoadError)
>        from D:/Users/Luis/ruby/ruby-1.8.6-p368-i386-mingw32/lib/ruby/ 
> site_ruby/1.8/rubygems.rb:141:in
> `activate'
>        from D:/Users/Luis/ruby/ruby-1.8.6-p368-i386-mingw32/lib/ruby/ 
> site_ruby/1.8/rubygems.rb:49:in
> `gem'
>        from D:/Users/Luis/.gem/ruby/1.8/bin/rake:18
>
> The rake from my GEM_HOME is invoked, but looks like ENV['GEM_HOME']
> and 'GEM_PATH' were tweaked, so it can no longer find that gem, thus
> failing.
>
> I wonder if this could affect other applications too, and what could
> ge the workaround besides .gemrc, since I've also 1.9.1 and want to
> avoid mixing the gem repositories between the two.
>
> 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
> _______________________________________________
> Rubygems-developers mailing list
> http://rubyforge.org/projects/rubygems
> Rubygems-developers at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubygems-developers


From djberg96 at gmail.com  Sun Apr 12 15:41:29 2009
From: djberg96 at gmail.com (Daniel Berger)
Date: Sun, 12 Apr 2009 13:41:29 -0600
Subject: [Rubygems-developers] Question: rake test requires rake outside
 GEM_PATH
In-Reply-To: <71166b3b0904100722v72c3aa01ved5139d54a996985@mail.gmail.com>
References: <71166b3b0904100722v72c3aa01ved5139d54a996985@mail.gmail.com>
Message-ID: <49E243E9.6070708@gmail.com>

Luis Lavena wrote:
> Hello Guys,
> 
> I have multiple versions of ruby installed, ranging from 1.8.5 to
> 1.8.6, p114 and p368.
> 
> To reduce duplication of common used gems, I set both GEM_HOME and
> GEM_PATH to my user folder:
> 
> D:/Users/Luis/.gem/ruby/1.8
> 
> I can run rake or any other gem without any kind of issue.
> 
> I've noticed that when running some RubyGems test, rake is invoked,
> and is failing:
> 
>  18) Error:
> test_path_ok_eh_legacy(TestGemUninstaller):
> Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native
> extension.
> 
> D:/Users/Luis/ruby/ruby-1.8.6-p368-i386-mingw32/bin/ruby.exe
> mkrf_conf.rb --build_arg1 --build_arg2
> 
> rake RUBYARCHDIR=D:/Temp/test_rubygems_2712/gemhome/gems/a-2/lib
> RUBYLIBDIR=D:/Temp/test_rubygems_2712/gemhome/gems/a-2/lib
> D:/Users/Luis/ruby/ruby-1.8.6-p368-i386-mingw32/lib/ruby/site_ruby/1.8/rubygems.rb:636:in
> `report_activate_error': Could not find RubyGem rake (>= 0)
> (Gem::LoadError)
>         from D:/Users/Luis/ruby/ruby-1.8.6-p368-i386-mingw32/lib/ruby/site_ruby/1.8/rubygems.rb:141:in
> `activate'
>         from D:/Users/Luis/ruby/ruby-1.8.6-p368-i386-mingw32/lib/ruby/site_ruby/1.8/rubygems.rb:49:in
> `gem'
>         from D:/Users/Luis/.gem/ruby/1.8/bin/rake:18
> 
> The rake from my GEM_HOME is invoked, but looks like ENV['GEM_HOME']
> and 'GEM_PATH' were tweaked, so it can no longer find that gem, thus
> failing.

Can you see where and why?

> I wonder if this could affect other applications too, and what could
> ge the workaround besides .gemrc, since I've also 1.9.1 and want to
> avoid mixing the gem repositories between the two.

Seems reasonable.

Regards,

Dan

From noreply at rubyforge.org  Mon Apr 13 00:32:42 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Mon, 13 Apr 2009 00:32:42 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25405 ] gem cleanup does not
	work with non-system gem installations
Message-ID: <20090413043242.909F818580F6@rubyforge.org>

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

Category: `gem` commands (other)
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Brett Eisenberg (brett)
Assigned to: Nobody (None)
Summary: gem cleanup does not work with non-system gem installations

Initial Comment:
[brett at rubygems]:~% gem cleanup --debug
Exception `NameError' at /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/command_manager.rb:134 - uninitialized constant Gem::Commands::CleanupCommand
Cleaning up installed gems...
Exception `NameError' at /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/command_manager.rb:134 - uninitialized constant Gem::Commands::UninstallCommand
Attempting to uninstall memcache-client-1.7.1
Exception `Gem::InstallError' at /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/uninstaller.rb:61 - Unknown gem memcache-client = 1.7.1
ERROR:  While executing gem ... (Gem::InstallError)
    Unknown gem memcache-client = 1.7.1
	/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/uninstaller.rb:61:in `uninstall'
	/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/commands/cleanup_command.rb:78:in `execute'
	/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/commands/cleanup_command.rb:65:in `each'
	/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/commands/cleanup_command.rb:65:in `execute'
	/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/command.rb:136:in `invoke'
	/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/command_manager.rb:105:in `process_args'
	/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/command_manager.rb:75:in `run'
	/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/gem_runner.rb:39:in `run'
	/opt/local/bin/gem:24
[brett at rubygems]:~% gem search memcache-client

*** LOCAL GEMS ***

memcache-client (1.7.2, 1.7.1)


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

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

From luislavena at gmail.com  Mon Apr 13 08:23:22 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Mon, 13 Apr 2009 09:23:22 -0300
Subject: [Rubygems-developers] Question: rake test requires rake outside
	GEM_PATH
In-Reply-To: <49E243E9.6070708@gmail.com>
References: <71166b3b0904100722v72c3aa01ved5139d54a996985@mail.gmail.com>
	<49E243E9.6070708@gmail.com>
Message-ID: <71166b3b0904130523u349b9dddg31b44800c372afba@mail.gmail.com>

On Sun, Apr 12, 2009 at 4:41 PM, Daniel Berger <djberg96 at gmail.com> wrote:
> Luis Lavena wrote:
>>
>> Hello Guys,
>>
>> I have multiple versions of ruby installed, ranging from 1.8.5 to
>> 1.8.6, p114 and p368.
>>
>> To reduce duplication of common used gems, I set both GEM_HOME and
>> GEM_PATH to my user folder:
>>
>> D:/Users/Luis/.gem/ruby/1.8
>>
>> I can run rake or any other gem without any kind of issue.
>>
>> I've noticed that when running some RubyGems test, rake is invoked,
>> and is failing:
>>
>> ?18) Error:
>> test_path_ok_eh_legacy(TestGemUninstaller):
>> Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native
>> extension.
>>
>> D:/Users/Luis/ruby/ruby-1.8.6-p368-i386-mingw32/bin/ruby.exe
>> mkrf_conf.rb --build_arg1 --build_arg2
>>
>> rake RUBYARCHDIR=D:/Temp/test_rubygems_2712/gemhome/gems/a-2/lib
>> RUBYLIBDIR=D:/Temp/test_rubygems_2712/gemhome/gems/a-2/lib
>>
>> D:/Users/Luis/ruby/ruby-1.8.6-p368-i386-mingw32/lib/ruby/site_ruby/1.8/rubygems.rb:636:in
>> `report_activate_error': Could not find RubyGem rake (>= 0)
>> (Gem::LoadError)
>> ? ? ? ?from
>> D:/Users/Luis/ruby/ruby-1.8.6-p368-i386-mingw32/lib/ruby/site_ruby/1.8/rubygems.rb:141:in
>> `activate'
>> ? ? ? ?from
>> D:/Users/Luis/ruby/ruby-1.8.6-p368-i386-mingw32/lib/ruby/site_ruby/1.8/rubygems.rb:49:in
>> `gem'
>> ? ? ? ?from D:/Users/Luis/.gem/ruby/1.8/bin/rake:18
>>
>> The rake from my GEM_HOME is invoked, but looks like ENV['GEM_HOME']
>> and 'GEM_PATH' were tweaked, so it can no longer find that gem, thus
>> failing.
>
> Can you see where and why?
>

test/gemutilities.rb:134 (teardown).

Is doing a cleanup, but not doing a safeguard of the values prior resetting.

>> I wonder if this could affect other applications too, and what could
>> ge the workaround besides .gemrc, since I've also 1.9.1 and want to
>> avoid mixing the gem repositories between the two.
>
> Seems reasonable.
>

Besides RubyGems own tests, couldn't find other being affected by
this, so is good.

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

From noreply at rubyforge.org  Mon Apr 13 16:39:24 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Mon, 13 Apr 2009 16:39:24 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25405 ] gem cleanup does not
	work with non-system gem installations
Message-ID: <20090413203924.5D6DA1598074@rubyforge.org>

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

Category: `gem` commands (other)
Group: v1.3.x
>Status: Closed
>Resolution: Out of Date
Priority: 3
Submitted By: Brett Eisenberg (brett)
>Assigned to: Eric Hodel (drbrain)
Summary: gem cleanup does not work with non-system gem installations

Initial Comment:
[brett at rubygems]:~% gem cleanup --debug
Exception `NameError' at /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/command_manager.rb:134 - uninitialized constant Gem::Commands::CleanupCommand
Cleaning up installed gems...
Exception `NameError' at /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/command_manager.rb:134 - uninitialized constant Gem::Commands::UninstallCommand
Attempting to uninstall memcache-client-1.7.1
Exception `Gem::InstallError' at /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/uninstaller.rb:61 - Unknown gem memcache-client = 1.7.1
ERROR:  While executing gem ... (Gem::InstallError)
    Unknown gem memcache-client = 1.7.1
	/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/uninstaller.rb:61:in `uninstall'
	/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/commands/cleanup_command.rb:78:in `execute'
	/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/commands/cleanup_command.rb:65:in `each'
	/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/commands/cleanup_command.rb:65:in `execute'
	/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/command.rb:136:in `invoke'
	/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/command_manager.rb:105:in `process_args'
	/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/command_manager.rb:75:in `run'
	/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/gem_runner.rb:39:in `run'
	/opt/local/bin/gem:24
[brett at rubygems]:~% gem search memcache-client

*** LOCAL GEMS ***

memcache-client (1.7.2, 1.7.1)


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

>Comment By: Eric Hodel (drbrain)
Date: 2009-04-13 13:39

Message:
This is fixed in trunk.

For non-GEM_HOME paths, you must specify the repo to clean up.

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

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

From drbrain at segment7.net  Mon Apr 13 16:42:58 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Mon, 13 Apr 2009 13:42:58 -0700
Subject: [Rubygems-developers] Question: rake test requires rake outside
	GEM_PATH
In-Reply-To: <71166b3b0904130523u349b9dddg31b44800c372afba@mail.gmail.com>
References: <71166b3b0904100722v72c3aa01ved5139d54a996985@mail.gmail.com>
	<49E243E9.6070708@gmail.com>
	<71166b3b0904130523u349b9dddg31b44800c372afba@mail.gmail.com>
Message-ID: <4723D666-C149-4862-8AD5-F67ECFC42843@segment7.net>

On Apr 13, 2009, at 05:23, Luis Lavena wrote:
> On Sun, Apr 12, 2009 at 4:41 PM, Daniel Berger <djberg96 at gmail.com>  
> wrote:
>> Luis Lavena wrote:
>>>
>>> Hello Guys,
>>>
>>> I have multiple versions of ruby installed, ranging from 1.8.5 to
>>> 1.8.6, p114 and p368.
>>>
>>> To reduce duplication of common used gems, I set both GEM_HOME and
>>> GEM_PATH to my user folder:
>>>
>>> D:/Users/Luis/.gem/ruby/1.8
>>>
>>> I can run rake or any other gem without any kind of issue.
>>>
>>> I've noticed that when running some RubyGems test, rake is invoked,
>>> and is failing:
>>>
>>>  18) Error:
>>> test_path_ok_eh_legacy(TestGemUninstaller):
>>> Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem  
>>> native
>>> extension.
>>>
>>> D:/Users/Luis/ruby/ruby-1.8.6-p368-i386-mingw32/bin/ruby.exe
>>> mkrf_conf.rb --build_arg1 --build_arg2
>>>
>>> rake RUBYARCHDIR=D:/Temp/test_rubygems_2712/gemhome/gems/a-2/lib
>>> RUBYLIBDIR=D:/Temp/test_rubygems_2712/gemhome/gems/a-2/lib
>>>
>>> D:/Users/Luis/ruby/ruby-1.8.6-p368-i386-mingw32/lib/ruby/site_ruby/ 
>>> 1.8/rubygems.rb:636:in
>>> `report_activate_error': Could not find RubyGem rake (>= 0)
>>> (Gem::LoadError)
>>>        from
>>> D:/Users/Luis/ruby/ruby-1.8.6-p368-i386-mingw32/lib/ruby/site_ruby/ 
>>> 1.8/rubygems.rb:141:in
>>> `activate'
>>>        from
>>> D:/Users/Luis/ruby/ruby-1.8.6-p368-i386-mingw32/lib/ruby/site_ruby/ 
>>> 1.8/rubygems.rb:49:in
>>> `gem'
>>>        from D:/Users/Luis/.gem/ruby/1.8/bin/rake:18
>>>
>>> The rake from my GEM_HOME is invoked, but looks like ENV['GEM_HOME']
>>> and 'GEM_PATH' were tweaked, so it can no longer find that gem, thus
>>> failing.
>>
>> Can you see where and why?
>>
>
> test/gemutilities.rb:134 (teardown).
>
> Is doing a cleanup, but not doing a safeguard of the values prior  
> resetting.
>
>>> I wonder if this could affect other applications too, and what could
>>> ge the workaround besides .gemrc, since I've also 1.9.1 and want to
>>> avoid mixing the gem repositories between the two.
>>
>> Seems reasonable.
>>
>
> Besides RubyGems own tests, couldn't find other being affected by
> this, so is good.

RubyGems tweaks GEM_HOME and GEM_PATH to point to a temporary test  
directory to avoid writing to files it shouldn't.

For tests that need rake, rake could be installed into the temporary  
test directory.

From drbrain at segment7.net  Mon Apr 13 16:45:44 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Mon, 13 Apr 2009 13:45:44 -0700
Subject: [Rubygems-developers] Question: rake test requires rake outside
	GEM_PATH
In-Reply-To: <441C452C-46EF-4F87-AFD5-DC0D8F143AB8@gmail.com>
References: <71166b3b0904100722v72c3aa01ved5139d54a996985@mail.gmail.com>
	<441C452C-46EF-4F87-AFD5-DC0D8F143AB8@gmail.com>
Message-ID: <49C8C9FD-AFDB-4E05-944E-E8B0ED822CB1@segment7.net>

On Apr 10, 2009, at 11:40, jirapong.nanta at gmail.com wrote:

> +1 vote for this feature.

Having RubyGems' tests pull in installed gems is a bad idea, if a test  
breaks it may end up writing files into your real gem repositories or  
in random other places on your disk.

Unless you meant some other feature, in which case you should be more  
verbose than "+1", a highly useless comment.


From drbrain at segment7.net  Mon Apr 13 17:36:52 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Mon, 13 Apr 2009 14:36:52 -0700
Subject: [Rubygems-developers] I think it's time to release 1.3.2
Message-ID: <D81A715C-425F-4A04-93F7-2A78623BEEE4@segment7.net>

Here's the finalized change list for the release notes:

Release 1.3.2 fixes some bugs and adds some features.

Select New Features:

* RubyGems now loads plugins from rubygems_plugin.rb in installed gems.
   This can be used to add commands (See Gem::CommandManager) or add
   install/uninstall hooks (See Gem::Installer and Gem::Uninstaller).
* Gem::Version now understands prerelease versions using letters. (eg.
   '1.2.1.b')  Thanks to Josh Susser, Alex Vollmer and Phil Hagelberg.
* RubyGems now includes a Rake task for creating gems which replaces  
rake's
   Rake::GemPackageTask.  See Gem::PackageTask.
* Gem::find_files now returns paths in $LOAD_PATH.
* Added Gem::promote_load_path for use with Gem::find_files
* Added Gem::bin_path to make finding executables easier.  Patch  
#24114 by
   James Tucker.
* Various improvements to build arguments for installing gems.
* `gem contents` added --all and --no-prefix.
* Gem::Specification
   * #validate strips directories and errors on not-files.
   * #description no longer removes newlines.
   * #name must be a String.
   * FIXME is no longer allowed in various fields.
   * Added support for a license attribute.  Feature #11041 (partial).
   * Removed Gem::Specification::list, too much process growth.  Bug  
#23668 by
     Steve Purcell.
* `gem generate_index`
   * Can now generate an RSS feed.
   * Modern indicies can now be updated incrementally.
   * Legacy indicies can be updated separately from modern.

Select Bugs Fixed:

* Better gem activation error message. Patch #23082.
* Kernel methods are now private.  Patch #20801 by James M. Lawrence.
* Fixed various usability issues with `gem check`.
* `gem update` now rescues InstallError and continues.  Bug #19268 by  
Gabriel
   Wilkins.
* Allow 'https', 'file' as a valid schemes for --source.  Patch #22485.
* `gem install`
   * Now removes existing path before installing.  Bug #22837.
   * Uses Gem::bin_path in executable stubs to work around Kernel#load  
bug in
     1.9.
   * Correctly handle build args (after --) via the API.  Bug #23210.
* --user-install
   * `gem install --no-user-install` now works.  Patch #23573 by Alf  
Mikula.
   * `gem uninstall` can now uninstall from ~/.gem.  Bug #23760 by  
Roger Pack.
* setup.rb
   * Clarify RubyGems RDoc installation location.  Bug #22656 by Gian  
Marco
     Gherardi.
   * Allow setup to run from read-only location.  Patch #21862 by Luis  
Herrera.
   * Fixed overwriting ruby executable when BASERUBY was not set.  Bug  
#24958
     by Michael Soulier.
   * Ensure we're in a RubyGems dir when installing.
   * Deal with extraneous quotation mark when autogenerating .bat file  
on MS
     Windows.  Bug #22712.

Deprecation Notices:

* Gem::manage_gems has been removed.
* Time::today will be removed in RubyGems 1.4.


From djberg96 at gmail.com  Wed Apr 15 09:02:00 2009
From: djberg96 at gmail.com (Daniel Berger)
Date: Wed, 15 Apr 2009 07:02:00 -0600
Subject: [Rubygems-developers] I think it's time to release 1.3.2
In-Reply-To: <D81A715C-425F-4A04-93F7-2A78623BEEE4@segment7.net>
References: <D81A715C-425F-4A04-93F7-2A78623BEEE4@segment7.net>
Message-ID: <49E5DAC8.8090905@gmail.com>

Eric Hodel wrote:
> Here's the finalized change list for the release notes:

<snip>

Looks good. I say release the hounds!

Regards,

Dan

From luislavena at gmail.com  Wed Apr 15 11:26:10 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Wed, 15 Apr 2009 12:26:10 -0300
Subject: [Rubygems-developers] I think it's time to release 1.3.2
In-Reply-To: <49E5DAC8.8090905@gmail.com>
References: <D81A715C-425F-4A04-93F7-2A78623BEEE4@segment7.net>
	<49E5DAC8.8090905@gmail.com>
Message-ID: <71166b3b0904150826i36ae6a07ud17aa7a605d03bc6@mail.gmail.com>

On Wed, Apr 15, 2009 at 10:02 AM, Daniel Berger <djberg96 at gmail.com> wrote:
> Eric Hodel wrote:
>>
>> Here's the finalized change list for the release notes:
>
> <snip>
>
> Looks good. I say release the hounds!
>

Looks great, eagerly waiting to replace the 1.3.1 one with this :-)

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 drbrain at segment7.net  Wed Apr 15 17:44:17 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Wed, 15 Apr 2009 14:44:17 -0700
Subject: [Rubygems-developers] [ANN] RubyGems 1.3.2
Message-ID: <BA8DAC9A-7FD3-4C5B-8D76-597FC89D9681@segment7.net>

= Announce: RubyGems Release 1.3.2

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

Release 1.3.2 fixes some bugs and adds some features.

Select New Features:

* RubyGems now loads plugins from rubygems_plugin.rb in installed gems.
   This can be used to add commands (See Gem::CommandManager) or add
   install/uninstall hooks (See Gem::Installer and Gem::Uninstaller).
* Gem::Version now understands prerelease versions using letters. (eg.
   '1.2.1.b')  Thanks to Josh Susser, Alex Vollmer and Phil Hagelberg.
* RubyGems now includes a Rake task for creating gems which replaces  
rake's
   Rake::GemPackageTask.  See Gem::PackageTask.
* Gem::find_files now returns paths in $LOAD_PATH.
* Added Gem::promote_load_path for use with Gem::find_files
* Added Gem::bin_path to make finding executables easier.  Patch  
#24114 by
   James Tucker.
* Various improvements to build arguments for installing gems.
* `gem contents` added --all and --no-prefix.
* Gem::Specification
   * #validate strips directories and errors on not-files.
   * #description no longer removes newlines.
   * #name must be a String.
   * FIXME and TODO are no longer allowed in various fields.
   * Added support for a license attribute.  Feature #11041 (partial).
   * Removed Gem::Specification::list, too much process growth.  Bug  
#23668 by
     Steve Purcell.
* `gem generate_index`
   * Can now generate an RSS feed.
   * Modern indicies can now be updated incrementally.
   * Legacy indicies can be updated separately from modern.

Select Bugs Fixed:

* Better gem activation error message. Patch #23082.
* Kernel methods are now private.  Patch #20801 by James M. Lawrence.
* Fixed various usability issues with `gem check`.
* `gem update` now rescues InstallError and continues.  Bug #19268 by  
Gabriel
   Wilkins.
* Allow 'https', 'file' as a valid schemes for --source.  Patch #22485.
* `gem install`
   * Now removes existing path before installing.  Bug #22837.
   * Uses Gem::bin_path in executable stubs to work around Kernel#load  
bug in
     1.9.
   * Correctly handle build args (after --) via the API.  Bug #23210.
* --user-install
   * `gem install --no-user-install` now works.  Patch #23573 by Alf  
Mikula.
   * `gem uninstall` can now uninstall from ~/.gem.  Bug #23760 by  
Roger Pack.
* setup.rb
   * Clarify RubyGems RDoc installation location.  Bug #22656 by Gian  
Marco
     Gherardi.
   * Allow setup to run from read-only location.  Patch #21862 by Luis  
Herrera.
   * Fixed overwriting ruby executable when BASERUBY was not set.  Bug  
#24958
     by Michael Soulier.
   * Ensure we're in a RubyGems dir when installing.
   * Deal with extraneous quotation mark when autogenerating .bat file  
on MS
     Windows.  Bug #22712.

Deprecation Notices:

* Gem::manage_gems has been removed.
* Time::today will be removed in RubyGems 1.4.

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

Special thanks to Chad Wooley for backwards compatibility testing and  
Luis
Lavena and Daniel Berger for continuing windows support.

== How can I get RubyGems?

NOTE:  If you have installed RubyGems using a package system you may  
want to
install a new RubyGems through the same packaging system.

If you have a recent version of RubyGems (0.8.5 or later), then all
you need to do is:

   $ gem update --system   (you might need to be admin/root)

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

NOTE: You may have to run the command twice if you have any previosly
installed rubygems-update gems.

If you have an older version of RubyGems installed, then you can still
do it in two steps:

   $ gem install rubygems-update  (again, might need to be admin/root)
   $ update_rubygems              (... here too)

If you don't have any gems install, there is still the pre-gem
approach to getting software ... doing it manually:

1. DOWNLOAD FROM: http://rubyforge.org/frs/?group_id=126
2. UNPACK INTO A DIRECTORY AND CD THERE
3. INSTALL WITH:  ruby setup.rb  (you may need admin/root privilege)

== To File Bugs

The RubyGems bug tracker can be found on RubyForge at:
http://rubyforge.org/tracker/?func=add&group_id=126&atid=575

When filing a bug, `gem env` output will be helpful in diagnosing the  
issue.

If you find a bug where RubyGems crashes, please provide debug output.  
You can
do that with `gem --debug the_command`.

== Thanks

Keep those gems coming!

-- The RubyGems team

PS: Happy Tax Day!

From noreply at rubyforge.org  Thu Apr 16 03:15:53 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 16 Apr 2009 03:15:53 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25493 ] Feature: Make
	trailing zeroes in gem version significant
Message-ID: <20090416071553.135D3159802C@rubyforge.org>

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

Category: #gem and #require methods
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Yossef Mendelssohn (ymendel)
Assigned to: Nobody (None)
Summary: Feature: Make trailing zeroes in gem version significant

Initial Comment:
I'd like for 1.0.0 to be seen as > 1.0

Patch (diffs from git show) and flog/reek output before/after the change can be seen at http://gist.github.com/96284

You can see a few specs had to change because they assume the trailing zeroes don't matter. If this is a hard requirement, then obviously my patch cannot be accepted, at least not without some transition and deprecation warning period.

The flog and reek output is included to show that as far as overall complexity and smell goes, the code is improved by this change. Only the Gem::Version#balance utility method takes a hit as its flog score jumps from 15.4 to 25.1

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

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

From noreply at rubyforge.org  Thu Apr 16 03:16:49 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 16 Apr 2009 03:16:49 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25493 ] Feature: Make
	trailing zeroes in gem version significant
Message-ID: <20090416071649.581CD159802C@rubyforge.org>

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

Category: #gem and #require methods
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Yossef Mendelssohn (ymendel)
>Assigned to: Phil Hagelberg (technomancy)
Summary: Feature: Make trailing zeroes in gem version significant

Initial Comment:
I'd like for 1.0.0 to be seen as > 1.0

Patch (diffs from git show) and flog/reek output before/after the change can be seen at http://gist.github.com/96284

You can see a few specs had to change because they assume the trailing zeroes don't matter. If this is a hard requirement, then obviously my patch cannot be accepted, at least not without some transition and deprecation warning period.

The flog and reek output is included to show that as far as overall complexity and smell goes, the code is improved by this change. Only the Gem::Version#balance utility method takes a hit as its flog score jumps from 15.4 to 25.1

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

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

From luislavena at gmail.com  Thu Apr 16 06:11:04 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Thu, 16 Apr 2009 07:11:04 -0300
Subject: [Rubygems-developers] The case of binary gems and Ruby versions.
Message-ID: <71166b3b0904160311w1d28a192oa81a127494b5d681@mail.gmail.com>

Hey Guys,

Been investing a lot of time in Ruby 1.9 as I move forward for updated
RubyInstaller (One-Click) for both 1.8.6 and 1.9.x branches.

Because of that, I've started to realize, even more and more, that
distributing binary gems between versions is set to failure.

Let me explain my logic with a simple example.

My gem contains a extension, which I compile, cross-compile and
package for 'i386-mswin32' (x86-mswin32) using my stock Ruby 1.8.6
installation. I can also compile for the new RubyInstaller platform
(mingw32) using the same approach.

At the time I upload that to rubyforge, I upload the following files:

my-gem-1.0.gem
my-gem-1.0-x86-mswin32-60.gem
my-gem-1.0-x86-mingw32.gem

At this point, everything is good.

Since the last 2 gems listed there are binary gems, those will be
linking with msvcrt-ruby18.dll, which is the runtime library for Ruby
on Windows (both MinGW and VC6). No problem so far.

You wonder, where is the problem then?

These gem where built for 1.8, so installing those in 1.9 will not
fail unless I specify require_ruby_version (which is something
rake-compiler now does).

Now, the real problem becomes when I want to provide binaries for BOTH
ruby version, since RubyGems, besides the required_ruby_version don't
provide a mechanism to distinguish 1.8 from 1.9 gems, I end with the
exact same gem names, with the exact same versions and platforms, thus
overwriting previous versions.

Someone suggested me that release 1.0.0 for Ruby 1.8 and 1.1.0 for
Ruby 1.9, but that is misleading.

I think we reached the point where RubyGems roadmap needs to start
considering these cases to provide a more mature solution for us.

Regards,
-- 
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  Thu Apr 16 06:24:20 2009
From: jftucker at gmail.com (James Tucker)
Date: Thu, 16 Apr 2009 11:24:20 +0100
Subject: [Rubygems-developers] The case of binary gems and Ruby versions.
In-Reply-To: <71166b3b0904160311w1d28a192oa81a127494b5d681@mail.gmail.com>
References: <71166b3b0904160311w1d28a192oa81a127494b5d681@mail.gmail.com>
Message-ID: <338EE626-A140-4BB7-A305-AF70CAEAC933@gmail.com>

On 16 Apr 2009, at 11:11, Luis Lavena wrote:

> Hey Guys,
>
> Been investing a lot of time in Ruby 1.9 as I move forward for updated
> RubyInstaller (One-Click) for both 1.8.6 and 1.9.x branches.
>
> Because of that, I've started to realize, even more and more, that
> distributing binary gems between versions is set to failure.
>
> Let me explain my logic with a simple example.
>
> My gem contains a extension, which I compile, cross-compile and
> package for 'i386-mswin32' (x86-mswin32) using my stock Ruby 1.8.6
> installation. I can also compile for the new RubyInstaller platform
> (mingw32) using the same approach.
>
> At the time I upload that to rubyforge, I upload the following files:
>
> my-gem-1.0.gem
> my-gem-1.0-x86-mswin32-60.gem
> my-gem-1.0-x86-mingw32.gem
>
> At this point, everything is good.
>
> Since the last 2 gems listed there are binary gems, those will be
> linking with msvcrt-ruby18.dll, which is the runtime library for Ruby
> on Windows (both MinGW and VC6). No problem so far.
>
> You wonder, where is the problem then?
>
> These gem where built for 1.8, so installing those in 1.9 will not
> fail unless I specify require_ruby_version (which is something
> rake-compiler now does).
>
> Now, the real problem becomes when I want to provide binaries for BOTH
> ruby version, since RubyGems, besides the required_ruby_version don't
> provide a mechanism to distinguish 1.8 from 1.9 gems, I end with the
> exact same gem names, with the exact same versions and platforms, thus
> overwriting previous versions.
>
> Someone suggested me that release 1.0.0 for Ruby 1.8 and 1.1.0 for
> Ruby 1.9, but that is misleading.
>
> I think we reached the point where RubyGems roadmap needs to start
> considering these cases to provide a more mature solution for us.

Agreed, I've been worried about this for a while.

>
> Regards,
> --  
> Luis Lavena
> AREA 17
> -
> Perfection in design is achieved not when there is nothing more to  
> add,
> but rather when there is nothing more to take away.
> Antoine de Saint-Exup?ry
> _______________________________________________
> Rubygems-developers mailing list
> http://rubyforge.org/projects/rubygems
> Rubygems-developers at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubygems-developers


From halostatue at gmail.com  Thu Apr 16 08:10:30 2009
From: halostatue at gmail.com (Austin Ziegler)
Date: Thu, 16 Apr 2009 08:10:30 -0400
Subject: [Rubygems-developers] [ rubygems-Bugs-25493 ] Feature: Make
	trailing zeroes in gem version significant
In-Reply-To: <20090416071553.135D3159802C@rubyforge.org>
References: <20090416071553.135D3159802C@rubyforge.org>
Message-ID: <9e7db9110904160510i2c1eb1a6h869fbe1d8c65b540@mail.gmail.com>

On Thu, Apr 16, 2009 at 3:15 AM,  <noreply at rubyforge.org> wrote:
> Summary: Feature: Make trailing zeroes in gem version significant
>
> Initial Comment:
> I'd like for 1.0.0 to be seen as > 1.0

I'm sorry, but this makes no sense to me and I suspect that it would
be significantly more confusing to users.

What's the use case for this? Why should (1.0.0 > 1.0) be true? To me,
1, 1.0, and 1.0.0 are all the same in a dotted versioning system.

-austin
-- 
Austin Ziegler * halostatue at gmail.com * http://www.halostatue.ca/
               * austin at halostatue.ca * http://www.halostatue.ca/feed/
               * austin at zieglers.ca

From hgs at dmu.ac.uk  Thu Apr 16 08:48:24 2009
From: hgs at dmu.ac.uk (Hugh Sasse)
Date: Thu, 16 Apr 2009 13:48:24 +0100 (BST)
Subject: [Rubygems-developers] [ rubygems-Bugs-25493 ] Feature: Make
 trailing zeroes in gem version significant
In-Reply-To: <9e7db9110904160510i2c1eb1a6h869fbe1d8c65b540@mail.gmail.com>
References: <20090416071553.135D3159802C@rubyforge.org>
	<9e7db9110904160510i2c1eb1a6h869fbe1d8c65b540@mail.gmail.com>
Message-ID: <alpine.LFD.2.00.0904161342150.15938@trueman.cs.cse.dmu.ac.uk>

On Thu, 16 Apr 2009, Austin Ziegler wrote:

> On Thu, Apr 16, 2009 at 3:15 AM,  <noreply at rubyforge.org> wrote:
> > Summary: Feature: Make trailing zeroes in gem version significant
> >
> > Initial Comment:
> > I'd like for 1.0.0 to be seen as > 1.0
> 
> I'm sorry, but this makes no sense to me and I suspect that it would
> be significantly more confusing to users.
> 
> What's the use case for this? Why should (1.0.0 > 1.0) be true? To me,
> 1, 1.0, and 1.0.0 are all the same in a dotted versioning system.

The only case I've heard of where this would occur is that of TeX;
I heard Donald Knuth uses successive digits of Pi and e for his
version numbers, adding one more digit for each release.  Conceivably
adding a digit which happens to do zero mus occur.  Maybe he just
adds more digits till he hits a nonzero. I don't know.

> 
> -austin

        Hugh

From noreply at rubyforge.org  Thu Apr 16 16:15:50 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 16 Apr 2009 16:15:50 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25509 ] exception using new
	generate_index in 1.3.2
Message-ID: <20090416201550.7651618580F8@rubyforge.org>

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

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Johnathan Conley (jconley)
Assigned to: Nobody (None)
Summary: exception using new generate_index in 1.3.2

Initial Comment:

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


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

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

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


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

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


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

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

From noreply at rubyforge.org  Thu Apr 16 16:40:43 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 16 Apr 2009 16:40:43 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25509 ] exception using new
	generate_index in 1.3.2
Message-ID: <20090416204044.E4113197857C@rubyforge.org>

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

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

Initial Comment:

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


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

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

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


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

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


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

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

Message:
Can you run with -V as well?

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

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

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

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

From noreply at rubyforge.org  Thu Apr 16 16:43:52 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 16 Apr 2009 16:43:52 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25493 ] Feature: Make
	trailing zeroes in gem version significant
Message-ID: <20090416204352.3F99E18580FF@rubyforge.org>

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

Category: #gem and #require methods
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Yossef Mendelssohn (ymendel)
Assigned to: Phil Hagelberg (technomancy)
Summary: Feature: Make trailing zeroes in gem version significant

Initial Comment:
I'd like for 1.0.0 to be seen as > 1.0

Patch (diffs from git show) and flog/reek output before/after the change can be seen at http://gist.github.com/96284

You can see a few specs had to change because they assume the trailing zeroes don't matter. If this is a hard requirement, then obviously my patch cannot be accepted, at least not without some transition and deprecation warning period.

The flog and reek output is included to show that as far as overall complexity and smell goes, the code is improved by this change. Only the Gem::Version#balance utility method takes a hit as its flog score jumps from 15.4 to 25.1

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

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

Message:
Echoing Austin's comments from the rubygems-developers list, what's the benefit to the users of RubyGems with this change?

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

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

From drbrain at segment7.net  Thu Apr 16 19:15:29 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Thu, 16 Apr 2009 16:15:29 -0700
Subject: [Rubygems-developers] The case of binary gems and Ruby versions.
In-Reply-To: <71166b3b0904160311w1d28a192oa81a127494b5d681@mail.gmail.com>
References: <71166b3b0904160311w1d28a192oa81a127494b5d681@mail.gmail.com>
Message-ID: <BF87CDB5-3322-4046-97FB-A8D2B9B864FF@segment7.net>

On Apr 16, 2009, at 03:11, Luis Lavena wrote:
> Been investing a lot of time in Ruby 1.9 as I move forward for updated
> RubyInstaller (One-Click) for both 1.8.6 and 1.9.x branches.
>
> Because of that, I've started to realize, even more and more, that
> distributing binary gems between versions is set to failure.
>
> Let me explain my logic with a simple example.
>
> My gem contains a extension, which I compile, cross-compile and
> package for 'i386-mswin32' (x86-mswin32) using my stock Ruby 1.8.6
> installation. I can also compile for the new RubyInstaller platform
> (mingw32) using the same approach.
>
> At the time I upload that to rubyforge, I upload the following files:
>
> my-gem-1.0.gem
> my-gem-1.0-x86-mswin32-60.gem
> my-gem-1.0-x86-mingw32.gem
>
> At this point, everything is good.
>
> Since the last 2 gems listed there are binary gems, those will be
> linking with msvcrt-ruby18.dll, which is the runtime library for Ruby
> on Windows (both MinGW and VC6). No problem so far.
>
> You wonder, where is the problem then?
>
> These gem where built for 1.8, so installing those in 1.9 will not
> fail unless I specify require_ruby_version (which is something
> rake-compiler now does).
>
> Now, the real problem becomes when I want to provide binaries for BOTH
> ruby version, since RubyGems, besides the required_ruby_version don't
> provide a mechanism to distinguish 1.8 from 1.9 gems, I end with the
> exact same gem names, with the exact same versions and platforms, thus
> overwriting previous versions.
>
> Someone suggested me that release 1.0.0 for Ruby 1.8 and 1.1.0 for
> Ruby 1.9, but that is misleading.
>
> I think we reached the point where RubyGems roadmap needs to start
> considering these cases to provide a more mature solution for us.

I see two solutions:

Package two separate gems with an indicator in the name for 1.8 vs 1.9

Package a gem with both libraries inside, and add something to  
require_paths for 1.8 vs 1.9

I prefer the later, as it'll be easiest to implement even though it  
will increase the burden on the packager.


From noreply at rubyforge.org  Thu Apr 16 19:20:02 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 16 Apr 2009 19:20:02 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25516 ] gem cleanup still
	dysfunctional in 1.3.2
Message-ID: <20090416232002.2FD2D1598075@rubyforge.org>

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

Category: `gem` commands (other)
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Brett Eisenberg (brett)
Assigned to: Nobody (None)
Summary: gem cleanup still dysfunctional in 1.3.2

Initial Comment:
[ruby at rubygems]:~% gem cleanup
Cleaning up installed gems...
Attempting to uninstall tzinfo-0.3.12
Unable to uninstall tzinfo-0.3.12:
	Gem::InstallError: cannot uninstall, check `gem list -d tzinfo`
[ruby at rubygems]:~% gem list -d tzinfo

*** LOCAL GEMS ***

tzinfo (0.3.13, 0.3.12)
    Author: Philip Ross
    Rubyforge: http://rubyforge.org/projects/tzinfo
    Homepage: http://tzinfo.rubyforge.org/
    Installed at (0.3.13): /Users/ruby/.gem/ruby/1.8
                 (0.3.12): /Users/ruby/.gem/ruby/1.8

    Daylight-savings aware timezone library
[ruby at rubygems]:~% gem uninstall tzinfo -v '= 0.3.12'
Successfully uninstalled tzinfo-0.3.12



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

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

From luislavena at gmail.com  Thu Apr 16 19:43:52 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Thu, 16 Apr 2009 20:43:52 -0300
Subject: [Rubygems-developers] The case of binary gems and Ruby versions.
In-Reply-To: <BF87CDB5-3322-4046-97FB-A8D2B9B864FF@segment7.net>
References: <71166b3b0904160311w1d28a192oa81a127494b5d681@mail.gmail.com>
	<BF87CDB5-3322-4046-97FB-A8D2B9B864FF@segment7.net>
Message-ID: <71166b3b0904161643u2bc69055l268890a247b1adf1@mail.gmail.com>

On Thu, Apr 16, 2009 at 8:15 PM, Eric Hodel <drbrain at segment7.net> wrote:
> On Apr 16, 2009, at 03:11, Luis Lavena wrote:
>>
>> Been investing a lot of time in Ruby 1.9 as I move forward for updated
>> RubyInstaller (One-Click) for both 1.8.6 and 1.9.x branches.
>>
>> Because of that, I've started to realize, even more and more, that
>> distributing binary gems between versions is set to failure.
>>
>> Let me explain my logic with a simple example.
>>
>> My gem contains a extension, which I compile, cross-compile and
>> package for 'i386-mswin32' (x86-mswin32) using my stock Ruby 1.8.6
>> installation. I can also compile for the new RubyInstaller platform
>> (mingw32) using the same approach.
>>
>> At the time I upload that to rubyforge, I upload the following files:
>>
>> my-gem-1.0.gem
>> my-gem-1.0-x86-mswin32-60.gem
>> my-gem-1.0-x86-mingw32.gem
>>
>> At this point, everything is good.
>>
>> Since the last 2 gems listed there are binary gems, those will be
>> linking with msvcrt-ruby18.dll, which is the runtime library for Ruby
>> on Windows (both MinGW and VC6). No problem so far.
>>
>> You wonder, where is the problem then?
>>
>> These gem where built for 1.8, so installing those in 1.9 will not
>> fail unless I specify require_ruby_version (which is something
>> rake-compiler now does).
>>
>> Now, the real problem becomes when I want to provide binaries for BOTH
>> ruby version, since RubyGems, besides the required_ruby_version don't
>> provide a mechanism to distinguish 1.8 from 1.9 gems, I end with the
>> exact same gem names, with the exact same versions and platforms, thus
>> overwriting previous versions.
>>
>> Someone suggested me that release 1.0.0 for Ruby 1.8 and 1.1.0 for
>> Ruby 1.9, but that is misleading.
>>
>> I think we reached the point where RubyGems roadmap needs to start
>> considering these cases to provide a more mature solution for us.
>
> I see two solutions:
>
> Package two separate gems with an indicator in the name for 1.8 vs 1.9
>

The problem is that indicating the version of ruby in the gem will not
make the installation easy.

> Package a gem with both libraries inside, and add something to require_paths
> for 1.8 vs 1.9
>
> I prefer the later, as it'll be easiest to implement even though it will
> increase the burden on the packager.
>

It will end being a huge problem.

What about adding officially support for gem-name-version-RUBY_VER-PLATFORM.gem

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

From djberg96 at gmail.com  Thu Apr 16 19:53:31 2009
From: djberg96 at gmail.com (Daniel Berger)
Date: Thu, 16 Apr 2009 17:53:31 -0600
Subject: [Rubygems-developers] The case of binary gems and Ruby versions.
In-Reply-To: <BF87CDB5-3322-4046-97FB-A8D2B9B864FF@segment7.net>
References: <71166b3b0904160311w1d28a192oa81a127494b5d681@mail.gmail.com>
	<BF87CDB5-3322-4046-97FB-A8D2B9B864FF@segment7.net>
Message-ID: <49E7C4FB.9060002@gmail.com>

Eric Hodel wrote:
> On Apr 16, 2009, at 03:11, Luis Lavena wrote:
>> Been investing a lot of time in Ruby 1.9 as I move forward for updated
>> RubyInstaller (One-Click) for both 1.8.6 and 1.9.x branches.
>>
>> Because of that, I've started to realize, even more and more, that
>> distributing binary gems between versions is set to failure.
>>
>> Let me explain my logic with a simple example.
>>
>> My gem contains a extension, which I compile, cross-compile and
>> package for 'i386-mswin32' (x86-mswin32) using my stock Ruby 1.8.6
>> installation. I can also compile for the new RubyInstaller platform
>> (mingw32) using the same approach.
>>
>> At the time I upload that to rubyforge, I upload the following files:
>>
>> my-gem-1.0.gem
>> my-gem-1.0-x86-mswin32-60.gem
>> my-gem-1.0-x86-mingw32.gem
>>
>> At this point, everything is good.
>>
>> Since the last 2 gems listed there are binary gems, those will be
>> linking with msvcrt-ruby18.dll, which is the runtime library for Ruby
>> on Windows (both MinGW and VC6). No problem so far.
>>
>> You wonder, where is the problem then?
>>
>> These gem where built for 1.8, so installing those in 1.9 will not
>> fail unless I specify require_ruby_version (which is something
>> rake-compiler now does).
>>
>> Now, the real problem becomes when I want to provide binaries for BOTH
>> ruby version, since RubyGems, besides the required_ruby_version don't
>> provide a mechanism to distinguish 1.8 from 1.9 gems, I end with the
>> exact same gem names, with the exact same versions and platforms, thus
>> overwriting previous versions.
>>
>> Someone suggested me that release 1.0.0 for Ruby 1.8 and 1.1.0 for
>> Ruby 1.9, but that is misleading.
>>
>> I think we reached the point where RubyGems roadmap needs to start
>> considering these cases to provide a more mature solution for us.
> 
> I see two solutions:
> 
> Package two separate gems with an indicator in the name for 1.8 vs 1.9
> 
> Package a gem with both libraries inside, and add something to 
> require_paths for 1.8 vs 1.9

Could this be automated somehow? Can we dynamically set the linkage 
within a gem on Windows based on the version of Ruby that's running it?

Regards,

Dan

From noreply at rubyforge.org  Thu Apr 16 20:24:40 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 16 Apr 2009 20:24:40 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25509 ] exception using new
	generate_index in 1.3.2
Message-ID: <20090417002440.71B8E159802B@rubyforge.org>

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

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

Initial Comment:

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


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

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

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


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

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


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

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

Message:

Here is my latest run with -V

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

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


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

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

Message:
Can you run with -V as well?

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

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

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

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

From luislavena at gmail.com  Thu Apr 16 20:33:21 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Thu, 16 Apr 2009 21:33:21 -0300
Subject: [Rubygems-developers] The case of binary gems and Ruby versions.
In-Reply-To: <49E7C4FB.9060002@gmail.com>
References: <71166b3b0904160311w1d28a192oa81a127494b5d681@mail.gmail.com>
	<BF87CDB5-3322-4046-97FB-A8D2B9B864FF@segment7.net>
	<49E7C4FB.9060002@gmail.com>
Message-ID: <71166b3b0904161733k3bc2e4afja6427cb426d917bf@mail.gmail.com>

On Thu, Apr 16, 2009 at 8:53 PM, Daniel Berger <djberg96 at gmail.com> wrote:
> Eric Hodel wrote:
>>
>> On Apr 16, 2009, at 03:11, Luis Lavena wrote:
>>>
>>> Been investing a lot of time in Ruby 1.9 as I move forward for updated
>>> RubyInstaller (One-Click) for both 1.8.6 and 1.9.x branches.
>>>
>>> Because of that, I've started to realize, even more and more, that
>>> distributing binary gems between versions is set to failure.
>>>
>>> Let me explain my logic with a simple example.
>>>
>>> My gem contains a extension, which I compile, cross-compile and
>>> package for 'i386-mswin32' (x86-mswin32) using my stock Ruby 1.8.6
>>> installation. I can also compile for the new RubyInstaller platform
>>> (mingw32) using the same approach.
>>>
>>> At the time I upload that to rubyforge, I upload the following files:
>>>
>>> my-gem-1.0.gem
>>> my-gem-1.0-x86-mswin32-60.gem
>>> my-gem-1.0-x86-mingw32.gem
>>>
>>> At this point, everything is good.
>>>
>>> Since the last 2 gems listed there are binary gems, those will be
>>> linking with msvcrt-ruby18.dll, which is the runtime library for Ruby
>>> on Windows (both MinGW and VC6). No problem so far.
>>>
>>> You wonder, where is the problem then?
>>>
>>> These gem where built for 1.8, so installing those in 1.9 will not
>>> fail unless I specify require_ruby_version (which is something
>>> rake-compiler now does).
>>>
>>> Now, the real problem becomes when I want to provide binaries for BOTH
>>> ruby version, since RubyGems, besides the required_ruby_version don't
>>> provide a mechanism to distinguish 1.8 from 1.9 gems, I end with the
>>> exact same gem names, with the exact same versions and platforms, thus
>>> overwriting previous versions.
>>>
>>> Someone suggested me that release 1.0.0 for Ruby 1.8 and 1.1.0 for
>>> Ruby 1.9, but that is misleading.
>>>
>>> I think we reached the point where RubyGems roadmap needs to start
>>> considering these cases to provide a more mature solution for us.
>>
>> I see two solutions:
>>
>> Package two separate gems with an indicator in the name for 1.8 vs 1.9
>>
>> Package a gem with both libraries inside, and add something to
>> require_paths for 1.8 vs 1.9
>
> Could this be automated somehow? Can we dynamically set the linkage within a
> gem on Windows based on the version of Ruby that's running it?
>

The extension link to so many different functions inside libruby that
perform the linkeage is kind of impossible.

An alternative will be build two versions of the same extension
(my_ext18 and my_ext19) and load it accordingly, but that's another
compilation complication that developers will need to work out.

-- 
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 ryand-ruby at zenspider.com  Thu Apr 16 20:44:30 2009
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Thu, 16 Apr 2009 17:44:30 -0700
Subject: [Rubygems-developers] The case of binary gems and Ruby versions.
In-Reply-To: <BF87CDB5-3322-4046-97FB-A8D2B9B864FF@segment7.net>
References: <71166b3b0904160311w1d28a192oa81a127494b5d681@mail.gmail.com>
	<BF87CDB5-3322-4046-97FB-A8D2B9B864FF@segment7.net>
Message-ID: <CB0516CD-7196-4F33-B762-DFDF018F421A@zenspider.com>


On Apr 16, 2009, at 16:15 , Eric Hodel wrote:

> I see two solutions:
>
> Package two separate gems with an indicator in the name for 1.8 vs 1.9
>
> Package a gem with both libraries inside, and add something to  
> require_paths for 1.8 vs 1.9

or:

package the gem normally (but specifying what version of ruby should  
be mandatory) and when it uploads it goes to a versioned depot. pure  
ruby gems go up to a shared depot, binaries go to a versioned one. gem  
fetch can deal with this since it has the spec already. I think this  
should be transparent... NOT as another gem source.


From jeremy at hinegardner.org  Thu Apr 16 22:07:56 2009
From: jeremy at hinegardner.org (Jeremy Hinegardner)
Date: Thu, 16 Apr 2009 20:07:56 -0600
Subject: [Rubygems-developers] The case of binary gems and Ruby	versions.
In-Reply-To: <CB0516CD-7196-4F33-B762-DFDF018F421A@zenspider.com>
References: <71166b3b0904160311w1d28a192oa81a127494b5d681@mail.gmail.com>
	<BF87CDB5-3322-4046-97FB-A8D2B9B864FF@segment7.net>
	<CB0516CD-7196-4F33-B762-DFDF018F421A@zenspider.com>
Message-ID: <20090417020756.GH4364@hinegardner.org>

On Thu, Apr 16, 2009 at 05:44:30PM -0700, Ryan Davis wrote:
>
> On Apr 16, 2009, at 16:15 , Eric Hodel wrote:
>
>> I see two solutions:
>>
>> Package two separate gems with an indicator in the name for 1.8 vs 1.9
>>
>> Package a gem with both libraries inside, and add something to 
>> require_paths for 1.8 vs 1.9
>
> or:
>
> package the gem normally (but specifying what version of ruby should be 
> mandatory) and when it uploads it goes to a versioned depot. pure ruby gems 
> go up to a shared depot, binaries go to a versioned one. gem fetch can deal 
> with this since it has the spec already. I think this should be 
> transparent... NOT as another gem source.

This was my thought too.  Solve this in the repo.  Instead of having

    gems/
    latest_specs.4.8.gz
    ...

Have

    gems/
    gems/1.8/
    gems/1.9/
    latest_specs.4.8.gz

Or something along those lines.

enjoy,

-jeremy

-- 
========================================================================
 Jeremy Hinegardner                              jeremy at hinegardner.org 


From luislavena at gmail.com  Thu Apr 16 22:17:23 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Thu, 16 Apr 2009 23:17:23 -0300
Subject: [Rubygems-developers] The case of binary gems and Ruby versions.
In-Reply-To: <20090417020756.GH4364@hinegardner.org>
References: <71166b3b0904160311w1d28a192oa81a127494b5d681@mail.gmail.com>
	<BF87CDB5-3322-4046-97FB-A8D2B9B864FF@segment7.net>
	<CB0516CD-7196-4F33-B762-DFDF018F421A@zenspider.com>
	<20090417020756.GH4364@hinegardner.org>
Message-ID: <71166b3b0904161917j7a6d469di987db895697095ec@mail.gmail.com>

On Thu, Apr 16, 2009 at 11:07 PM, Jeremy Hinegardner
<jeremy at hinegardner.org> wrote:
> On Thu, Apr 16, 2009 at 05:44:30PM -0700, Ryan Davis wrote:
>>
>> On Apr 16, 2009, at 16:15 , Eric Hodel wrote:
>>
>>> I see two solutions:
>>>
>>> Package two separate gems with an indicator in the name for 1.8 vs 1.9
>>>
>>> Package a gem with both libraries inside, and add something to
>>> require_paths for 1.8 vs 1.9
>>
>> or:
>>
>> package the gem normally (but specifying what version of ruby should be
>> mandatory) and when it uploads it goes to a versioned depot. pure ruby gems
>> go up to a shared depot, binaries go to a versioned one. gem fetch can deal
>> with this since it has the spec already. I think this should be
>> transparent... NOT as another gem source.
>
> This was my thought too. ?Solve this in the repo. ?Instead of having
>
> ? ?gems/
> ? ?latest_specs.4.8.gz
> ? ?...
>
> Have
>
> ? ?gems/
> ? ?gems/1.8/
> ? ?gems/1.9/
> ? ?latest_specs.4.8.gz
>
> Or something along those lines.
>
> enjoy,
>
> -jeremy
>

I agree with both, this should be solved from the server perspective, however:

1) I cannot generate both 1.8 and 1.9 cross compiled gems from my
package in an automated way, since the gem will override the previous
generated one.

2) When upload the file to rubyforge (either web-based or rubyforge
gem) I cannot upload 2 files with the same name.

-- 
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  Thu Apr 16 22:53:29 2009
From: djberg96 at gmail.com (Daniel Berger)
Date: Thu, 16 Apr 2009 20:53:29 -0600
Subject: [Rubygems-developers] The case of binary gems and Ruby versions.
In-Reply-To: <71166b3b0904161917j7a6d469di987db895697095ec@mail.gmail.com>
References: <71166b3b0904160311w1d28a192oa81a127494b5d681@mail.gmail.com>	<BF87CDB5-3322-4046-97FB-A8D2B9B864FF@segment7.net>	<CB0516CD-7196-4F33-B762-DFDF018F421A@zenspider.com>	<20090417020756.GH4364@hinegardner.org>
	<71166b3b0904161917j7a6d469di987db895697095ec@mail.gmail.com>
Message-ID: <49E7EF29.5010701@gmail.com>

Luis Lavena wrote:
> On Thu, Apr 16, 2009 at 11:07 PM, Jeremy Hinegardner
> <jeremy at hinegardner.org> wrote:
>> On Thu, Apr 16, 2009 at 05:44:30PM -0700, Ryan Davis wrote:
>>> On Apr 16, 2009, at 16:15 , Eric Hodel wrote:
>>>
>>>> I see two solutions:
>>>>
>>>> Package two separate gems with an indicator in the name for 1.8 vs 1.9
>>>>
>>>> Package a gem with both libraries inside, and add something to
>>>> require_paths for 1.8 vs 1.9
>>> or:
>>>
>>> package the gem normally (but specifying what version of ruby should be
>>> mandatory) and when it uploads it goes to a versioned depot. pure ruby gems
>>> go up to a shared depot, binaries go to a versioned one. gem fetch can deal
>>> with this since it has the spec already. I think this should be
>>> transparent... NOT as another gem source.
>> This was my thought too.  Solve this in the repo.  Instead of having
>>
>>    gems/
>>    latest_specs.4.8.gz
>>    ...
>>
>> Have
>>
>>    gems/
>>    gems/1.8/
>>    gems/1.9/
>>    latest_specs.4.8.gz
>>
>> Or something along those lines.
>>
>> enjoy,
>>
>> -jeremy
>>
> 
> I agree with both, this should be solved from the server perspective, however:
> 
> 1) I cannot generate both 1.8 and 1.9 cross compiled gems from my
> package in an automated way, since the gem will override the previous
> generated one.

I think this is solvable with a Rake task. I know it's a bit of a pain, 
but it's not _that_ bad.

> 2) When upload the file to rubyforge (either web-based or rubyforge
> gem) I cannot upload 2 files with the same name.

This will be a problem, and we'll have to get Tom involved. On the "Add 
Release" screen we'll need to add a "Ruby Branch" drop down menu. So 
long as the same branch isn't re-used, it should work.

Personally I'd be in favor of replacing the "Processor" drop down, as it 
is completely useless as far as I can tell.

Regards,

Dan

From cfis at savagexi.com  Fri Apr 17 00:10:20 2009
From: cfis at savagexi.com (Charlie Savage)
Date: Thu, 16 Apr 2009 22:10:20 -0600
Subject: [Rubygems-developers] The case of binary gems and Ruby versions.
In-Reply-To: <71166b3b0904161643u2bc69055l268890a247b1adf1@mail.gmail.com>
References: <71166b3b0904160311w1d28a192oa81a127494b5d681@mail.gmail.com>	<BF87CDB5-3322-4046-97FB-A8D2B9B864FF@segment7.net>
	<71166b3b0904161643u2bc69055l268890a247b1adf1@mail.gmail.com>
Message-ID: <49E8012C.7080708@savagexi.com>

> 
> What about adding officially support for gem-name-version-RUBY_VER-PLATFORM.gem

I agree with Luis's proposal.  It has some nice benefits:

* Its fairly clear how it works
* Its builds on a precedent already set by ruby gems (i.e., include the
platform name in a binary gem name)
* It doesn't add any additional burden on gem developers
* It conceptually makes sense in that my-gem-1.8-mswin32 is a different
gem than my-gem-1.9-mswin32 or my-gem-1.8-linux.

In contrast, the idea of having a single gem containing multiple
binaries seems a more difficult road to go down.  How would the right
gem get loaded?  How would that work across Ruby versions?  How would it
work across all OSes?  What binaries would get included?  Is this per
platform (so 1.8 windows gem and 1.9 windows gem) or per ruby version
(1.8 windows gem and 1.8 linux gem)?  How would a gem developer manage
to actually build such a gem with multiple binaries in it (seems like it
could be tricky to setup the right build environment).  What if you
decide to stop supporting Ruby 1.8 - how would a Ruby 1.8 installation
realize it has to pull version 1 of your gem but not version 2?  Etc., etc.

And out of curiosity, is there a precedent of a packaging system making
this choice (I guess COM with multiple interfaces - but that didn't work
so well)?

Obviously versioning is a near impossible problem to solve, so there
probably isn't a "perfect" answer, but option #1 seems more appealing to me.

Thanks,

Charlie

From thewoolleyman at gmail.com  Sun Apr 19 03:48:00 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Sun, 19 Apr 2009 00:48:00 -0700
Subject: [Rubygems-developers] Problem after installing RubyGems 1.3.2:
	"RubyGems 1.2+ index not found for... nothing???"
Message-ID: <e3af97510904190048x72fbba3fj29e03d7598f8419a@mail.gmail.com>

It's degrading my performance, but doesn't tell me why :(

Is this a bug?

chadmac:webgen woolley$ sudo gem install webgen-0.5.8.20090419.gem
Password:
WARNING:  RubyGems 1.2+ index not found for:
	

RubyGems will revert to legacy indexes degrading performance.
Bulk updating Gem source index for: http://gems.rubyforge.org/
Bulk updating Gem source index for: http://gems.github.com/
Bulk updating Gem source index for: http://gems.rubyforge.org/
Bulk updating Gem source index for: http://gems.github.com/


-- Chad

From noreply at rubyforge.org  Sun Apr 19 17:29:59 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun, 19 Apr 2009 17:29:59 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25541 ] Ruby sqlite/gem
	error: Could not load sqlite adapter
Message-ID: <20090419212959.B668C1858134@rubyforge.org>

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

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: John  Spanton (jhs408)
Assigned to: Nobody (None)
Summary: Ruby sqlite/gem error: Could not load sqlite adapter

Initial Comment:
Executing sample program on windows xp syste,.

The sample  "c:\tmp'Test_sequel.rb"   generates the error: 
  Could not load sqlite adapter. 

Yet, when the example is executed in the sequel directory,  
  no error occur, sample gives the proper results.

The sqlite3.dll is located in the PATH. 

It appears that rubygems is not able to locate sqlite.rb in the 
directory:C:\Ruby\lib\ruby\gems\1.8\gems\sequel-2.12.0\lib\sequel 
\adapters 
when the sample program is executed from c:\tmp 

Which leads me to suspect that rubygem is having a problem 
or the is a coding problem in sequel or rubygems.

Any suggestion or changes to the sample to resolve the error. 
Thanks for the help, 

John email:  jhs408 at gmail.com

------------------------------------ 
Windows XP SP3 
Using  ruby 1.8.7,   gem 1.3.2,   sqlite3-ruby 1.2.4,    sequel 2.12.0 
product 
Environment set:  RUBYOPT=rubygems 
PATH=c:\tools\sqlite3   ... 
-----running sample----> c:\tmp\test_sqlite.rb -------------- 
require 'sequel' 
DB = Sequel.sqlite("test-sequel.db") 
# create an items table 
DB.create_table :items do 
  primary_key :id 
  column :name, :text 
  column :price, :float 
end 
# create a dataset from the items table 
items = DB[:items] 
# populate the table 
items << {:name => 'abc', :price => rand * 100} 
items << {:name => 'def', :price => rand * 100} 
items << {:name => 'ghi', :price => rand * 100} 
# print out the number of records 
puts "Item count: #{ items.count }" 
# print out the records in descending order by price 
items.reverse_order(:price).print 
# print out the average price 
puts "The average price is: #{ items.avg :price }" 

------Error Msg---- 
C:\tmp>test_sequel.rb 
C:/ruby/lib/ruby/gems/1.8/gems/sequel-2.11.0/lib/sequel_core/ 
database.rb:105:in `adapter_class': Could not load sqlite a 
dapter: (Sequel::Error::AdapterNotFound) 
  no such file to load -- sqlite3 
        from C:/ruby/lib/ruby/gems/1.8/gems/sequel-2.11.0/lib/ 
sequel_core/database.rb:141:in `connect' 
        from C:/ruby/lib/ruby/gems/1.8/gems/sequel-2.11.0/lib/ 
sequel_core.rb:68:in `connect' 
        from C:/ruby/lib/ruby/gems/1.8/gems/sequel-2.11.0/lib/ 
sequel_core.rb:157:in `adapter_method' 
        from (eval):1:in `sqlite' 
        from C:/tmp/test_sequel.rb:7 



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

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

From noreply at rubyforge.org  Sun Apr 19 17:41:47 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun, 19 Apr 2009 17:41:47 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25541 ] Ruby sqlite/gem
	error: Could not load sqlite adapter
Message-ID: <20090419214147.8FAB618581E8@rubyforge.org>

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

Category: None
Group: None
Status: Open
>Resolution: Rejected
Priority: 3
Submitted By: John  Spanton (jhs408)
Assigned to: Nobody (None)
Summary: Ruby sqlite/gem error: Could not load sqlite adapter

Initial Comment:
Executing sample program on windows xp syste,.

The sample  "c:\tmp'Test_sequel.rb"   generates the error: 
  Could not load sqlite adapter. 

Yet, when the example is executed in the sequel directory,  
  no error occur, sample gives the proper results.

The sqlite3.dll is located in the PATH. 

It appears that rubygems is not able to locate sqlite.rb in the 
directory:C:\Ruby\lib\ruby\gems\1.8\gems\sequel-2.12.0\lib\sequel 
\adapters 
when the sample program is executed from c:\tmp 

Which leads me to suspect that rubygem is having a problem 
or the is a coding problem in sequel or rubygems.

Any suggestion or changes to the sample to resolve the error. 
Thanks for the help, 

John email:  jhs408 at gmail.com

------------------------------------ 
Windows XP SP3 
Using  ruby 1.8.7,   gem 1.3.2,   sqlite3-ruby 1.2.4,    sequel 2.12.0 
product 
Environment set:  RUBYOPT=rubygems 
PATH=c:\tools\sqlite3   ... 
-----running sample----> c:\tmp\test_sqlite.rb -------------- 
require 'sequel' 
DB = Sequel.sqlite("test-sequel.db") 
# create an items table 
DB.create_table :items do 
  primary_key :id 
  column :name, :text 
  column :price, :float 
end 
# create a dataset from the items table 
items = DB[:items] 
# populate the table 
items << {:name => 'abc', :price => rand * 100} 
items << {:name => 'def', :price => rand * 100} 
items << {:name => 'ghi', :price => rand * 100} 
# print out the number of records 
puts "Item count: #{ items.count }" 
# print out the records in descending order by price 
items.reverse_order(:price).print 
# print out the average price 
puts "The average price is: #{ items.avg :price }" 

------Error Msg---- 
C:\tmp>test_sequel.rb 
C:/ruby/lib/ruby/gems/1.8/gems/sequel-2.11.0/lib/sequel_core/ 
database.rb:105:in `adapter_class': Could not load sqlite a 
dapter: (Sequel::Error::AdapterNotFound) 
  no such file to load -- sqlite3 
        from C:/ruby/lib/ruby/gems/1.8/gems/sequel-2.11.0/lib/ 
sequel_core/database.rb:141:in `connect' 
        from C:/ruby/lib/ruby/gems/1.8/gems/sequel-2.11.0/lib/ 
sequel_core.rb:68:in `connect' 
        from C:/ruby/lib/ruby/gems/1.8/gems/sequel-2.11.0/lib/ 
sequel_core.rb:157:in `adapter_method' 
        from (eval):1:in `sqlite' 
        from C:/tmp/test_sequel.rb:7 



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

>Comment By: Luis Lavena (luislavena)
Date: 2009-04-19 18:41

Message:
First, this should have been reported to Sequel and Sqlite3 project, not rubygems.

I'll check if sqlite3-ruby gem was compiled properly for your platform, since looks like you're using windows and there is no binary for sqlite3-ruby out there yet.

I just did the exact same test:

Luis at KEORE (D:\Users\Luis\Desktop)
$ ruby test.rb
Item count: 3
Sequel::Dataset#print is deprecated and will be removed in Sequel 3.0.  require "sequel/extensions/pretty_table" first.
D:/Users/Luis/.gem/ruby/1.8/gems/sequel-2.12.0/lib/sequel/deprecated.rb:245:in `print'
test.rb:20
Sequel::PrettyTable#print is deprecated and will be removed in Sequel 3.0.  require "sequel/extensions/pretty_table" first.
D:/Users/Luis/.gem/ruby/1.8/gems/sequel-2.12.0/lib/sequel/deprecated.rb:304:in `print'
D:/Users/Luis/.gem/ruby/1.8/gems/sequel-2.12.0/lib/sequel/deprecated.rb:246:in `print'
test.rb:20
+--+----+----------------+
|id|name|price           |
+--+----+----------------+
| 3|ghi |         76.3733|
| 2|def |         60.0457|
| 1|abc |         26.7445|
+--+----+----------------+
The average price is: 54.3878553800661

Luis at KEORE (D:\Users\Luis\Desktop)
$ gem --version
1.3.2

Luis at KEORE (D:\Users\Luis\Desktop)
$ ruby -v
ruby 1.8.6 (2009-03-31 patchlevel 368) [i386-mingw32]

sqlite3-ruby (1.2.4)
sequel (2.12.0)


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

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

From noreply at rubyforge.org  Sun Apr 19 17:46:16 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun, 19 Apr 2009 17:46:16 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25516 ] gem cleanup still
	dysfunctional in 1.3.2
Message-ID: <20090419214616.361711978571@rubyforge.org>

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

Category: `gem` commands (other)
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Brett Eisenberg (brett)
Assigned to: Nobody (None)
Summary: gem cleanup still dysfunctional in 1.3.2

Initial Comment:
[ruby at rubygems]:~% gem cleanup
Cleaning up installed gems...
Attempting to uninstall tzinfo-0.3.12
Unable to uninstall tzinfo-0.3.12:
	Gem::InstallError: cannot uninstall, check `gem list -d tzinfo`
[ruby at rubygems]:~% gem list -d tzinfo

*** LOCAL GEMS ***

tzinfo (0.3.13, 0.3.12)
    Author: Philip Ross
    Rubyforge: http://rubyforge.org/projects/tzinfo
    Homepage: http://tzinfo.rubyforge.org/
    Installed at (0.3.13): /Users/ruby/.gem/ruby/1.8
                 (0.3.12): /Users/ruby/.gem/ruby/1.8

    Daylight-savings aware timezone library
[ruby at rubygems]:~% gem uninstall tzinfo -v '= 0.3.12'
Successfully uninstalled tzinfo-0.3.12



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

>Comment By: Luis Lavena (luislavena)
Date: 2009-04-19 18:46

Message:
Can you try running the exact same command with debug information turned on?

gem cleanup --debug


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

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

From noreply at rubyforge.org  Sun Apr 19 19:46:24 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun, 19 Apr 2009 19:46:24 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25516 ] gem cleanup still
	dysfunctional in 1.3.2
Message-ID: <20090419234624.C6E03197828E@rubyforge.org>

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

Category: `gem` commands (other)
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Brett Eisenberg (brett)
Assigned to: Nobody (None)
Summary: gem cleanup still dysfunctional in 1.3.2

Initial Comment:
[ruby at rubygems]:~% gem cleanup
Cleaning up installed gems...
Attempting to uninstall tzinfo-0.3.12
Unable to uninstall tzinfo-0.3.12:
	Gem::InstallError: cannot uninstall, check `gem list -d tzinfo`
[ruby at rubygems]:~% gem list -d tzinfo

*** LOCAL GEMS ***

tzinfo (0.3.13, 0.3.12)
    Author: Philip Ross
    Rubyforge: http://rubyforge.org/projects/tzinfo
    Homepage: http://tzinfo.rubyforge.org/
    Installed at (0.3.13): /Users/ruby/.gem/ruby/1.8
                 (0.3.12): /Users/ruby/.gem/ruby/1.8

    Daylight-savings aware timezone library
[ruby at rubygems]:~% gem uninstall tzinfo -v '= 0.3.12'
Successfully uninstalled tzinfo-0.3.12



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

>Comment By: Brett Eisenberg (brett)
Date: 2009-04-19 19:46

Message:
[ruby at rubygems]:~% gem cleanup --debug
Exception `NameError' at
/opt/local/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:161
- uninitialized constant Gem::Commands::CleanupCommand
Cleaning up installed gems...
Attempting to uninstall memcache-client-1.7.1
Exception `Gem::InstallError' at
/opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:76
- cannot uninstall, check `gem list -d memcache-client`
Unable to uninstall memcache-client-1.7.1:
	Gem::InstallError: cannot uninstall, check `gem list -d
memcache-client`
Attempting to uninstall ruby-openid-2.1.2
Exception `Gem::InstallError' at
/opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:76
- cannot uninstall, check `gem list -d ruby-openid`
Unable to uninstall ruby-openid-2.1.2:
	Gem::InstallError: cannot uninstall, check `gem list -d
ruby-openid`
Attempting to uninstall rspec-1.2.2
Exception `Gem::InstallError' at
/opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:76
- cannot uninstall, check `gem list -d rspec`
Unable to uninstall rspec-1.2.2:
	Gem::InstallError: cannot uninstall, check `gem list -d rspec`
Attempting to uninstall fastthread-1.0.6
Exception `Gem::InstallError' at
/opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:76
- cannot uninstall, check `gem list -d fastthread`
Unable to uninstall fastthread-1.0.6:
	Gem::InstallError: cannot uninstall, check `gem list -d
fastthread`
Attempting to uninstall json-1.1.3
Exception `Gem::InstallError' at
/opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:76
- cannot uninstall, check `gem list -d json`
Unable to uninstall json-1.1.3:
	Gem::InstallError: cannot uninstall, check `gem list -d json`
Attempting to uninstall cucumber-0.2.3
Exception `Gem::InstallError' at
/opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:76
- cannot uninstall, check `gem list -d cucumber`
Unable to uninstall cucumber-0.2.3:
	Gem::InstallError: cannot uninstall, check `gem list -d
cucumber`
Attempting to uninstall hoe-1.12.1
Exception `Gem::InstallError' at
/opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:76
- cannot uninstall, check `gem list -d hoe`
Unable to uninstall hoe-1.12.1:
	Gem::InstallError: cannot uninstall, check `gem list -d hoe`
Attempting to uninstall thoughtbot-factory_girl-1.2.0
Exception `Gem::InstallError' at
/opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:76
- cannot uninstall, check `gem list -d thoughtbot-factory_girl`
Unable to uninstall thoughtbot-factory_girl-1.2.0:
	Gem::InstallError: cannot uninstall, check `gem list -d
thoughtbot-factory_girl`
Attempting to uninstall rake-compiler-0.4.0
Exception `Gem::InstallError' at
/opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:76
- cannot uninstall, check `gem list -d rake-compiler`
Unable to uninstall rake-compiler-0.4.0:
	Gem::InstallError: cannot uninstall, check `gem list -d
rake-compiler`
Clean Up Complete


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

Comment By: Luis Lavena (luislavena)
Date: 2009-04-19 17:46

Message:
Can you try running the exact same command with debug information turned on?

gem cleanup --debug


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

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

From noreply at rubyforge.org  Mon Apr 20 14:15:26 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Mon, 20 Apr 2009 14:15:26 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25555 ] gem uninstall does
	not handle binaries in non-system locations
Message-ID: <20090420181526.CDD2C18580F5@rubyforge.org>

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

Category: `gem` commands (other)
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Brett Eisenberg (brett)
Assigned to: Nobody (None)
Summary: gem uninstall does not handle binaries in non-system locations

Initial Comment:
[ruby at rubygems]:~% gem uninstall aws-s3
Remove executables:
	s3sh

in addition to the gem? [Yn]  Y
ERROR:  While executing gem ... (Gem::FilePermissionError)
    You don't have write permissions into the /opt/local/bin directory.
[ruby at rubygems]:~% which s3sh
/Users/ruby/.gem/ruby/1.8/bin/s3sh

--

[ruby at rubygems]:~% gem uninstall aws-s3 --debug
Exception `NameError' at /opt/local/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:161 - uninitialized constant Gem::Commands::UninstallCommand
Remove executables:
	s3sh

in addition to the gem? [Yn]  Y
Exception `Gem::FilePermissionError' at /opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:154 - You don't have write permissions into the /opt/local/bin directory.
ERROR:  While executing gem ... (Gem::FilePermissionError)
    You don't have write permissions into the /opt/local/bin directory.
	/opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:154:in `remove_executables'
	/opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:109:in `uninstall_gem'
	/opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:109:in `each'
	/opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:109:in `uninstall_gem'
	/opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:95:in `uninstall'
	/opt/local/lib/ruby/site_ruby/1.8/rubygems/commands/uninstall_command.rb:73:in `execute'
	/opt/local/lib/ruby/site_ruby/1.8/rubygems/commands/uninstall_command.rb:71:in `each'
	/opt/local/lib/ruby/site_ruby/1.8/rubygems/commands/uninstall_command.rb:71:in `execute'
	/opt/local/lib/ruby/site_ruby/1.8/rubygems/command.rb:254:in `invoke'
	/opt/local/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:132:in `process_args'
	/opt/local/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:102:in `run'
	/opt/local/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:58:in `run'
	/opt/local/bin/gem:21



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

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

From drbrain at segment7.net  Mon Apr 20 20:13:54 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Mon, 20 Apr 2009 17:13:54 -0700
Subject: [Rubygems-developers] Problem after installing RubyGems 1.3.2:
	"RubyGems 1.2+ index not found for... nothing???"
In-Reply-To: <e3af97510904190048x72fbba3fj29e03d7598f8419a@mail.gmail.com>
References: <e3af97510904190048x72fbba3fj29e03d7598f8419a@mail.gmail.com>
Message-ID: <21A99311-42B4-41A1-AE25-589FC709551C@segment7.net>

On Apr 19, 2009, at 00:48, Chad Woolley wrote:

> It's degrading my performance, but doesn't tell me why :(
>
> Is this a bug?
>
> chadmac:webgen woolley$ sudo gem install webgen-0.5.8.20090419.gem
> Password:
> WARNING:  RubyGems 1.2+ index not found for:
> 	
>
> RubyGems will revert to legacy indexes degrading performance.
> Bulk updating Gem source index for: http://gems.rubyforge.org/
> Bulk updating Gem source index for: http://gems.github.com/
> Bulk updating Gem source index for: http://gems.rubyforge.org/
> Bulk updating Gem source index for: http://gems.github.com/

What happens when you run with -V?

From thewoolleyman at gmail.com  Mon Apr 20 21:26:05 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Mon, 20 Apr 2009 18:26:05 -0700
Subject: [Rubygems-developers] Problem after installing RubyGems 1.3.2:
	"RubyGems 1.2+ index not found for... nothing???"
In-Reply-To: <21A99311-42B4-41A1-AE25-589FC709551C@segment7.net>
References: <e3af97510904190048x72fbba3fj29e03d7598f8419a@mail.gmail.com> 
	<21A99311-42B4-41A1-AE25-589FC709551C@segment7.net>
Message-ID: <e3af97510904201826p239142ffl3725ecff43772d2b@mail.gmail.com>

This was the first install after my upgrade, I don't get the message anymore.

In order to reproduce, I think I would have to revert to 1.3.1,
regenerate my indexes, then upgrade to 1.3.2, then run the install
command with -V.

Right?

On Mon, Apr 20, 2009 at 5:13 PM, Eric Hodel <drbrain at segment7.net> wrote:
> On Apr 19, 2009, at 00:48, Chad Woolley wrote:
>
>> It's degrading my performance, but doesn't tell me why :(
>>
>> Is this a bug?
>>
>> chadmac:webgen woolley$ sudo gem install webgen-0.5.8.20090419.gem
>> Password:
>> WARNING: ?RubyGems 1.2+ index not found for:
>>
>>
>> RubyGems will revert to legacy indexes degrading performance.
>> Bulk updating Gem source index for: http://gems.rubyforge.org/
>> Bulk updating Gem source index for: http://gems.github.com/
>> Bulk updating Gem source index for: http://gems.rubyforge.org/
>> Bulk updating Gem source index for: http://gems.github.com/
>
> What happens when you run with -V?
> _______________________________________________
> Rubygems-developers mailing list
> http://rubyforge.org/projects/rubygems
> Rubygems-developers at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubygems-developers
>

From noreply at rubyforge.org  Tue Apr 21 02:30:33 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue, 21 Apr 2009 02:30:33 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25564 ] Time.today not
	working with 1.3.2
Message-ID: <20090421063033.10F1818581E1@rubyforge.org>

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

Category: other
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Emanuele Vicentini (emanuelev)
Assigned to: Nobody (None)
Summary: Time.today not working with 1.3.2

Initial Comment:
$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.2
  - RUBY VERSION: 1.8.6 (2008-03-03 patchlevel 114) [universal-darwin9.0]
  - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8
  - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - universal-darwin-9
  - GEM PATHS:
     - /Library/Ruby/Gems/1.8
     - /Users/emanuele/.gem/ruby/1.8
     - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/


Running the following gives problem:

$ ruby -rubygems -e 'puts Time.today'
/Library/Ruby/Site/1.8/rubygems/specification.rb:16:in `today': undefined local variable or method `location_of_caller' for Time:Class (NameError)
	from -e:1


Noted this even on an Ubuntu GNU/Linux box with Ruby 1.8.7. On both machines there are some gems (Rails, Rake, Rack and many others), but the load paths do not seem to be messed up:

$ ruby -rubygems -e 'puts Time.today rescue nil; puts $:'
/Library/Ruby/Site/1.8
/Library/Ruby/Site/1.8/powerpc-darwin9.0
/Library/Ruby/Site/1.8/universal-darwin9.0
/Library/Ruby/Site
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/powerpc-darwin9.0
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin9.0
.



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

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

From noreply at rubyforge.org  Tue Apr 21 09:03:28 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue, 21 Apr 2009 09:03:28 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25564 ] Time.today not
	working with 1.3.2
Message-ID: <20090421130329.0A34D18581E2@rubyforge.org>

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

Category: other
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Emanuele Vicentini (emanuelev)
Assigned to: Nobody (None)
Summary: Time.today not working with 1.3.2

Initial Comment:
$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.2
  - RUBY VERSION: 1.8.6 (2008-03-03 patchlevel 114) [universal-darwin9.0]
  - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8
  - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - universal-darwin-9
  - GEM PATHS:
     - /Library/Ruby/Gems/1.8
     - /Users/emanuele/.gem/ruby/1.8
     - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/


Running the following gives problem:

$ ruby -rubygems -e 'puts Time.today'
/Library/Ruby/Site/1.8/rubygems/specification.rb:16:in `today': undefined local variable or method `location_of_caller' for Time:Class (NameError)
	from -e:1


Noted this even on an Ubuntu GNU/Linux box with Ruby 1.8.7. On both machines there are some gems (Rails, Rake, Rack and many others), but the load paths do not seem to be messed up:

$ ruby -rubygems -e 'puts Time.today rescue nil; puts $:'
/Library/Ruby/Site/1.8
/Library/Ruby/Site/1.8/powerpc-darwin9.0
/Library/Ruby/Site/1.8/universal-darwin9.0
/Library/Ruby/Site
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/powerpc-darwin9.0
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin9.0
.



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

>Comment By: Luis Lavena (luislavena)
Date: 2009-04-21 10:03

Message:
Time.today has been deprecated.

See the release notes.

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

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

From noreply at rubyforge.org  Wed Apr 22 02:03:18 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Wed, 22 Apr 2009 02:03:18 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25564 ] Time.today not
	working with 1.3.2
Message-ID: <20090422060319.05E9A159802D@rubyforge.org>

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

Category: other
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Emanuele Vicentini (emanuelev)
Assigned to: Nobody (None)
Summary: Time.today not working with 1.3.2

Initial Comment:
$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.2
  - RUBY VERSION: 1.8.6 (2008-03-03 patchlevel 114) [universal-darwin9.0]
  - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8
  - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - universal-darwin-9
  - GEM PATHS:
     - /Library/Ruby/Gems/1.8
     - /Users/emanuele/.gem/ruby/1.8
     - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/


Running the following gives problem:

$ ruby -rubygems -e 'puts Time.today'
/Library/Ruby/Site/1.8/rubygems/specification.rb:16:in `today': undefined local variable or method `location_of_caller' for Time:Class (NameError)
	from -e:1


Noted this even on an Ubuntu GNU/Linux box with Ruby 1.8.7. On both machines there are some gems (Rails, Rake, Rack and many others), but the load paths do not seem to be messed up:

$ ruby -rubygems -e 'puts Time.today rescue nil; puts $:'
/Library/Ruby/Site/1.8
/Library/Ruby/Site/1.8/powerpc-darwin9.0
/Library/Ruby/Site/1.8/universal-darwin9.0
/Library/Ruby/Site
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/powerpc-darwin9.0
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin9.0
.



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

>Comment By: Emanuele Vicentini (emanuelev)
Date: 22/04/2009 08:03

Message:
Right; that's why I expected it to show a warning, not to raise a NameError 
exception.

Anyway, I agree with you that it is a no-priority issue.

Have a nice day.

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

Comment By: Luis Lavena (luislavena)
Date: 21/04/2009 15:03

Message:
Time.today has been deprecated.

See the release notes.

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

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

From noreply at rubyforge.org  Wed Apr 22 07:47:19 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Wed, 22 Apr 2009 07:47:19 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25564 ] Time.today not
	working with 1.3.2
Message-ID: <20090422114719.6B63118580EA@rubyforge.org>

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

Category: other
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Emanuele Vicentini (emanuelev)
Assigned to: Nobody (None)
Summary: Time.today not working with 1.3.2

Initial Comment:
$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.2
  - RUBY VERSION: 1.8.6 (2008-03-03 patchlevel 114) [universal-darwin9.0]
  - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8
  - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - universal-darwin-9
  - GEM PATHS:
     - /Library/Ruby/Gems/1.8
     - /Users/emanuele/.gem/ruby/1.8
     - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/


Running the following gives problem:

$ ruby -rubygems -e 'puts Time.today'
/Library/Ruby/Site/1.8/rubygems/specification.rb:16:in `today': undefined local variable or method `location_of_caller' for Time:Class (NameError)
	from -e:1


Noted this even on an Ubuntu GNU/Linux box with Ruby 1.8.7. On both machines there are some gems (Rails, Rake, Rack and many others), but the load paths do not seem to be messed up:

$ ruby -rubygems -e 'puts Time.today rescue nil; puts $:'
/Library/Ruby/Site/1.8
/Library/Ruby/Site/1.8/powerpc-darwin9.0
/Library/Ruby/Site/1.8/universal-darwin9.0
/Library/Ruby/Site
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/powerpc-darwin9.0
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin9.0
.



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

>Comment By: Luis Lavena (luislavena)
Date: 2009-04-22 08:47

Message:
Was under deprecation warning between 1.x and 1.3, now it got removed.


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

Comment By: Emanuele Vicentini (emanuelev)
Date: 2009-04-22 03:03

Message:
Right; that's why I expected it to show a warning, not to raise a NameError 
exception.

Anyway, I agree with you that it is a no-priority issue.

Have a nice day.

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

Comment By: Luis Lavena (luislavena)
Date: 2009-04-21 10:03

Message:
Time.today has been deprecated.

See the release notes.

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

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

From noreply at rubyforge.org  Wed Apr 22 18:28:55 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Wed, 22 Apr 2009 18:28:55 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25493 ] Feature: Make
	trailing zeroes in gem version significant
Message-ID: <20090422222855.E36EC1858185@rubyforge.org>

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

Category: #gem and #require methods
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Yossef Mendelssohn (ymendel)
Assigned to: Phil Hagelberg (technomancy)
Summary: Feature: Make trailing zeroes in gem version significant

Initial Comment:
I'd like for 1.0.0 to be seen as > 1.0

Patch (diffs from git show) and flog/reek output before/after the change can be seen at http://gist.github.com/96284

You can see a few specs had to change because they assume the trailing zeroes don't matter. If this is a hard requirement, then obviously my patch cannot be accepted, at least not without some transition and deprecation warning period.

The flog and reek output is included to show that as far as overall complexity and smell goes, the code is improved by this change. Only the Gem::Version#balance utility method takes a hit as its flog score jumps from 15.4 to 25.1

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

>Comment By: Yossef Mendelssohn (ymendel)
Date: 2009-04-22 17:28

Message:
To be perfectly honest, I mostly want this change so I can
release updates to truthy with version numbers converging on
an important constant. Other people and programs have used
pi and e, but I'm shooting for 1.0 (or 1.0.0.0.0.0.0.0.0.0).

Given how many of the tests specifically point out (or
pointed out prior to this patch) that trailing zeroes are
not significant, maybe it's not that great an idea after
all. I could have almost as much fun using silly 1.0.1
prereleases.

Really, I was convinced that the flog output would be enough
to get this accepted without any deliberation.

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

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

Message:
Echoing Austin's comments from the rubygems-developers list, what's the benefit to the users of RubyGems with this change?

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

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

From noreply at rubyforge.org  Thu Apr 23 05:55:34 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 23 Apr 2009 05:55:34 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25632 ] Deprecation warning
	with -t
Message-ID: <20090423095534.90E6E18581EA@rubyforge.org>

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

Category: `gem install` command (extensions)
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: Deprecation warning with -t

Initial Comment:
Ruby 1.8.6-p114
Rubygems 1.3.2

Running "gem install" with the "-t" (test) option generates the following warning:

/usr/local/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:118:Warning: Gem::SourceIndex#search support for String patterns is deprecated

This should be updated/removed.

Regards,

Dan

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

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

From noreply at rubyforge.org  Thu Apr 23 06:10:40 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 23 Apr 2009 06:10:40 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Feature Requests-25633 ] Improved
	"gem install -t" behavior
Message-ID: <20090423101041.1CFA415B8020@rubyforge.org>

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

Category: `gem install` command
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: Improved "gem install -t" behavior

Initial Comment:
Hi,

The sequence for "gem install -t" looks something like this in Rubygems 1.3.2 when at least one test fails:

> gem install io-extra -t

Successfully installed io-extra-1.1.1
1 gem installed
Installing ri documentation for io-extra-1.1.1...
Updating ri class cache with 1916 classes...
Installing RDoc documentation for io-extra-1.1.1...

Failure:
test_pread_ptr(TC_IO_Extra) [./test/test_io_extra.rb:65]:
<1667855729>
expected to be kind_of?
<Fixnum> but was
<Bignum>.
ERROR:  5 tests, 9 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
...keep Gem? [Yn] n
Successfully uninstalled io-extra-1.1.1

There are a couple of things I don't like. First, it gives the impression that it successfully installed, or rather that it's installing before it's testing. I don't like that. I'd rather it downloaded it somewhere else, say the Dir.tmpdir directory, and ran the tests from there, instead of potentially mucking around in my gem lib dir.

Second, I'd rather it didn't generate ri and/or rdoc documentation (or update the ri class cache) until _after_ the tests have passed (or I've chosen to ignore failures and install anyway). Generating them beforehand is a waste of time if a user chooses to back out because of failed tests.

In both cases, the console messages (both content and order) should be changed.

Regards,

Dan

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

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

From noreply at rubyforge.org  Thu Apr 23 06:13:13 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 23 Apr 2009 06:13:13 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Feature Requests-25634 ] Make -t a
	default option for gem installs
Message-ID: <20090423101313.63E2C15B801E@rubyforge.org>

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

Category: `gem install` command
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: Make -t a default option for gem installs

Initial Comment:
Hi,

If we're really as test obsessed as we like to think we are, shouldn't -t be a default option for 'gem install'? I think so.

(Depends on Feature Request #25633)

Regards,

Dan

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

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

From noreply at rubyforge.org  Thu Apr 23 10:34:15 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 23 Apr 2009 10:34:15 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Feature Requests-25635 ] Add the
	"--as=" option: allow users to select gem name on install
Message-ID: <20090423143415.5C3CC18581EA@rubyforge.org>

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

Category: `gem install` command
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: Add the "--as=" option: allow users to select gem name on install

Initial Comment:
Hi,

With the growing popularity of github and forks of available gems, I think giving the end users the ability to select the gem name at the moment of installation would be very useful.

Consider a situation where there's a 'foo' gem, but there is also a fork of 'foo' on github called 'alpha-foo'. You, the end user, have some code that calls "require 'foo'". You realize one day that you want to use 'alpha-foo' instead of 'foo' because the original 'foo' is no longer maintained and the github fork has some critical patches.

But, you really don't want to have to go through all your code and change all the possible require lines. Giving the user the ability to install the gem by a different name would solve that problem:

gem install alpha-foo --as=foo

What do you think?

Regards,

Dan

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

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

From djberg96 at gmail.com  Fri Apr 24 04:41:33 2009
From: djberg96 at gmail.com (Daniel Berger)
Date: Fri, 24 Apr 2009 02:41:33 -0600
Subject: [Rubygems-developers] Making plugins easier to install
Message-ID: <49F17B3D.7050509@gmail.com>

Hi,

I was just reading over this nice article from Gabriel Horner:

http://tagaholic.me/2009/04/23/how-to-write-a-rubygem-command-plugin.html

One thing he describes that I didn't like was step 3 - the manual 
copy/paste bit.

I think we need a way to automate that.

One idea I had was to add the '--plugin' option for 'gem install'.

Another idea that James Tucker brought up was to have users perform a 
regular gem install for a plugin, and to activate it later via 'gem 
activate plugin' or something along those lines.

If we go the --plugin route, I think that means having to add extra 
attributes to the specification, which we may not want. As you can see, 
I haven't thought about the actual implementation yet. :)

Regards,

Dan

From noreply at rubyforge.org  Fri Apr 24 10:32:21 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 24 Apr 2009 10:32:21 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25564 ] Time.today not
	working with 1.3.2
Message-ID: <20090424143221.D0A5C18580EA@rubyforge.org>

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

Category: other
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Emanuele Vicentini (emanuelev)
Assigned to: Nobody (None)
Summary: Time.today not working with 1.3.2

Initial Comment:
$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.2
  - RUBY VERSION: 1.8.6 (2008-03-03 patchlevel 114) [universal-darwin9.0]
  - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8
  - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - universal-darwin-9
  - GEM PATHS:
     - /Library/Ruby/Gems/1.8
     - /Users/emanuele/.gem/ruby/1.8
     - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/


Running the following gives problem:

$ ruby -rubygems -e 'puts Time.today'
/Library/Ruby/Site/1.8/rubygems/specification.rb:16:in `today': undefined local variable or method `location_of_caller' for Time:Class (NameError)
	from -e:1


Noted this even on an Ubuntu GNU/Linux box with Ruby 1.8.7. On both machines there are some gems (Rails, Rake, Rack and many others), but the load paths do not seem to be messed up:

$ ruby -rubygems -e 'puts Time.today rescue nil; puts $:'
/Library/Ruby/Site/1.8
/Library/Ruby/Site/1.8/powerpc-darwin9.0
/Library/Ruby/Site/1.8/universal-darwin9.0
/Library/Ruby/Site
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/powerpc-darwin9.0
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin9.0
.



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

>Comment By: James Tucker (raggi)
Date: 2009-04-24 14:32

Message:
It's not been removed, but it's broken due to a missing method in Kernel.

Possibly worth noting that Kernel#location_of_caller move to Gem was not in the ChangeLog afaics.

Diff: http://pastie.textmate.org/private/w2qtrafnu6s3zizkoolba

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

Comment By: Luis Lavena (luislavena)
Date: 2009-04-22 11:47

Message:
Was under deprecation warning between 1.x and 1.3, now it got removed.


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

Comment By: Emanuele Vicentini (emanuelev)
Date: 2009-04-22 06:03

Message:
Right; that's why I expected it to show a warning, not to raise a NameError 
exception.

Anyway, I agree with you that it is a no-priority issue.

Have a nice day.

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

Comment By: Luis Lavena (luislavena)
Date: 2009-04-21 13:03

Message:
Time.today has been deprecated.

See the release notes.

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

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

From noreply at rubyforge.org  Fri Apr 24 20:51:56 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 24 Apr 2009 20:51:56 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25564 ] Time.today not
	working with 1.3.2
Message-ID: <20090425005156.9A8A21858137@rubyforge.org>

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

Category: other
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Emanuele Vicentini (emanuelev)
Assigned to: Nobody (None)
Summary: Time.today not working with 1.3.2

Initial Comment:
$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.2
  - RUBY VERSION: 1.8.6 (2008-03-03 patchlevel 114) [universal-darwin9.0]
  - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8
  - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - universal-darwin-9
  - GEM PATHS:
     - /Library/Ruby/Gems/1.8
     - /Users/emanuele/.gem/ruby/1.8
     - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/


Running the following gives problem:

$ ruby -rubygems -e 'puts Time.today'
/Library/Ruby/Site/1.8/rubygems/specification.rb:16:in `today': undefined local variable or method `location_of_caller' for Time:Class (NameError)
	from -e:1


Noted this even on an Ubuntu GNU/Linux box with Ruby 1.8.7. On both machines there are some gems (Rails, Rake, Rack and many others), but the load paths do not seem to be messed up:

$ ruby -rubygems -e 'puts Time.today rescue nil; puts $:'
/Library/Ruby/Site/1.8
/Library/Ruby/Site/1.8/powerpc-darwin9.0
/Library/Ruby/Site/1.8/universal-darwin9.0
/Library/Ruby/Site
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/powerpc-darwin9.0
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin9.0
.



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

>Comment By: Eric Hodel (drbrain)
Date: 2009-04-24 17:51

Message:
Since Gem::Specification is always loaded with RubyGems and Time.today is defined in it, Time.today isn't easily overrideable to avoid the warning (its check for definition is useless).

I think I should remove it outright.

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

Comment By: James Tucker (raggi)
Date: 2009-04-24 07:32

Message:
It's not been removed, but it's broken due to a missing method in Kernel.

Possibly worth noting that Kernel#location_of_caller move to Gem was not in the ChangeLog afaics.

Diff: http://pastie.textmate.org/private/w2qtrafnu6s3zizkoolba

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

Comment By: Luis Lavena (luislavena)
Date: 2009-04-22 04:47

Message:
Was under deprecation warning between 1.x and 1.3, now it got removed.


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

Comment By: Emanuele Vicentini (emanuelev)
Date: 2009-04-21 23:03

Message:
Right; that's why I expected it to show a warning, not to raise a NameError 
exception.

Anyway, I agree with you that it is a no-priority issue.

Have a nice day.

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

Comment By: Luis Lavena (luislavena)
Date: 2009-04-21 06:03

Message:
Time.today has been deprecated.

See the release notes.

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

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

From drbrain at segment7.net  Fri Apr 24 20:53:49 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Fri, 24 Apr 2009 17:53:49 -0700
Subject: [Rubygems-developers] Making plugins easier to install
In-Reply-To: <49F17B3D.7050509@gmail.com>
References: <49F17B3D.7050509@gmail.com>
Message-ID: <46FB224A-6F5A-4328-AF83-80C7CF00A384@segment7.net>

On Apr 24, 2009, at 01:41, Daniel Berger wrote:

> I was just reading over this nice article from Gabriel Horner:
>
> http://tagaholic.me/2009/04/23/how-to-write-a-rubygem-command-plugin.html
>
> One thing he describes that I didn't like was step 3 - the manual  
> copy/paste bit.
>
> I think we need a way to automate that.

I don't see a copy/paste bit, maybe it has been edited since?

> One idea I had was to add the '--plugin' option for 'gem install'.
>
> Another idea that James Tucker brought up was to have users perform  
> a regular gem install for a plugin, and to activate it later via  
> 'gem activate plugin' or something along those lines.
>
> If we go the --plugin route, I think that means having to add extra  
> attributes to the specification, which we may not want. As you can  
> see, I haven't thought about the actual implementation yet. :)

I decided not to try anything special to allow feedback through pain.   
Either plugin authors will get feedback about their plugins causing  
pain or RubyGems may get feedback because its plugin system causes pain.

I think we can avoid --plugin and plugin activation by improved  
documentation on how to be friendly.  The main danger here is that  
plugins always get loaded so they may carry extra baggage around.  For  
command plugins and for install hook plugins I think this can be  
avoided since RubyGems is designed to be lazy about running those.

From noreply at rubyforge.org  Sat Apr 25 04:09:50 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sat, 25 Apr 2009 04:09:50 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25677 ]
	Gem::Specification#validate fails if homepage is unspecified
Message-ID: <20090425080950.E7DFF18581DF@rubyforge.org>

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

Category: other
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Mike Burrows (asplake)
Assigned to: Nobody (None)
Summary: Gem::Specification#validate fails if homepage is unspecified

Initial Comment:
rubygems/specification.rb:886:
    unless homepage.empty? or homepage =~ /\A[a-z][a-z\d+.-]*:/i then

The above line fails with
  undefined method `empty?' for nil:NilClass
if homepage is nil, and the helpful "no #{attribute} specified" warning a few lines later is never reached.

Perhaps someone assumed that everyone has #empty? defined on NilClass?  I worked around this problem (and identified my missing homepage setting) by doing just that in my Rakefile.

Thank you for an otherwise wonderful thing!
Mike


RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.2
  - RUBY VERSION: 1.8.6 (2008-03-03 patchlevel 114) [universal-darwin9.0]
  - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8
  - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - universal-darwin-9
  - GEM PATHS:
     - /Library/Ruby/Gems/1.8
     - /Users/asplake/.gem/ruby/1.8
     - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/


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

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

From noreply at rubyforge.org  Sun Apr 26 12:17:43 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun, 26 Apr 2009 12:17:43 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25683 ] 'gem list --remote
	--details' returns nothing
Message-ID: <20090426161744.1411918580F7@rubyforge.org>

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

Category: `gem` commands (other)
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Ricardo Sazima (rsazima)
Assigned to: Nobody (None)
Summary: 'gem list --remote --details' returns nothing

Initial Comment:
Hi,

'gem list --remote' works fine, but 'gem list --remote --details' freezes and never returns anything:

root at developer-vm:/usr/bin# gem list --remote --details

*** REMOTE GEMS ***



Cheers, Sazima

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

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

From noreply at rubyforge.org  Sun Apr 26 12:19:08 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun, 26 Apr 2009 12:19:08 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25683 ] 'gem list --remote
	--details' returns nothing
Message-ID: <20090426161908.4D31318580FE@rubyforge.org>

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

Category: `gem` commands (other)
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Ricardo Sazima (rsazima)
Assigned to: Nobody (None)
Summary: 'gem list --remote --details' returns nothing

Initial Comment:
Hi,

'gem list --remote' works fine, but 'gem list --remote --details' freezes and never returns anything:

root at developer-vm:/usr/bin# gem list --remote --details

*** REMOTE GEMS ***



Cheers, Sazima

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

>Comment By: Ricardo Sazima (rsazima)
Date: 2009-04-26 13:19

Message:
root at developer-vm:/usr/bin# gem -v
1.3.2


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

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

From noreply at rubyforge.org  Sun Apr 26 12:20:52 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun, 26 Apr 2009 12:20:52 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25683 ] 'gem list --remote
	--details' returns nothing
Message-ID: <20090426162052.7371B18580FE@rubyforge.org>

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

Category: `gem` commands (other)
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Ricardo Sazima (rsazima)
Assigned to: Nobody (None)
Summary: 'gem list --remote --details' returns nothing

Initial Comment:
Hi,

'gem list --remote' works fine, but 'gem list --remote --details' freezes and never returns anything:

root at developer-vm:/usr/bin# gem list --remote --details

*** REMOTE GEMS ***



Cheers, Sazima

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

>Comment By: Ricardo Sazima (rsazima)
Date: 2009-04-26 13:20

Message:
SORRY, ACTUALLY WORKED, BUT WAS VEEEEERY SLOW...

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

Comment By: Ricardo Sazima (rsazima)
Date: 2009-04-26 13:19

Message:
root at developer-vm:/usr/bin# gem -v
1.3.2


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

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

From noreply at rubyforge.org  Sun Apr 26 12:21:10 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun, 26 Apr 2009 12:21:10 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25683 ] 'gem list --remote
	--details' returns nothing
Message-ID: <20090426162110.6C0251858104@rubyforge.org>

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

Category: `gem` commands (other)
Group: None
>Status: Closed
>Resolution: Rejected
Priority: 3
Submitted By: Ricardo Sazima (rsazima)
Assigned to: Nobody (None)
Summary: 'gem list --remote --details' returns nothing

Initial Comment:
Hi,

'gem list --remote' works fine, but 'gem list --remote --details' freezes and never returns anything:

root at developer-vm:/usr/bin# gem list --remote --details

*** REMOTE GEMS ***



Cheers, Sazima

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

Comment By: Ricardo Sazima (rsazima)
Date: 2009-04-26 13:20

Message:
SORRY, ACTUALLY WORKED, BUT WAS VEEEEERY SLOW...

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

Comment By: Ricardo Sazima (rsazima)
Date: 2009-04-26 13:19

Message:
root at developer-vm:/usr/bin# gem -v
1.3.2


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

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

From noreply at rubyforge.org  Sun Apr 26 12:21:31 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun, 26 Apr 2009 12:21:31 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25683 ] 'gem list --remote
	--details' returns nothing
Message-ID: <20090426162132.0F6C51598077@rubyforge.org>

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

Category: `gem` commands (other)
Group: None
>Status: Deleted
Resolution: Rejected
Priority: 3
Submitted By: Ricardo Sazima (rsazima)
Assigned to: Nobody (None)
Summary: 'gem list --remote --details' returns nothing

Initial Comment:
Hi,

'gem list --remote' works fine, but 'gem list --remote --details' freezes and never returns anything:

root at developer-vm:/usr/bin# gem list --remote --details

*** REMOTE GEMS ***



Cheers, Sazima

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

Comment By: Ricardo Sazima (rsazima)
Date: 2009-04-26 13:20

Message:
SORRY, ACTUALLY WORKED, BUT WAS VEEEEERY SLOW...

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

Comment By: Ricardo Sazima (rsazima)
Date: 2009-04-26 13:19

Message:
root at developer-vm:/usr/bin# gem -v
1.3.2


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

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

From noreply at rubyforge.org  Sun Apr 26 17:48:51 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun, 26 Apr 2009 17:48:51 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-22226 ] RubyGems 1.3 fails on
	windows (undefined method `uid' for nil:NilClass)
Message-ID: <20090426214851.C49061598030@rubyforge.org>

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

Category: RubyGems installer (setup.rb)
Group: None
Status: Closed
Resolution: Out of Date
Priority: 3
Submitted By: Philippe Vaucher (silex)
Assigned to: Luis Lavena (luislavena)
Summary: RubyGems 1.3 fails on windows (undefined method `uid' for nil:NilClass)

Initial Comment:
Gem 1.3 does not work out of the box on windows.

Here is what happens:

C:\>gem update
Updating installed gems
ERROR:  While executing gem ... (NoMethodError)
    undefined method `uid' for nil:NilClass

The problem is in C:\ruby\lib\ruby\site_ruby\1.8\rubygems.rb, line 713:

"if 0 == File.expand_path(path).index(Gem.user_home) and Etc.getpwuid.uid != File::Stat.new(Gem.user_home).uid then"

Which should be replaced with:

"if 0 == File.expand_path(path).index(Gem.user_home) and !Gem.win_platform? and Etc.getpwuid.uid != File::Stat.new(Gem.user_home).uid then"

Then everything works as expected.

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

Comment By: Dustin Carver (bsdpunk)
Date: 2009-04-26 16:48

Message:
This is happening to me in 1.3.2, on Windows.

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

Comment By: Luis Lavena (luislavena)
Date: 2008-10-29 15:23

Message:
Thank you for reporting this.

This is actually fixed in RubyGems 1.3.1 and should be available to you in the form of zip package.

Please follow the instructions here:

http://blog.mmediasys.com/2008/08/04/problems-with-rubygems-find-here-some-handy-tips/

HTH,
--
Luis Lavena




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

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

From noreply at rubyforge.org  Mon Apr 27 14:52:15 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Mon, 27 Apr 2009 14:52:15 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25564 ] Time.today not
	working with 1.3.2
Message-ID: <20090427185216.0707E1779926@rubyforge.org>

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

Category: other
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Emanuele Vicentini (emanuelev)
Assigned to: Nobody (None)
Summary: Time.today not working with 1.3.2

Initial Comment:
$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.2
  - RUBY VERSION: 1.8.6 (2008-03-03 patchlevel 114) [universal-darwin9.0]
  - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8
  - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - universal-darwin-9
  - GEM PATHS:
     - /Library/Ruby/Gems/1.8
     - /Users/emanuele/.gem/ruby/1.8
     - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/


Running the following gives problem:

$ ruby -rubygems -e 'puts Time.today'
/Library/Ruby/Site/1.8/rubygems/specification.rb:16:in `today': undefined local variable or method `location_of_caller' for Time:Class (NameError)
	from -e:1


Noted this even on an Ubuntu GNU/Linux box with Ruby 1.8.7. On both machines there are some gems (Rails, Rake, Rack and many others), but the load paths do not seem to be messed up:

$ ruby -rubygems -e 'puts Time.today rescue nil; puts $:'
/Library/Ruby/Site/1.8
/Library/Ruby/Site/1.8/powerpc-darwin9.0
/Library/Ruby/Site/1.8/universal-darwin9.0
/Library/Ruby/Site
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/powerpc-darwin9.0
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin9.0
.



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

Comment By: Luke Ivers (technodolt1)
Date: 2009-04-27 11:52

Message:
Hey,

I fixed this on my local install by changing the line in specification.rb to use Gem.location_of_caller instead of just location_of_caller in the Time.today function.

Given that I'm using MacOS and the default install of Ruby, and also that I'm using an application (Tracks, specifically) which uses this function, I figured it'd be better to fix the bug rubygems 1.3.2 for now.

Also going to report this to Tracks so they know to take out the deprecated code if they want this to work with Rubygems on 1.8.*

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

Comment By: Eric Hodel (drbrain)
Date: 2009-04-24 17:51

Message:
Since Gem::Specification is always loaded with RubyGems and Time.today is defined in it, Time.today isn't easily overrideable to avoid the warning (its check for definition is useless).

I think I should remove it outright.

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

Comment By: James Tucker (raggi)
Date: 2009-04-24 07:32

Message:
It's not been removed, but it's broken due to a missing method in Kernel.

Possibly worth noting that Kernel#location_of_caller move to Gem was not in the ChangeLog afaics.

Diff: http://pastie.textmate.org/private/w2qtrafnu6s3zizkoolba

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

Comment By: Luis Lavena (luislavena)
Date: 2009-04-22 04:47

Message:
Was under deprecation warning between 1.x and 1.3, now it got removed.


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

Comment By: Emanuele Vicentini (emanuelev)
Date: 2009-04-21 23:03

Message:
Right; that's why I expected it to show a warning, not to raise a NameError 
exception.

Anyway, I agree with you that it is a no-priority issue.

Have a nice day.

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

Comment By: Luis Lavena (luislavena)
Date: 2009-04-21 06:03

Message:
Time.today has been deprecated.

See the release notes.

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

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

From noreply at rubyforge.org  Wed Apr 29 20:05:30 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Wed, 29 Apr 2009 20:05:30 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25734 ] Gem::Ext::RakeBuilder
	fails under windows if ENV['rake'] not set
Message-ID: <20090430000530.C29231D78824@rubyforge.org>

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

Category: `gem install` command
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Paolo Angelini (pablito)
Assigned to: Nobody (None)
Summary: Gem::Ext::RakeBuilder fails under windows if ENV['rake'] not set

Initial Comment:
line 22 of rake_builder.rb builds a rake command and defaults to Gem.bin_path('rake') if ENV['rake'] is not set:
cmd = ENV['rake'] || Gem.bin_path('rake') rescue Gem.default_exec_format % 'rake'

unfortunately under windows Gem.bin_path('rake') is not an executable file and line 26:
run cmd, results 
raise an error:
'C:/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.4/bin/rake' is not recognized as an int
ernal or external command,
operable program or batch file.

(see also <a href='http://rubyforge.org/forum/forum.php?thread_id=32969&forum_id=2129'>this thread</a>
Including Gem.ruby in the command solves the problem:

bin_path = /mswin/ =~ RUBY_PLATFORM ? "#{Gem.ruby} #{Gem.bin_path('rake')}" : Gem.bin_path('rake')
cmd = ENV['rake'] || bin_path rescue Gem.default_exec_format % 'rake'

I didn't file a patch because I couldn't test this under linux and I wanted to avoid any regression bug

this is my environment

RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.2
  - 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/Administrator/.gem/ruby/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/


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

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

From noreply at rubyforge.org  Wed Apr 29 20:19:31 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Wed, 29 Apr 2009 20:19:31 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25734 ] Gem::Ext::RakeBuilder
	fails under windows if ENV['rake'] not set
Message-ID: <20090430001931.319E31858207@rubyforge.org>

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

Category: `gem install` command
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Paolo Angelini (pablito)
Assigned to: Nobody (None)
Summary: Gem::Ext::RakeBuilder fails under windows if ENV['rake'] not set

Initial Comment:
line 22 of rake_builder.rb builds a rake command and defaults to Gem.bin_path('rake') if ENV['rake'] is not set:
cmd = ENV['rake'] || Gem.bin_path('rake') rescue Gem.default_exec_format % 'rake'

unfortunately under windows Gem.bin_path('rake') is not an executable file and line 26:
run cmd, results 
raise an error:
'C:/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.4/bin/rake' is not recognized as an int
ernal or external command,
operable program or batch file.

(see also <a href='http://rubyforge.org/forum/forum.php?thread_id=32969&forum_id=2129'>this thread</a>
Including Gem.ruby in the command solves the problem:

bin_path = /mswin/ =~ RUBY_PLATFORM ? "#{Gem.ruby} #{Gem.bin_path('rake')}" : Gem.bin_path('rake')
cmd = ENV['rake'] || bin_path rescue Gem.default_exec_format % 'rake'

I didn't file a patch because I couldn't test this under linux and I wanted to avoid any regression bug

this is my environment

RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.2
  - 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/Administrator/.gem/ruby/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/


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

>Comment By: Luis Lavena (luislavena)
Date: 2009-04-29 21:19

Message:
The problem I see is that RakeBuild should use Gem.ruby + Gem.bin_path('rake') and not rake directly.

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

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

From noreply at rubyforge.org  Thu Apr 30 08:05:19 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 30 Apr 2009 08:05:19 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25734 ] Gem::Ext::RakeBuilder
	fails under windows if ENV['rake'] not set
Message-ID: <20090430120519.ECF7C18581E2@rubyforge.org>

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

Category: `gem install` command
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Paolo Angelini (pablito)
Assigned to: Nobody (None)
Summary: Gem::Ext::RakeBuilder fails under windows if ENV['rake'] not set

Initial Comment:
line 22 of rake_builder.rb builds a rake command and defaults to Gem.bin_path('rake') if ENV['rake'] is not set:
cmd = ENV['rake'] || Gem.bin_path('rake') rescue Gem.default_exec_format % 'rake'

unfortunately under windows Gem.bin_path('rake') is not an executable file and line 26:
run cmd, results 
raise an error:
'C:/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.4/bin/rake' is not recognized as an int
ernal or external command,
operable program or batch file.

(see also <a href='http://rubyforge.org/forum/forum.php?thread_id=32969&forum_id=2129'>this thread</a>
Including Gem.ruby in the command solves the problem:

bin_path = /mswin/ =~ RUBY_PLATFORM ? "#{Gem.ruby} #{Gem.bin_path('rake')}" : Gem.bin_path('rake')
cmd = ENV['rake'] || bin_path rescue Gem.default_exec_format % 'rake'

I didn't file a patch because I couldn't test this under linux and I wanted to avoid any regression bug

this is my environment

RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.2
  - 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/Administrator/.gem/ruby/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/


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

>Comment By: James Tucker (raggi)
Date: 2009-04-30 12:05

Message:
What is required for normal operation on most builds should be:

"#{Gem.ruby} -rubygems #{Gem.bin_path('rake')}"


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

Comment By: Luis Lavena (luislavena)
Date: 2009-04-30 00:19

Message:
The problem I see is that RakeBuild should use Gem.ruby + Gem.bin_path('rake') and not rake directly.

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

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

From noreply at rubyforge.org  Thu Apr 30 08:10:19 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 30 Apr 2009 08:10:19 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25734 ] Gem::Ext::RakeBuilder
	fails under windows if ENV['rake'] not set
Message-ID: <20090430121038.3F86B15B8023@rubyforge.org>

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

Category: `gem install` command
Group: None
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: Paolo Angelini (pablito)
>Assigned to: James Tucker (raggi)
Summary: Gem::Ext::RakeBuilder fails under windows if ENV['rake'] not set

Initial Comment:
line 22 of rake_builder.rb builds a rake command and defaults to Gem.bin_path('rake') if ENV['rake'] is not set:
cmd = ENV['rake'] || Gem.bin_path('rake') rescue Gem.default_exec_format % 'rake'

unfortunately under windows Gem.bin_path('rake') is not an executable file and line 26:
run cmd, results 
raise an error:
'C:/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.4/bin/rake' is not recognized as an int
ernal or external command,
operable program or batch file.

(see also <a href='http://rubyforge.org/forum/forum.php?thread_id=32969&forum_id=2129'>this thread</a>
Including Gem.ruby in the command solves the problem:

bin_path = /mswin/ =~ RUBY_PLATFORM ? "#{Gem.ruby} #{Gem.bin_path('rake')}" : Gem.bin_path('rake')
cmd = ENV['rake'] || bin_path rescue Gem.default_exec_format % 'rake'

I didn't file a patch because I couldn't test this under linux and I wanted to avoid any regression bug

this is my environment

RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.2
  - 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/Administrator/.gem/ruby/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/


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

>Comment By: James Tucker (raggi)
Date: 2009-04-30 12:10

Message:
Fixed in r2180.

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

Comment By: James Tucker (raggi)
Date: 2009-04-30 12:05

Message:
What is required for normal operation on most builds should be:

"#{Gem.ruby} -rubygems #{Gem.bin_path('rake')}"


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

Comment By: Luis Lavena (luislavena)
Date: 2009-04-30 00:19

Message:
The problem I see is that RakeBuild should use Gem.ruby + Gem.bin_path('rake') and not rake directly.

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

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

From rick.denatale at gmail.com  Thu Apr 30 13:32:18 2009
From: rick.denatale at gmail.com (Rick DeNatale)
Date: Thu, 30 Apr 2009 13:32:18 -0400
Subject: [Rubygems-developers] Standard practice re: tests and specs in gems
Message-ID: <deb2337a0904301032w1773aad0qc25ee0db6abe2377@mail.gmail.com>

I asked Dr. Nic about this, but thought I might raise it here.

I'm getting a gem ready for publication.  I'm using newgem/hoe.

One of my alpha testers is asking about why things like the rake tasks
and specs are being included in the gem.  AFAIK rubygems doesn't
provide an easy way to run them, or does it.  Are they just
unnecessary bloat for deployment?

Similarly, what about the rake tasks and the rakefile itself.  Newgem
and or hoe seems to be including this whether or not the they are
included in the manifest, is this right or am I misconfigured somehow?

-- 
Rick DeNatale

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

From luislavena at gmail.com  Thu Apr 30 13:49:30 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Thu, 30 Apr 2009 14:49:30 -0300
Subject: [Rubygems-developers] Standard practice re: tests and specs in
	gems
In-Reply-To: <deb2337a0904301032w1773aad0qc25ee0db6abe2377@mail.gmail.com>
References: <deb2337a0904301032w1773aad0qc25ee0db6abe2377@mail.gmail.com>
Message-ID: <71166b3b0904301049j2188ad5y4b4617fe417794e4@mail.gmail.com>

On Thu, Apr 30, 2009 at 2:32 PM, Rick DeNatale <rick.denatale at gmail.com> wrote:
> I asked Dr. Nic about this, but thought I might raise it here.
>
> I'm getting a gem ready for publication. ?I'm using newgem/hoe.
>
> One of my alpha testers is asking about why things like the rake tasks
> and specs are being included in the gem. ?AFAIK rubygems doesn't
> provide an easy way to run them, or does it. ?Are they just
> unnecessary bloat for deployment?
>

Well, is not bloatware.

I found myself doing gem unpack and checking the Rakefile to test some
gems, either with RSpec or TestUnit.

> Similarly, what about the rake tasks and the rakefile itself. ?Newgem
> and or hoe seems to be including this whether or not the they are
> included in the manifest, is this right or am I misconfigured somehow?
>

Same that previous point. The files including the gem, from my PoV,
should be the same that you have in the repository or the ones you
will zip up to share with someone else (or a system without packaging
like RubyGems)

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

From noreply at rubyforge.org  Thu Apr 30 13:59:12 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 30 Apr 2009 13:59:12 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25734 ] Gem::Ext::RakeBuilder
	fails under windows if ENV['rake'] not set
Message-ID: <20090430175912.678191779921@rubyforge.org>

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

Category: `gem install` command
Group: None
Status: Closed
Resolution: Accepted
Priority: 3
Submitted By: Paolo Angelini (pablito)
Assigned to: James Tucker (raggi)
Summary: Gem::Ext::RakeBuilder fails under windows if ENV['rake'] not set

Initial Comment:
line 22 of rake_builder.rb builds a rake command and defaults to Gem.bin_path('rake') if ENV['rake'] is not set:
cmd = ENV['rake'] || Gem.bin_path('rake') rescue Gem.default_exec_format % 'rake'

unfortunately under windows Gem.bin_path('rake') is not an executable file and line 26:
run cmd, results 
raise an error:
'C:/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.4/bin/rake' is not recognized as an int
ernal or external command,
operable program or batch file.

(see also <a href='http://rubyforge.org/forum/forum.php?thread_id=32969&forum_id=2129'>this thread</a>
Including Gem.ruby in the command solves the problem:

bin_path = /mswin/ =~ RUBY_PLATFORM ? "#{Gem.ruby} #{Gem.bin_path('rake')}" : Gem.bin_path('rake')
cmd = ENV['rake'] || bin_path rescue Gem.default_exec_format % 'rake'

I didn't file a patch because I couldn't test this under linux and I wanted to avoid any regression bug

this is my environment

RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.2
  - 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/Administrator/.gem/ruby/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/


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

>Comment By: Luis Lavena (luislavena)
Date: 2009-04-30 14:59

Message:
James, take in consideration that "Gem.ruby" could be inside a PATH with spaces and it need to be handled properly.

The same applies to rake.

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

Comment By: James Tucker (raggi)
Date: 2009-04-30 09:10

Message:
Fixed in r2180.

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

Comment By: James Tucker (raggi)
Date: 2009-04-30 09:05

Message:
What is required for normal operation on most builds should be:

"#{Gem.ruby} -rubygems #{Gem.bin_path('rake')}"


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

Comment By: Luis Lavena (luislavena)
Date: 2009-04-29 21:19

Message:
The problem I see is that RakeBuild should use Gem.ruby + Gem.bin_path('rake') and not rake directly.

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

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

From jim.weirich at gmail.com  Thu Apr 30 14:32:15 2009
From: jim.weirich at gmail.com (Jim Weirich)
Date: Thu, 30 Apr 2009 14:32:15 -0400
Subject: [Rubygems-developers] Standard practice re: tests and specs in
	gems
In-Reply-To: <deb2337a0904301032w1773aad0qc25ee0db6abe2377@mail.gmail.com>
References: <deb2337a0904301032w1773aad0qc25ee0db6abe2377@mail.gmail.com>
Message-ID: <BFD7BAE8-C1BE-4275-AE20-31CB464659C8@gmail.com>


On Apr 30, 2009, at 1:32 PM, Rick DeNatale wrote:

> One of my alpha testers is asking about why things like the rake tasks
> and specs are being included in the gem.  AFAIK rubygems doesn't
> provide an easy way to run them, or does it.  Are they just
> unnecessary bloat for deployment?

I strongly recommend including everything in the gem that one would  
include in a TAR file one might give to a developer to work on.  There  
are people who repackage gems for distribution on Unbutu or Debian and  
their job is much harder if everything is not included.

-- 
-- Jim Weirich
-- jim.weirich at gmail.com


From drbrain at segment7.net  Thu Apr 30 16:47:56 2009
From: drbrain at segment7.net (Eric Hodel)
Date: Thu, 30 Apr 2009 13:47:56 -0700
Subject: [Rubygems-developers] Standard practice re: tests and specs in
	gems
In-Reply-To: <deb2337a0904301032w1773aad0qc25ee0db6abe2377@mail.gmail.com>
References: <deb2337a0904301032w1773aad0qc25ee0db6abe2377@mail.gmail.com>
Message-ID: <E3045372-DB69-4588-8C0F-C5975E5B2305@segment7.net>

On Apr 30, 2009, at 10:32, Rick DeNatale wrote:

> I asked Dr. Nic about this, but thought I might raise it here.
>
> I'm getting a gem ready for publication.  I'm using newgem/hoe.
>
> One of my alpha testers is asking about why things like the rake tasks
> and specs are being included in the gem.  AFAIK rubygems doesn't
> provide an easy way to run them, or does it.  Are they just
> unnecessary bloat for deployment?

gem check -t / gem install -t, but these need work (there might be a  
GSoC student working on it in for a Gentoo/RubyGems project).

From noreply at rubyforge.org  Thu Apr 30 18:30:01 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 30 Apr 2009 18:30:01 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25632 ] Deprecation warning
	with -t
Message-ID: <20090430223001.5815018581F3@rubyforge.org>

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

Category: `gem install` command (extensions)
Group: v1.3.x
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: Daniel Berger (djberg96)
>Assigned to: Daniel Berger (djberg96)
Summary: Deprecation warning with -t

Initial Comment:
Ruby 1.8.6-p114
Rubygems 1.3.2

Running "gem install" with the "-t" (test) option generates the following warning:

/usr/local/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:118:Warning: Gem::SourceIndex#search support for String patterns is deprecated

This should be updated/removed.

Regards,

Dan

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

>Comment By: Daniel Berger (djberg96)
Date: 2009-04-30 15:30

Message:
Fixed in SVN. Replaced 'search' with 'find_name'.

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

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

From noreply at rubyforge.org  Thu Apr 30 18:42:49 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 30 Apr 2009 18:42:49 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25741 ]
	Gem::Specification#installation_path should raise a proper exception
Message-ID: <20090430224249.333EB1D787F0@rubyforge.org>

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

Category: other
Group: v1.3.x
Status: Open
Resolution: None
Priority: 2
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: Gem::Specification#installation_path should raise a proper exception

Initial Comment:
Hi,

The Gem::Specification#installation_path is a public method, but it isn't meant for direct use in a .gemspec file. If you try to call that method directly in a .gemspec file it will result in this error:

/usr/local/lib/ruby/site_ruby/1.8/rubygems/specification.rb:624:in `dirname': can't convert nil into String (TypeError)

Looking at the source we can see why:

def installation_path
  File.expand_path(File.dirname(File.dirname(@loaded_from)))
end

The @loaded_from instance variable is nil, so it blows up. Instead, this should raise a proper exception of some sort to let people (like me) know that it isn't meant for direct use, but for inspection after installation.

Regards,

Dan

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

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

From noreply at rubyforge.org  Thu Apr 30 19:00:18 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 30 Apr 2009 19:00:18 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25677 ]
	Gem::Specification#validate fails if homepage is unspecified
Message-ID: <20090430230019.080E21D787E5@rubyforge.org>

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

Category: other
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Mike Burrows (asplake)
Assigned to: Nobody (None)
Summary: Gem::Specification#validate fails if homepage is unspecified

Initial Comment:
rubygems/specification.rb:886:
    unless homepage.empty? or homepage =~ /\A[a-z][a-z\d+.-]*:/i then

The above line fails with
  undefined method `empty?' for nil:NilClass
if homepage is nil, and the helpful "no #{attribute} specified" warning a few lines later is never reached.

Perhaps someone assumed that everyone has #empty? defined on NilClass?  I worked around this problem (and identified my missing homepage setting) by doing just that in my Rakefile.

Thank you for an otherwise wonderful thing!
Mike


RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.2
  - RUBY VERSION: 1.8.6 (2008-03-03 patchlevel 114) [universal-darwin9.0]
  - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8
  - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - universal-darwin-9
  - GEM PATHS:
     - /Library/Ruby/Gems/1.8
     - /Users/asplake/.gem/ruby/1.8
     - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/


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

>Comment By: Daniel Berger (djberg96)
Date: 2009-04-30 16:00

Message:
Proposed change:

--- specification.rb    2009-04-30 16:48:09.000000000 -0600
+++ specification.new   2009-04-30 16:47:56.000000000 -0600
@@ -883,9 +883,13 @@
             '"FIXME" or "TODO" is not a summary'
     end
 
-    unless homepage.empty? or homepage =~ /\A[a-z][a-z\d+.-]*:/i then
-      raise Gem::InvalidSpecificationException,
-            "\#{homepage}\ is not a URI"
+    if homepage
+      begin
+        URI.parse(homepage)
+      rescue URI::InvalidURIError
+        raise Gem::InvalidSpecificationException,
+          "#{homepage} is not a valid URI"
+      end
     end
 
     # Warnings

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

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

From noreply at rubyforge.org  Thu Apr 30 22:07:50 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 30 Apr 2009 22:07:50 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25677 ]
	Gem::Specification#validate fails if homepage is unspecified
Message-ID: <20090501020750.5FE861978513@rubyforge.org>

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

Category: other
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Mike Burrows (asplake)
Assigned to: Nobody (None)
Summary: Gem::Specification#validate fails if homepage is unspecified

Initial Comment:
rubygems/specification.rb:886:
    unless homepage.empty? or homepage =~ /\A[a-z][a-z\d+.-]*:/i then

The above line fails with
  undefined method `empty?' for nil:NilClass
if homepage is nil, and the helpful "no #{attribute} specified" warning a few lines later is never reached.

Perhaps someone assumed that everyone has #empty? defined on NilClass?  I worked around this problem (and identified my missing homepage setting) by doing just that in my Rakefile.

Thank you for an otherwise wonderful thing!
Mike


RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.2
  - RUBY VERSION: 1.8.6 (2008-03-03 patchlevel 114) [universal-darwin9.0]
  - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8
  - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - universal-darwin-9
  - GEM PATHS:
     - /Library/Ruby/Gems/1.8
     - /Users/asplake/.gem/ruby/1.8
     - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/


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

>Comment By: Daniel Berger (djberg96)
Date: 2009-04-30 19:07

Message:
BTW, the downside of my suggested patch is that URI.parse appears to be pretty liberal with what's legal and what isn't (including empty strings), compared to the current regex.

Dan

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

Comment By: Daniel Berger (djberg96)
Date: 2009-04-30 16:00

Message:
Proposed change:

--- specification.rb    2009-04-30 16:48:09.000000000 -0600
+++ specification.new   2009-04-30 16:47:56.000000000 -0600
@@ -883,9 +883,13 @@
             '"FIXME" or "TODO" is not a summary'
     end
 
-    unless homepage.empty? or homepage =~ /\A[a-z][a-z\d+.-]*:/i then
-      raise Gem::InvalidSpecificationException,
-            "\#{homepage}\ is not a URI"
+    if homepage
+      begin
+        URI.parse(homepage)
+      rescue URI::InvalidURIError
+        raise Gem::InvalidSpecificationException,
+          "#{homepage} is not a valid URI"
+      end
     end
 
     # Warnings

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

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

From noreply at rubyforge.org  Thu Apr 30 22:15:12 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 30 Apr 2009 22:15:12 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25743 ] Gem::Platform#=== bug
	- returns false when it should return true
Message-ID: <20090501021513.3C0A118581E3@rubyforge.org>

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

Category: other
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: Gem::Platform#=== bug - returns false when it should return true

Initial Comment:
As per IRC, this appears to be a bug:

irb(main):005:0> s1 = Gem::Platform.new(['universal', 'darwin', '9'])
=> #<Gem::Platform:0x822bac @cpu="universal", @os="darwin", @version="9">

irb(main):006:0> s2 = Gem::Platform.new(['x86', 'darwin', '8'])
=> #<Gem::Platform:0x820d02 @cpu="x86", @os="darwin", @version="8">

irb(main):007:0> s1 === s2
=> false

This caused a user on a newer version of OS X some grief when they tried to install sys-proctable, but it was failing because their platform was 'universal-darwin' but the gem is built as 'x86-darwin'.

Regards,

Dan


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

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

From noreply at rubyforge.org  Thu Apr 30 22:19:04 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 30 Apr 2009 22:19:04 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25743 ] Gem::Platform#=== bug
	- returns false when it should return true
Message-ID: <20090501021904.7CD6418581DD@rubyforge.org>

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

Category: other
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: Gem::Platform#=== bug - returns false when it should return true

Initial Comment:
As per IRC, this appears to be a bug:

irb(main):005:0> s1 = Gem::Platform.new(['universal', 'darwin', '9'])
=> #<Gem::Platform:0x822bac @cpu="universal", @os="darwin", @version="9">

irb(main):006:0> s2 = Gem::Platform.new(['x86', 'darwin', '8'])
=> #<Gem::Platform:0x820d02 @cpu="x86", @os="darwin", @version="8">

irb(main):007:0> s1 === s2
=> false

This caused a user on a newer version of OS X some grief when they tried to install sys-proctable, but it was failing because their platform was 'universal-darwin' but the gem is built as 'x86-darwin'.

Regards,

Dan


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

>Comment By: Daniel Berger (djberg96)
Date: 2009-04-30 19:19

Message:
And not a minute after I posted this, I think the problem is actually the versions, i.e. 8 vs 9.

So, perhaps this is expected behavior after all.

Dan

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

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

From noreply at rubyforge.org  Thu Apr 30 23:49:53 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 30 Apr 2009 23:49:53 -0400 (EDT)
Subject: [Rubygems-developers] [ rubygems-Bugs-25743 ] Gem::Platform#=== bug
	- returns false when it should return true
Message-ID: <20090501034954.00771197857C@rubyforge.org>

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

Category: other
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: Gem::Platform#=== bug - returns false when it should return true

Initial Comment:
As per IRC, this appears to be a bug:

irb(main):005:0> s1 = Gem::Platform.new(['universal', 'darwin', '9'])
=> #<Gem::Platform:0x822bac @cpu="universal", @os="darwin", @version="9">

irb(main):006:0> s2 = Gem::Platform.new(['x86', 'darwin', '8'])
=> #<Gem::Platform:0x820d02 @cpu="x86", @os="darwin", @version="8">

irb(main):007:0> s1 === s2
=> false

This caused a user on a newer version of OS X some grief when they tried to install sys-proctable, but it was failing because their platform was 'universal-darwin' but the gem is built as 'x86-darwin'.

Regards,

Dan


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

>Comment By: Luis Lavena (luislavena)
Date: 2009-05-01 00:49

Message:
It is the expected behavior.

universal-darwin-9 is not compatible with universal-darwin-8

Only universal-darwin is compatible with 9 and 8.

Similar with mswin32-60 and mswin32-80 or mswin32-90, since these link to different CRT version, similar thing happens on OSX.

At least, that was the last time I've checked.


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

Comment By: Daniel Berger (djberg96)
Date: 2009-04-30 23:19

Message:
And not a minute after I posted this, I think the problem is actually the versions, i.e. 8 vs 9.

So, perhaps this is expected behavior after all.

Dan

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

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