From thewoolleyman at gmail.com  Sat Jan  1 05:05:42 2011
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Sat, 1 Jan 2011 03:05:42 -0700
Subject: [Rubygems-developers] CI Status (was: RubyGemsGitHub build
 1e71d86 failed)
In-Reply-To: <BE2B4C92-3CFC-46D6-BB97-80B2754148C1@zenspider.com>
References: <AANLkTimj0C_iDx5OZMegAAA+fawOUzf5StP9BGTe1jVu@mail.gmail.com>
	<AANLkTi=okPTdqRRwJD=7f44n5xhg_a9ae8b+cHjCmjH-@mail.gmail.com>
	<BE2B4C92-3CFC-46D6-BB97-80B2754148C1@zenspider.com>
Message-ID: <AANLkTikHjpBLWKMOVQEV2nZ3JeoMeP1dGbQPj04m2bCg@mail.gmail.com>

Summary:

CI is green on 1.8.7, failing on 1.9.1 and 1.9.2.  Notifications to
dev list can now be enabled per-interpreter (and are currently only
enabled for 1.8.7).  All the 1.9.x problems are locally reproducible
for me, AFAIK there are no issues with the CI environment, and let me
know if you believe otherwise.

Details:

I merged the CI improvements to master:

https://github.com/rubygems/rubygems/commit/fda095d32a56f0c595b12d361885d9fad29780d8

"Continuous Integration config enhancements and wrapper script.
Support for multiple interpeters via RVM, better reproducibility of
failed builds via environment auto-setup in wrapper script, and
granular control over failure notifications emails for selected
interpreters"

Responses to your prior feedback inline below...

On Tue, Dec 21, 2010 at 2:16 PM, Ryan Davis <ryand-ruby at zenspider.com> wrote:
> On Dec 13, 2010, at 22:52 , Chad Woolley wrote:
>>> http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_8_7-p302
> This is the latest version of 1.8.7 and runs clean.

Yep, it does.  Yay!

> I dunno if you have control over this, but not having good titles on the HTML page makes distinguishing tabs a PITA.

Only if I hack CCRB, which I don't want to.  I'd rather put effort
into moving everything to Hudson, which is a whole other side project.
 For now, I'd recommend http://ccmenu.sourceforge.net/ if you want to
easily monitor build status.

> p430 is the latest release on 1.9.1.

Done: http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_1-p430
...but it has the same problem:

> This fails:
>
>> rake aborted!
>> no such file to load -- hoe
>>
>> /home/pivotal/.cruise/projects/RubyGems-1_9_1-p429/work/Rakefile:8
>> :in `require'
>
> So, environmental problem here...

No, you can see that Hoe was just installed successfully, but then
Rake can't find it.  It's probably something related to the
immediately preceding errors about gem_prelude and the frozen load
path.  I tried hacking the wrapper script to run rake in a subshell
(thinking it would then know the gems WERE actually installed), but
this didn't make any difference.

It is also reproducible locally if you install RVM and run the
following (let me know if it isn't locally reproducible for you):

./ci_build.sh '1.9.1-p430 at rubygems'

> p0 is the latest release for 1.9.2.

Done: http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_2-p0

The 1.9.2-p0 build is failing with "NoMethodError: undefined method
`dump' for Psych:Module", which is also locally reproducible:

./ci_build.sh '1.9.2-p0 at rubygems'

> Why is it building ruby on every run?

It isn't, only if the specified RVM interpreter at rubygems isn't already
installed.

It IS installing the gems every run, but that's an intentional hack
because you still haven't told me how to make hoe not use sudo for
"check_extra_deps".

Let me know

Thanks,
-- Chad

From thewoolleyman at gmail.com  Mon Jan  3 13:11:34 2011
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Mon, 3 Jan 2011 11:11:34 -0700
Subject: [Rubygems-developers] CI Status (was: RubyGemsGitHub build
 1e71d86 failed)
In-Reply-To: <AANLkTikHjpBLWKMOVQEV2nZ3JeoMeP1dGbQPj04m2bCg@mail.gmail.com>
References: <AANLkTimj0C_iDx5OZMegAAA+fawOUzf5StP9BGTe1jVu@mail.gmail.com>
	<AANLkTi=okPTdqRRwJD=7f44n5xhg_a9ae8b+cHjCmjH-@mail.gmail.com>
	<BE2B4C92-3CFC-46D6-BB97-80B2754148C1@zenspider.com>
	<AANLkTikHjpBLWKMOVQEV2nZ3JeoMeP1dGbQPj04m2bCg@mail.gmail.com>
Message-ID: <AANLkTiku-51UJPEaeZwB1Hb6p32f9=9=CjDsQ-9oGHfd@mail.gmail.com>

FYI, if you happen to be ccmenu running for ci and it's spamming you,
it's because git fetch seems to be borked just for the 1.8.7 branch
and just on the CI box.  Probably a github issue.  Waiting to see if
it works itself out, if not I'll look into it.

Also, any input on the locally reproducible failing 1.9.x builds are
welcome.  I'd love to get them green.  hint hint.

Thanks,
-- Chad

From drbrain at segment7.net  Mon Jan  3 18:41:46 2011
From: drbrain at segment7.net (Eric Hodel)
Date: Mon, 3 Jan 2011 15:41:46 -0800
Subject: [Rubygems-developers] RubyGems on 1.9 workaround
Message-ID: <DD4E5889-0528-4D5B-8EA9-6FCB193CCA0B@segment7.net>

I've provided a workaround for RubyGems on 1.9 and committed it.

It cost us the following features:

* Legacy remote repository support (fetching /yaml.Z and friends)

* Setting GEM_PATH and GEM_HOME via ~/.gemrc

The first feature didn't strictly need to be removed.  I just got annoyed that Gem::SourceIndex loaded Gem::UserInteraction.

I don't see a way around the restoring the second feature without more hacks.

In gem_prelude-land rubygems/custom_require is already kinda-sorta loaded.  When loading rubygems.rb we depend on rescuing several LoadErrors, but gem_prelude is interfering when rubygems.rb is partially loaded.

The interference causes ruby to try to try load files like rubygems/defaults/operating_system.rb in rubygems.rb and Win32API in rubygems/config_file.rb when RubyGems isn't ready to load them from a gem.

RubyGems::ConfigFile is required to figure out what gem path and gem home to use.  This involves loading YAML as well.

On the upside, RubyGems should start a little faster now that it no longer loads rubygems/specification, rubygems/config_file or yaml.

From noreply at rubyforge.org  Mon Jan  3 18:45:37 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Mon,  3 Jan 2011 18:45:37 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28746 ] gem install complains
	of frozen filename on 1.8.7-p302
Message-ID: <20110103234537.233381858385@rubyforge.org>

Bugs item #28746, was opened at 2010-11-23 01:39
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28746&group_id=126

Category: `gem install` command
Group: next
Status: Closed
Resolution: None
Priority: 3
Submitted By: Erik Hollensbe (erikh)
Assigned to: Luis Lavena (luislavena)
Summary: gem install complains of frozen filename on 1.8.7-p302

Initial Comment:
This patch solves this issue, although it may not be satisfactory. Best I can tell this is not a gems issue but a side-effect of it using optparse.

https://gist.github.com/b50b26a6e5cc2124ffee

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

>Comment By: Eric Hodel (drbrain)
Date: 2011-01-03 15:45

Message:
Fixed in 1.4.1

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

Comment By: Erik Hollensbe (erikh)
Date: 2010-12-31 18:17

Message:
I don't remember! It was gem build but this feels like an eternity since I reported 
it.

Anyhow, I'll just close it.

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

Comment By: Luis Lavena (luislavena)
Date: 2010-12-31 15:23

Message:
Hello Eric,

Can you provide more information about gem install issues? which gems this happens? which version of Ruby?

Try to include the whole "gem env" information to help us debug this issue.

I've been using p302 for quite some time and never encountered this issue.

Thank you.

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

Comment By: Erik Hollensbe (erikh)
Date: 2010-11-23 01:39

Message:
gem build... gah! sorry.

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

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

From nick at quaran.to  Mon Jan  3 19:33:33 2011
From: nick at quaran.to (Nick Quaranto)
Date: Mon, 3 Jan 2011 19:33:33 -0500
Subject: [Rubygems-developers] RubyGems on 1.9 workaround
In-Reply-To: <DD4E5889-0528-4D5B-8EA9-6FCB193CCA0B@segment7.net>
References: <DD4E5889-0528-4D5B-8EA9-6FCB193CCA0B@segment7.net>
Message-ID: <AANLkTik3kQLy2=pi-a8sxTWjKyWpt=Tn+xBywvmcrDre@mail.gmail.com>

Nice. Is this going released as 1.4.2?

Also, a blog post denoting the history of why this situation is all
messed up would be really nice to distribute. Watching the tweets for
"rubygems" (an uptime notifier for me along with general PR watch)
about this 1.9 stuff makes me a sad panda.

-Nick

On Mon, Jan 3, 2011 at 6:41 PM, Eric Hodel <drbrain at segment7.net> wrote:
> I've provided a workaround for RubyGems on 1.9 and committed it.
>
> It cost us the following features:
>
> * Legacy remote repository support (fetching /yaml.Z and friends)
>
> * Setting GEM_PATH and GEM_HOME via ~/.gemrc
>
> The first feature didn't strictly need to be removed. ?I just got annoyed that Gem::SourceIndex loaded Gem::UserInteraction.
>
> I don't see a way around the restoring the second feature without more hacks.
>
> In gem_prelude-land rubygems/custom_require is already kinda-sorta loaded. ?When loading rubygems.rb we depend on rescuing several LoadErrors, but gem_prelude is interfering when rubygems.rb is partially loaded.
>
> The interference causes ruby to try to try load files like rubygems/defaults/operating_system.rb in rubygems.rb and Win32API in rubygems/config_file.rb when RubyGems isn't ready to load them from a gem.
>
> RubyGems::ConfigFile is required to figure out what gem path and gem home to use. ?This involves loading YAML as well.
>
> On the upside, RubyGems should start a little faster now that it no longer loads rubygems/specification, rubygems/config_file or yaml.
> _______________________________________________
> Rubygems-developers mailing list
> http://rubyforge.org/projects/rubygems
> Rubygems-developers at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubygems-developers
>

From drbrain at segment7.net  Mon Jan  3 20:39:20 2011
From: drbrain at segment7.net (Eric Hodel)
Date: Mon, 3 Jan 2011 17:39:20 -0800
Subject: [Rubygems-developers] RubyGems on 1.9 workaround
In-Reply-To: <AANLkTik3kQLy2=pi-a8sxTWjKyWpt=Tn+xBywvmcrDre@mail.gmail.com>
References: <DD4E5889-0528-4D5B-8EA9-6FCB193CCA0B@segment7.net>
	<AANLkTik3kQLy2=pi-a8sxTWjKyWpt=Tn+xBywvmcrDre@mail.gmail.com>
Message-ID: <F666BB7E-8C7E-4A5A-9D43-7C442BCA0AC8@segment7.net>

On Jan 3, 2011, at 16:33, Nick Quaranto wrote:

> Nice. Is this going released as 1.4.2?

Dropping support for two features is too much for a 1.4.2.

> Also, a blog post denoting the history of why this situation is all
> messed up would be really nice to distribute. Watching the tweets for
> "rubygems" (an uptime notifier for me along with general PR watch)
> about this 1.9 stuff makes me a sad panda.

Yes ?

While I have earned a thicker skin based on my trips around the internet it never seems to be thick enough.

I'll try to write a blog post tomorrow.

From ryand-ruby at zenspider.com  Wed Jan  5 04:21:28 2011
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Wed, 5 Jan 2011 01:21:28 -0800
Subject: [Rubygems-developers] Gem.find_files is busted
Message-ID: <3E9FB8B2-B8DC-4FF0-8600-9AFDBF47F24E@zenspider.com>

Gem.find_files("hoe/*.rb") returns [].

I just pushed a fix that gets it working again.

The changes made to Gem.find_files were completely untested. Adding 'raise "no"' at the top of the find_all_dot_rb method caused no tests to fail. I've switched find_files back to Searcher#find_all.

Since the method didn't actually work as intended, I've removed it. Since find_files was the only caller and it has only been publicly available for 6 days, this _should_ be fairly safe. But I'll obviously concede this change if we know of someone using it. My guess is that could only be bundler. I just looked at their commits and it looks clean.

I think this needs to go out in 1.4.2. Any objections?

Should eric's changes to defeat gem_prelude go in 1.4.2 as well? Or does it need more testing and/or more time to percolate?


From luislavena at gmail.com  Wed Jan  5 06:53:24 2011
From: luislavena at gmail.com (Luis Lavena)
Date: Wed, 5 Jan 2011 08:53:24 -0300
Subject: [Rubygems-developers] Gem.find_files is busted
In-Reply-To: <3E9FB8B2-B8DC-4FF0-8600-9AFDBF47F24E@zenspider.com>
References: <3E9FB8B2-B8DC-4FF0-8600-9AFDBF47F24E@zenspider.com>
Message-ID: <AANLkTi=0V0GKxfnnVi4UP=ADnkArQh=O0HiFfqdnOdHW@mail.gmail.com>

On Wed, Jan 5, 2011 at 6:21 AM, Ryan Davis <ryand-ruby at zenspider.com> wrote:
>
> Should eric's changes to defeat gem_prelude go in 1.4.2 as well? Or does it need more testing and/or more time to percolate?
>

I would like to have a bit more of time to test under 1.9.2 specially
in the light of your gem_prelude kill conversation.
-- 
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 Jan  6 12:20:12 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu,  6 Jan 2011 12:20:12 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28824 ] Add way to load gem
	commands that does not load them whenever rubygems is loaded
Message-ID: <20110106172012.599AF18583BC@rubyforge.org>

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

Category: `gem` commands (other)
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: M G (grosser)
Assigned to: Nobody (None)
Summary: Add way to load gem commands that does not load them whenever rubygems is loaded

Initial Comment:
If i install something like gem-open / gem-dependet they are loaded every time rubygems is loaded (all rubygem_plugin.rb`s are loaded) which is an overhead and prevents these gems from having any dependency (which then too would be required)

Therefore I propose that when doing "gem foo" all rubygems_command.rb files are parsed, but this should not happen when simply doing 'require "rubygems"'

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

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

From noreply at rubyforge.org  Thu Jan  6 12:21:29 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu,  6 Jan 2011 12:21:29 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28825 ] Add an url to this
	bug reporter to the readme, i needed to google it...
Message-ID: <20110106172129.24C8019782DB@rubyforge.org>

Bugs item #28825, was opened at 2011-01-06 17:21
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28825&group_id=126

Category: documentation
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: M G (grosser)
Assigned to: Nobody (None)
Summary: Add an url to this bug reporter to the readme, i needed to google it...

Initial Comment:
message body is required

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

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

From noreply at rubyforge.org  Thu Jan  6 12:24:03 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu,  6 Jan 2011 12:24:03 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28826 ] Add --recursive to
	gem dependency
Message-ID: <20110106172403.3055A18583BA@rubyforge.org>

Bugs item #28826, was opened at 2011-01-06 17:24
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28826&group_id=126

Category: `gem` commands (other)
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: M G (grosser)
Assigned to: Nobody (None)
Summary: Add --recursive to gem dependency

Initial Comment:
I want to see all dependencies of a gem, so please add a way to see them e.g. gem dependency passenger --recursive


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

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

From noreply at rubyforge.org  Thu Jan  6 12:25:56 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu,  6 Jan 2011 12:25:56 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28827 ] add --version to gem
	clean
Message-ID: <20110106172556.7603D19782DB@rubyforge.org>

Bugs item #28827, was opened at 2011-01-06 17:25
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28827&group_id=126

Category: `gem` commands (other)
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: M G (grosser)
Assigned to: Nobody (None)
Summary: add --version to gem clean

Initial Comment:
I want to e.g. remove all versions of rack except 1.0.1 --> gem clean rack --version 1.0.1

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

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

From noreply at rubyforge.org  Thu Jan  6 13:01:33 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu,  6 Jan 2011 13:01:33 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28824 ] Add way to load gem
	commands that does not load them whenever rubygems is loaded
Message-ID: <20110106180133.EF41D18583BA@rubyforge.org>

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

Category: `gem` commands (other)
Group: None
>Status: Closed
>Resolution: Out of Date
Priority: 3
Submitted By: M G (grosser)
>Assigned to: Luis Lavena (luislavena)
Summary: Add way to load gem commands that does not load them whenever rubygems is loaded

Initial Comment:
If i install something like gem-open / gem-dependet they are loaded every time rubygems is loaded (all rubygem_plugin.rb`s are loaded) which is an overhead and prevents these gems from having any dependency (which then too would be required)

Therefore I propose that when doing "gem foo" all rubygems_command.rb files are parsed, but this should not happen when simply doing 'require "rubygems"'

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

>Comment By: Luis Lavena (luislavena)
Date: 2011-01-06 15:01

Message:
Hello,

This is what RubyGems 1.4.0 already does, no gem plugin is loaded when require 'rubygems' is invoked.


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

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

From erik at hollensbe.org  Thu Jan  6 19:14:49 2011
From: erik at hollensbe.org (Erik Hollensbe)
Date: Thu, 6 Jan 2011 19:14:49 -0500
Subject: [Rubygems-developers] [halp] rubygems-test could use a beating!
Message-ID: <541D8F9D-149E-4B4D-9310-869397B58709@hollensbe.org>

rubygems-test is a testing facility for gems. It provides several
features:

* A replaced 'gem test' command that leverages rake and an opt-in
  system, via the gemspec, that allows authors to indicate what gems
  can be tested by end users.
* The ability to upload the verbatim test results to
  http://www.gem-testers.org, a sister site used to collect and
  aggregate these reports.
* Configuration facilities to run 'gem test' automatically and to
  uninstall gems with failing tests. (These are not the defaults)

More info:
https://github.com/rubygems/rubygems-test/blob/master/README.txt

We need your help testing these features and the
http://www.gem-testers.org site. If you have time, run:

$ gem install rubygems-test
$ gem test rubygems-test

(may require sudo)

On your platform(s) of choice, and could post any adverse results you
receive to me directly or the list, I'd greatly appreciate it. We've
been beating on it for a few months now, but this is the first large
scale test. Ensure you have 0.2.0, which should be mirrored by now.

There are some issues on Windows still and they're still being worked
out. The tests *should* run and pass however, just with additional
warnings about double-requires. I should resolve these before the
week is out.

Additionally, if you have concerns about how testing is facilitated or
suggestions, please feel free to reply to list, me directly, or use our
tracker:

http://github.com/rubygems/rubygems-test/issues

Comments welcome! We are aiming for a more public release this
weekend, and we're hoping to iron out the last of the major bugs
before then.

Thanks for your time!

-Erik


From ryand-ruby at zenspider.com  Thu Jan  6 19:53:54 2011
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Thu, 6 Jan 2011 16:53:54 -0800
Subject: [Rubygems-developers] [ANN] rubygems 1.4.2 released
Message-ID: <FE2647DD-305F-4D0E-BEEF-020BE5611D84@zenspider.com>

Again: DO NOT UPDATE RUBYGEMS ON RUBY 1.9! See UPGRADING.rdoc for details.

rubygems version 1.4.2 has been released!

* <http://rubygems.org>
* <http://docs.rubygems.org>
* <http://help.rubygems.org>
* <http://github.com/rubygems>

RubyGems is a package management framework for Ruby.

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

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

To upgrade to the latest RubyGems, run:

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

-----

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

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

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

-----

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

1. Download from: http://rubyforge.org/frs/?group_id=126
2. Unpack into a directory and cd there
3. Install with: ruby setup.rb  # you may need admin/root privilege

For more details and other options, see:

 ruby setup.rb --help

Changes:

=== 1.4.2 / 2011-01-06

Bug fixes:

* Gem::Versions: "1.b1" != "1.b.1", but "1.b1" eql? "1.b.1". Fixes gem indexing.
* Fixed Gem.find_files.
* Removed otherwise unused #find_all_dot_rb. Only 6 days old and hella buggy.


From luislavena at gmail.com  Thu Jan  6 20:49:11 2011
From: luislavena at gmail.com (Luis Lavena)
Date: Thu, 6 Jan 2011 22:49:11 -0300
Subject: [Rubygems-developers] [halp] rubygems-test could use a beating!
In-Reply-To: <541D8F9D-149E-4B4D-9310-869397B58709@hollensbe.org>
References: <541D8F9D-149E-4B4D-9310-869397B58709@hollensbe.org>
Message-ID: <AANLkTim7+mo3dOXcFchkhuG_LikfvwRttJOdxXxeRPGj@mail.gmail.com>

On Thu, Jan 6, 2011 at 9:14 PM, Erik Hollensbe <erik at hollensbe.org> wrote:
> rubygems-test is a testing facility for gems. It provides several
> features:
>
> $ gem install rubygems-test
> $ gem test rubygems-test
>
> (may require sudo)
>

C:\Users\Luis>gem test rubygems-test --backtrace
ERROR:  While executing gem ... (NameError)
    uninitialized constant Fcntl::F_SETFD
        C:/Users/Luis/.gem/ruby/x86-mingw32/1.8/gems/rubygems-test-0.2.0/lib/open4-vendor.rb:20:in
`popen4'
        C:/Users/Luis/.gem/ruby/x86-mingw32/1.8/gems/rubygems-test-0.2.0/lib/rubygems/commands/test_command.rb:236:in
`run_tests'
        C:/Users/Luis/.gem/ruby/x86-mingw32/1.8/gems/rubygems-test-0.2.0/lib/rubygems/commands/test_command.rb:188:in
`chdir'
        C:/Users/Luis/.gem/ruby/x86-mingw32/1.8/gems/rubygems-test-0.2.0/lib/rubygems/commands/test_command.rb:188:in
`run_tests'
        C:/Users/Luis/.gem/ruby/x86-mingw32/1.8/gems/rubygems-test-0.2.0/lib/rubygems/commands/test_command.rb:282:in
`execute'
        C:/Users/Luis/.gem/ruby/x86-mingw32/1.8/gems/rubygems-test-0.2.0/lib/rubygems/commands/test_command.rb:266:in
`each'
        C:/Users/Luis/.gem/ruby/x86-mingw32/1.8/gems/rubygems-test-0.2.0/lib/rubygems/commands/test_command.rb:266:in
`execute'
        C:/Users/Luis/Tools/Ruby/ruby-1.8.7-p330-i386-mingw32/lib/ruby/site_ruby/1.8/rubygems/command.rb:278:in
`invoke'
        C:/Users/Luis/Tools/Ruby/ruby-1.8.7-p330-i386-mingw32/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:134:in
`process_args'
        C:/Users/Luis/Tools/Ruby/ruby-1.8.7-p330-i386-mingw32/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:104:in
`run'
        C:/Users/Luis/Tools/Ruby/ruby-1.8.7-p330-i386-mingw32/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:63:in
`run'
        C:/Users/Luis/Tools/Ruby/ruby-1.8.7-p330-i386-mingw32/bin/gem:21

> There are some issues on Windows still and they're still being worked
> out. The tests *should* run and pass however, just with additional
> warnings about double-requires. I should resolve these before the
> week is out.
>

Above example doesn't pass the test. Tried cloning rubygems-test and
running rake test there:

C:\Users\Luis\Projects\oss\rubygems-test>rake test
(in C:/Users/Luis/Projects/oss/rubygems-test)
C:/Users/Luis/Tools/Ruby/ruby-1.8.7-p330-i386-mingw32/bin/ruby.exe -w
-Ilib;bin;test;. -e 'require "rubygems"; require "test/unit"; require
"test/test_execute.rb"' --
./test/helper.rb:57: warning: method redefined; discarding old setup
Loaded suite -e
Started

----- This test is interactive -----

...Successfully uninstalled test-gem-0.0.0
ERROR:  Could not find gem test-gem (0.0.0)
.Successfully uninstalled test-gem-0.0.0
ERROR:  Couldn't find rakefile -- this gem cannot be tested. Aborting.
Successfully uninstalled test-gem-0.0.0
...
Finished in 2.424139 seconds.

7 tests, 13 assertions, 0 failures, 0 errors

The ERROR is the part I'm not confident with :-P

> Comments welcome! We are aiming for a more public release this
> weekend, and we're hoping to iron out the last of the major bugs
> before then.
>

I would like to know what is required from the Windows side (if you
heard of problems beyond the ones I shown above).

I can spare some hours this weekend to hack some solutions if required.

Cheers and thank you for working on this.
-- 
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 erik at hollensbe.org  Thu Jan  6 21:17:26 2011
From: erik at hollensbe.org (Erik Hollensbe)
Date: Thu, 6 Jan 2011 21:17:26 -0500
Subject: [Rubygems-developers] [halp] rubygems-test could use a beating!
In-Reply-To: <AANLkTim7+mo3dOXcFchkhuG_LikfvwRttJOdxXxeRPGj@mail.gmail.com>
References: <541D8F9D-149E-4B4D-9310-869397B58709@hollensbe.org>
	<AANLkTim7+mo3dOXcFchkhuG_LikfvwRttJOdxXxeRPGj@mail.gmail.com>
Message-ID: <0FAF5C91-8262-45F1-AACD-63022B8656E5@hollensbe.org>

On Jan 6, 2011, at 8:49 PM, Luis Lavena wrote:

> C:\Users\Luis>gem test rubygems-test --backtrace
> ERROR:  While executing gem ... (NameError)
>    uninitialized constant Fcntl::F_SETFD
>        C:/Users/Luis/.gem/ruby/x86-mingw32/1.8/gems/rubygems-test-0.2.0/lib/open4-vendor.rb:20:in
> `popen4'
> 
<snip>

This is definitely not intended. I'm guessing its the vendored open4 that we're using to support 1.8 elsewhere, and probably just needs a special case in the procs we use to abstract the IO portion of the system. You can see in /lib/rubygems/commands/test_command.rb we case through a couple of scenarios to support 1.8, 1.9, JRuby, etc. I imagine we just need a case that basically says, "if 1.8 and on windows, use the 1.9 version", but I might be off on that. If not we can probably combine the procs I use to build out the reader into something cohesive.

> Above example doesn't pass the test. Tried cloning rubygems-test and
> running rake test there:
> 
> C:\Users\Luis\Projects\oss\rubygems-test>rake test
> (in C:/Users/Luis/Projects/oss/rubygems-test)
> C:/Users/Luis/Tools/Ruby/ruby-1.8.7-p330-i386-mingw32/bin/ruby.exe -w
> -Ilib;bin;test;. -e 'require "rubygems"; require "test/unit"; require
> "test/test_execute.rb"' --
> ./test/helper.rb:57: warning: method redefined; discarding old setup
> Loaded suite -e
> Started
> 
> ----- This test is interactive -----
> 
> ...Successfully uninstalled test-gem-0.0.0
> ERROR:  Could not find gem test-gem (0.0.0)
> .Successfully uninstalled test-gem-0.0.0
> ERROR:  Couldn't find rakefile -- this gem cannot be tested. Aborting.
> Successfully uninstalled test-gem-0.0.0
> ...
> Finished in 2.424139 seconds.
> 
> 7 tests, 13 assertions, 0 failures, 0 errors
> 
> The ERROR is the part I'm not confident with :-P

That ERROR you see there is actually intended, it's testing the system itself, including the failure cases.

> I would like to know what is required from the Windows side (if you
> heard of problems beyond the ones I shown above).

There's a circular require issue (this is what I was talking about in that email) in 1.9 mingw that I haven't figured out yet, but I'll keep hacking on it, I need to learn more about windows ruby anyhow. :)

> I can spare some hours this weekend to hack some solutions if required.

That would be *awesome*. Thank you!

-Erik

From erik at hollensbe.org  Fri Jan  7 09:35:19 2011
From: erik at hollensbe.org (Erik Hollensbe)
Date: Fri, 7 Jan 2011 09:35:19 -0500
Subject: [Rubygems-developers] [halp] rubygems-test could use a beating!
In-Reply-To: <541D8F9D-149E-4B4D-9310-869397B58709@hollensbe.org>
References: <541D8F9D-149E-4B4D-9310-869397B58709@hollensbe.org>
Message-ID: <62BE0858-F9BF-4FFC-B00F-A527B791D2B1@hollensbe.org>


On Jan 6, 2011, at 7:14 PM, Erik Hollensbe wrote:

> rubygems-test is a testing facility for gems. It provides several
> features:
> 

On 1.9, you will see a circular require issue (a LOT of output) on most installations. I'm aware of the issue and hope to get a fix out tonight.

The warnings are harmless.

-Erik


From noreply at rubyforge.org  Fri Jan  7 20:00:46 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri,  7 Jan 2011 20:00:46 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28837 ] `gem update` attempts
	to upgrade rubygems without using the --system flag
Message-ID: <20110108010046.3CE61185837F@rubyforge.org>

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

Category: `gem` commands (other)
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Lee Jarvis (injekt)
Assigned to: Nobody (None)
Summary: `gem update` attempts to upgrade rubygems without using the --system flag

Initial Comment:
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [i686-linux]
  - INSTALLATION DIRECTORY: /home/injekt/.rvm/gems/ruby-1.9.2-p136
  - RUBY EXECUTABLE: /home/injekt/.rvm/rubies/ruby-1.9.2-p136/bin/ruby
  - EXECUTABLE DIRECTORY: /home/injekt/.rvm/gems/ruby-1.9.2-p136/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /home/injekt/.rvm/gems/ruby-1.9.2-p136
     - /home/injekt/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://gemcutter.org

Verbose output of `gem update` can be found attached.

Even after running `gem uninstall rubygems-update`, this issue still occurs.

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

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

From noreply at rubyforge.org  Sat Jan  8 02:24:50 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sat,  8 Jan 2011 02:24:50 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28837 ] `gem update` attempts
	to upgrade rubygems without using the --system flag
Message-ID: <20110108072450.A3B201678320@rubyforge.org>

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

Category: `gem` commands (other)
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Lee Jarvis (injekt)
Assigned to: Nobody (None)
Summary: `gem update` attempts to upgrade rubygems without using the --system flag

Initial Comment:
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [i686-linux]
  - INSTALLATION DIRECTORY: /home/injekt/.rvm/gems/ruby-1.9.2-p136
  - RUBY EXECUTABLE: /home/injekt/.rvm/rubies/ruby-1.9.2-p136/bin/ruby
  - EXECUTABLE DIRECTORY: /home/injekt/.rvm/gems/ruby-1.9.2-p136/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /home/injekt/.rvm/gems/ruby-1.9.2-p136
     - /home/injekt/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://gemcutter.org

Verbose output of `gem update` can be found attached.

Even after running `gem uninstall rubygems-update`, this issue still occurs.

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

>Comment By: Ryan Davis (zenspider)
Date: 2011-01-07 23:24

Message:
Not attached. Make sure you check that infernal checkbox.

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

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

From noreply at rubyforge.org  Sat Jan  8 04:46:34 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sat,  8 Jan 2011 04:46:34 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28837 ] `gem update` attempts
	to upgrade rubygems without using the --system flag
Message-ID: <20110108094634.404C91858387@rubyforge.org>

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

Category: `gem` commands (other)
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Lee Jarvis (injekt)
Assigned to: Nobody (None)
Summary: `gem update` attempts to upgrade rubygems without using the --system flag

Initial Comment:
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [i686-linux]
  - INSTALLATION DIRECTORY: /home/injekt/.rvm/gems/ruby-1.9.2-p136
  - RUBY EXECUTABLE: /home/injekt/.rvm/rubies/ruby-1.9.2-p136/bin/ruby
  - EXECUTABLE DIRECTORY: /home/injekt/.rvm/gems/ruby-1.9.2-p136/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /home/injekt/.rvm/gems/ruby-1.9.2-p136
     - /home/injekt/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://gemcutter.org

Verbose output of `gem update` can be found attached.

Even after running `gem uninstall rubygems-update`, this issue still occurs.

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

Comment By: Ryan Davis (zenspider)
Date: 2011-01-08 07:24

Message:
Not attached. Make sure you check that infernal checkbox.

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

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

From noreply at rubyforge.org  Sat Jan  8 04:47:14 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sat,  8 Jan 2011 04:47:14 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28837 ] `gem update` attempts
	to upgrade rubygems without using the --system flag
Message-ID: <20110108094714.3F64C1858387@rubyforge.org>

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

Category: `gem` commands (other)
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Lee Jarvis (injekt)
Assigned to: Nobody (None)
Summary: `gem update` attempts to upgrade rubygems without using the --system flag

Initial Comment:
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [i686-linux]
  - INSTALLATION DIRECTORY: /home/injekt/.rvm/gems/ruby-1.9.2-p136
  - RUBY EXECUTABLE: /home/injekt/.rvm/rubies/ruby-1.9.2-p136/bin/ruby
  - EXECUTABLE DIRECTORY: /home/injekt/.rvm/gems/ruby-1.9.2-p136/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /home/injekt/.rvm/gems/ruby-1.9.2-p136
     - /home/injekt/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://gemcutter.org

Verbose output of `gem update` can be found attached.

Even after running `gem uninstall rubygems-update`, this issue still occurs.

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

>Comment By: Lee Jarvis (injekt)
Date: 2011-01-08 09:47

Message:
Whoops! Didn't see that there. Attached.

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

Comment By: Ryan Davis (zenspider)
Date: 2011-01-08 07:24

Message:
Not attached. Make sure you check that infernal checkbox.

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

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

From noreply at rubyforge.org  Sat Jan  8 14:07:20 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sat,  8 Jan 2011 14:07:20 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28839 ] File not found:
	README when upgrading to 1.4.2
Message-ID: <20110108190720.B5D491858391@rubyforge.org>

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

Category: other
Group: v1.4.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: File not found: README when upgrading to 1.4.2

Initial Comment:
I saw this warning when I updated from rubygems 1.3.5 to 1.4.2 on FreeBSD 7, with ruby 1.8.6:

File not found: README

Regards,

Dan



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

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

From noreply at rubyforge.org  Sun Jan  9 01:19:48 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun,  9 Jan 2011 01:19:48 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28837 ] `gem update` attempts
	to upgrade rubygems without using the --system flag
Message-ID: <20110109061948.C03EC1858374@rubyforge.org>

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

Category: `gem` commands (other)
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Lee Jarvis (injekt)
Assigned to: Nobody (None)
Summary: `gem update` attempts to upgrade rubygems without using the --system flag

Initial Comment:
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [i686-linux]
  - INSTALLATION DIRECTORY: /home/injekt/.rvm/gems/ruby-1.9.2-p136
  - RUBY EXECUTABLE: /home/injekt/.rvm/rubies/ruby-1.9.2-p136/bin/ruby
  - EXECUTABLE DIRECTORY: /home/injekt/.rvm/gems/ruby-1.9.2-p136/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /home/injekt/.rvm/gems/ruby-1.9.2-p136
     - /home/injekt/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://gemcutter.org

Verbose output of `gem update` can be found attached.

Even after running `gem uninstall rubygems-update`, this issue still occurs.

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

>Comment By: Ryan Davis (zenspider)
Date: 2011-01-08 22:19

Message:
I can't repro this at all:

% gem update -V
Updating installed gems
Nothing to update


% gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [x86_64-darwin10.6.0]
  - INSTALLATION DIRECTORY: /Users/ryan/.rvm/gems/ruby-1.9.2-p136
  - RUBY EXECUTABLE: /Users/ryan/.rvm/rubies/ruby-1.9.2-p136/bin/ruby
  - EXECUTABLE DIRECTORY: /Users/ryan/.rvm/gems/ruby-1.9.2-p136/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-darwin-10
  - GEM PATHS:
     - /Users/ryan/.rvm/gems/ruby-1.9.2-p136
     - /Users/ryan/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - "gemcutter_key" => "********************************"
  - REMOTE SOURCES:
     - http://rubygems.org/


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

Comment By: Lee Jarvis (injekt)
Date: 2011-01-08 01:47

Message:
Whoops! Didn't see that there. Attached.

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

Comment By: Ryan Davis (zenspider)
Date: 2011-01-07 23:24

Message:
Not attached. Make sure you check that infernal checkbox.

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

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

From noreply at rubyforge.org  Sun Jan  9 01:21:04 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun,  9 Jan 2011 01:21:04 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28837 ] `gem update` attempts
	to upgrade rubygems without using the --system flag
Message-ID: <20110109062104.98C911858374@rubyforge.org>

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

Category: `gem` commands (other)
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Lee Jarvis (injekt)
>Assigned to: Ryan Davis (zenspider)
Summary: `gem update` attempts to upgrade rubygems without using the --system flag

Initial Comment:
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [i686-linux]
  - INSTALLATION DIRECTORY: /home/injekt/.rvm/gems/ruby-1.9.2-p136
  - RUBY EXECUTABLE: /home/injekt/.rvm/rubies/ruby-1.9.2-p136/bin/ruby
  - EXECUTABLE DIRECTORY: /home/injekt/.rvm/gems/ruby-1.9.2-p136/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /home/injekt/.rvm/gems/ruby-1.9.2-p136
     - /home/injekt/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://gemcutter.org

Verbose output of `gem update` can be found attached.

Even after running `gem uninstall rubygems-update`, this issue still occurs.

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

>Comment By: Ryan Davis (zenspider)
Date: 2011-01-08 22:21

Message:
I just updated:

https://github.com/rubygems/rubygems/blob/master/UPGRADING.rdoc

with force downgrade instructions appropriate for 1.9.2 & rubygems 1.4.x.

Without a working repro, I can't address this ticket and will prolly have to reject it.

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

Comment By: Ryan Davis (zenspider)
Date: 2011-01-08 22:19

Message:
I can't repro this at all:

% gem update -V
Updating installed gems
Nothing to update


% gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [x86_64-darwin10.6.0]
  - INSTALLATION DIRECTORY: /Users/ryan/.rvm/gems/ruby-1.9.2-p136
  - RUBY EXECUTABLE: /Users/ryan/.rvm/rubies/ruby-1.9.2-p136/bin/ruby
  - EXECUTABLE DIRECTORY: /Users/ryan/.rvm/gems/ruby-1.9.2-p136/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-darwin-10
  - GEM PATHS:
     - /Users/ryan/.rvm/gems/ruby-1.9.2-p136
     - /Users/ryan/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - "gemcutter_key" => "********************************"
  - REMOTE SOURCES:
     - http://rubygems.org/


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

Comment By: Lee Jarvis (injekt)
Date: 2011-01-08 01:47

Message:
Whoops! Didn't see that there. Attached.

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

Comment By: Ryan Davis (zenspider)
Date: 2011-01-07 23:24

Message:
Not attached. Make sure you check that infernal checkbox.

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

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

From noreply at rubyforge.org  Sun Jan  9 01:57:24 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun,  9 Jan 2011 01:57:24 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28837 ] `gem update` attempts
	to upgrade rubygems without using the --system flag
Message-ID: <20110109065724.2E5111858321@rubyforge.org>

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

Category: `gem` commands (other)
Group: v1.3.x
Status: Open
>Resolution: Accepted
Priority: 3
Submitted By: Lee Jarvis (injekt)
Assigned to: Ryan Davis (zenspider)
Summary: `gem update` attempts to upgrade rubygems without using the --system flag

Initial Comment:
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [i686-linux]
  - INSTALLATION DIRECTORY: /home/injekt/.rvm/gems/ruby-1.9.2-p136
  - RUBY EXECUTABLE: /home/injekt/.rvm/rubies/ruby-1.9.2-p136/bin/ruby
  - EXECUTABLE DIRECTORY: /home/injekt/.rvm/gems/ruby-1.9.2-p136/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /home/injekt/.rvm/gems/ruby-1.9.2-p136
     - /home/injekt/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://gemcutter.org

Verbose output of `gem update` can be found attached.

Even after running `gem uninstall rubygems-update`, this issue still occurs.

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

>Comment By: Ryan Davis (zenspider)
Date: 2011-01-08 22:57

Message:
OK. I have a repro, and this is indeed a bug:

% gem uninstall -a rubygems-update
% gem install rubygems-update -v 1.3.7
% gem update -V

Extra notes:

It doesn't actually update your system, as it fails before writing anything.

It shouldn't be doing what it is doing regardless. We need to look into this asap.

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

Comment By: Ryan Davis (zenspider)
Date: 2011-01-08 22:21

Message:
I just updated:

https://github.com/rubygems/rubygems/blob/master/UPGRADING.rdoc

with force downgrade instructions appropriate for 1.9.2 & rubygems 1.4.x.

Without a working repro, I can't address this ticket and will prolly have to reject it.

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

Comment By: Ryan Davis (zenspider)
Date: 2011-01-08 22:19

Message:
I can't repro this at all:

% gem update -V
Updating installed gems
Nothing to update


% gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [x86_64-darwin10.6.0]
  - INSTALLATION DIRECTORY: /Users/ryan/.rvm/gems/ruby-1.9.2-p136
  - RUBY EXECUTABLE: /Users/ryan/.rvm/rubies/ruby-1.9.2-p136/bin/ruby
  - EXECUTABLE DIRECTORY: /Users/ryan/.rvm/gems/ruby-1.9.2-p136/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-darwin-10
  - GEM PATHS:
     - /Users/ryan/.rvm/gems/ruby-1.9.2-p136
     - /Users/ryan/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - "gemcutter_key" => "********************************"
  - REMOTE SOURCES:
     - http://rubygems.org/


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

Comment By: Lee Jarvis (injekt)
Date: 2011-01-08 01:47

Message:
Whoops! Didn't see that there. Attached.

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

Comment By: Ryan Davis (zenspider)
Date: 2011-01-07 23:24

Message:
Not attached. Make sure you check that infernal checkbox.

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

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

From noreply at rubyforge.org  Sun Jan  9 01:57:57 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun,  9 Jan 2011 01:57:57 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28837 ] `gem update` attempts
	to upgrade rubygems without using the --system flag
Message-ID: <20110109065757.309DC1858321@rubyforge.org>

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

Category: `gem` commands (other)
>Group: v1.4.x
Status: Open
Resolution: Accepted
Priority: 3
Submitted By: Lee Jarvis (injekt)
Assigned to: Ryan Davis (zenspider)
Summary: `gem update` attempts to upgrade rubygems without using the --system flag

Initial Comment:
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [i686-linux]
  - INSTALLATION DIRECTORY: /home/injekt/.rvm/gems/ruby-1.9.2-p136
  - RUBY EXECUTABLE: /home/injekt/.rvm/rubies/ruby-1.9.2-p136/bin/ruby
  - EXECUTABLE DIRECTORY: /home/injekt/.rvm/gems/ruby-1.9.2-p136/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /home/injekt/.rvm/gems/ruby-1.9.2-p136
     - /home/injekt/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://gemcutter.org

Verbose output of `gem update` can be found attached.

Even after running `gem uninstall rubygems-update`, this issue still occurs.

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

Comment By: Ryan Davis (zenspider)
Date: 2011-01-08 22:57

Message:
OK. I have a repro, and this is indeed a bug:

% gem uninstall -a rubygems-update
% gem install rubygems-update -v 1.3.7
% gem update -V

Extra notes:

It doesn't actually update your system, as it fails before writing anything.

It shouldn't be doing what it is doing regardless. We need to look into this asap.

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

Comment By: Ryan Davis (zenspider)
Date: 2011-01-08 22:21

Message:
I just updated:

https://github.com/rubygems/rubygems/blob/master/UPGRADING.rdoc

with force downgrade instructions appropriate for 1.9.2 & rubygems 1.4.x.

Without a working repro, I can't address this ticket and will prolly have to reject it.

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

Comment By: Ryan Davis (zenspider)
Date: 2011-01-08 22:19

Message:
I can't repro this at all:

% gem update -V
Updating installed gems
Nothing to update


% gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [x86_64-darwin10.6.0]
  - INSTALLATION DIRECTORY: /Users/ryan/.rvm/gems/ruby-1.9.2-p136
  - RUBY EXECUTABLE: /Users/ryan/.rvm/rubies/ruby-1.9.2-p136/bin/ruby
  - EXECUTABLE DIRECTORY: /Users/ryan/.rvm/gems/ruby-1.9.2-p136/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-darwin-10
  - GEM PATHS:
     - /Users/ryan/.rvm/gems/ruby-1.9.2-p136
     - /Users/ryan/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - "gemcutter_key" => "********************************"
  - REMOTE SOURCES:
     - http://rubygems.org/


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

Comment By: Lee Jarvis (injekt)
Date: 2011-01-08 01:47

Message:
Whoops! Didn't see that there. Attached.

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

Comment By: Ryan Davis (zenspider)
Date: 2011-01-07 23:24

Message:
Not attached. Make sure you check that infernal checkbox.

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

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

From noreply at rubyforge.org  Sun Jan  9 03:05:37 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun,  9 Jan 2011 03:05:37 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28839 ] File not found:
	README when upgrading to 1.4.2
Message-ID: <20110109080537.6537A1858344@rubyforge.org>

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

Category: other
Group: v1.4.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: File not found: README when upgrading to 1.4.2

Initial Comment:
I saw this warning when I updated from rubygems 1.3.5 to 1.4.2 on FreeBSD 7, with ruby 1.8.6:

File not found: README

Regards,

Dan



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

>Comment By: Ryan Davis (zenspider)
Date: 2011-01-09 00:05

Message:
rdoc problem

Installing RDoc documentation for rubygems-update-1.3.7...
Could not find main page README
Could not find main page README
Could not find main page README
Could not find main page README


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

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

From noreply at rubyforge.org  Sun Jan  9 03:05:50 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun,  9 Jan 2011 03:05:50 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28839 ] File not found:
	README when upgrading to 1.4.2
Message-ID: <20110109080550.611361858356@rubyforge.org>

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

Category: other
Group: v1.4.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Daniel Berger (djberg96)
>Assigned to: Ryan Davis (zenspider)
Summary: File not found: README when upgrading to 1.4.2

Initial Comment:
I saw this warning when I updated from rubygems 1.3.5 to 1.4.2 on FreeBSD 7, with ruby 1.8.6:

File not found: README

Regards,

Dan



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

Comment By: Ryan Davis (zenspider)
Date: 2011-01-09 00:05

Message:
rdoc problem

Installing RDoc documentation for rubygems-update-1.3.7...
Could not find main page README
Could not find main page README
Could not find main page README
Could not find main page README


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

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

From noreply at rubyforge.org  Sun Jan  9 03:10:25 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun,  9 Jan 2011 03:10:25 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28839 ] File not found:
	README when upgrading to 1.4.2
Message-ID: <20110109081025.C609F1858356@rubyforge.org>

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

Category: other
Group: v1.4.x
>Status: Closed
Resolution: None
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Ryan Davis (zenspider)
Summary: File not found: README when upgrading to 1.4.2

Initial Comment:
I saw this warning when I updated from rubygems 1.3.5 to 1.4.2 on FreeBSD 7, with ruby 1.8.6:

File not found: README

Regards,

Dan



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

>Comment By: Ryan Davis (zenspider)
Date: 2011-01-09 00:10

Message:
OK. The problem is that the 1.3.7 and below had README and we switched up to README.rdoc in 1.4.0. 

4123 % gem spec rubygems-update -v 1.3.5 | grep README
- README
- README
4124 % gem spec rubygems-update -v 1.3.7 | grep README
- README
- README
4125 % gem spec rubygems-update -v 1.4.2 | grep README
- README.rdoc
- README.rdoc
- README.rdoc
4129 % gem update --system
Updating RubyGems
Updating rubygems-update
Successfully installed rubygems-update-1.4.2
Updating RubyGems to 1.4.2
Installing RubyGems 1.4.2
RubyGems 1.4.2 installed
File not found: README
4130 % echo $?
0

Since this is just a warning and only for rdoc (it won't affect RI info), I'm gonna go ahead and close this bug. Feel free to reopen if you feel I'm missing something.

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

Comment By: Ryan Davis (zenspider)
Date: 2011-01-09 00:05

Message:
rdoc problem

Installing RDoc documentation for rubygems-update-1.3.7...
Could not find main page README
Could not find main page README
Could not find main page README
Could not find main page README


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

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

From thewoolleyman at gmail.com  Sun Jan  9 05:56:21 2011
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Sun, 9 Jan 2011 03:56:21 -0700
Subject: [Rubygems-developers] Release coming,
	but still no response on broken 1.9.x CI builds
Message-ID: <AANLkTi=dye+Q9JYUtghGaiB-+rGDisV9xUZPt8sBOQMK@mail.gmail.com>

On Sat, Jan 8, 2011 at 11:16 PM,  <thewoolleyman+rubygems-ci at gmail.com> wrote:
> The build failed.
>
> CHANGES
> -------
> Revision ...414d2f8a78205ed0b2465dbdc7c2ab5fd2ffc371 committed by Ryan Davis <ryand-ruby at zenspider.com> on 2011-01-09 06:12:19
>
> ? ?Added appropriate instructions on downgrading on 1.9.2
>
> ?UPGRADING.rdoc | ? 13 +++++++++++++
> ?1 files changed, 13 insertions(+), 0 deletions(-)
> Revision ...86b5b973b1f75ddebe4de733f2a01311bff5dfc0 committed by Ryan Davis <ryand-ruby at zenspider.com> on 2011-01-06 23:59:45
>
> ? ?prepping for release
>
> ?History.txt ? ? | ? 10 +++++++++-
> ?lib/rubygems.rb | ? ?2 +-
> ?2 files changed, 10 insertions(+), 2 deletions(-)
>
>
>
> See http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_1-p430/414d2f8a78205ed0b2465dbdc7c2ab5fd2ffc371 for details.

I see we are prepping for another release.  Just a gentle reminder
that CI is running now for all requested interpreters, it is still red
for 1.9.1 and 1.9.2, the failures are locally reproducible, and
there's still no response on the thread about the broken builds:

http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_1-p430
http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_2-p0
http://rubyforge.org/pipermail/rubygems-developers/2011-January/005974.html

I realize 1.9.x has issues, and these issues won't get addressed for
this release, but I'd at least like to see a response to my detailed
description of the failures, and tickets to ensure they are on the
radar.

Again, I have created a wrapper script to ensure these failures are
locally and easily reproducible under RVM outside the CI box.  Ball is
out of my court AFAIK because these errors are beyond my Rubygems
debugging fu (and available time).

If the developers show they care about getting and keeping CI green,
I'll keep it running, and even try to add more builds (JRuby,
Windows).  But if CI is just going to get ignored or paid lip service,
I don't want to waste my time.

Thanks,
-- Chad

From ryand-ruby at zenspider.com  Sun Jan  9 08:34:11 2011
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Sun, 9 Jan 2011 05:34:11 -0800
Subject: [Rubygems-developers] Release coming,
	but still no response on broken 1.9.x CI builds
In-Reply-To: <AANLkTi=dye+Q9JYUtghGaiB-+rGDisV9xUZPt8sBOQMK@mail.gmail.com>
References: <AANLkTi=dye+Q9JYUtghGaiB-+rGDisV9xUZPt8sBOQMK@mail.gmail.com>
Message-ID: <E3A1EC32-A0D4-4F6E-94E9-180E77B26F63@zenspider.com>


On Jan 9, 2011, at 02:56 , Chad Woolley wrote:

> http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_1-p430

This isn't reproducible on my side. I've got a clean run using rvm. Ah... rvm installed ruby 1.9.1p378. It is clean. 1.9.1p430 apparently has some regression in it on its side.

Please back up to 378 for the time-being. 

I just installed using "1.9.1" as my specifier. You might want to do the same for all of them so you're not constantly maintaining the versions.

> http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_2-p0

This isn't up to date anymore.


From thewoolleyman at gmail.com  Sun Jan  9 10:04:00 2011
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Sun, 9 Jan 2011 08:04:00 -0700
Subject: [Rubygems-developers] Release coming,
 but still no response on broken 1.9.x CI builds
In-Reply-To: <E3A1EC32-A0D4-4F6E-94E9-180E77B26F63@zenspider.com>
References: <AANLkTi=dye+Q9JYUtghGaiB-+rGDisV9xUZPt8sBOQMK@mail.gmail.com>
	<E3A1EC32-A0D4-4F6E-94E9-180E77B26F63@zenspider.com>
Message-ID: <AANLkTikT5BT0s0xyKX4FTdPG=zXh6HRMGHU3GSHzQOcR@mail.gmail.com>

On Sun, Jan 9, 2011 at 6:34 AM, Ryan Davis <ryand-ruby at zenspider.com> wrote:
>
> On Jan 9, 2011, at 02:56 , Chad Woolley wrote:
>
>> http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_1-p430
>
> This isn't reproducible on my side. I've got a clean run using rvm. Ah... rvm installed ruby 1.9.1p378. It is clean. 1.9.1p430 apparently has some regression in it on its side.
>
> Please back up to 378 for the time-being.
>
> I just installed using "1.9.1" as my specifier. You might want to do the same for all of them so you're not constantly maintaining the versions.
>
>> http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_2-p0
>
> This isn't up to date anymore.

OK, so to be clear, we want to try to commit to trying to keep the
latest (according to RVM) ruby releases green for 1.8.7, 1.9.1, and
1.9.2?  Pretty sure that is always the latest patch release, but
sometimes Wayne overrides the default to not be the latest if there
are problems (e.g. when there were segfaults in some of the <
1.8.7p299 releases).

Thanks,
-- Chad

From noreply at rubyforge.org  Sun Jan  9 17:52:56 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun,  9 Jan 2011 17:52:56 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28837 ] `gem update` attempts
	to upgrade rubygems without using the --system flag
Message-ID: <20110109225256.A58081858321@rubyforge.org>

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

Category: `gem` commands (other)
Group: v1.4.x
Status: Open
Resolution: Accepted
Priority: 3
Submitted By: Lee Jarvis (injekt)
Assigned to: Ryan Davis (zenspider)
Summary: `gem update` attempts to upgrade rubygems without using the --system flag

Initial Comment:
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [i686-linux]
  - INSTALLATION DIRECTORY: /home/injekt/.rvm/gems/ruby-1.9.2-p136
  - RUBY EXECUTABLE: /home/injekt/.rvm/rubies/ruby-1.9.2-p136/bin/ruby
  - EXECUTABLE DIRECTORY: /home/injekt/.rvm/gems/ruby-1.9.2-p136/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /home/injekt/.rvm/gems/ruby-1.9.2-p136
     - /home/injekt/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://gemcutter.org

Verbose output of `gem update` can be found attached.

Even after running `gem uninstall rubygems-update`, this issue still occurs.

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

>Comment By: Ryan Davis (zenspider)
Date: 2011-01-09 14:52

Message:
This _should_ (or at least could) be fixed on trunk. There are exactly zero tests for update --system but eric has a strategy for that so we'll get it patched up soon. In the meantime, manual verification would be great.

Just to note: we can't do a damn thing about this bug being released in 1.9... so... yeah.

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

Comment By: Ryan Davis (zenspider)
Date: 2011-01-08 22:57

Message:
OK. I have a repro, and this is indeed a bug:

% gem uninstall -a rubygems-update
% gem install rubygems-update -v 1.3.7
% gem update -V

Extra notes:

It doesn't actually update your system, as it fails before writing anything.

It shouldn't be doing what it is doing regardless. We need to look into this asap.

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

Comment By: Ryan Davis (zenspider)
Date: 2011-01-08 22:21

Message:
I just updated:

https://github.com/rubygems/rubygems/blob/master/UPGRADING.rdoc

with force downgrade instructions appropriate for 1.9.2 & rubygems 1.4.x.

Without a working repro, I can't address this ticket and will prolly have to reject it.

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

Comment By: Ryan Davis (zenspider)
Date: 2011-01-08 22:19

Message:
I can't repro this at all:

% gem update -V
Updating installed gems
Nothing to update


% gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [x86_64-darwin10.6.0]
  - INSTALLATION DIRECTORY: /Users/ryan/.rvm/gems/ruby-1.9.2-p136
  - RUBY EXECUTABLE: /Users/ryan/.rvm/rubies/ruby-1.9.2-p136/bin/ruby
  - EXECUTABLE DIRECTORY: /Users/ryan/.rvm/gems/ruby-1.9.2-p136/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-darwin-10
  - GEM PATHS:
     - /Users/ryan/.rvm/gems/ruby-1.9.2-p136
     - /Users/ryan/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - "gemcutter_key" => "********************************"
  - REMOTE SOURCES:
     - http://rubygems.org/


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

Comment By: Lee Jarvis (injekt)
Date: 2011-01-08 01:47

Message:
Whoops! Didn't see that there. Attached.

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

Comment By: Ryan Davis (zenspider)
Date: 2011-01-07 23:24

Message:
Not attached. Make sure you check that infernal checkbox.

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

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

From drbrain at segment7.net  Sun Jan  9 18:57:57 2011
From: drbrain at segment7.net (Eric Hodel)
Date: Sun, 9 Jan 2011 15:57:57 -0800
Subject: [Rubygems-developers] Release coming,
	but still no response on broken 1.9.x CI builds
In-Reply-To: <AANLkTi=dye+Q9JYUtghGaiB-+rGDisV9xUZPt8sBOQMK@mail.gmail.com>
References: <AANLkTi=dye+Q9JYUtghGaiB-+rGDisV9xUZPt8sBOQMK@mail.gmail.com>
Message-ID: <300AF5C3-C708-436E-86E5-F83000C61DC2@segment7.net>


On Jan 9, 2011, at 02:56, Chad Woolley wrote:

> On Sat, Jan 8, 2011 at 11:16 PM,  <thewoolleyman+rubygems-ci at gmail.com> wrote:
>> The build failed.
>> 
>> CHANGES
>> -------
>> Revision ...414d2f8a78205ed0b2465dbdc7c2ab5fd2ffc371 committed by Ryan Davis <ryand-ruby at zenspider.com> on 2011-01-09 06:12:19
>> 
>>    Added appropriate instructions on downgrading on 1.9.2
>> 
>>  UPGRADING.rdoc |   13 +++++++++++++
>>  1 files changed, 13 insertions(+), 0 deletions(-)
>> Revision ...86b5b973b1f75ddebe4de733f2a01311bff5dfc0 committed by Ryan Davis <ryand-ruby at zenspider.com> on 2011-01-06 23:59:45
>> 
>>    prepping for release
>> 
>>  History.txt     |   10 +++++++++-
>>  lib/rubygems.rb |    2 +-
>>  2 files changed, 10 insertions(+), 2 deletions(-)
>> 
>> 
>> 
>> See http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_1-p430/414d2f8a78205ed0b2465dbdc7c2ab5fd2ffc371 for details.
> 
> I see we are prepping for another release.  Just a gentle reminder
> that CI is running now for all requested interpreters, it is still red
> for 1.9.1 and 1.9.2, the failures are locally reproducible, and
> there's still no response on the thread about the broken builds:
> 
> http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_1-p430
> http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_2-p0

Your 1.9.2 is not installed correctly if it says "/home/pivotal/.cruise/projects/RubyGems-1_9_2-p0/work/lib/rubygems/specification.rb:725:in `to_yaml': YAML.quick_emit is deprecated"

You need to install libyaml before building ruby.


From drbrain at segment7.net  Sun Jan  9 18:59:27 2011
From: drbrain at segment7.net (Eric Hodel)
Date: Sun, 9 Jan 2011 15:59:27 -0800
Subject: [Rubygems-developers] [halp] rubygems-test could use a beating!
In-Reply-To: <541D8F9D-149E-4B4D-9310-869397B58709@hollensbe.org>
References: <541D8F9D-149E-4B4D-9310-869397B58709@hollensbe.org>
Message-ID: <F00FE35E-42D8-4132-8EE2-4F999F20C371@segment7.net>

On Jan 6, 2011, at 16:14, Erik Hollensbe wrote:

> rubygems-test is a testing facility for gems. It provides several
> features:
> 
> * A replaced 'gem test' command that leverages rake and an opt-in
>  system, via the gemspec, that allows authors to indicate what gems
>  can be tested by end users.

I've removed the 'test' command and all attached functionality from RubyGems.  1.5 will not ship with testing capability.


From noreply at rubyforge.org  Sun Jan  9 20:24:50 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun,  9 Jan 2011 20:24:50 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28844 ] rubygems plugins,
	1.9 and circular requires
Message-ID: <20110110012450.DE58C18582EE@rubyforge.org>

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

Category: #gem and #require methods
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Erik Hollensbe (erikh)
Assigned to: Nobody (None)
Summary: rubygems plugins, 1.9 and circular requires

Initial Comment:
I apologize in advance if this is confusing.

I'm not entirely sure if this is gem_prelude's fault or rubygems's or even ruby proper's fault, but here goes:

http://www.gem-testers.org/gems/rubygems-test/v/0.2.1/test_results/2

If you carefully examine the stack trace, you'll see that the rdoc plugin is being pulled in, then hanna is being pulled in. What happens in hanna is that rubygems is pulled in, ergo our problem. This is all done in from a rake process spawned by rubygems-test which uses open4 which in 1.9 uses threads, so threading may be a part of the issue here.

This issue does not exhibit in 1.8, but it uses fork there. I was unable to test in RG 1.4 because of the obvious.

I was able to fix this in rubygems-test 0.2.1 for the 'gem test' provider. The commit below is the fix.

https://github.com/rubygems/rubygems-test/commit/72b0e136889fcd2509bb040de3fe9220c4b8bc13

You can see that I abuse autoload there to ensure that any rubygems dependencies (and YAML to be safe)  are only loaded once. This is because of the above issue. These patches fix it but not for rdoc and (I presume) other plugins.

What probably needs to happen is some beyond-the-call-of-duty $:/$" inspection before plugin load runs or to somehow load plugins with autoload (I don't think this is possible though). Obviously I'm deferring to your experience.

Please feel free to tell me where to stick this bug report if it does not belong here, I'm just convinced after the discrete repros that it at least gets close to starting in rubygems.

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

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

From erik at hollensbe.org  Sun Jan  9 21:29:13 2011
From: erik at hollensbe.org (Erik Hollensbe)
Date: Sun, 9 Jan 2011 21:29:13 -0500
Subject: [Rubygems-developers] [halp] rubygems-test could use a beating!
In-Reply-To: <AANLkTim7+mo3dOXcFchkhuG_LikfvwRttJOdxXxeRPGj@mail.gmail.com>
References: <541D8F9D-149E-4B4D-9310-869397B58709@hollensbe.org>
	<AANLkTim7+mo3dOXcFchkhuG_LikfvwRttJOdxXxeRPGj@mail.gmail.com>
Message-ID: <05A0EF5D-A498-4797-963D-E3D4334D6526@hollensbe.org>


On Jan 6, 2011, at 8:49 PM, Luis Lavena wrote:

> On Thu, Jan 6, 2011 at 9:14 PM, Erik Hollensbe <erik at hollensbe.org> wrote:
>> rubygems-test is a testing facility for gems. It provides several
>> features:
>> 
>> $ gem install rubygems-test
>> $ gem test rubygems-test
>> 
>> (may require sudo)
>> 
> 
> C:\Users\Luis>gem test rubygems-test --backtrace
> ERROR:  While executing gem ... (NameError)

Hey Luis, I just patched in a fix for this; do you mind looking at the commit to sanity check it? I'm new to working with windows in this fashion.

I'm using Berger and Heesob's win32-open gem to accomplish it on 1.8, 1.9 works with standard 1.9 (threaded) Open3.

https://github.com/rubygems/rubygems-test/commit/7663627693ce442e06be4709ebee613ad32f18a0

Thanks,

-Erik

From noreply at rubyforge.org  Sun Jan  9 22:23:12 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun,  9 Jan 2011 22:23:12 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28845 ] Please move
	RubyGemTestCase to lib/
Message-ID: <20110110032312.BC30E1858354@rubyforge.org>

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

Category: other
Group: next
Status: Open
Resolution: None
Priority: 3
Submitted By: Erik Hollensbe (erikh)
Assigned to: Nobody (None)
Summary: Please move RubyGemTestCase to lib/

Initial Comment:
Eric requested I insert this ticket.

rubygems-test could use this to perform better testing of its own suite. I will be happy to provide a pull request at a later time, but wanted to get this in here.

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

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

From noreply at rubyforge.org  Sun Jan  9 22:24:35 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun,  9 Jan 2011 22:24:35 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28846 ]
	rubygems/userinteraction not included in key libraries
Message-ID: <20110110032435.ED0191858354@rubyforge.org>

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

Category: other
Group: v1.4.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Erik Hollensbe (erikh)
Assigned to: Nobody (None)
Summary: rubygems/userinteraction not included in key libraries

Initial Comment:
Gem::Installer and Gem::Format do not include this require, and therefore using them independently causes an explosion on 1.4.



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

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

From ryand-ruby at zenspider.com  Tue Jan 11 16:11:02 2011
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Tue, 11 Jan 2011 13:11:02 -0800
Subject: [Rubygems-developers] Release coming,
	but still no response on broken 1.9.x CI builds
In-Reply-To: <300AF5C3-C708-436E-86E5-F83000C61DC2@segment7.net>
References: <AANLkTi=dye+Q9JYUtghGaiB-+rGDisV9xUZPt8sBOQMK@mail.gmail.com>
	<300AF5C3-C708-436E-86E5-F83000C61DC2@segment7.net>
Message-ID: <2C5AB12B-5171-4A2B-BD80-85AA15CF877E@zenspider.com>


On Jan 9, 2011, at 15:57 , Eric Hodel wrote:

> 
> On Jan 9, 2011, at 02:56, Chad Woolley wrote:
> 
>> On Sat, Jan 8, 2011 at 11:16 PM,  <thewoolleyman+rubygems-ci at gmail.com> wrote:
>> 
>> http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_1-p430
>> http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_2-p0
> 
> Your 1.9.2 is not installed correctly if it says "/home/pivotal/.cruise/projects/RubyGems-1_9_2-p0/work/lib/rubygems/specification.rb:725:in `to_yaml': YAML.quick_emit is deprecated"
> 
> You need to install libyaml before building ruby.

Still running 1.9.2-p0.

Still doesn't have libyaml installed.

Still running 1.9.1-p430.

We'd be green otherwise...


From noreply at rubyforge.org  Tue Jan 11 17:39:57 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue, 11 Jan 2011 17:39:57 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28850 ] Invalid argument -
	./</cdesc-<.yaml
Message-ID: <20110111223957.BD1AE185837B@rubyforge.org>

Bugs item #28850, was opened at 2011-01-11 14:39
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28850&group_id=126

Category: `gem install` command
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Greg Hazel (ghazel)
Assigned to: Nobody (None)
Summary: Invalid argument - ./</cdesc-<.yaml

Initial Comment:
S:\>gem install activerecord
Fetching: activesupport-3.0.3.gem (100%)
Fetching: activemodel-3.0.3.gem (100%)
Fetching: activerecord-3.0.3.gem (100%)
Successfully installed activesupport-3.0.3
Successfully installed activemodel-3.0.3
Successfully installed activerecord-3.0.3
3 gems installed
Installing ri documentation for activesupport-3.0.3...
Installing ri documentation for activemodel-3.0.3...
Installing ri documentation for activerecord-3.0.3...
ERROR:  While executing gem ... (Errno::EINVAL)
    Invalid argument - ./</cdesc-<.yaml


S:\>ruby -v
ruby 1.8.7 (2010-01-10 patchlevel 249) [i386-mingw32]

S:\>gem -v
1.4.2

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

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

From noreply at rubyforge.org  Tue Jan 11 17:49:51 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue, 11 Jan 2011 17:49:51 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28850 ] Invalid argument -
	./</cdesc-<.yaml
Message-ID: <20110111224951.4C9361858387@rubyforge.org>

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

Category: `gem install` command
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Greg Hazel (ghazel)
Assigned to: Nobody (None)
Summary: Invalid argument - ./</cdesc-<.yaml

Initial Comment:
S:\>gem install activerecord
Fetching: activesupport-3.0.3.gem (100%)
Fetching: activemodel-3.0.3.gem (100%)
Fetching: activerecord-3.0.3.gem (100%)
Successfully installed activesupport-3.0.3
Successfully installed activemodel-3.0.3
Successfully installed activerecord-3.0.3
3 gems installed
Installing ri documentation for activesupport-3.0.3...
Installing ri documentation for activemodel-3.0.3...
Installing ri documentation for activerecord-3.0.3...
ERROR:  While executing gem ... (Errno::EINVAL)
    Invalid argument - ./</cdesc-<.yaml


S:\>ruby -v
ruby 1.8.7 (2010-01-10 patchlevel 249) [i386-mingw32]

S:\>gem -v
1.4.2

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

>Comment By: Luis Lavena (luislavena)
Date: 2011-01-11 19:49

Message:
Hello,

When reporting RubyGems bugs, please include:

The full output of "gem env"

The full output of the same command that failed with --debug -V options


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

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

From noreply at rubyforge.org  Tue Jan 11 17:55:36 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue, 11 Jan 2011 17:55:36 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28850 ] Invalid argument -
	./&lt; /cdesc-&lt; .yaml
Message-ID: <20110111225536.7B9E21858385@rubyforge.org>

Bugs item #28850, was opened at 2011-01-11 14:39
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28850&group_id=126

Category: `gem install` command
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Greg Hazel (ghazel)
Assigned to: Nobody (None)
>Summary: Invalid argument - ./&lt;/cdesc-&lt;.yaml

Initial Comment:
S:\>gem install activerecord
Fetching: activesupport-3.0.3.gem (100%)
Fetching: activemodel-3.0.3.gem (100%)
Fetching: activerecord-3.0.3.gem (100%)
Successfully installed activesupport-3.0.3
Successfully installed activemodel-3.0.3
Successfully installed activerecord-3.0.3
3 gems installed
Installing ri documentation for activesupport-3.0.3...
Installing ri documentation for activemodel-3.0.3...
Installing ri documentation for activerecord-3.0.3...
ERROR:  While executing gem ... (Errno::EINVAL)
    Invalid argument - ./</cdesc-<.yaml


S:\>ruby -v
ruby 1.8.7 (2010-01-10 patchlevel 249) [i386-mingw32]

S:\>gem -v
1.4.2

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

>Comment By: Greg Hazel (ghazel)
Date: 2011-01-11 14:55

Message:
S:\>gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.4.2
  - RUBY VERSION: 1.8.7 (2010-01-10 patchlevel 249) [i386-mingw32]
  - INSTALLATION DIRECTORY: C:/Ruby187/lib/ruby/gems/1.8
  - RUBY EXECUTABLE: C:/Ruby187/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/Ruby187/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mingw32
  - GEM PATHS:
     - C:/Ruby187/lib/ruby/gems/1.8
     - C:/Users/Greg/.gem/ruby/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://rubygems.org/

The output of "gem install activerecord --debug -V" is a whopping 35 MB. Perhaps the part you're interested in is:

ERROR:  While executing gem ... (Errno::EINVAL)
    Invalid argument - ./</cdesc-<.yaml
	C:/Ruby187/lib/ruby/1.8/rdoc/ri/ri_writer.rb:36:in `initialize'
	C:/Ruby187/lib/ruby/1.8/rdoc/ri/ri_writer.rb:36:in `open'
	C:/Ruby187/lib/ruby/1.8/rdoc/ri/ri_writer.rb:36:in `add_class'
	C:/Ruby187/lib/ruby/1.8/rdoc/generators/ri_generator.rb:258:in `update_or_replace'
	C:/Ruby187/lib/ruby/1.8/rdoc/generators/ri_generator.rb:130:in `generate_class_info'
	C:/Ruby187/lib/ruby/1.8/rdoc/generators/ri_generator.rb:90:in `process_class'
	C:/Ruby187/lib/ruby/1.8/rdoc/generators/ri_generator.rb:85:in `generate'
	C:/Ruby187/lib/ruby/1.8/rdoc/generators/ri_generator.rb:84:in `each'
	C:/Ruby187/lib/ruby/1.8/rdoc/generators/ri_generator.rb:84:in `generate'
	C:/Ruby187/lib/ruby/1.8/rdoc/rdoc.rb:284:in `document'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/doc_manager.rb:187:in `run_rdoc'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/doc_manager.rb:156:in `install_ri'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/doc_manager.rb:116:in `generate_ri'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:147:in `execute'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:146:in `each'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:146:in `execute'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/command.rb:278:in `invoke'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:134:in `process_args'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:104:in `run'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:63:in `run'
	C:/Ruby187/bin/gem:21



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

Comment By: Luis Lavena (luislavena)
Date: 2011-01-11 14:49

Message:
Hello,

When reporting RubyGems bugs, please include:

The full output of "gem env"

The full output of the same command that failed with --debug -V options


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

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

From noreply at rubyforge.org  Tue Jan 11 17:57:12 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue, 11 Jan 2011 17:57:12 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28850 ] Invalid argument -
	./&lt; /cdesc-&lt; .yaml
Message-ID: <20110111225712.3400A1858389@rubyforge.org>

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

Category: `gem install` command
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Greg Hazel (ghazel)
>Assigned to: Luis Lavena (luislavena)
Summary: Invalid argument - ./&lt;/cdesc-&lt;.yaml

Initial Comment:
S:\>gem install activerecord
Fetching: activesupport-3.0.3.gem (100%)
Fetching: activemodel-3.0.3.gem (100%)
Fetching: activerecord-3.0.3.gem (100%)
Successfully installed activesupport-3.0.3
Successfully installed activemodel-3.0.3
Successfully installed activerecord-3.0.3
3 gems installed
Installing ri documentation for activesupport-3.0.3...
Installing ri documentation for activemodel-3.0.3...
Installing ri documentation for activerecord-3.0.3...
ERROR:  While executing gem ... (Errno::EINVAL)
    Invalid argument - ./</cdesc-<.yaml


S:\>ruby -v
ruby 1.8.7 (2010-01-10 patchlevel 249) [i386-mingw32]

S:\>gem -v
1.4.2

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

>Comment By: Luis Lavena (luislavena)
Date: 2011-01-11 19:57

Message:
Hello,

Please disable ri/rdoc generation or update to newer RDoc first:

gem install rdoc


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

Comment By: Greg Hazel (ghazel)
Date: 2011-01-11 19:55

Message:
S:\>gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.4.2
  - RUBY VERSION: 1.8.7 (2010-01-10 patchlevel 249) [i386-mingw32]
  - INSTALLATION DIRECTORY: C:/Ruby187/lib/ruby/gems/1.8
  - RUBY EXECUTABLE: C:/Ruby187/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/Ruby187/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mingw32
  - GEM PATHS:
     - C:/Ruby187/lib/ruby/gems/1.8
     - C:/Users/Greg/.gem/ruby/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://rubygems.org/

The output of "gem install activerecord --debug -V" is a whopping 35 MB. Perhaps the part you're interested in is:

ERROR:  While executing gem ... (Errno::EINVAL)
    Invalid argument - ./</cdesc-<.yaml
	C:/Ruby187/lib/ruby/1.8/rdoc/ri/ri_writer.rb:36:in `initialize'
	C:/Ruby187/lib/ruby/1.8/rdoc/ri/ri_writer.rb:36:in `open'
	C:/Ruby187/lib/ruby/1.8/rdoc/ri/ri_writer.rb:36:in `add_class'
	C:/Ruby187/lib/ruby/1.8/rdoc/generators/ri_generator.rb:258:in `update_or_replace'
	C:/Ruby187/lib/ruby/1.8/rdoc/generators/ri_generator.rb:130:in `generate_class_info'
	C:/Ruby187/lib/ruby/1.8/rdoc/generators/ri_generator.rb:90:in `process_class'
	C:/Ruby187/lib/ruby/1.8/rdoc/generators/ri_generator.rb:85:in `generate'
	C:/Ruby187/lib/ruby/1.8/rdoc/generators/ri_generator.rb:84:in `each'
	C:/Ruby187/lib/ruby/1.8/rdoc/generators/ri_generator.rb:84:in `generate'
	C:/Ruby187/lib/ruby/1.8/rdoc/rdoc.rb:284:in `document'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/doc_manager.rb:187:in `run_rdoc'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/doc_manager.rb:156:in `install_ri'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/doc_manager.rb:116:in `generate_ri'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:147:in `execute'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:146:in `each'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:146:in `execute'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/command.rb:278:in `invoke'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:134:in `process_args'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:104:in `run'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:63:in `run'
	C:/Ruby187/bin/gem:21



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

Comment By: Luis Lavena (luislavena)
Date: 2011-01-11 19:49

Message:
Hello,

When reporting RubyGems bugs, please include:

The full output of "gem env"

The full output of the same command that failed with --debug -V options


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

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

From noreply at rubyforge.org  Tue Jan 11 18:00:47 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue, 11 Jan 2011 18:00:47 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28850 ] Invalid argument -
	./&lt; /cdesc-&lt; .yaml
Message-ID: <20110111230047.DEE72167831F@rubyforge.org>

Bugs item #28850, was opened at 2011-01-11 14:39
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28850&group_id=126

Category: `gem install` command
Group: None
>Status: Closed
>Resolution: Rejected
Priority: 3
Submitted By: Greg Hazel (ghazel)
Assigned to: Luis Lavena (luislavena)
Summary: Invalid argument - ./&lt;/cdesc-&lt;.yaml

Initial Comment:
S:\>gem install activerecord
Fetching: activesupport-3.0.3.gem (100%)
Fetching: activemodel-3.0.3.gem (100%)
Fetching: activerecord-3.0.3.gem (100%)
Successfully installed activesupport-3.0.3
Successfully installed activemodel-3.0.3
Successfully installed activerecord-3.0.3
3 gems installed
Installing ri documentation for activesupport-3.0.3...
Installing ri documentation for activemodel-3.0.3...
Installing ri documentation for activerecord-3.0.3...
ERROR:  While executing gem ... (Errno::EINVAL)
    Invalid argument - ./</cdesc-<.yaml


S:\>ruby -v
ruby 1.8.7 (2010-01-10 patchlevel 249) [i386-mingw32]

S:\>gem -v
1.4.2

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

>Comment By: Eric Hodel (drbrain)
Date: 2011-01-11 15:00

Message:
Yes, this is an rdoc bug.  Either upgrade to a newer version of RDoc or disable rdoc and ri generation through --no-rdoc --no-ri.

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

Comment By: Luis Lavena (luislavena)
Date: 2011-01-11 14:57

Message:
Hello,

Please disable ri/rdoc generation or update to newer RDoc first:

gem install rdoc


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

Comment By: Greg Hazel (ghazel)
Date: 2011-01-11 14:55

Message:
S:\>gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.4.2
  - RUBY VERSION: 1.8.7 (2010-01-10 patchlevel 249) [i386-mingw32]
  - INSTALLATION DIRECTORY: C:/Ruby187/lib/ruby/gems/1.8
  - RUBY EXECUTABLE: C:/Ruby187/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/Ruby187/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mingw32
  - GEM PATHS:
     - C:/Ruby187/lib/ruby/gems/1.8
     - C:/Users/Greg/.gem/ruby/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://rubygems.org/

The output of "gem install activerecord --debug -V" is a whopping 35 MB. Perhaps the part you're interested in is:

ERROR:  While executing gem ... (Errno::EINVAL)
    Invalid argument - ./</cdesc-<.yaml
	C:/Ruby187/lib/ruby/1.8/rdoc/ri/ri_writer.rb:36:in `initialize'
	C:/Ruby187/lib/ruby/1.8/rdoc/ri/ri_writer.rb:36:in `open'
	C:/Ruby187/lib/ruby/1.8/rdoc/ri/ri_writer.rb:36:in `add_class'
	C:/Ruby187/lib/ruby/1.8/rdoc/generators/ri_generator.rb:258:in `update_or_replace'
	C:/Ruby187/lib/ruby/1.8/rdoc/generators/ri_generator.rb:130:in `generate_class_info'
	C:/Ruby187/lib/ruby/1.8/rdoc/generators/ri_generator.rb:90:in `process_class'
	C:/Ruby187/lib/ruby/1.8/rdoc/generators/ri_generator.rb:85:in `generate'
	C:/Ruby187/lib/ruby/1.8/rdoc/generators/ri_generator.rb:84:in `each'
	C:/Ruby187/lib/ruby/1.8/rdoc/generators/ri_generator.rb:84:in `generate'
	C:/Ruby187/lib/ruby/1.8/rdoc/rdoc.rb:284:in `document'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/doc_manager.rb:187:in `run_rdoc'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/doc_manager.rb:156:in `install_ri'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/doc_manager.rb:116:in `generate_ri'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:147:in `execute'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:146:in `each'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:146:in `execute'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/command.rb:278:in `invoke'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:134:in `process_args'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:104:in `run'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:63:in `run'
	C:/Ruby187/bin/gem:21



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

Comment By: Luis Lavena (luislavena)
Date: 2011-01-11 14:49

Message:
Hello,

When reporting RubyGems bugs, please include:

The full output of "gem env"

The full output of the same command that failed with --debug -V options


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

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

From noreply at rubyforge.org  Tue Jan 11 18:05:08 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue, 11 Jan 2011 18:05:08 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28850 ] Invalid argument -
	./&amp; lt; /cdesc-&amp; lt; .yaml
Message-ID: <20110111230508.1B7011858389@rubyforge.org>

Bugs item #28850, was opened at 2011-01-11 14:39
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28850&group_id=126

Category: `gem install` command
Group: None
Status: Closed
Resolution: Rejected
Priority: 3
Submitted By: Greg Hazel (ghazel)
Assigned to: Luis Lavena (luislavena)
>Summary: Invalid argument - ./&amp;lt;/cdesc-&amp;lt;.yaml

Initial Comment:
S:\>gem install activerecord
Fetching: activesupport-3.0.3.gem (100%)
Fetching: activemodel-3.0.3.gem (100%)
Fetching: activerecord-3.0.3.gem (100%)
Successfully installed activesupport-3.0.3
Successfully installed activemodel-3.0.3
Successfully installed activerecord-3.0.3
3 gems installed
Installing ri documentation for activesupport-3.0.3...
Installing ri documentation for activemodel-3.0.3...
Installing ri documentation for activerecord-3.0.3...
ERROR:  While executing gem ... (Errno::EINVAL)
    Invalid argument - ./</cdesc-<.yaml


S:\>ruby -v
ruby 1.8.7 (2010-01-10 patchlevel 249) [i386-mingw32]

S:\>gem -v
1.4.2

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

>Comment By: Greg Hazel (ghazel)
Date: 2011-01-11 15:05

Message:
"gem install rdoc" presented a few unclear options for 
upgrading, and I don't have any use for rdoc, so I disabled 
it.

Installation works fine now - thanks!

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

Comment By: Eric Hodel (drbrain)
Date: 2011-01-11 15:00

Message:
Yes, this is an rdoc bug.  Either upgrade to a newer version of RDoc or disable rdoc and ri generation through --no-rdoc --no-ri.

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

Comment By: Luis Lavena (luislavena)
Date: 2011-01-11 14:57

Message:
Hello,

Please disable ri/rdoc generation or update to newer RDoc first:

gem install rdoc


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

Comment By: Greg Hazel (ghazel)
Date: 2011-01-11 14:55

Message:
S:\>gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.4.2
  - RUBY VERSION: 1.8.7 (2010-01-10 patchlevel 249) [i386-mingw32]
  - INSTALLATION DIRECTORY: C:/Ruby187/lib/ruby/gems/1.8
  - RUBY EXECUTABLE: C:/Ruby187/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/Ruby187/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mingw32
  - GEM PATHS:
     - C:/Ruby187/lib/ruby/gems/1.8
     - C:/Users/Greg/.gem/ruby/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://rubygems.org/

The output of "gem install activerecord --debug -V" is a whopping 35 MB. Perhaps the part you're interested in is:

ERROR:  While executing gem ... (Errno::EINVAL)
    Invalid argument - ./</cdesc-<.yaml
	C:/Ruby187/lib/ruby/1.8/rdoc/ri/ri_writer.rb:36:in `initialize'
	C:/Ruby187/lib/ruby/1.8/rdoc/ri/ri_writer.rb:36:in `open'
	C:/Ruby187/lib/ruby/1.8/rdoc/ri/ri_writer.rb:36:in `add_class'
	C:/Ruby187/lib/ruby/1.8/rdoc/generators/ri_generator.rb:258:in `update_or_replace'
	C:/Ruby187/lib/ruby/1.8/rdoc/generators/ri_generator.rb:130:in `generate_class_info'
	C:/Ruby187/lib/ruby/1.8/rdoc/generators/ri_generator.rb:90:in `process_class'
	C:/Ruby187/lib/ruby/1.8/rdoc/generators/ri_generator.rb:85:in `generate'
	C:/Ruby187/lib/ruby/1.8/rdoc/generators/ri_generator.rb:84:in `each'
	C:/Ruby187/lib/ruby/1.8/rdoc/generators/ri_generator.rb:84:in `generate'
	C:/Ruby187/lib/ruby/1.8/rdoc/rdoc.rb:284:in `document'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/doc_manager.rb:187:in `run_rdoc'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/doc_manager.rb:156:in `install_ri'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/doc_manager.rb:116:in `generate_ri'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:147:in `execute'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:146:in `each'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:146:in `execute'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/command.rb:278:in `invoke'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:134:in `process_args'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:104:in `run'
	C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:63:in `run'
	C:/Ruby187/bin/gem:21



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

Comment By: Luis Lavena (luislavena)
Date: 2011-01-11 14:49

Message:
Hello,

When reporting RubyGems bugs, please include:

The full output of "gem env"

The full output of the same command that failed with --debug -V options


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

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

From thewoolleyman at gmail.com  Wed Jan 12 01:28:08 2011
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Tue, 11 Jan 2011 23:28:08 -0700
Subject: [Rubygems-developers] Release coming,
 but still no response on broken 1.9.x CI builds
In-Reply-To: <2C5AB12B-5171-4A2B-BD80-85AA15CF877E@zenspider.com>
References: <AANLkTi=dye+Q9JYUtghGaiB-+rGDisV9xUZPt8sBOQMK@mail.gmail.com>
	<300AF5C3-C708-436E-86E5-F83000C61DC2@segment7.net>
	<2C5AB12B-5171-4A2B-BD80-85AA15CF877E@zenspider.com>
Message-ID: <AANLkTikL-Py6+x3xgBpW=tSL3E8J1GgWTvByT8GWYmnW@mail.gmail.com>

On Tue, Jan 11, 2011 at 2:11 PM, Ryan Davis <ryand-ruby at zenspider.com> wrote:
> Still running 1.9.2-p0.
>
> Still doesn't have libyaml installed.
>
> Still running 1.9.1-p430.
>
> We'd be green otherwise...

Having trouble making rvm ruby patchlevels float in ccrb's build
script.  Discussing it with Wayne.  If I don't get it soon I'll punt
and just hardcode the patchlevels, which works fine, but will need to
be updated manually as new patchlevels come out.

Also, default 1.9.2 for rvm is p0, and it was green.  Do we need a
different one?

-- Chad

From ryand-ruby at zenspider.com  Wed Jan 12 02:33:09 2011
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Tue, 11 Jan 2011 23:33:09 -0800
Subject: [Rubygems-developers] Release coming,
	but still no response on broken 1.9.x CI builds
In-Reply-To: <AANLkTikL-Py6+x3xgBpW=tSL3E8J1GgWTvByT8GWYmnW@mail.gmail.com>
References: <AANLkTi=dye+Q9JYUtghGaiB-+rGDisV9xUZPt8sBOQMK@mail.gmail.com>
	<300AF5C3-C708-436E-86E5-F83000C61DC2@segment7.net>
	<2C5AB12B-5171-4A2B-BD80-85AA15CF877E@zenspider.com>
	<AANLkTikL-Py6+x3xgBpW=tSL3E8J1GgWTvByT8GWYmnW@mail.gmail.com>
Message-ID: <0A0C96EE-7849-4A0A-84B8-E19F0021A066@zenspider.com>


On Jan 11, 2011, at 22:28 , Chad Woolley wrote:

> Also, default 1.9.2 for rvm is p0, and it was green.  Do we need a
> different one?

Not anymore.

% rvm list known
...
[ruby-]1.9.2[-p136]
...

From luislavena at gmail.com  Thu Jan 13 10:46:27 2011
From: luislavena at gmail.com (Luis Lavena)
Date: Thu, 13 Jan 2011 12:46:27 -0300
Subject: [Rubygems-developers] [halp] rubygems-test could use a beating!
In-Reply-To: <05A0EF5D-A498-4797-963D-E3D4334D6526@hollensbe.org>
References: <541D8F9D-149E-4B4D-9310-869397B58709@hollensbe.org>
	<AANLkTim7+mo3dOXcFchkhuG_LikfvwRttJOdxXxeRPGj@mail.gmail.com>
	<05A0EF5D-A498-4797-963D-E3D4334D6526@hollensbe.org>
Message-ID: <AANLkTin2SytirdAO+zUP=+XbpeZFY0NVYqfT1g8zPHsf@mail.gmail.com>

On Sun, Jan 9, 2011 at 11:29 PM, Erik Hollensbe <erik at hollensbe.org> wrote:
>
> Hey Luis, I just patched in a fix for this; do you mind looking at the commit to sanity check it? I'm new to working with windows in this fashion.
>

Hello Erik, I'm late on this (you know, work) :P

> I'm using Berger and Heesob's win32-open gem to accomplish it on 1.8, 1.9 works with standard 1.9 (threaded) Open3.
>
> https://github.com/rubygems/rubygems-test/commit/7663627693ce442e06be4709ebee613ad32f18a0
>

RUBY_PLATFORM = /mingw|mswin/

If you discard mswin you left the "other" version of Ruby out there
(compiled with Visual Studio) out of the equation.

There are plenty of these users in the wild, so let's consider them for now ;-)

> Thanks,
>

Thanks to you for taking the time.

-- 
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 erik at hollensbe.org  Thu Jan 13 12:39:13 2011
From: erik at hollensbe.org (Erik Hollensbe)
Date: Thu, 13 Jan 2011 12:39:13 -0500
Subject: [Rubygems-developers] [halp] rubygems-test could use a beating!
In-Reply-To: <AANLkTin2SytirdAO+zUP=+XbpeZFY0NVYqfT1g8zPHsf@mail.gmail.com>
References: <541D8F9D-149E-4B4D-9310-869397B58709@hollensbe.org>
	<AANLkTim7+mo3dOXcFchkhuG_LikfvwRttJOdxXxeRPGj@mail.gmail.com>
	<05A0EF5D-A498-4797-963D-E3D4334D6526@hollensbe.org>
	<AANLkTin2SytirdAO+zUP=+XbpeZFY0NVYqfT1g8zPHsf@mail.gmail.com>
Message-ID: <544D9829-D924-4D51-8397-178A23B0EA4B@hollensbe.org>


On Jan 13, 2011, at 10:46 AM, Luis Lavena wrote:
>> I'm using Berger and Heesob's win32-open gem to accomplish it on 1.8, 1.9 works with standard 1.9 (threaded) Open3.
>> 
>> https://github.com/rubygems/rubygems-test/commit/7663627693ce442e06be4709ebee613ad32f18a0
>> 
> 
> RUBY_PLATFORM = /mingw|mswin/
> 
> If you discard mswin you left the "other" version of Ruby out there
> (compiled with Visual Studio) out of the equation.
> 
> There are plenty of these users in the wild, so let's consider them for now ;-)

I'll put out 0.2.5 later today after some testing. Thanks for the tips.

To everyone (sorry, this got a bit long):

We're probably going to go live RSN. We've been "ready" for about a week on the site side and are just waiting for some other cool opportunities to vivify, so I've been waiting to flip the switch on the hype machine. 

Josiah and I trying very hard for a pain-minimal launch, so if anyone has 2 minutes and can test on their favorite platform, I'd really appreciate it and I know others would too. Feel free to upload bugs and just shoot me the URL that comes back to you; that part should always work at least. :) 

Roll and test your own gems with hoe HEAD or follow the README if you don't use Hoe. It should be very easy to fit your gems to work with rubygems-test and I want to hear about cases where it's not.

Any comments on the UX or utility of the http://gem-testers.org site would also be very welcome.

We're targeting on all supported operating systems:

1.8
1.9
JRuby (1.8 and 1.9 modes in 1.6 should work, but I haven't tested 1.6 yet)
Rubinius

There are still some RG bugs (in the tracker) which our test suite exposes (such as having to 'sudo gem test' with our gem if you install gems as root) but those are anomalies I don't have a lot of time to invest in controlling just yet. I posted them to the tracker earlier this week.

I haven't had the time or chance to check maglev and macruby yet, and ironruby will almost definitely break. Results from properly built and installed versions of these would be awesome.

Thanks for your time,

-Erik

From ryand-ruby at zenspider.com  Fri Jan 14 04:20:33 2011
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Fri, 14 Jan 2011 01:20:33 -0800
Subject: [Rubygems-developers] gem_prelude in 1.9
Message-ID: <66A8BF9C-FF39-4846-89E2-7407506745C6@zenspider.com>

I committed changes to ruby trunk that reduces gem_prelude to a simple require of rubygems.

I also made one commit to rubygems that fixes upgrading from 1.3.7/ruby-core (distinguished from our release of 1.3.7). I tested this on a private install and it seems to work well:

> % /tmp/ruby19/bin/gem19 -v
> 1.4.2

I think we should release that 1 line change as 1.4.3.

But how do we get ruby-core to release 1.9.2 w/ our change? I've been asking for weeks and heard nothing to approve of or deny such a release. Suggestions?


From jon.forums at gmail.com  Fri Jan 14 09:36:05 2011
From: jon.forums at gmail.com (Jon)
Date: Fri, 14 Jan 2011 09:36:05 -0500
Subject: [Rubygems-developers] gem_prelude in 1.9
In-Reply-To: <66A8BF9C-FF39-4846-89E2-7407506745C6@zenspider.com>
References: <66A8BF9C-FF39-4846-89E2-7407506745C6@zenspider.com>
Message-ID: <20110114093605.176035c9.jon.forums@gmail.com>

> But how do we get ruby-core to release 1.9.2 w/ our change? I've been asking for weeks and heard nothing to approve of or deny such a release. Suggestions?

Just read your and Yusuke's latest...a few comments:

1) Show time ./ruby -ve '' on ruby 1.9.2p136 (2010-12-25 revision 30363) in addition to trunk...hopefully these numbers will be larger than his ruby 1.9.3dev (2011-01-14 trunk 30544) [i686-linux] results showing the patches incrementally improve startup performance as well.

2) Summarize your positive cross-platform testing results. FWIW I upgraded to 1.4.2 on ruby 1.8.7 (2010-12-23 patchlevel 330) [i386-mingw32] and haven't yet had a problem, but I've not really stressed it. Luis probably has some good Windows data you could include. Maybe summarize how well the new patch works for some well known users and well known gems?

3) Rerereresummarize the critical mods (high level) addressed by 1.4.x patch.

4) Reiterate your plan (and timeline) to first fix the 1.9.x upgrade issue and then incrementally address any performance issues. Hopefully this in combo with (1) will show that at least things are no worse off performance wise than what exists on 1.9.2p136.


Jon

---
blog: http://jonforums.github.com/

From jon.forums at gmail.com  Fri Jan 14 10:28:22 2011
From: jon.forums at gmail.com (Jon)
Date: Fri, 14 Jan 2011 10:28:22 -0500
Subject: [Rubygems-developers] gem_prelude in 1.9
In-Reply-To: <20110114093605.176035c9.jon.forums@gmail.com>
References: <66A8BF9C-FF39-4846-89E2-7407506745C6@zenspider.com>
	<20110114093605.176035c9.jon.forums@gmail.com>
Message-ID: <20110114102822.4c5edaaf.jon.forums@gmail.com>

> > But how do we get ruby-core to release 1.9.2 w/ our change? I've been asking for weeks and heard nothing to approve of or deny such a release. Suggestions?
> 
> Just read your and Yusuke's latest...a few comments:
> 
> 1) Show time ./ruby -ve '' on ruby 1.9.2p136 (2010-12-25 revision 30363) in addition to trunk...hopefully these numbers will be larger than his ruby 1.9.3dev (2011-01-14 trunk 30544) [i686-linux] results showing the patches incrementally improve startup performance as well.

red herring :(

# running on VirtualBox 4.0.0 on Win7 Ultimate 32-bit...

$ uname -a
Linux archee 2.6.36-ARCH #1 SMP PREEMPT Sat Jan 8 13:16:43 UTC 2011 i686 Intel(R) Core(TM)2 Duo CPU T9300 @ 2.50GHz GenuineIntel GNU/Linux

$ gem list | wc -l
34

$ time ./ruby -ve ''
ruby 1.9.2p136 (2010-12-25 revision 30363) [i686-Linux]

real    0m0.047s
user    0m0.013s
sys     0m0.030s


$ time ./ruby -ve ''
ruby 1.9.3dev (2011-01-14 trunk 30545) [i686-Linux]

real    0m0.175s
user    0m0.133s
sys     0m0.043s


$ time ./ruby --disable-gems -ve ''
ruby 1.9.3dev (2011-01-14 trunk 30545) [i686-Linux]

real    0m0.048s
user    0m0.010s
sys     0m0.040s


Jon

---
blog: http://jonforums.github.com/

From noreply at rubyforge.org  Fri Jan 14 14:28:25 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 14 Jan 2011 14:28:25 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-27324 ] string contains null
	byte
Message-ID: <20110114192825.2A639185836C@rubyforge.org>

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

Category: `gem install` command
Group: v1.3.x
Status: Closed
Resolution: None
Priority: 3
Submitted By: Thomas Preymesser (thopre)
Assigned to: Nobody (None)
Summary: string contains null byte 

Initial Comment:
Hello,

i get this error when i try to install rails. 
Many other gems can be installed without problems.


$ sudo gem install  rails --backtrace
ERROR:  While executing gem ... (ArgumentError)
    string contains null byte
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_reader/entry.rb:66:in `join'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_reader/entry.rb:66:in `full_name'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_input.rb:32:in `block in initialize'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_reader.rb:63:in `block in each'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_reader.rb:54:in `loop'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_reader.rb:54:in `each'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_input.rb:31:in `initialize'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_input.rb:16:in `new'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_input.rb:16:in `open'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package.rb:56:in `open'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/format.rb:67:in `from_io'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/format.rb:51:in `block in from_file_by_path'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/format.rb:50:in `open'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/format.rb:50:in `from_file_by_path'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/installer.rb:119:in `initialize'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/dependency_installer.rb:239:in `new'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/dependency_installer.rb:239:in `block in install'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/dependency_installer.rb:222:in `each'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/dependency_installer.rb:222:in `install'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/commands/install_command.rb:118:in `block in execute'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/commands/install_command.rb:115:in `each'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/commands/install_command.rb:115:in `execute'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command.rb:257:in `invoke'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command_manager.rb:132:in `process_args'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command_manager.rb:102:in `run'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/gem_runner.rb:58:in `run'
	/usr/local/bin/gem:21:in `<main>'

$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.5
  - RUBY VERSION: 1.9.2 (2009-10-21 patchlevel -1) [i686-linux]
  - INSTALLATION DIRECTORY: /usr/local/lib/ruby/gems/1.9.1
  - RUBYGEMS PREFIX: /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5
  - RUBY EXECUTABLE: /usr/local/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/local/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /usr/local/lib/ruby/gems/1.9.1
     - /home/tp/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://gems.rubyforge.org/"]
     - "rdoc" => "--inline-source --line-numbers --format=html --template=hanna"
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/


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

Comment By: Jan-Jan vdVyver (iibtrih)
Date: 2011-01-14 21:28

Message:
I have a similar error for both installing bundler and rails:

$ gem install bundler --backtrace
ERROR:  While executing gem ... (Zlib::DataError)
    invalid block type
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:215:in `finish'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:215:in `ensure in zipped_stream'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:215:in `zipped_stream'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:122:in `block in each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_reader.rb:64:in `block in each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_reader.rb:55:in `loop'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_reader.rb:55:in `each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:120:in `each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:67:in `block in from_io'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:19:in `open'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package.rb:58:in `open'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:63:in `from_io'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:51:in `block in from_file_by_path'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:50:in `open'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:50:in `from_file_by_path'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/installer.rb:118:in `initialize'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/dependency_installer.rb:264:in `new'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/dependency_installer.rb:264:in `block in install'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/dependency_installer.rb:247:in `each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/dependency_installer.rb:247:in `install'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/commands/install_command.rb:119:in `block in execute'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/commands/install_command.rb:116:in `each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/commands/install_command.rb:116:in `execute'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/command.rb:270:in `invoke'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/command_manager.rb:134:in `process_args'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/command_manager.rb:104:in `run'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/gem_runner.rb:58:in `run'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/bin/gem:25:in `<main>'



$ gem install rails --backtrace
ERROR:  While executing gem ... (ArgumentError)
    string contains null byte
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_reader/entry.rb:66:in `join'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_reader/entry.rb:66:in `full_name'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:33:in `block in initialize'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_reader.rb:64:in `block in each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_reader.rb:55:in `loop'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_reader.rb:55:in `each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:32:in `initialize'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:17:in `new'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:17:in `open'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package.rb:58:in `open'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:63:in `from_io'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:51:in `block in from_file_by_path'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:50:in `open'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:50:in `from_file_by_path'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/installer.rb:118:in `initialize'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/dependency_installer.rb:264:in `new'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/dependency_installer.rb:264:in `block in install'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/dependency_installer.rb:247:in `each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/dependency_installer.rb:247:in `install'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/commands/install_command.rb:119:in `block in execute'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/commands/install_command.rb:116:in `each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/commands/install_command.rb:116:in `execute'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/command.rb:270:in `invoke'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/command_manager.rb:134:in `process_args'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/command_manager.rb:104:in `run'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/gem_runner.rb:58:in `run'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/bin/gem:25:in `<main>'



$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [x86_64-darwin10.6.0]
  - INSTALLATION DIRECTORY: /Users/iibtrih/.rvm/gems/ruby-head
  - RUBY EXECUTABLE: /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/bin/ruby
  - EXECUTABLE DIRECTORY: /Users/iibtrih/.rvm/gems/ruby-head/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-darwin-10
  - GEM PATHS:
     - /Users/iibtrih/.rvm/gems/ruby-head
     - /Users/iibtrih/.rvm/gems/ruby-head at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://rubygems.org/

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

Comment By: Ryan Davis (zenspider)
Date: 2010-11-13 00:46

Message:
This ticket has been deemed stale and we're closing it in order to catch up 
with our ticket list. If you think it is still valid, please reopen.

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

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

From noreply at rubyforge.org  Fri Jan 14 20:04:15 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 14 Jan 2011 20:04:15 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-27324 ] string contains null
	byte
Message-ID: <20110115010415.260A5185838C@rubyforge.org>

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

Category: `gem install` command
Group: v1.3.x
Status: Closed
Resolution: None
Priority: 3
Submitted By: Thomas Preymesser (thopre)
Assigned to: Nobody (None)
Summary: string contains null byte 

Initial Comment:
Hello,

i get this error when i try to install rails. 
Many other gems can be installed without problems.


$ sudo gem install  rails --backtrace
ERROR:  While executing gem ... (ArgumentError)
    string contains null byte
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_reader/entry.rb:66:in `join'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_reader/entry.rb:66:in `full_name'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_input.rb:32:in `block in initialize'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_reader.rb:63:in `block in each'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_reader.rb:54:in `loop'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_reader.rb:54:in `each'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_input.rb:31:in `initialize'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_input.rb:16:in `new'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_input.rb:16:in `open'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package.rb:56:in `open'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/format.rb:67:in `from_io'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/format.rb:51:in `block in from_file_by_path'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/format.rb:50:in `open'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/format.rb:50:in `from_file_by_path'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/installer.rb:119:in `initialize'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/dependency_installer.rb:239:in `new'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/dependency_installer.rb:239:in `block in install'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/dependency_installer.rb:222:in `each'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/dependency_installer.rb:222:in `install'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/commands/install_command.rb:118:in `block in execute'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/commands/install_command.rb:115:in `each'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/commands/install_command.rb:115:in `execute'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command.rb:257:in `invoke'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command_manager.rb:132:in `process_args'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command_manager.rb:102:in `run'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/gem_runner.rb:58:in `run'
	/usr/local/bin/gem:21:in `<main>'

$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.5
  - RUBY VERSION: 1.9.2 (2009-10-21 patchlevel -1) [i686-linux]
  - INSTALLATION DIRECTORY: /usr/local/lib/ruby/gems/1.9.1
  - RUBYGEMS PREFIX: /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5
  - RUBY EXECUTABLE: /usr/local/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/local/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /usr/local/lib/ruby/gems/1.9.1
     - /home/tp/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://gems.rubyforge.org/"]
     - "rdoc" => "--inline-source --line-numbers --format=html --template=hanna"
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/


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

>Comment By: Eric Hodel (drbrain)
Date: 2011-01-14 17:04

Message:
You have corrupt downloads.

This is either an issue with your network or your filesystem.

Try removing the cache/ directory from your gem paths.

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

Comment By: Jan-Jan vdVyver (iibtrih)
Date: 2011-01-14 11:28

Message:
I have a similar error for both installing bundler and rails:

$ gem install bundler --backtrace
ERROR:  While executing gem ... (Zlib::DataError)
    invalid block type
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:215:in `finish'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:215:in `ensure in zipped_stream'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:215:in `zipped_stream'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:122:in `block in each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_reader.rb:64:in `block in each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_reader.rb:55:in `loop'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_reader.rb:55:in `each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:120:in `each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:67:in `block in from_io'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:19:in `open'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package.rb:58:in `open'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:63:in `from_io'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:51:in `block in from_file_by_path'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:50:in `open'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:50:in `from_file_by_path'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/installer.rb:118:in `initialize'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/dependency_installer.rb:264:in `new'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/dependency_installer.rb:264:in `block in install'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/dependency_installer.rb:247:in `each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/dependency_installer.rb:247:in `install'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/commands/install_command.rb:119:in `block in execute'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/commands/install_command.rb:116:in `each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/commands/install_command.rb:116:in `execute'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/command.rb:270:in `invoke'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/command_manager.rb:134:in `process_args'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/command_manager.rb:104:in `run'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/gem_runner.rb:58:in `run'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/bin/gem:25:in `<main>'



$ gem install rails --backtrace
ERROR:  While executing gem ... (ArgumentError)
    string contains null byte
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_reader/entry.rb:66:in `join'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_reader/entry.rb:66:in `full_name'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:33:in `block in initialize'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_reader.rb:64:in `block in each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_reader.rb:55:in `loop'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_reader.rb:55:in `each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:32:in `initialize'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:17:in `new'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:17:in `open'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package.rb:58:in `open'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:63:in `from_io'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:51:in `block in from_file_by_path'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:50:in `open'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:50:in `from_file_by_path'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/installer.rb:118:in `initialize'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/dependency_installer.rb:264:in `new'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/dependency_installer.rb:264:in `block in install'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/dependency_installer.rb:247:in `each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/dependency_installer.rb:247:in `install'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/commands/install_command.rb:119:in `block in execute'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/commands/install_command.rb:116:in `each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/commands/install_command.rb:116:in `execute'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/command.rb:270:in `invoke'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/command_manager.rb:134:in `process_args'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/command_manager.rb:104:in `run'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/gem_runner.rb:58:in `run'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/bin/gem:25:in `<main>'



$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [x86_64-darwin10.6.0]
  - INSTALLATION DIRECTORY: /Users/iibtrih/.rvm/gems/ruby-head
  - RUBY EXECUTABLE: /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/bin/ruby
  - EXECUTABLE DIRECTORY: /Users/iibtrih/.rvm/gems/ruby-head/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-darwin-10
  - GEM PATHS:
     - /Users/iibtrih/.rvm/gems/ruby-head
     - /Users/iibtrih/.rvm/gems/ruby-head at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://rubygems.org/

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

Comment By: Ryan Davis (zenspider)
Date: 2010-11-12 14:46

Message:
This ticket has been deemed stale and we're closing it in order to catch up 
with our ticket list. If you think it is still valid, please reopen.

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

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

From nakahiro at gmail.com  Mon Jan 17 10:35:21 2011
From: nakahiro at gmail.com (Hiroshi Nakamura)
Date: Tue, 18 Jan 2011 00:35:21 +0900
Subject: [Rubygems-developers] Proposal: deprecation of 'cert' command (and
	gem security features)
Message-ID: <AANLkTimuFgGYYsHot-H4fvUiDX_GZu3w7kiW+LCxW+TY@mail.gmail.com>

Hi, rubygems developers!

Subject says it all, let me put forward a proposal of 'cert' command
deprecation (and eventually removal.)

- 'cert' command is not used. There's almost no signed gem distributed.

- the gem security feature discussed in RDoc of
lib/rubygems/security.rb looks it's an original trust-framework, which
means no security auditing is performed. It uses PKIX X509
certificates but the certificate trust chain validation and
certificate verification is not conformed to RFC5280/3280. No CA
check, no keyUsage check, and validity period is checked partly
(test/rubygems/public_cert.pem is expired but test passes.)

- the gem security implementation still has lots of TODOs according to
the RDoc but AFAIK no sign of progress.

- It's the only reason why rubygems depends on openssl. With removing
'cert' command, rubygems gets openssl free.

To be honest, the last one is the most important reason for me, as an
author of CRuby's ext/openssl and as a committer of JRuby. :)

I'm not familiar with rubygems so I should be misunderstanding
something. Please correct me if I'm wrong. Thank you for your
attention to my proposal.

Regards,
// NaHi

From nick at quaran.to  Mon Jan 17 11:01:54 2011
From: nick at quaran.to (Nick Quaranto)
Date: Mon, 17 Jan 2011 11:01:54 -0500
Subject: [Rubygems-developers] Proposal: deprecation of 'cert' command
 (and gem security features)
In-Reply-To: <AANLkTimuFgGYYsHot-H4fvUiDX_GZu3w7kiW+LCxW+TY@mail.gmail.com>
References: <AANLkTimuFgGYYsHot-H4fvUiDX_GZu3w7kiW+LCxW+TY@mail.gmail.com>
Message-ID: <AANLkTi=Da9WyQbFuAfqHNgS_dUkkURBeZA4nsZKdETkw@mail.gmail.com>

I'm not sure what to do about the cert stuff, but we do need OpenSSL
as a dependency since `gem push`, `gem owner`, and the like use SSL to
talk to rubygems.org. Unless if you prefer your passwords sent in the
clear. :)

On Mon, Jan 17, 2011 at 10:35 AM, Hiroshi Nakamura <nakahiro at gmail.com> wrote:
> Hi, rubygems developers!
>
> Subject says it all, let me put forward a proposal of 'cert' command
> deprecation (and eventually removal.)
>
> - 'cert' command is not used. There's almost no signed gem distributed.
>
> - the gem security feature discussed in RDoc of
> lib/rubygems/security.rb looks it's an original trust-framework, which
> means no security auditing is performed. It uses PKIX X509
> certificates but the certificate trust chain validation and
> certificate verification is not conformed to RFC5280/3280. No CA
> check, no keyUsage check, and validity period is checked partly
> (test/rubygems/public_cert.pem is expired but test passes.)
>
> - the gem security implementation still has lots of TODOs according to
> the RDoc but AFAIK no sign of progress.
>
> - It's the only reason why rubygems depends on openssl. With removing
> 'cert' command, rubygems gets openssl free.
>
> To be honest, the last one is the most important reason for me, as an
> author of CRuby's ext/openssl and as a committer of JRuby. :)
>
> I'm not familiar with rubygems so I should be misunderstanding
> something. Please correct me if I'm wrong. Thank you for your
> attention to my proposal.
>
> Regards,
> // NaHi
> _______________________________________________
> 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  Mon Jan 17 11:18:56 2011
From: halostatue at gmail.com (Austin Ziegler)
Date: Mon, 17 Jan 2011 11:18:56 -0500
Subject: [Rubygems-developers] Proposal: deprecation of 'cert' command
 (and gem security features)
In-Reply-To: <AANLkTimuFgGYYsHot-H4fvUiDX_GZu3w7kiW+LCxW+TY@mail.gmail.com>
References: <AANLkTimuFgGYYsHot-H4fvUiDX_GZu3w7kiW+LCxW+TY@mail.gmail.com>
Message-ID: <AANLkTin_33H8CWWbKgO8CDhKPNX8V6FEsgUBZoZP5-85@mail.gmail.com>

On Mon, Jan 17, 2011 at 10:35 AM, Hiroshi Nakamura <nakahiro at gmail.com> wrote:
> Subject says it all, let me put forward a proposal of 'cert' command
> deprecation (and eventually removal.)

Would it be possible to implement 'cert' as a plug-in? But otherwise,
I agree. I think we should be moving toward signature verification,
but IMO the infrastructure isn't sufficient yet to warrant it and it's
an unnecessary dependency until we have a better idea of how we're
going to validate that a given gem is valid.

-a
-- 
Austin Ziegler ? halostatue at gmail.com ? austin at halostatue.ca
http://www.halostatue.ca/ ? http://twitter.com/halostatue

From nakahiro at gmail.com  Mon Jan 17 20:23:15 2011
From: nakahiro at gmail.com (Hiroshi Nakamura)
Date: Tue, 18 Jan 2011 10:23:15 +0900
Subject: [Rubygems-developers] Proposal: deprecation of 'cert' command
 (and gem security features)
In-Reply-To: <AANLkTi=Da9WyQbFuAfqHNgS_dUkkURBeZA4nsZKdETkw@mail.gmail.com>
References: <AANLkTimuFgGYYsHot-H4fvUiDX_GZu3w7kiW+LCxW+TY@mail.gmail.com>
	<AANLkTi=Da9WyQbFuAfqHNgS_dUkkURBeZA4nsZKdETkw@mail.gmail.com>
Message-ID: <AANLkTiktepQAMJJ2KC1qrwN2ymMXeKKm89rfORkaw1tL@mail.gmail.com>

Hi Nick,

You are right. Thanks for pointing this!

On Tue, Jan 18, 2011 at 01:01, Nick Quaranto <nick at quaran.to> wrote:
> I'm not sure what to do about the cert stuff, but we do need OpenSSL
> as a dependency since `gem push`, `gem owner`, and the like use SSL to
> talk to rubygems.org. Unless if you prefer your passwords sent in the
> clear. :)

I wrote too much. Sorry. I should have written;

- It's the only reason why rubygems depends on openssl *by default*,
even if user doesn't want to use its feature. With removing 'cert'
command, *some features of* rubygems gets openss free.

Users who want to push gem still needs openssl. And users who adds
'https://rubygems.org/' like me needs openssl to scan the central
repository.

*For me*, it's more important that rubygems tries to require 'openssl'
only when it's really needed, not by default. I know current rubygems
doesn't depends on openssl. It works even if there's no openssl
installed but this hidden dependency makes it harder for jruby to
reduce startup time.

Of course it's jruby and jruby-ossl issue and it's not a point of my
proposal. If rubygems really has an openssl dependency, it's OK.
Please consider other points I wrote regardless of this point. :)

Regards,
// NaHi

From thewoolleyman at gmail.com  Tue Jan 18 01:01:01 2011
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Mon, 17 Jan 2011 23:01:01 -0700
Subject: [Rubygems-developers] Release coming,
 but still no response on broken 1.9.x CI builds
In-Reply-To: <AANLkTikL-Py6+x3xgBpW=tSL3E8J1GgWTvByT8GWYmnW@mail.gmail.com>
References: <AANLkTi=dye+Q9JYUtghGaiB-+rGDisV9xUZPt8sBOQMK@mail.gmail.com>
	<300AF5C3-C708-436E-86E5-F83000C61DC2@segment7.net>
	<2C5AB12B-5171-4A2B-BD80-85AA15CF877E@zenspider.com>
	<AANLkTikL-Py6+x3xgBpW=tSL3E8J1GgWTvByT8GWYmnW@mail.gmail.com>
Message-ID: <AANLkTinA7Y3Vm2NxfPNoHMneS0fvfpEbepMetn9Ega2O@mail.gmail.com>

On Tue, Jan 11, 2011 at 11:28 PM, Chad Woolley <thewoolleyman at gmail.com> wrote:
> On Tue, Jan 11, 2011 at 2:11 PM, Ryan Davis <ryand-ruby at zenspider.com> wrote:
>> Still running 1.9.2-p0.
>>
>> Still doesn't have libyaml installed.
>>
>> Still running 1.9.1-p430.
>>
>> We'd be green otherwise...
>
> Having trouble making rvm ruby patchlevels float in ccrb's build
> script. ?Discussing it with Wayne. ?If I don't get it soon I'll punt
> and just hardcode the patchlevels, which works fine, but will need to
> be updated manually as new patchlevels come out.

OK, there's definitely a bug with 'rvm use' not overriding a different
default interpreter when called from a script.  Reproducible outside
of ccrb (git://github.com/thewoolleyman/ccrb_rvm_test.git).  I'll work
with Wayne on that, but for now I've given up on floating patch
levels, and hardcoded the latest supported by rvm head.

Here's the status:

1.8.7-p330 - Green:
http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_8_7-p330

1.9.1-p378 - Red: (<"no such file to load -- io/console">)
http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_1-p378

1.9.2-p136 - Red (<"no such file to load -- io/console">):
http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_2-p136

1.9.2 still has YAML spam too, even though I installed libyaml-dev.
I'm not sure what exact Debian yaml package gets rid of these, I'll
look into it later.  For now just view the raw log to see the errors
after the spam.

So, I think it is close!  Just the io/console problem.  As soon as
these go green, I'm going to turn back on failure emails to this list
- which can always be disabled by any committer by editing
cruise_config.rb.

Thanks,
-- Chad

From erik at hollensbe.org  Tue Jan 18 02:00:06 2011
From: erik at hollensbe.org (Erik Hollensbe)
Date: Tue, 18 Jan 2011 02:00:06 -0500
Subject: [Rubygems-developers] Release coming,
	but still no response on broken 1.9.x CI builds
In-Reply-To: <AANLkTinA7Y3Vm2NxfPNoHMneS0fvfpEbepMetn9Ega2O@mail.gmail.com>
References: <AANLkTi=dye+Q9JYUtghGaiB-+rGDisV9xUZPt8sBOQMK@mail.gmail.com>
	<300AF5C3-C708-436E-86E5-F83000C61DC2@segment7.net>
	<2C5AB12B-5171-4A2B-BD80-85AA15CF877E@zenspider.com>
	<AANLkTikL-Py6+x3xgBpW=tSL3E8J1GgWTvByT8GWYmnW@mail.gmail.com>
	<AANLkTinA7Y3Vm2NxfPNoHMneS0fvfpEbepMetn9Ega2O@mail.gmail.com>
Message-ID: <D107012B-967B-480E-AA6A-1EDA8F8EC012@hollensbe.org>


On Jan 18, 2011, at 1:01 AM, Chad Woolley wrote:

> On Tue, Jan 11, 2011 at 11:28 PM, Chad Woolley <thewoolleyman at gmail.com> wrote:
>> On Tue, Jan 11, 2011 at 2:11 PM, Ryan Davis <ryand-ruby at zenspider.com> wrote:
>>> Still running 1.9.2-p0.
>>> 
>>> Still doesn't have libyaml installed.
>>> 
>>> Still running 1.9.1-p430.
>>> 
>>> We'd be green otherwise...
>> 
>> Having trouble making rvm ruby patchlevels float in ccrb's build
>> script.  Discussing it with Wayne.  If I don't get it soon I'll punt
>> and just hardcode the patchlevels, which works fine, but will need to
>> be updated manually as new patchlevels come out.
> 
> OK, there's definitely a bug with 'rvm use' not overriding a different
> default interpreter when called from a script.  Reproducible outside
> of ccrb (git://github.com/thewoolleyman/ccrb_rvm_test.git).  I'll work
> with Wayne on that, but for now I've given up on floating patch
> levels, and hardcoded the latest supported by rvm head.

I'm not wayne or anything, but you might have better success with rvm-shell -c.

Usage:

rvm-shell '1.9.2' -c 'some command that will have ruby 1.9.2 in the path'

We use it at work (root installed) to split between unicorns that run 1.9.2 and REE apps. Works great with rake, cap, etc.

HTH.

-Erik

From jftucker at gmail.com  Tue Jan 18 17:28:39 2011
From: jftucker at gmail.com (James Tucker)
Date: Tue, 18 Jan 2011 14:28:39 -0800
Subject: [Rubygems-developers] Proposal: deprecation of 'cert' command
	(and gem security features)
In-Reply-To: <AANLkTiktepQAMJJ2KC1qrwN2ymMXeKKm89rfORkaw1tL@mail.gmail.com>
References: <AANLkTimuFgGYYsHot-H4fvUiDX_GZu3w7kiW+LCxW+TY@mail.gmail.com>
	<AANLkTi=Da9WyQbFuAfqHNgS_dUkkURBeZA4nsZKdETkw@mail.gmail.com>
	<AANLkTiktepQAMJJ2KC1qrwN2ymMXeKKm89rfORkaw1tL@mail.gmail.com>
Message-ID: <D8BD1B78-7B2F-42AC-9B69-2D1857136923@gmail.com>


On Jan 17, 2011, at 5:23 PM, Hiroshi Nakamura wrote:

> Hi Nick,
> 
> You are right. Thanks for pointing this!
> 
> On Tue, Jan 18, 2011 at 01:01, Nick Quaranto <nick at quaran.to> wrote:
>> I'm not sure what to do about the cert stuff, but we do need OpenSSL
>> as a dependency since `gem push`, `gem owner`, and the like use SSL to
>> talk to rubygems.org. Unless if you prefer your passwords sent in the
>> clear. :)
> 
> I wrote too much. Sorry. I should have written;
> 
> - It's the only reason why rubygems depends on openssl *by default*,
> even if user doesn't want to use its feature. With removing 'cert'
> command, *some features of* rubygems gets openss free.
> 
> Users who want to push gem still needs openssl. And users who adds
> 'https://rubygems.org/' like me needs openssl to scan the central
> repository.
> 
> *For me*, it's more important that rubygems tries to require 'openssl'
> only when it's really needed, not by default. I know current rubygems
> doesn't depends on openssl. It works even if there's no openssl
> installed but this hidden dependency makes it harder for jruby to
> reduce startup time.


i think i already did this in the rubygems repo, didn't i?


> 
> Of course it's jruby and jruby-ossl issue and it's not a point of my
> proposal. If rubygems really has an openssl dependency, it's OK.
> Please consider other points I wrote regardless of this point. :)
> 
> Regards,
> // NaHi
> _______________________________________________
> Rubygems-developers mailing list
> http://rubyforge.org/projects/rubygems
> Rubygems-developers at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubygems-developers


From ryand-ruby at zenspider.com  Tue Jan 18 18:34:04 2011
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Tue, 18 Jan 2011 15:34:04 -0800
Subject: [Rubygems-developers] The 1.9 Plan
In-Reply-To: <D5B459BB-BD8A-4D3B-8FD6-109F2CF3EEA7@zenspider.com>
References: <D5B459BB-BD8A-4D3B-8FD6-109F2CF3EEA7@zenspider.com>
Message-ID: <D94B5B04-05EB-4ACF-88C9-4F42C91D04BB@zenspider.com>

This is an update to my 1.9 status report from 3 weeks ago.

The short story is: we're set to release 1.5 at the end of the month and we're going to import our code into ruby trunk shortly. This release has workarounds for the 1.9.2 upgrade problems we've been seeing.

Luis: heads up. See last paragraph.

On Dec 21, 2010, at 17:00 , Ryan Davis wrote:

> I just pulled the rubygems in ruby-core's trunk into our 1.9 branch and tweaked it enough to make it pass under 1.8.7. The changes were minimal to lib and mostly just annoying in test. I've pushed this back up so that others can review.
> 
> Moving forward:
> 
> + I'm prolly gonna move everything from test/* to test/rubygems/* to match ruby-core. They switched us to require_relative on everything (ugh).

done

> + We need to selectively pull additions and changes from the 1.9 branch to master.
>  + I don't have a handle on what (or why) changes have happened on ruby trunk.
>  + Input is welcome.
>  + It is about 3k line o' diff. Help is welcome too.

done - I think... Eric and I reviewed the diffs and we brought over a minimum of changes.

See 36e6afff7bb3c14e03a71c1cf1a61c03a7da685c for specifics.

> + Once we reconcile differences between the 1.9 branch and master, we nuke the 1.9 branch and push all our changes to ruby trunk.

This will be done when we release...

I'm ready and prepping my push back to ruby trunk.

> + ruby trunk pushes will be automated and include a warning header in every file.

done

> + Any changes that occur in ruby trunk will be reverted immediately.
>  + I'd rather push every single day to ruby trunk than to ever do this reconciliation again.

And we already had to do one. :/

Nobu made a 1.8-incompatible change w/o a test so I reverted it today.

> Raggi says that he's close to a rack release, which is the big blocker for rails, which is our big blocker. He estimates the dam will break sometime this week and we'll be free to release after that.

The dam was broken for our 1.4 release on our side. It seems to have gone well (enough).

Eric's changes are in that make this work against 1.9.2 (w/ rubygems 1.3.7 installed). Luis, if you have any platform showstoppers, we need to know about them soon. Manual testing seems to show that this thing works and we'll get the 1.9.2 problems flushed out when we release 1.5.0.

From luislavena at gmail.com  Tue Jan 18 18:39:45 2011
From: luislavena at gmail.com (Luis Lavena)
Date: Tue, 18 Jan 2011 20:39:45 -0300
Subject: [Rubygems-developers] The 1.9 Plan
In-Reply-To: <D94B5B04-05EB-4ACF-88C9-4F42C91D04BB@zenspider.com>
References: <D5B459BB-BD8A-4D3B-8FD6-109F2CF3EEA7@zenspider.com>
	<D94B5B04-05EB-4ACF-88C9-4F42C91D04BB@zenspider.com>
Message-ID: <AANLkTi=rZorQX3hw_QfsmdmvUaOojQueq9weo3kJzmbp@mail.gmail.com>

On Tue, Jan 18, 2011 at 8:34 PM, Ryan Davis <ryand-ruby at zenspider.com> wrote:
> This is an update to my 1.9 status report from 3 weeks ago.
>
> The short story is: we're set to release 1.5 at the end of the month and we're going to import our code into ruby trunk shortly. This release has workarounds for the 1.9.2 upgrade problems we've been seeing.
>
> Luis: heads up. See last paragraph.
>
> Eric's changes are in that make this work against 1.9.2 (w/ rubygems 1.3.7 installed). Luis, if you have any platform showstoppers, we need to know about them soon. Manual testing seems to show that this thing works and we'll get the 1.9.2 problems flushed out when we release 1.5.0.

I'll start running my tests with master against all known versions of
RubyInstaller. It will take a bit but want to ensure nothing goes
wrong.

Will have some results for you tomorrow.

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

From jftucker at gmail.com  Tue Jan 18 18:56:47 2011
From: jftucker at gmail.com (James Tucker)
Date: Tue, 18 Jan 2011 15:56:47 -0800
Subject: [Rubygems-developers] The 1.9 Plan
In-Reply-To: <D94B5B04-05EB-4ACF-88C9-4F42C91D04BB@zenspider.com>
References: <D5B459BB-BD8A-4D3B-8FD6-109F2CF3EEA7@zenspider.com>
	<D94B5B04-05EB-4ACF-88C9-4F42C91D04BB@zenspider.com>
Message-ID: <75C725E0-F274-41FE-9B76-4AEADA279ABF@gmail.com>


On Jan 18, 2011, at 3:34 PM, Ryan Davis wrote:
>> Raggi says that he's close to a rack release, which is the big blocker for rails, which is our big blocker. He estimates the dam will break sometime this week and we'll be free to release after that.
> 
> The dam was broken for our 1.4 release on our side. It seems to have gone well (enough).

Yeah sorry, I've been AWOL, just haven't had the time. I got a 1.1 rack release prepped in my last run, but ran out of time for cherrying up the 1.2.x branches, so a rack release is still some time away.

At this point leaving in the thread require is enough to prevent breakage on these apps. I've informed the bundler guys to get on this list, but I think they'd appreciate a heads up prior to release if at all possible, or a beta release to test against.

Good work on moving things forward, and sorry again for not having more time, I had to move again, among other things.

From ryand-ruby at zenspider.com  Tue Jan 18 19:30:50 2011
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Tue, 18 Jan 2011 16:30:50 -0800
Subject: [Rubygems-developers] rubygems 1.5.0 merged to ruby-core/trunk
Message-ID: <898B8358-25A6-4D3C-BA3C-D7DC9D7EBE8A@zenspider.com>

I've finished pushing rubygems to ruby-core/trunk. Right now we're focusing entirely on releasing 1.5.0 at the end of the month.

PLEASE: do not make changes to master w/o coordinating with us first.

Once 1.5.0 is out the door, we're agenda-less and can more freely develop. I'm still set on the idea of releasing minor releases every month until we feel like we've caught up with our backlog and have the feature-set the way we want it.

Thank you.


From luislavena at gmail.com  Tue Jan 18 21:18:29 2011
From: luislavena at gmail.com (Luis Lavena)
Date: Tue, 18 Jan 2011 23:18:29 -0300
Subject: [Rubygems-developers] The 1.9 Plan
In-Reply-To: <AANLkTi=rZorQX3hw_QfsmdmvUaOojQueq9weo3kJzmbp@mail.gmail.com>
References: <D5B459BB-BD8A-4D3B-8FD6-109F2CF3EEA7@zenspider.com>
	<D94B5B04-05EB-4ACF-88C9-4F42C91D04BB@zenspider.com>
	<AANLkTi=rZorQX3hw_QfsmdmvUaOojQueq9weo3kJzmbp@mail.gmail.com>
Message-ID: <AANLkTimY_gMi=2mhg0_9Sti8271vMkgTNLWaTWSAF1GL@mail.gmail.com>

On Tue, Jan 18, 2011 at 8:39 PM, Luis Lavena <luislavena at gmail.com> wrote:
>
> I'll start running my tests with master against all known versions of
> RubyInstaller. It will take a bit but want to ensure nothing goes
> wrong.
>

As commit b388ed417150bb259dbb6f46111c4dde1e86db0f:

ruby 1.8.7 (2010-12-23 patchlevel 330) [i386-mingw32]
757 tests, 2451 assertions, 0 failures, 0 errors, 13 skips

ruby 1.9.2p136 (2010-12-25) [i386-mingw32]
758 tests, 2450 assertions, 0 failures, 0 errors, 15 skips

ruby 1.9.3dev (2010-12-30 trunk 30431) [i386-mingw32]
758 tests, 2450 assertions, 0 failures, 0 errors, 15 skips

> Will have some results for you tomorrow.
>

Real life results will come next, building trunk as we speak and will
start using it to see any particular issue with the merge.

Or possible update process.

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 drbrain at segment7.net  Tue Jan 18 22:58:39 2011
From: drbrain at segment7.net (Eric Hodel)
Date: Tue, 18 Jan 2011 19:58:39 -0800
Subject: [Rubygems-developers] Proposal: deprecation of 'cert' command
	(and gem security features)
In-Reply-To: <D8BD1B78-7B2F-42AC-9B69-2D1857136923@gmail.com>
References: <AANLkTimuFgGYYsHot-H4fvUiDX_GZu3w7kiW+LCxW+TY@mail.gmail.com>
	<AANLkTi=Da9WyQbFuAfqHNgS_dUkkURBeZA4nsZKdETkw@mail.gmail.com>
	<AANLkTiktepQAMJJ2KC1qrwN2ymMXeKKm89rfORkaw1tL@mail.gmail.com>
	<D8BD1B78-7B2F-42AC-9B69-2D1857136923@gmail.com>
Message-ID: <56EB0605-231F-489A-A68C-8D9A2BCE3A96@segment7.net>

On Jan 18, 2011, at 14:28, James Tucker wrote:
> On Jan 17, 2011, at 5:23 PM, Hiroshi Nakamura wrote:
> 
>> Hi Nick,
>> 
>> You are right. Thanks for pointing this!
>> 
>> On Tue, Jan 18, 2011 at 01:01, Nick Quaranto <nick at quaran.to> wrote:
>>> I'm not sure what to do about the cert stuff, but we do need OpenSSL
>>> as a dependency since `gem push`, `gem owner`, and the like use SSL to
>>> talk to rubygems.org. Unless if you prefer your passwords sent in the
>>> clear. :)
>> 
>> I wrote too much. Sorry. I should have written;
>> 
>> - It's the only reason why rubygems depends on openssl *by default*,
>> even if user doesn't want to use its feature. With removing 'cert'
>> command, *some features of* rubygems gets openss free.
>> 
>> Users who want to push gem still needs openssl. And users who adds
>> 'https://rubygems.org/' like me needs openssl to scan the central
>> repository.
>> 
>> *For me*, it's more important that rubygems tries to require 'openssl'
>> only when it's really needed, not by default. I know current rubygems
>> doesn't depends on openssl. It works even if there's no openssl
>> installed but this hidden dependency makes it harder for jruby to
>> reduce startup time.
> 
> 
> i think i already did this in the rubygems repo, didn't i?

rubygems/security (thus rubygems/gem_openssl and openssl) are required only from commands, rubygems/package and rubygems/builder.  None of these are required by require 'rubygems':

$ ruby -Ilib -e 'require "rubygems"; p $".grep(/openssl/)'
[]

$ ruby -v -Ilib -e 'require "rubygems"; p $"'
ruby 1.8.7 (2009-06-12 patchlevel 174) [universal-darwin10.0]
["enumerator.so", "rubygems/defaults.rb", "rbconfig.rb", "thread.bundle", "thread.rb", "rubygems/exceptions.rb", "rubygems/custom_require.rb", "rubygems.rb"]

$ ruby19 -v -Ilib -e 'require "rubygems"; p $"'
ruby 1.9.3dev (2011-01-19 trunk 30599) [x86_64-darwin10.6.0]
["enumerator.so", "/usr/local/lib/ruby/1.9.1/x86_64-darwin10.6.0/enc/encdb.bundle", "/usr/local/lib/ruby/1.9.1/x86_64-darwin10.6.0/enc/trans/transdb.bundle", "/Users/drbrain/Work/git/rubygems/lib/rubygems/defaults.rb", "/usr/local/lib/ruby/1.9.1/x86_64-darwin10.6.0/rbconfig.rb", "/usr/local/lib/ruby/1.9.1/thread.rb", "/Users/drbrain/Work/git/rubygems/lib/rubygems/exceptions.rb", "/Users/drbrain/Work/git/rubygems/lib/rubygems/custom_require.rb", "/Users/drbrain/Work/git/rubygems/lib/rubygems.rb"]

From drbrain at segment7.net  Tue Jan 18 23:04:28 2011
From: drbrain at segment7.net (Eric Hodel)
Date: Tue, 18 Jan 2011 20:04:28 -0800
Subject: [Rubygems-developers] Proposal: deprecation of 'cert' command
	(and gem security features)
In-Reply-To: <AANLkTimuFgGYYsHot-H4fvUiDX_GZu3w7kiW+LCxW+TY@mail.gmail.com>
References: <AANLkTimuFgGYYsHot-H4fvUiDX_GZu3w7kiW+LCxW+TY@mail.gmail.com>
Message-ID: <9EF624E7-08CD-4E09-9E1A-31F38D89ED95@segment7.net>


On Jan 17, 2011, at 07:35, Hiroshi Nakamura wrote:

> Hi, rubygems developers!
> 
> Subject says it all, let me put forward a proposal of 'cert' command
> deprecation (and eventually removal.)
> 
> - 'cert' command is not used. There's almost no signed gem distributed.

I would like there to be more signed gems.  Like many commands of RubyGems, users do not know about it.

> - the gem security feature discussed in RDoc of
> lib/rubygems/security.rb looks it's an original trust-framework, which
> means no security auditing is performed. It uses PKIX X509
> certificates but the certificate trust chain validation and
> certificate verification is not conformed to RFC5280/3280. No CA
> check, no keyUsage check, and validity period is checked partly
> (test/rubygems/public_cert.pem is expired but test passes.)

Can you help us conform?  I will look into these RFCs to improve validation.

> - the gem security implementation still has lots of TODOs according to
> the RDoc but AFAIK no sign of progress.

Unfortunately I do not know much about building good security for gems.  I am afraid to write code because I do not want to do it wrong (and there have been bigger problems to solve).

> - It's the only reason why rubygems depends on openssl. With removing
> 'cert' command, rubygems gets openssl free.
> 
> To be honest, the last one is the most important reason for me, as an
> author of CRuby's ext/openssl and as a committer of JRuby. :)
> 
> I'm not familiar with rubygems so I should be misunderstanding
> something. Please correct me if I'm wrong. Thank you for your
> attention to my proposal.

Since I have seen your other post, I will make openssl optional even for gem commands so that openssl is required only when necessary.

Will this be sufficient?

From drbrain at segment7.net  Wed Jan 19 01:06:28 2011
From: drbrain at segment7.net (Eric Hodel)
Date: Tue, 18 Jan 2011 22:06:28 -0800
Subject: [Rubygems-developers] RubyGems install plugins
In-Reply-To: <B3FC0A03-1AE8-44FA-9BD5-3981B2C28F11@segment7.net>
References: <B3FC0A03-1AE8-44FA-9BD5-3981B2C28F11@segment7.net>
Message-ID: <9AC3036A-8A93-4B76-8AC7-693DC262C74A@segment7.net>


On Nov 15, 2010, at 17:59, Eric Hodel wrote:

> I think we need at least the following hooks:
> 
> 1) Before install, after download, "pre-install".  I'm not sure what this would be used for.  The hook should be able to abort the install.

I have modified pre-install to abort the install only if false (not nil) is returned.

> 2) After files have been written and extensions have been built but before executable stubs have been written or specification is written, "post-build".  This would be used for test tasks.  The hook should be able to abort the install, cleaning up the unpacked files and built extensions.

I have implemented post-build hooks that abort the install only if false (not nil) is returned.

> 3) After executable stubs and specification has been written, "post-install".  This could be used for documentation generation.  Gem::DocManager should be rewritten to use this hook.  The hook should not be able to abort the install.

post-install hooks work as-is.

> For each hook both the installer and the gemspec from the .gem file should be provided to the callback.

Per Jon's comments, a install hook user can retrieve the spec from the installer.


From headius at headius.com  Wed Jan 19 01:54:44 2011
From: headius at headius.com (Charles Oliver Nutter)
Date: Wed, 19 Jan 2011 00:54:44 -0600
Subject: [Rubygems-developers] The 1.9 Plan
In-Reply-To: <AANLkTimY_gMi=2mhg0_9Sti8271vMkgTNLWaTWSAF1GL@mail.gmail.com>
References: <D5B459BB-BD8A-4D3B-8FD6-109F2CF3EEA7@zenspider.com>
	<D94B5B04-05EB-4ACF-88C9-4F42C91D04BB@zenspider.com>
	<AANLkTi=rZorQX3hw_QfsmdmvUaOojQueq9weo3kJzmbp@mail.gmail.com>
	<AANLkTimY_gMi=2mhg0_9Sti8271vMkgTNLWaTWSAF1GL@mail.gmail.com>
Message-ID: <AANLkTimu5cb8Hwx61Ms1bcovUFrVNM=UgMDbYFTL-_cD@mail.gmail.com>

For what it's worth, JRuby in 1.8 mode running RubyGems master tests:

766 tests, 2516 assertions, 4 failures, 8 errors, 0 skips

I had to patch something to get it to run, though, and 1.9 mode blows
up with an internal JRuby error.

All documented here: http://jira.codehaus.org/browse/JRUBY-5386

- Charlie

From erik at hollensbe.org  Wed Jan 19 01:55:40 2011
From: erik at hollensbe.org (Erik Hollensbe)
Date: Wed, 19 Jan 2011 01:55:40 -0500
Subject: [Rubygems-developers] RubyGems install plugins
In-Reply-To: <9AC3036A-8A93-4B76-8AC7-693DC262C74A@segment7.net>
References: <B3FC0A03-1AE8-44FA-9BD5-3981B2C28F11@segment7.net>
	<9AC3036A-8A93-4B76-8AC7-693DC262C74A@segment7.net>
Message-ID: <22306AA4-B6A8-4C82-B983-7F9D5C5236FC@hollensbe.org>


On Jan 19, 2011, at 1:06 AM, Eric Hodel wrote:

> 
> On Nov 15, 2010, at 17:59, Eric Hodel wrote:
> 
>> I think we need at least the following hooks:
>> 
>> 1) Before install, after download, "pre-install".  I'm not sure what this would be used for.  The hook should be able to abort the install.
> 
> I have modified pre-install to abort the install only if false (not nil) is returned.
> 
>> 2) After files have been written and extensions have been built but before executable stubs have been written or specification is written, "post-build".  This would be used for test tasks.  The hook should be able to abort the install, cleaning up the unpacked files and built extensions.
> 
> I have implemented post-build hooks that abort the install only if false (not nil) is returned.
> 
>> 3) After executable stubs and specification has been written, "post-install".  This could be used for documentation generation.  Gem::DocManager should be rewritten to use this hook.  The hook should not be able to abort the install.
> 
> post-install hooks work as-is.
> 
>> For each hook both the installer and the gemspec from the .gem file should be provided to the callback.
> 
> Per Jon's comments, a install hook user can retrieve the spec from the installer.

Sorry if I'm being dense, but implemented as in already committed? I would really like to surf a branch of rg-t with some of the features listed here.

-Erik

From noreply at rubyforge.org  Wed Jan 19 06:14:56 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Wed, 19 Jan 2011 06:14:56 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28867 ] rubygems 1.5.0 breaks
	MRI build process (rdoc) on Windows
Message-ID: <20110119111456.BEA691858344@rubyforge.org>

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

Category: other
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Usaku Nakamura (usa)
Assigned to: Nobody (None)
Summary: rubygems 1.5.0 breaks MRI build process (rdoc) on Windows

Initial Comment:
C:\Users\usa\work> nmake
(snip)
Generating RDoc documentation
C:/Users/usa/ruby-trunk/lib/rubygems.rb:989:in `block in suffixes': undefined method `empty?' for nil:NilClass (NoMethodError)
        from C:/Users/usa/ruby-trunk/lib/rubygems.rb:987:in `map'
        from C:/Users/usa/ruby-trunk/lib/rubygems.rb:987:in `suffixes'
        from C:/Users/usa/ruby-trunk/lib/rubygems.rb:978:in `suffix_pattern'
        from C:/Users/usa/ruby-trunk/lib/rubygems.rb:510:in `blockin find_files'
        from C:/Users/usa/ruby-trunk/lib/rubygems.rb:509:in `map'
        from C:/Users/usa/ruby-trunk/lib/rubygems.rb:509:in `find_files'
        from C:/Users/usa/ruby-trunk/lib/rdoc/rdoc.rb:470:in `<top(required)>'
        from C:/Users/usa/ruby-trunk/lib/rubygems/custom_require.rb:35:in `require'
        from C:/Users/usa/ruby-trunk/lib/rubygems/custom_require.rb:35:in `require'
        from ../ruby-trunk/bin/rdoc:11:in `<main>'
NMAKE : fatal error U1077: '.\ruby.exe' : ???? ??? '0x1'
Stop.


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

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

From drbrain at segment7.net  Wed Jan 19 13:16:52 2011
From: drbrain at segment7.net (Eric Hodel)
Date: Wed, 19 Jan 2011 10:16:52 -0800
Subject: [Rubygems-developers] RubyGems install plugins
In-Reply-To: <22306AA4-B6A8-4C82-B983-7F9D5C5236FC@hollensbe.org>
References: <B3FC0A03-1AE8-44FA-9BD5-3981B2C28F11@segment7.net>
	<9AC3036A-8A93-4B76-8AC7-693DC262C74A@segment7.net>
	<22306AA4-B6A8-4C82-B983-7F9D5C5236FC@hollensbe.org>
Message-ID: <B3A0CFF2-EEA3-4A17-B2EF-6D65CF13D5B9@segment7.net>


On Jan 18, 2011, at 22:55, Erik Hollensbe wrote:

>> [?]
> 
> Sorry if I'm being dense, but implemented as in already committed? I would really like to surf a branch of rg-t with some of the features listed here.

They are committed, top two commits for yesterday:

https://github.com/rubygems/rubygems/commits/master

From noreply at rubyforge.org  Wed Jan 19 16:40:14 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Wed, 19 Jan 2011 16:40:14 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28867 ] rubygems 1.5.0 breaks
	MRI build process (rdoc) on Windows
Message-ID: <20110119214014.51F561858361@rubyforge.org>

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

Category: other
Group: None
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: Usaku Nakamura (usa)
Assigned to: Nobody (None)
Summary: rubygems 1.5.0 breaks MRI build process (rdoc) on Windows

Initial Comment:
C:\Users\usa\work> nmake
(snip)
Generating RDoc documentation
C:/Users/usa/ruby-trunk/lib/rubygems.rb:989:in `block in suffixes': undefined method `empty?' for nil:NilClass (NoMethodError)
        from C:/Users/usa/ruby-trunk/lib/rubygems.rb:987:in `map'
        from C:/Users/usa/ruby-trunk/lib/rubygems.rb:987:in `suffixes'
        from C:/Users/usa/ruby-trunk/lib/rubygems.rb:978:in `suffix_pattern'
        from C:/Users/usa/ruby-trunk/lib/rubygems.rb:510:in `blockin find_files'
        from C:/Users/usa/ruby-trunk/lib/rubygems.rb:509:in `map'
        from C:/Users/usa/ruby-trunk/lib/rubygems.rb:509:in `find_files'
        from C:/Users/usa/ruby-trunk/lib/rdoc/rdoc.rb:470:in `<top(required)>'
        from C:/Users/usa/ruby-trunk/lib/rubygems/custom_require.rb:35:in `require'
        from C:/Users/usa/ruby-trunk/lib/rubygems/custom_require.rb:35:in `require'
        from ../ruby-trunk/bin/rdoc:11:in `<main>'
NMAKE : fatal error U1077: '.\ruby.exe' : ???? ??? '0x1'
Stop.


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

>Comment By: Ryan Davis (zenspider)
Date: 2011-01-19 13:40

Message:
Not sure why some platforms have DLEXT2 as "" and some as nil.

Fixed. Thank you for the report.

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

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

From ryand-ruby at zenspider.com  Wed Jan 19 17:02:56 2011
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Wed, 19 Jan 2011 14:02:56 -0800
Subject: [Rubygems-developers] The 1.9 Plan
In-Reply-To: <AANLkTimu5cb8Hwx61Ms1bcovUFrVNM=UgMDbYFTL-_cD@mail.gmail.com>
References: <D5B459BB-BD8A-4D3B-8FD6-109F2CF3EEA7@zenspider.com>
	<D94B5B04-05EB-4ACF-88C9-4F42C91D04BB@zenspider.com>
	<AANLkTi=rZorQX3hw_QfsmdmvUaOojQueq9weo3kJzmbp@mail.gmail.com>
	<AANLkTimY_gMi=2mhg0_9Sti8271vMkgTNLWaTWSAF1GL@mail.gmail.com>
	<AANLkTimu5cb8Hwx61Ms1bcovUFrVNM=UgMDbYFTL-_cD@mail.gmail.com>
Message-ID: <D34C003F-1C3B-4ADB-B58F-A48740902B3D@zenspider.com>


On Jan 18, 2011, at 22:54 , Charles Oliver Nutter wrote:

> For what it's worth, JRuby in 1.8 mode running RubyGems master tests:
> 
> 766 tests, 2516 assertions, 4 failures, 8 errors, 0 skips
> 
> I had to patch something to get it to run, though, and 1.9 mode blows
> up with an internal JRuby error.
> 
> All documented here: http://jira.codehaus.org/browse/JRUBY-5386

I've fixed the first issue, also described by usa in RF#28867, and I've merged it (and all other recent changes) to ruby-core's trunk.

This won't address your other issue tho, I don't think. The first of which looks like a pathing or pwd problem? I can't tell. Can you verify that you have the pem file is the right place? We recently moved everything under test to test/rubygems.

% f pem$
./test/rubygems/data/gem-private_key.pem
./test/rubygems/data/gem-public_cert.pem
./test/rubygems/private_key.pem
./test/rubygems/public_cert.pem



From nakahiro at gmail.com  Wed Jan 19 18:30:35 2011
From: nakahiro at gmail.com (Hiroshi Nakamura)
Date: Thu, 20 Jan 2011 08:30:35 +0900
Subject: [Rubygems-developers] The 1.9 Plan
In-Reply-To: <D34C003F-1C3B-4ADB-B58F-A48740902B3D@zenspider.com>
References: <D5B459BB-BD8A-4D3B-8FD6-109F2CF3EEA7@zenspider.com>
	<D94B5B04-05EB-4ACF-88C9-4F42C91D04BB@zenspider.com>
	<AANLkTi=rZorQX3hw_QfsmdmvUaOojQueq9weo3kJzmbp@mail.gmail.com>
	<AANLkTimY_gMi=2mhg0_9Sti8271vMkgTNLWaTWSAF1GL@mail.gmail.com>
	<AANLkTimu5cb8Hwx61Ms1bcovUFrVNM=UgMDbYFTL-_cD@mail.gmail.com>
	<D34C003F-1C3B-4ADB-B58F-A48740902B3D@zenspider.com>
Message-ID: <AANLkTinAPGoqQ+ubFku74WzwfHmJNpiwr+U_W9P=m2f=@mail.gmail.com>

Hi,

On Thu, Jan 20, 2011 at 07:02, Ryan Davis <ryand-ruby at zenspider.com> wrote:
> Can you verify that you have the pem file is the right place? We recently moved everything under test to test/rubygems.

PEM file thing must be related to jruby-ossl implementation. I'll check this.

Regards,
// NaHi

From nahi at ruby-lang.org  Thu Jan 20 01:04:24 2011
From: nahi at ruby-lang.org (Hiroshi Nakamura)
Date: Thu, 20 Jan 2011 15:04:24 +0900
Subject: [Rubygems-developers] Proposal: deprecation of 'cert' command
 (and gem security features)
In-Reply-To: <56EB0605-231F-489A-A68C-8D9A2BCE3A96@segment7.net>
References: <AANLkTimuFgGYYsHot-H4fvUiDX_GZu3w7kiW+LCxW+TY@mail.gmail.com>	<AANLkTi=Da9WyQbFuAfqHNgS_dUkkURBeZA4nsZKdETkw@mail.gmail.com>	<AANLkTiktepQAMJJ2KC1qrwN2ymMXeKKm89rfORkaw1tL@mail.gmail.com>	<D8BD1B78-7B2F-42AC-9B69-2D1857136923@gmail.com>
	<56EB0605-231F-489A-A68C-8D9A2BCE3A96@segment7.net>
Message-ID: <4D37D068.2060900@ruby-lang.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Sorry for late response.

(2011/01/19 12:58), Eric Hodel wrote:
>>> - It's the only reason why rubygems depends on openssl *by default*,
>>> even if user doesn't want to use its feature. With removing 'cert'
>>> command, *some features of* rubygems gets openss free.
>>>
>>> Users who want to push gem still needs openssl. And users who adds
>>> 'https://rubygems.org/' like me needs openssl to scan the central
>>> repository.
>>>
>>> *For me*, it's more important that rubygems tries to require 'openssl'
>>> only when it's really needed, not by default. I know current rubygems
>>> doesn't depends on openssl. It works even if there's no openssl
>>> installed but this hidden dependency makes it harder for jruby to
>>> reduce startup time.
>>
>> i think i already did this in the rubygems repo, didn't i?
> 
> rubygems/security (thus rubygems/gem_openssl and openssl) are required only from commands, rubygems/package and rubygems/builder.  None of these are required by require 'rubygems':
> 
> $ ruby -Ilib -e 'require "rubygems"; p $".grep(/openssl/)'
> []
> 
> $ ruby -v -Ilib -e 'require "rubygems"; p $"'
> ruby 1.8.7 (2009-06-12 patchlevel 174) [universal-darwin10.0]
> ["enumerator.so", "rubygems/defaults.rb", "rbconfig.rb", "thread.bundle", "thread.rb", "rubygems/exceptions.rb", "rubygems/custom_require.rb", "rubygems.rb"]
> 
> $ ruby19 -v -Ilib -e 'require "rubygems"; p $"'
> ruby 1.9.3dev (2011-01-19 trunk 30599) [x86_64-darwin10.6.0]
> ["enumerator.so", "/usr/local/lib/ruby/1.9.1/x86_64-darwin10.6.0/enc/encdb.bundle", "/usr/local/lib/ruby/1.9.1/x86_64-darwin10.6.0/enc/trans/transdb.bundle", "/Users/drbrain/Work/git/rubygems/lib/rubygems/defaults.rb", "/usr/local/lib/ruby/1.9.1/x86_64-darwin10.6.0/rbconfig.rb", "/usr/local/lib/ruby/1.9.1/thread.rb", "/Users/drbrain/Work/git/rubygems/lib/rubygems/exceptions.rb", "/Users/drbrain/Work/git/rubygems/lib/rubygems/custom_require.rb", "/Users/drbrain/Work/git/rubygems/lib/rubygems.rb"]

I confirmed that rubygems 1.3.7 already does not have openssl
dependency. rubygems/security.rb is loaded only when install/update,
cert, and packaging. My claim was completely wrong. I'm very sorry for
bothering you.

Regards,
// NaHi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)

iQEcBAEBAgAGBQJNN9BoAAoJEC7N6P3yLbI2bs0IAN3W2IEWfRM+h6q3V3VASo/+
T/c/GmjjVPNpOAJmRc+fBuCMVj27aB2nhyl7WHSCRoczxFwwKraU1MwSLLyEpvpj
r6SwKjDCOjXTOtRdFQFzFlQzIRLKC1dEOePG1J7Ww9BSq95F3S5zofJ+MxugQlMz
PrgkZVaE4DE9vTSFlnPxRpfSp700rh7+ex5iPLrtoGFq4fWYGdkCe39zEOArw2rq
Gnwt118FLmEXXch4kW0I1PeyGuyWiamCOtY+9joK105CH6dgbT8kSq2ofQm20grK
KyZbKFRLTSGpoA/7FoKJc17+IOl7rl5wFHMw9gjHH0XacngnRANiJp05ui0BPq4=
=/7Mx
-----END PGP SIGNATURE-----

From drbrain at segment7.net  Thu Jan 20 14:06:24 2011
From: drbrain at segment7.net (Eric Hodel)
Date: Thu, 20 Jan 2011 11:06:24 -0800
Subject: [Rubygems-developers] RubyGemTestCase has moved
Message-ID: <DA83B0C9-21CB-4AE1-98D9-8E42BF3A0E93@segment7.net>

RubyGemTestCase in test/rubygems/gemutilities.rb has moved!

Now it is Gem::TestCase in lib/rubygems/test_case!

I've added some documentation to Gem::TestCase to help you use it when you build extensions to RubyGems that would like to use the gem environment sandbox features Gem::TestCase provides.

I've also moved some other TestCases from test/ to lib/, but I doubt they will be useful outside of RubyGems itself:

GemInstallerTestCase is now Gem::InstallerTestCase in lib/rubygems/installer_test_case.rb

GemPackageTestCase (I think) is now Gem::Package::TarTestCase in lib/rubygems/package/tar_test_case.rb

From noreply at rubyforge.org  Thu Jan 20 22:37:28 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 20 Jan 2011 22:37:28 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28846 ]
	rubygems/userinteraction not included in key libraries
Message-ID: <20110121033728.AD46E18583C1@rubyforge.org>

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

Category: other
Group: v1.4.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Erik Hollensbe (erikh)
Assigned to: Nobody (None)
Summary: rubygems/userinteraction not included in key libraries

Initial Comment:
Gem::Installer and Gem::Format do not include this require, and therefore using them independently causes an explosion on 1.4.



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

>Comment By: Eric Hodel (drbrain)
Date: 2011-01-20 19:37

Message:
Fixed, thanks!

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

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

From drbrain at segment7.net  Fri Jan 21 19:13:02 2011
From: drbrain at segment7.net (Eric Hodel)
Date: Fri, 21 Jan 2011 16:13:02 -0800
Subject: [Rubygems-developers] Proposal: deprecation of 'cert' command
	(and gem security features)
Message-ID: <0586B50B-7AE2-4C77-898E-34F4A9E4E9B0@segment7.net>

On Jan 19, 2011, at 22:04, Hiroshi Nakamura wrote:

> I confirmed that rubygems 1.3.7 already does not have openssl
> dependency. rubygems/security.rb is loaded only when install/update,
> cert, and packaging. My claim was completely wrong. I'm very sorry for
> bothering you.

No problem, please bring any other concerns you have forward, it helps us make RubyGems better.

From noreply at rubyforge.org  Sat Jan 22 04:33:17 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sat, 22 Jan 2011 04:33:17 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28875 ] undefined method
	`path' for Gem:Module (NoMethodError)
Message-ID: <20110122093319.077B4167831F@rubyforge.org>

Bugs item #28875, was opened at 22/01/2011 10:33
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28875&group_id=126

Category: RubyGems installer (setup.rb)
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: guillaume Dorchies (gdorchie)
Assigned to: Nobody (None)
Summary: undefined method `path' for Gem:Module (NoMethodError)

Initial Comment:
I use rvm and bundler 1.0.7 and I try to update RubyGems

Updating RubyGems
Updating rubygems-update
Successfully installed rubygems-update-1.4.2
Updating RubyGems to 1.4.2
Installing RubyGems 1.4.2
/home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/source_index.rb:62:in `installed_spec_directories': undefined method `path' for Gem:Module (NoMethodError)
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/source_index.rb:52:in `from_installed_gems'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:914:in `source_index'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/gem_path_searcher.rb:83:in `init_gemspecs'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/gem_path_searcher.rb:13:in `initialize'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:873:in `new'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:873:in `searcher'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:495:in `find_files'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:1034:in `load_plugins'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/gem_runner.rb:84:in `<top (required)>'
	from <internal:lib/rubygems/custom_require>:29:in `require'
	from <internal:lib/rubygems/custom_require>:29:in `require'
	from setup.rb:25:in `<main>'


ENV

RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [i686-linux]
  - INSTALLATION DIRECTORY: /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag
  - RUBY EXECUTABLE: /home/gdo/.rvm/rubies/ruby-1.9.2-p136/bin/ruby
  - EXECUTABLE DIRECTORY: /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag
     - /home/gdo/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://rubygems.org/


best regards

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

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

From noreply at rubyforge.org  Sat Jan 22 04:33:18 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sat, 22 Jan 2011 04:33:18 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28877 ] undefined method
	`path' for Gem:Module (NoMethodError)
Message-ID: <20110122093318.A73A8185835A@rubyforge.org>

Bugs item #28877, was opened at 22/01/2011 10:33
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28877&group_id=126

Category: RubyGems installer (setup.rb)
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: guillaume Dorchies (gdorchie)
Assigned to: Nobody (None)
Summary: undefined method `path' for Gem:Module (NoMethodError)

Initial Comment:
I use rvm and bundler 1.0.7 and I try to update RubyGems

Updating RubyGems
Updating rubygems-update
Successfully installed rubygems-update-1.4.2
Updating RubyGems to 1.4.2
Installing RubyGems 1.4.2
/home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/source_index.rb:62:in `installed_spec_directories': undefined method `path' for Gem:Module (NoMethodError)
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/source_index.rb:52:in `from_installed_gems'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:914:in `source_index'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/gem_path_searcher.rb:83:in `init_gemspecs'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/gem_path_searcher.rb:13:in `initialize'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:873:in `new'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:873:in `searcher'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:495:in `find_files'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:1034:in `load_plugins'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/gem_runner.rb:84:in `<top (required)>'
	from <internal:lib/rubygems/custom_require>:29:in `require'
	from <internal:lib/rubygems/custom_require>:29:in `require'
	from setup.rb:25:in `<main>'


ENV

RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [i686-linux]
  - INSTALLATION DIRECTORY: /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag
  - RUBY EXECUTABLE: /home/gdo/.rvm/rubies/ruby-1.9.2-p136/bin/ruby
  - EXECUTABLE DIRECTORY: /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag
     - /home/gdo/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://rubygems.org/


best regards

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

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

From noreply at rubyforge.org  Sat Jan 22 04:33:18 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sat, 22 Jan 2011 04:33:18 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28876 ] undefined method
	`path' for Gem:Module (NoMethodError)
Message-ID: <20110122093319.3617D185836B@rubyforge.org>

Bugs item #28876, was opened at 22/01/2011 10:33
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28876&group_id=126

Category: RubyGems installer (setup.rb)
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: guillaume Dorchies (gdorchie)
Assigned to: Nobody (None)
Summary: undefined method `path' for Gem:Module (NoMethodError)

Initial Comment:
I use rvm and bundler 1.0.7 and I try to update RubyGems

Updating RubyGems
Updating rubygems-update
Successfully installed rubygems-update-1.4.2
Updating RubyGems to 1.4.2
Installing RubyGems 1.4.2
/home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/source_index.rb:62:in `installed_spec_directories': undefined method `path' for Gem:Module (NoMethodError)
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/source_index.rb:52:in `from_installed_gems'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:914:in `source_index'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/gem_path_searcher.rb:83:in `init_gemspecs'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/gem_path_searcher.rb:13:in `initialize'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:873:in `new'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:873:in `searcher'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:495:in `find_files'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:1034:in `load_plugins'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/gem_runner.rb:84:in `<top (required)>'
	from <internal:lib/rubygems/custom_require>:29:in `require'
	from <internal:lib/rubygems/custom_require>:29:in `require'
	from setup.rb:25:in `<main>'

best regards

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

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

From noreply at rubyforge.org  Sat Jan 22 08:12:42 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sat, 22 Jan 2011 08:12:42 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28876 ] undefined method
	`path' for Gem:Module (NoMethodError)
Message-ID: <20110122131242.D40AE1858375@rubyforge.org>

Bugs item #28876, was opened at 2011-01-22 06:33
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28876&group_id=126

Category: RubyGems installer (setup.rb)
Group: None
>Status: Closed
>Resolution: Rejected
Priority: 3
Submitted By: guillaume Dorchies (gdorchie)
Assigned to: Nobody (None)
Summary: undefined method `path' for Gem:Module (NoMethodError)

Initial Comment:
I use rvm and bundler 1.0.7 and I try to update RubyGems

Updating RubyGems
Updating rubygems-update
Successfully installed rubygems-update-1.4.2
Updating RubyGems to 1.4.2
Installing RubyGems 1.4.2
/home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/source_index.rb:62:in `installed_spec_directories': undefined method `path' for Gem:Module (NoMethodError)
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/source_index.rb:52:in `from_installed_gems'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:914:in `source_index'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/gem_path_searcher.rb:83:in `init_gemspecs'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/gem_path_searcher.rb:13:in `initialize'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:873:in `new'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:873:in `searcher'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:495:in `find_files'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:1034:in `load_plugins'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/gem_runner.rb:84:in `<top (required)>'
	from <internal:lib/rubygems/custom_require>:29:in `require'
	from <internal:lib/rubygems/custom_require>:29:in `require'
	from setup.rb:25:in `<main>'

best regards

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

>Comment By: Luis Lavena (luislavena)
Date: 2011-01-22 10:12

Message:
You can't update to RubyGems 1.4.2 with Ruby 1.9.2:

https://github.com/rubygems/rubygems/blob/v1.4.2/History.txt#L13
https://github.com/rubygems/rubygems/blob/master/UPGRADING.rdoc

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

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

From noreply at rubyforge.org  Sat Jan 22 08:13:40 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sat, 22 Jan 2011 08:13:40 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28875 ] undefined method
	`path' for Gem:Module (NoMethodError)
Message-ID: <20110122131340.81C0F1858375@rubyforge.org>

Bugs item #28875, was opened at 2011-01-22 06:33
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28875&group_id=126

Category: RubyGems installer (setup.rb)
Group: None
>Status: Closed
>Resolution: Rejected
Priority: 3
Submitted By: guillaume Dorchies (gdorchie)
Assigned to: Nobody (None)
Summary: undefined method `path' for Gem:Module (NoMethodError)

Initial Comment:
I use rvm and bundler 1.0.7 and I try to update RubyGems

Updating RubyGems
Updating rubygems-update
Successfully installed rubygems-update-1.4.2
Updating RubyGems to 1.4.2
Installing RubyGems 1.4.2
/home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/source_index.rb:62:in `installed_spec_directories': undefined method `path' for Gem:Module (NoMethodError)
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/source_index.rb:52:in `from_installed_gems'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:914:in `source_index'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/gem_path_searcher.rb:83:in `init_gemspecs'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/gem_path_searcher.rb:13:in `initialize'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:873:in `new'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:873:in `searcher'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:495:in `find_files'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:1034:in `load_plugins'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/gem_runner.rb:84:in `<top (required)>'
	from <internal:lib/rubygems/custom_require>:29:in `require'
	from <internal:lib/rubygems/custom_require>:29:in `require'
	from setup.rb:25:in `<main>'


ENV

RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [i686-linux]
  - INSTALLATION DIRECTORY: /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag
  - RUBY EXECUTABLE: /home/gdo/.rvm/rubies/ruby-1.9.2-p136/bin/ruby
  - EXECUTABLE DIRECTORY: /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag
     - /home/gdo/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://rubygems.org/


best regards

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

>Comment By: Luis Lavena (luislavena)
Date: 2011-01-22 10:13

Message:
Duplicate of

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

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

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

From noreply at rubyforge.org  Sat Jan 22 08:13:58 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sat, 22 Jan 2011 08:13:58 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28877 ] undefined method
	`path' for Gem:Module (NoMethodError)
Message-ID: <20110122131358.369201858375@rubyforge.org>

Bugs item #28877, was opened at 2011-01-22 06:33
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28877&group_id=126

Category: RubyGems installer (setup.rb)
Group: None
>Status: Closed
>Resolution: Rejected
Priority: 3
Submitted By: guillaume Dorchies (gdorchie)
Assigned to: Nobody (None)
Summary: undefined method `path' for Gem:Module (NoMethodError)

Initial Comment:
I use rvm and bundler 1.0.7 and I try to update RubyGems

Updating RubyGems
Updating rubygems-update
Successfully installed rubygems-update-1.4.2
Updating RubyGems to 1.4.2
Installing RubyGems 1.4.2
/home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/source_index.rb:62:in `installed_spec_directories': undefined method `path' for Gem:Module (NoMethodError)
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/source_index.rb:52:in `from_installed_gems'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:914:in `source_index'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/gem_path_searcher.rb:83:in `init_gemspecs'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/gem_path_searcher.rb:13:in `initialize'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:873:in `new'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:873:in `searcher'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:495:in `find_files'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems.rb:1034:in `load_plugins'
	from /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/gems/rubygems-update-1.4.2/lib/rubygems/gem_runner.rb:84:in `<top (required)>'
	from <internal:lib/rubygems/custom_require>:29:in `require'
	from <internal:lib/rubygems/custom_require>:29:in `require'
	from setup.rb:25:in `<main>'


ENV

RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [i686-linux]
  - INSTALLATION DIRECTORY: /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag
  - RUBY EXECUTABLE: /home/gdo/.rvm/rubies/ruby-1.9.2-p136/bin/ruby
  - EXECUTABLE DIRECTORY: /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /home/gdo/.rvm/gems/ruby-1.9.2-p136 at manag
     - /home/gdo/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://rubygems.org/


best regards

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

>Comment By: Luis Lavena (luislavena)
Date: 2011-01-22 10:13

Message:
Duplicate of http://rubyforge.org/tracker/?func=detail&atid=575&aid=28876&group_id=126

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

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

From tim at gfxmonk.net  Mon Jan 24 05:01:31 2011
From: tim at gfxmonk.net (Tim Cuthbertson)
Date: Mon, 24 Jan 2011 21:01:31 +1100
Subject: [Rubygems-developers] mime-type of a .gem file
In-Reply-To: <AANLkTinO-TkOCb0XGv34gS7uY1i7uk_EXNp=AxGSEMLS@mail.gmail.com>
References: <AANLkTinO-TkOCb0XGv34gS7uY1i7uk_EXNp=AxGSEMLS@mail.gmail.com>
Message-ID: <AANLkTim7Dz5HV839g5ZJ=oqxJwk2nYKCdGxSsLaYafF9@mail.gmail.com>

Hi all,

I'm doing a little bit of work on zero install (0install.net), which
is a dependency manager that can speak a bunch of archive formats
(.tgz, .deb, .rpm, etc). I'd like to add .gem to that list.
Internally, it distinguishes formats by their mime type. So you have
"application/x-bzip-compressed-tar" for a .tar.bz, etc...

So I was wondering if there is an official or agreed-upon mime-type
for .gem files? I see rubygems serves them up as
application/octet-stream, but that isn't really enough to tell what it
is if you don't have the .gem extension.

If not, does anyone have any suggestions? I've no idea how these
things are agreed upon, but how about I throw "application/x-rubygem"
out there for starters...

While I'm at it, is there any spec for the format of a .gem file? From
looking at examples I've come across, I'm pretty sure I can get away
with `tar x` on the gem and then `tar xz` on the data.tar.gz contained
inside. Can anyone see a potential problem with that?

Cheers,
 - Tim Cuthbertson

From headius at headius.com  Mon Jan 24 16:40:29 2011
From: headius at headius.com (Charles Oliver Nutter)
Date: Mon, 24 Jan 2011 15:40:29 -0600
Subject: [Rubygems-developers] mime-type of a .gem file
In-Reply-To: <AANLkTim7Dz5HV839g5ZJ=oqxJwk2nYKCdGxSsLaYafF9@mail.gmail.com>
References: <AANLkTinO-TkOCb0XGv34gS7uY1i7uk_EXNp=AxGSEMLS@mail.gmail.com>
	<AANLkTim7Dz5HV839g5ZJ=oqxJwk2nYKCdGxSsLaYafF9@mail.gmail.com>
Message-ID: <AANLkTimi6w-40wiXS5=dD+0g-f3B1Lns=qp6UUv6phJq@mail.gmail.com>

On Mon, Jan 24, 2011 at 4:01 AM, Tim Cuthbertson <tim at gfxmonk.net> wrote:
> I'm doing a little bit of work on zero install (0install.net), which
> is a dependency manager that can speak a bunch of archive formats
> (.tgz, .deb, .rpm, etc). I'd like to add .gem to that list.
> Internally, it distinguishes formats by their mime type. So you have
> "application/x-bzip-compressed-tar" for a .tar.bz, etc...
>
> So I was wondering if there is an official or agreed-upon mime-type
> for .gem files? I see rubygems serves them up as
> application/octet-stream, but that isn't really enough to tell what it
> is if you don't have the .gem extension.
>
> If not, does anyone have any suggestions? I've no idea how these
> things are agreed upon, but how about I throw "application/x-rubygem"
> out there for starters...
>
> While I'm at it, is there any spec for the format of a .gem file? From
> looking at examples I've come across, I'm pretty sure I can get away
> with `tar x` on the gem and then `tar xz` on the data.tar.gz contained
> inside. Can anyone see a potential problem with that?

Well the gem format is a tar of a tar-gz-ball and some gzip compressed
stuff. Rather than adding a new "x" mime type, what's wrong with just
tar format?

Not sure if that layering is formally specified anywhere, but that's
what it is and has been forever.

- Charlie

From luislavena at gmail.com  Mon Jan 24 17:20:22 2011
From: luislavena at gmail.com (Luis Lavena)
Date: Mon, 24 Jan 2011 19:20:22 -0300
Subject: [Rubygems-developers] mime-type of a .gem file
In-Reply-To: <AANLkTimi6w-40wiXS5=dD+0g-f3B1Lns=qp6UUv6phJq@mail.gmail.com>
References: <AANLkTinO-TkOCb0XGv34gS7uY1i7uk_EXNp=AxGSEMLS@mail.gmail.com>
	<AANLkTim7Dz5HV839g5ZJ=oqxJwk2nYKCdGxSsLaYafF9@mail.gmail.com>
	<AANLkTimi6w-40wiXS5=dD+0g-f3B1Lns=qp6UUv6phJq@mail.gmail.com>
Message-ID: <AANLkTinkKtzJw3L=w2NQp-5X30oG86MPk-7LB_JNVZTo@mail.gmail.com>

On Mon, Jan 24, 2011 at 6:40 PM, Charles Oliver Nutter
<headius at headius.com> wrote:
>
> Well the gem format is a tar of a tar-gz-ball and some gzip compressed
> stuff. Rather than adding a new "x" mime type, what's wrong with just
> tar format?
>
> Not sure if that layering is formally specified anywhere, but that's
> what it is and has been forever.
>

>tar tf rake-compiler-0.7.5.gem
data.tar.gz
metadata.gz

So sees tar recognizes .gem as tar files :-)

And file also:

>file rake-compiler-0.7.5.gem
rake-compiler-0.7.5.gem: POSIX tar archive

-- 
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 headius at headius.com  Mon Jan 24 17:41:09 2011
From: headius at headius.com (Charles Oliver Nutter)
Date: Mon, 24 Jan 2011 16:41:09 -0600
Subject: [Rubygems-developers] mime-type of a .gem file
In-Reply-To: <AANLkTinkKtzJw3L=w2NQp-5X30oG86MPk-7LB_JNVZTo@mail.gmail.com>
References: <AANLkTinO-TkOCb0XGv34gS7uY1i7uk_EXNp=AxGSEMLS@mail.gmail.com>
	<AANLkTim7Dz5HV839g5ZJ=oqxJwk2nYKCdGxSsLaYafF9@mail.gmail.com>
	<AANLkTimi6w-40wiXS5=dD+0g-f3B1Lns=qp6UUv6phJq@mail.gmail.com>
	<AANLkTinkKtzJw3L=w2NQp-5X30oG86MPk-7LB_JNVZTo@mail.gmail.com>
Message-ID: <AANLkTin5dYG2pWxodfEQUzneDH3QZTdNatJmgh8=5hxN@mail.gmail.com>

On Mon, Jan 24, 2011 at 4:20 PM, Luis Lavena <luislavena at gmail.com> wrote:
>>tar tf rake-compiler-0.7.5.gem
> data.tar.gz
> metadata.gz
>
> So sees tar recognizes .gem as tar files :-)
>
> And file also:
>
>>file rake-compiler-0.7.5.gem
> rake-compiler-0.7.5.gem: POSIX tar archive

Yes, that's what I meant. A gem is a tar containing a tarball and a
gzipped file. So I feel like just using the mime type for "tar files"
would be fine for RubyGems.

I suppose a x-rubygems mime type would convey more information, but to whom?

- Charlie

From drbrain at segment7.net  Mon Jan 24 18:33:58 2011
From: drbrain at segment7.net (Eric Hodel)
Date: Mon, 24 Jan 2011 15:33:58 -0800
Subject: [Rubygems-developers] mime-type of a .gem file
In-Reply-To: <AANLkTim7Dz5HV839g5ZJ=oqxJwk2nYKCdGxSsLaYafF9@mail.gmail.com>
References: <AANLkTinO-TkOCb0XGv34gS7uY1i7uk_EXNp=AxGSEMLS@mail.gmail.com>
	<AANLkTim7Dz5HV839g5ZJ=oqxJwk2nYKCdGxSsLaYafF9@mail.gmail.com>
Message-ID: <B30A47AC-6D42-40A5-9E49-2216DA50F3AF@segment7.net>

On Jan 24, 2011, at 02:01, Tim Cuthbertson wrote:

> Hi all,
> 
> I'm doing a little bit of work on zero install (0install.net), which
> is a dependency manager that can speak a bunch of archive formats
> (.tgz, .deb, .rpm, etc). I'd like to add .gem to that list.
> Internally, it distinguishes formats by their mime type. So you have
> "application/x-bzip-compressed-tar" for a .tar.bz, etc...
> 
> So I was wondering if there is an official or agreed-upon mime-type
> for .gem files? I see rubygems serves them up as
> application/octet-stream, but that isn't really enough to tell what it
> is if you don't have the .gem extension.
> 
> If not, does anyone have any suggestions? I've no idea how these
> things are agreed upon, but how about I throw "application/x-rubygem"
> out there for starters?

I don't see a problem with this.  Nick is in charge of rubygems.org so he'd need to make the changes to switch mime types.

> While I'm at it, is there any spec for the format of a .gem file? From
> looking at examples I've come across, I'm pretty sure I can get away
> with `tar x` on the gem and then `tar xz` on the data.tar.gz contained
> inside. Can anyone see a potential problem with that?

No problem.

If there's a .sig file you may wish to verify it:

$ tar tf pkg/rubygems-update-1.5.0.gem 
data.tar.gz
metadata.gz
data.tar.gz.sig
metadata.gz.sig

See Gem::Security for details.

From drbrain at segment7.net  Mon Jan 24 19:04:08 2011
From: drbrain at segment7.net (Eric Hodel)
Date: Mon, 24 Jan 2011 16:04:08 -0800
Subject: [Rubygems-developers] mime-type of a .gem file
In-Reply-To: <AANLkTim7Dz5HV839g5ZJ=oqxJwk2nYKCdGxSsLaYafF9@mail.gmail.com>
References: <AANLkTinO-TkOCb0XGv34gS7uY1i7uk_EXNp=AxGSEMLS@mail.gmail.com>
	<AANLkTim7Dz5HV839g5ZJ=oqxJwk2nYKCdGxSsLaYafF9@mail.gmail.com>
Message-ID: <B5E13BFD-9DC1-4464-AE06-293045D1DE98@segment7.net>

On Jan 24, 2011, at 02:01, Tim Cuthbertson wrote:

> If not, does anyone have any suggestions? I've no idea how these
> things are agreed upon, but how about I throw "application/x-rubygem"
> out there for starters?

There's two files to deal with, .gem files and .gemspec files which are usually deflated.  How about:

application/x-ruby-gem
application/x-ruby-gemspec-deflate


From tim at gfxmonk.net  Mon Jan 24 20:04:12 2011
From: tim at gfxmonk.net (Tim Cuthbertson)
Date: Tue, 25 Jan 2011 12:04:12 +1100
Subject: [Rubygems-developers] mime-type of a .gem file
In-Reply-To: <AANLkTimi6w-40wiXS5=dD+0g-f3B1Lns=qp6UUv6phJq@mail.gmail.com>
References: <AANLkTinO-TkOCb0XGv34gS7uY1i7uk_EXNp=AxGSEMLS@mail.gmail.com>
	<AANLkTim7Dz5HV839g5ZJ=oqxJwk2nYKCdGxSsLaYafF9@mail.gmail.com>
	<AANLkTimi6w-40wiXS5=dD+0g-f3B1Lns=qp6UUv6phJq@mail.gmail.com>
Message-ID: <AANLkTikd+_nJ62ws3QRA-oocd9jhveU7dPgd+PmQV3NU@mail.gmail.com>

On Tue, Jan 25, 2011 at 8:40 AM, Charles Oliver Nutter
<headius at headius.com> wrote:
> On Mon, Jan 24, 2011 at 4:01 AM, Tim Cuthbertson <tim at gfxmonk.net> wrote:
>> I'm doing a little bit of work on zero install (0install.net), which
>> is a dependency manager that can speak a bunch of archive formats
>> (.tgz, .deb, .rpm, etc). I'd like to add .gem to that list.
>> Internally, it distinguishes formats by their mime type. So you have
>> "application/x-bzip-compressed-tar" for a .tar.bz, etc...
>>
>> So I was wondering if there is an official or agreed-upon mime-type
>> for .gem files? I see rubygems serves them up as
>> application/octet-stream, but that isn't really enough to tell what it
>> is if you don't have the .gem extension.
>>
>> If not, does anyone have any suggestions? I've no idea how these
>> things are agreed upon, but how about I throw "application/x-rubygem"
>> out there for starters...
>>
>> While I'm at it, is there any spec for the format of a .gem file? From
>> looking at examples I've come across, I'm pretty sure I can get away
>> with `tar x` on the gem and then `tar xz` on the data.tar.gz contained
>> inside. Can anyone see a potential problem with that?
>
> Well the gem format is a tar of a tar-gz-ball and some gzip compressed
> stuff. Rather than adding a new "x" mime type, what's wrong with just
> tar format?

Because to actually get at the payload of a .gem (i.e the .rb files
and associated directories that ruby will actually read), you need to
untar the top level .gem file and then untar the second-level gzipped
data tar file. For most purposes, the "contents" of a gem are these
.rb files, not the two data.tar.gz and metadata.gz files. So it's not
the same as just a .tar, because additional processing needs to be
done if you want the actual files that make up the gem.

Cheers,
 - Tim.

From tim at gfxmonk.net  Mon Jan 24 20:04:27 2011
From: tim at gfxmonk.net (Tim Cuthbertson)
Date: Tue, 25 Jan 2011 12:04:27 +1100
Subject: [Rubygems-developers] mime-type of a .gem file
In-Reply-To: <AANLkTin5dYG2pWxodfEQUzneDH3QZTdNatJmgh8=5hxN@mail.gmail.com>
References: <AANLkTinO-TkOCb0XGv34gS7uY1i7uk_EXNp=AxGSEMLS@mail.gmail.com>
	<AANLkTim7Dz5HV839g5ZJ=oqxJwk2nYKCdGxSsLaYafF9@mail.gmail.com>
	<AANLkTimi6w-40wiXS5=dD+0g-f3B1Lns=qp6UUv6phJq@mail.gmail.com>
	<AANLkTinkKtzJw3L=w2NQp-5X30oG86MPk-7LB_JNVZTo@mail.gmail.com>
	<AANLkTin5dYG2pWxodfEQUzneDH3QZTdNatJmgh8=5hxN@mail.gmail.com>
Message-ID: <AANLkTimhGQvxejsqCuRQYKim9nGxpqMCzz5L9p_fgcn-@mail.gmail.com>

On Tue, Jan 25, 2011 at 9:41 AM, Charles Oliver Nutter
<headius at headius.com> wrote:
> On Mon, Jan 24, 2011 at 4:20 PM, Luis Lavena <luislavena at gmail.com> wrote:
>>>tar tf rake-compiler-0.7.5.gem
>> data.tar.gz
>> metadata.gz
>>
>> So sees tar recognizes .gem as tar files :-)
>>
>> And file also:
>>
>>>file rake-compiler-0.7.5.gem
>> rake-compiler-0.7.5.gem: POSIX tar archive
>
> Yes, that's what I meant. A gem is a tar containing a tarball and a
> gzipped file. So I feel like just using the mime type for "tar files"
> would be fine for RubyGems.
>
> I suppose a x-rubygems mime type would convey more information, but to whom?

To programs who know how to handle a bunch of archive formats,
including both "tar" and "gem". If you treat a gem file like a tar
file, you don't get terribly useful files out of it.

From tim at gfxmonk.net  Mon Jan 24 20:05:41 2011
From: tim at gfxmonk.net (Tim Cuthbertson)
Date: Tue, 25 Jan 2011 12:05:41 +1100
Subject: [Rubygems-developers] mime-type of a .gem file
In-Reply-To: <B5E13BFD-9DC1-4464-AE06-293045D1DE98@segment7.net>
References: <AANLkTinO-TkOCb0XGv34gS7uY1i7uk_EXNp=AxGSEMLS@mail.gmail.com>
	<AANLkTim7Dz5HV839g5ZJ=oqxJwk2nYKCdGxSsLaYafF9@mail.gmail.com>
	<B5E13BFD-9DC1-4464-AE06-293045D1DE98@segment7.net>
Message-ID: <AANLkTi=kzTxD45vJWgBg71n61vz1arQZkWp3O0L46JsD@mail.gmail.com>

On Tue, Jan 25, 2011 at 11:04 AM, Eric Hodel <drbrain at segment7.net> wrote:
> On Jan 24, 2011, at 02:01, Tim Cuthbertson wrote:
>
>> If not, does anyone have any suggestions? I've no idea how these
>> things are agreed upon, but how about I throw "application/x-rubygem"
>> out there for starters?
>
> There's two files to deal with, .gem files and .gemspec files which are usually deflated. ?How about:
>
> application/x-ruby-gem
> application/x-ruby-gemspec-deflate

If I understand correctly, a gemspec is the contents of metadata.gz in
the .gem tar-file.
Do gemspecs get distributed outside of a .gem file? If not, they
probably don't need to have their own mime-type. But if they do, then
yes that sounds like a good idea to have both.

Cheers,
 - Tim.

From tim at gfxmonk.net  Mon Jan 24 20:11:01 2011
From: tim at gfxmonk.net (Tim Cuthbertson)
Date: Tue, 25 Jan 2011 12:11:01 +1100
Subject: [Rubygems-developers] mime-type of a .gem file
In-Reply-To: <B30A47AC-6D42-40A5-9E49-2216DA50F3AF@segment7.net>
References: <AANLkTinO-TkOCb0XGv34gS7uY1i7uk_EXNp=AxGSEMLS@mail.gmail.com>
	<AANLkTim7Dz5HV839g5ZJ=oqxJwk2nYKCdGxSsLaYafF9@mail.gmail.com>
	<B30A47AC-6D42-40A5-9E49-2216DA50F3AF@segment7.net>
Message-ID: <AANLkTimi--gBxGFYGP0MuYimtP6MmU8ZZq+3bV0Kjiyy@mail.gmail.com>

On Tue, Jan 25, 2011 at 10:33 AM, Eric Hodel <drbrain at segment7.net> wrote:
> On Jan 24, 2011, at 02:01, Tim Cuthbertson wrote:
>
>> Hi all,
>>
>> I'm doing a little bit of work on zero install (0install.net), which
>> is a dependency manager that can speak a bunch of archive formats
>> (.tgz, .deb, .rpm, etc). I'd like to add .gem to that list.
>> Internally, it distinguishes formats by their mime type. So you have
>> "application/x-bzip-compressed-tar" for a .tar.bz, etc...
>>
>> So I was wondering if there is an official or agreed-upon mime-type
>> for .gem files? I see rubygems serves them up as
>> application/octet-stream, but that isn't really enough to tell what it
>> is if you don't have the .gem extension.
>>
>> If not, does anyone have any suggestions? I've no idea how these
>> things are agreed upon, but how about I throw "application/x-rubygem"
>> out there for starters?
>
> I don't see a problem with this. ?Nick is in charge of rubygems.org so he'd need to make the changes to switch mime types.
>
>> While I'm at it, is there any spec for the format of a .gem file? From
>> looking at examples I've come across, I'm pretty sure I can get away
>> with `tar x` on the gem and then `tar xz` on the data.tar.gz contained
>> inside. Can anyone see a potential problem with that?
>
> No problem.
>
> If there's a .sig file you may wish to verify it:
>
> $ tar tf pkg/rubygems-update-1.5.0.gem
> data.tar.gz
> metadata.gz
> data.tar.gz.sig
> metadata.gz.sig
>
> See Gem::Security for details.

For zero install, this shouldn't be necessary as the published feeds
already uses PGP and archive content digests to protect against both
tampering and corruption, but thanks for the tip :)

Cheers,
 - Tim.

From drbrain at segment7.net  Tue Jan 25 02:15:53 2011
From: drbrain at segment7.net (Eric Hodel)
Date: Mon, 24 Jan 2011 23:15:53 -0800
Subject: [Rubygems-developers] mime-type of a .gem file
In-Reply-To: <AANLkTi=kzTxD45vJWgBg71n61vz1arQZkWp3O0L46JsD@mail.gmail.com>
References: <AANLkTinO-TkOCb0XGv34gS7uY1i7uk_EXNp=AxGSEMLS@mail.gmail.com>
	<AANLkTim7Dz5HV839g5ZJ=oqxJwk2nYKCdGxSsLaYafF9@mail.gmail.com>
	<B5E13BFD-9DC1-4464-AE06-293045D1DE98@segment7.net>
	<AANLkTi=kzTxD45vJWgBg71n61vz1arQZkWp3O0L46JsD@mail.gmail.com>
Message-ID: <85763AF0-895D-4088-84A3-4DEB80A5AC05@segment7.net>

On Jan 24, 2011, at 17:05, Tim Cuthbertson wrote:
> On Tue, Jan 25, 2011 at 11:04 AM, Eric Hodel <drbrain at segment7.net> wrote:
>> On Jan 24, 2011, at 02:01, Tim Cuthbertson wrote:
>> 
>>> If not, does anyone have any suggestions? I've no idea how these
>>> things are agreed upon, but how about I throw "application/x-rubygem"
>>> out there for starters?
>> 
>> There's two files to deal with, .gem files and .gemspec files which are usually deflated.  How about:
>> 
>> application/x-ruby-gem
>> application/x-ruby-gemspec-deflate
> 
> If I understand correctly, a gemspec is the contents of metadata.gz in
> the .gem tar-file.
> Do gemspecs get distributed outside of a .gem file?

Yes.

From noreply at rubyforge.org  Tue Jan 25 10:49:27 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue, 25 Jan 2011 10:49:27 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-27324 ] string contains null
	byte
Message-ID: <20110125154927.D74291678323@rubyforge.org>

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

Category: `gem install` command
Group: v1.3.x
Status: Closed
Resolution: None
Priority: 3
Submitted By: Thomas Preymesser (thopre)
Assigned to: Nobody (None)
Summary: string contains null byte 

Initial Comment:
Hello,

i get this error when i try to install rails. 
Many other gems can be installed without problems.


$ sudo gem install  rails --backtrace
ERROR:  While executing gem ... (ArgumentError)
    string contains null byte
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_reader/entry.rb:66:in `join'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_reader/entry.rb:66:in `full_name'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_input.rb:32:in `block in initialize'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_reader.rb:63:in `block in each'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_reader.rb:54:in `loop'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_reader.rb:54:in `each'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_input.rb:31:in `initialize'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_input.rb:16:in `new'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_input.rb:16:in `open'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package.rb:56:in `open'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/format.rb:67:in `from_io'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/format.rb:51:in `block in from_file_by_path'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/format.rb:50:in `open'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/format.rb:50:in `from_file_by_path'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/installer.rb:119:in `initialize'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/dependency_installer.rb:239:in `new'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/dependency_installer.rb:239:in `block in install'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/dependency_installer.rb:222:in `each'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/dependency_installer.rb:222:in `install'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/commands/install_command.rb:118:in `block in execute'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/commands/install_command.rb:115:in `each'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/commands/install_command.rb:115:in `execute'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command.rb:257:in `invoke'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command_manager.rb:132:in `process_args'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command_manager.rb:102:in `run'
	/usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/gem_runner.rb:58:in `run'
	/usr/local/bin/gem:21:in `<main>'

$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.5
  - RUBY VERSION: 1.9.2 (2009-10-21 patchlevel -1) [i686-linux]
  - INSTALLATION DIRECTORY: /usr/local/lib/ruby/gems/1.9.1
  - RUBYGEMS PREFIX: /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5
  - RUBY EXECUTABLE: /usr/local/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/local/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /usr/local/lib/ruby/gems/1.9.1
     - /home/tp/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://gems.rubyforge.org/"]
     - "rdoc" => "--inline-source --line-numbers --format=html --template=hanna"
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/


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

Comment By: Jan-Jan vdVyver (iibtrih)
Date: 2011-01-25 17:49

Message:
Thank you. Your suggestion solved my problem

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

Comment By: Eric Hodel (drbrain)
Date: 2011-01-15 03:04

Message:
You have corrupt downloads.

This is either an issue with your network or your filesystem.

Try removing the cache/ directory from your gem paths.

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

Comment By: Jan-Jan vdVyver (iibtrih)
Date: 2011-01-14 21:28

Message:
I have a similar error for both installing bundler and rails:

$ gem install bundler --backtrace
ERROR:  While executing gem ... (Zlib::DataError)
    invalid block type
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:215:in `finish'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:215:in `ensure in zipped_stream'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:215:in `zipped_stream'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:122:in `block in each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_reader.rb:64:in `block in each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_reader.rb:55:in `loop'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_reader.rb:55:in `each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:120:in `each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:67:in `block in from_io'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:19:in `open'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package.rb:58:in `open'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:63:in `from_io'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:51:in `block in from_file_by_path'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:50:in `open'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:50:in `from_file_by_path'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/installer.rb:118:in `initialize'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/dependency_installer.rb:264:in `new'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/dependency_installer.rb:264:in `block in install'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/dependency_installer.rb:247:in `each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/dependency_installer.rb:247:in `install'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/commands/install_command.rb:119:in `block in execute'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/commands/install_command.rb:116:in `each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/commands/install_command.rb:116:in `execute'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/command.rb:270:in `invoke'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/command_manager.rb:134:in `process_args'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/command_manager.rb:104:in `run'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/gem_runner.rb:58:in `run'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/bin/gem:25:in `<main>'



$ gem install rails --backtrace
ERROR:  While executing gem ... (ArgumentError)
    string contains null byte
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_reader/entry.rb:66:in `join'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_reader/entry.rb:66:in `full_name'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:33:in `block in initialize'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_reader.rb:64:in `block in each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_reader.rb:55:in `loop'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_reader.rb:55:in `each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:32:in `initialize'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:17:in `new'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package/tar_input.rb:17:in `open'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/package.rb:58:in `open'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:63:in `from_io'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:51:in `block in from_file_by_path'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:50:in `open'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/format.rb:50:in `from_file_by_path'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/installer.rb:118:in `initialize'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/dependency_installer.rb:264:in `new'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/dependency_installer.rb:264:in `block in install'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/dependency_installer.rb:247:in `each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/dependency_installer.rb:247:in `install'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/commands/install_command.rb:119:in `block in execute'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/commands/install_command.rb:116:in `each'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/commands/install_command.rb:116:in `execute'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/command.rb:270:in `invoke'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/command_manager.rb:134:in `process_args'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/command_manager.rb:104:in `run'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems/gem_runner.rb:58:in `run'
        /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/bin/gem:25:in `<main>'



$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [x86_64-darwin10.6.0]
  - INSTALLATION DIRECTORY: /Users/iibtrih/.rvm/gems/ruby-head
  - RUBY EXECUTABLE: /Users/iibtrih/.rvm/rubies/ruby-1.9.2-p136/bin/ruby
  - EXECUTABLE DIRECTORY: /Users/iibtrih/.rvm/gems/ruby-head/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-darwin-10
  - GEM PATHS:
     - /Users/iibtrih/.rvm/gems/ruby-head
     - /Users/iibtrih/.rvm/gems/ruby-head at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://rubygems.org/

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

Comment By: Ryan Davis (zenspider)
Date: 2010-11-13 00:46

Message:
This ticket has been deemed stale and we're closing it in order to catch up 
with our ticket list. If you think it is still valid, please reopen.

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

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

From jon.forums at gmail.com  Tue Jan 25 12:09:43 2011
From: jon.forums at gmail.com (Jon)
Date: Tue, 25 Jan 2011 12:09:43 -0500
Subject: [Rubygems-developers] operating_system.rb behavior on ruby-core
	trunk@30653
Message-ID: <20110125120943.8ce19e25.jon.forums@gmail.com>

Knowing you're in the middle of readying 1.5.0, I'm want to see whether this is a real RubyGems issue or something else.

I use an operating_system.rb and a custom devkit.rb to enhance how "gem install my_native_gem" and "ruby -r devkit extconf.rb" behaves when building for Windows using RubyInstaller. As of ruby-core trunk at 30653 the operating_system.rb functionality appears to have stopped working. Things stil work on "ruby 1.9.2p160 (2011-01-16 revision 30579) [i386-mingw32]"

I suspect this isn't a RubyGems issue, but an expected ruby-core trunk stabilization issue.  Is the following "failure" (operating_system.rb's pre_install hook not working so build tools not put on PATH) expected at this point in the RubyGems refactoring?


=== FAILING CASE ===

# file: C:\ruby19trunk\lib\ruby\1.9.1\rubygems\defaults\operating_system.rb
#
# :DK-BEG: override 'gem install' to enable RubyInstaller DevKit usage
Gem.pre_install do |gem_installer|
  unless gem_installer.spec.extensions.empty?
    unless ENV['PATH'].include?('C:\\DevKit\\mingw\\bin') then
      Gem.ui.say 'Temporarily enhancing PATH to include DevKit...' if Gem.configuration.verbose
      ENV['PATH'] = 'C:\\DevKit\\bin;C:\\DevKit\\mingw\\bin;' + ENV['PATH']
    end
    ENV['RI_DEVKIT'] = 'C:\\DevKit'
    ENV['CC'] = 'gcc'
    ENV['CPP'] = 'cpp'
    ENV['CXX'] = 'g++'
  end
end
# :DK-END:


C:\Users\Jon\Documents>gem install rdiscount
Building native extensions.  This could take a while...
ERROR:  Error installing rdiscount:
        ERROR: Failed to build gem native extension.

C:/ruby19trunk/bin/ruby.exe extconf.rb
checking for random()... C:/ruby19trunk/lib/ruby/1.9.1/mkmf.rb:381:in `try_do': The compiler failed to generate an executable file. (RuntimeError)
You have to install development tools first.
        from C:/ruby19trunk/lib/ruby/1.9.1/mkmf.rb:460:in `try_link0'
        from C:/ruby19trunk/lib/ruby/1.9.1/mkmf.rb:475:in `try_link'
        from C:/ruby19trunk/lib/ruby/1.9.1/mkmf.rb:618:in `try_func'
        from C:/ruby19trunk/lib/ruby/1.9.1/mkmf.rb:893:in `block in have_func'
        from C:/ruby19trunk/lib/ruby/1.9.1/mkmf.rb:789:in `block in checking_for'
        from C:/ruby19trunk/lib/ruby/1.9.1/mkmf.rb:284:in `block (2 levels) in postpone'
        from C:/ruby19trunk/lib/ruby/1.9.1/mkmf.rb:254:in `open'
        from C:/ruby19trunk/lib/ruby/1.9.1/mkmf.rb:284:in `block in postpone'
        from C:/ruby19trunk/lib/ruby/1.9.1/mkmf.rb:254:in `open'
        from C:/ruby19trunk/lib/ruby/1.9.1/mkmf.rb:280:in `postpone'
        from C:/ruby19trunk/lib/ruby/1.9.1/mkmf.rb:788:in `checking_for'
        from C:/ruby19trunk/lib/ruby/1.9.1/mkmf.rb:892:in `have_func'
        from extconf.rb:5:in `<main>'


Gem files will remain installed in C:/ruby19trunk/lib/ruby/gems/1.9.1/gems/rdiscount-1.6.8 for inspection.
Results logged to C:/ruby19trunk/lib/ruby/gems/1.9.1/gems/rdiscount-1.6.8/ext/gem_make.out



=== WORKING CASE ===

While I'm tracking down other rdiscount 1.6.8 functionality issues, with the following devkit.rb library I can manually get this build to work:

# file: C:\ruby19trunk\lib\ruby\site_ruby\devkit.rb
#
# enable RubyInstaller DevKit usage as a vendorable helper library
unless ENV['PATH'].include?('C:\\DevKit\\mingw\\bin') then
  puts 'Temporarily enhancing PATH to include DevKit...'
  ENV['PATH'] = 'C:\\DevKit\\bin;C:\\DevKit\\mingw\\bin;' + ENV['PATH']
end
ENV['RI_DEVKIT'] = 'C:\\DevKit'
ENV['CC'] = 'gcc'
ENV['CPP'] = 'cpp'
ENV['CXX'] = 'g++'

C:\ruby192\lib\ruby\gems\1.9.1\gems\rdiscount-1.6.8\ext>ruby -r devkit extconf.rb
checking for random()... no
checking for srandom()... no
checking for rand()... yes
checking for srand()... yes
creating Makefile

C:\ruby192\lib\ruby\gems\1.9.1\gems\rdiscount-1.6.8\ext>\DevKit\devkitvars.bat
Adding the DevKit to PATH...

C:\ruby192\lib\ruby\gems\1.9.1\gems\rdiscount-1.6.8\ext>make && make install
...SNIP BUNCH-O-WARNINGS...
linking shared-object rdiscount.so
/usr/bin/install -c -m 0755 rdiscount.so C:/ruby19trunk/lib/ruby/site_ruby/1.9.1/i386-msvcrt
installing default rdiscount libraries


Jon

---
blog: http://jonforums.github.com/
twitter: @jonforums

From luislavena at gmail.com  Fri Jan 28 07:43:30 2011
From: luislavena at gmail.com (Luis Lavena)
Date: Fri, 28 Jan 2011 09:43:30 -0300
Subject: [Rubygems-developers] Inability to use RubyGems against trunk
Message-ID: <AANLkTinnkT6WWAq33+83rTmfQG2_aoUdyhDEo-6UX16y@mail.gmail.com>

Hey guys,

We are aiming at 1.5.0 release next week, and I'm having my doubts.

The following are the steps I conducted on a fresh 1.9.3 (trunk) compilation:

>ruby -v
ruby 1.9.3dev (2011-01-28 trunk 30684) [i386-mingw32]

RubyGems checked out at f82a8d1

>ruby setup.rb --no-ri --no-rdoc

RubyGems 1.5.0 installed

(1.4.2 release notes)

RubyGems installed the following executables:
        C:/Users/Luis/Tools/Ruby/ruby-1.9.3-dev-i386-mingw32/bin/gem

Then:

>gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.0
  - RUBY VERSION: 1.9.3 (2011-01-28 patchlevel -1) [i386-mingw32]
  - INSTALLATION DIRECTORY: C:/Users/Luis/.gem/ruby/x86-mingw32/1.9.1
  - RUBY EXECUTABLE:
C:/Users/Luis/Tools/Ruby/ruby-1.9.3-dev-i386-mingw32/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/Users/Luis/.gem/ruby/x86-mingw32/1.9.1/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mingw32
  - GEM PATHS:
     - C:/Users/Luis/.gem/ruby/x86-mingw32/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://rubygems.org"]
     - "install" => "--no-ri --no-rdoc --env-shebang"
     - "update" => "--no-ri --no-rdoc --env-shebang"
  - REMOTE SOURCES:
     - http://rubygems.org


>gem list sqlite3

*** LOCAL GEMS ***

sqlite3 (1.3.3 x86-mingw32)
sqlite3-ruby (1.3.1 x86-mingw32)

C:\Users\Luis\Projects\oss\rubygems>irb
irb(main):001:0> require 'sqlite3'
LoadError: cannot load such file -- sqlite3
        from (irb):1:in `require'
        from (irb):1
        from C:/Users/Luis/Tools/Ruby/ruby-1.9.3-dev-i386-mingw32/bin/irb:12:in
`<main>'
irb(main):002:0> require 'rubygems'
=> false
irb(main):003:0> require 'sqlite3'
LoadError: cannot load such file -- sqlite3
        from (irb):3:in `require'
        from (irb):3
        from C:/Users/Luis/Tools/Ruby/ruby-1.9.3-dev-i386-mingw32/bin/irb:12:in
`<main>'
irb(main):004:0> exit

C:\Users\Luis\Projects\oss\rubygems>ruby --disable-gems -S irb
irb(main):001:0> require 'rubygems'
=> true
irb(main):002:0> require 'sqlite3'
LoadError: cannot load such file -- sqlite3
        from (irb):2:in `require'
        from (irb):2
        from C:/Users/Luis/Tools/Ruby/ruby-1.9.3-dev-i386-mingw32/bin/irb:12:in
`<main>'
irb(main):003:0> exit

I'm missing something?

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

From luislavena at gmail.com  Fri Jan 28 11:28:38 2011
From: luislavena at gmail.com (Luis Lavena)
Date: Fri, 28 Jan 2011 13:28:38 -0300
Subject: [Rubygems-developers] Inability to use RubyGems against trunk
In-Reply-To: <AANLkTinnkT6WWAq33+83rTmfQG2_aoUdyhDEo-6UX16y@mail.gmail.com>
References: <AANLkTinnkT6WWAq33+83rTmfQG2_aoUdyhDEo-6UX16y@mail.gmail.com>
Message-ID: <AANLkTiniWtKRKibkNhfpg7dGNFfzb=URQo1LM13CHPcY@mail.gmail.com>

On Fri, Jan 28, 2011 at 9:43 AM, Luis Lavena <luislavena at gmail.com> wrote:
> Hey guys,
>
> We are aiming at 1.5.0 release next week, and I'm having my doubts.
>

Here are the what I experienced using ruby 1.9.3 from trunk on OSX:

https://gist.github.com/800501

I'm doing something wrong?
-- 
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  Fri Jan 28 15:07:07 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 28 Jan 2011 15:07:07 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28889 ] gem rdoc --all
	--overwrite doesn't work
Message-ID: <20110128200707.31B851858376@rubyforge.org>

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

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: V?t Ondruch (voxik)
Assigned to: Nobody (None)
Summary: gem rdoc --all --overwrite doesn't work

Initial Comment:
C:\>gem rdoc --all --overwrite
Installing ri documentation for bundler-1.0.9...
Installing ri documentation for minitest-2.0.2...
ERROR:  While executing gem ... (Errno::ENOENT)
    No such file or directory - C:/Users/vita/.pik/rubies/Ruby-193-dev/lib/ruby/gems/1.9.1/gems/minitest-2.0.2

It is apparently one of the bundled gems, therefore the directory cannot be found.

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

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

From noreply at rubyforge.org  Fri Jan 28 15:55:55 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 28 Jan 2011 15:55:55 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28890 ]
	rubygems/defaults/operating_system.rb not called?
Message-ID: <20110128205555.9DCB9167831F@rubyforge.org>

Bugs item #28890, was opened at 2011-01-28 21:55
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28890&group_id=126

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: V?t Ondruch (voxik)
Assigned to: Nobody (None)
Summary: rubygems/defaults/operating_system.rb not called?

Initial Comment:
It appears that rubygems/defaults/operating_system.rb is not executed anymore. This file is used by Windows RubyInstaller for cooperation with DevKit.

C:\>gem --version
1.5.0

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

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

From noreply at rubyforge.org  Fri Jan 28 16:04:42 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 28 Jan 2011 16:04:42 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28891 ] rubygems bin for
	windows changed intentionally?
Message-ID: <20110128210442.37C38167831F@rubyforge.org>

Bugs item #28891, was opened at 2011-01-28 22:04
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28891&group_id=126

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: V?t Ondruch (voxik)
Assigned to: Nobody (None)
Summary: rubygems bin for windows changed intentionally?

Initial Comment:
The gem binaries were traditionally placed in the Ruby\bin folder, however that it not the case for Rubygems bundled with Ruby 1.9.3:

C:\>ruby -v
ruby 1.9.3dev (2011-01-28) [i386-mingw32]

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

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

From noreply at rubyforge.org  Fri Jan 28 16:41:13 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 28 Jan 2011 16:41:13 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28891 ] rubygems bin for
	windows changed intentionally?
Message-ID: <20110128214113.6692118583B9@rubyforge.org>

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

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: V?t Ondruch (voxik)
Assigned to: Nobody (None)
Summary: rubygems bin for windows changed intentionally?

Initial Comment:
The gem binaries were traditionally placed in the Ruby\bin folder, however that it not the case for Rubygems bundled with Ruby 1.9.3:

C:\>ruby -v
ruby 1.9.3dev (2011-01-28) [i386-mingw32]

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

>Comment By: Luis Lavena (luislavena)
Date: 2011-01-28 18:41

Message:
Hello,

Can you be more specific? binaries for rubygems *are* inside Ruby/bin directory.


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

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

From ryand-ruby at zenspider.com  Fri Jan 28 16:47:51 2011
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Fri, 28 Jan 2011 13:47:51 -0800
Subject: [Rubygems-developers] Inability to use RubyGems against trunk
In-Reply-To: <AANLkTiniWtKRKibkNhfpg7dGNFfzb=URQo1LM13CHPcY@mail.gmail.com>
References: <AANLkTinnkT6WWAq33+83rTmfQG2_aoUdyhDEo-6UX16y@mail.gmail.com>
	<AANLkTiniWtKRKibkNhfpg7dGNFfzb=URQo1LM13CHPcY@mail.gmail.com>
Message-ID: <537DB504-8720-4913-917F-B14535ABA577@zenspider.com>


On Jan 28, 2011, at 08:28 , Luis Lavena wrote:

> On Fri, Jan 28, 2011 at 9:43 AM, Luis Lavena <luislavena at gmail.com> wrote:
>> Hey guys,
>> 
>> We are aiming at 1.5.0 release next week, and I'm having my doubts.
>> 
> 
> Here are the what I experienced using ruby 1.9.3 from trunk on OSX:
> 
> https://gist.github.com/800501
> 
> I'm doing something wrong?

Dunno. I've got a repro:

6911 % sudo gem install sqlite3
Fetching: sqlite3-1.3.3.gem (100%)
Building native extensions.  This could take a while...
Successfully installed sqlite3-1.3.3
1 gem installed
Installing ri documentation for sqlite3-1.3.3...
Installing RDoc documentation for sqlite3-1.3.3...
6912 % ruby -rubygems -e 'require "sqlite3"'
6913 % gem -v
1.5.0
6914 % ruby -v
ruby 1.8.7 (2009-06-12 patchlevel 174) [universal-darwin10.0]

It works for Aaron @ 30655:

13:27 : [apatterson at higgins nokogiri (master)]$ ruby -v -rubygems -e 'require "sqlite3"' 
ruby 1.9.3dev (2011-01-26 trunk 30655) [x86_64-darwin10.6.0]

But not for me @ 30716. It has the same problems as above.

I've confirmed that it works for me at 30655:

6978 % /tmp/ruby19/bin/ruby19 -v -e 'require "sqlite3"'
ruby 1.9.3dev (2011-01-26 trunk 30655) [x86_64-darwin10.6.0]
6978 % 

But I've been seeing a lot of rdoc encoding problems.

We need a better guard for rdoc before we ship 1.5.0.

I'm digging deeper into both the rdoc issue and into the activation issue at tip.

From noreply at rubyforge.org  Fri Jan 28 16:57:32 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 28 Jan 2011 16:57:32 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28891 ] rubygems bin for
	windows changed intentionally?
Message-ID: <20110128215732.C9D9818583BA@rubyforge.org>

Bugs item #28891, was opened at 2011-01-28 22:04
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28891&group_id=126

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: V?t Ondruch (voxik)
Assigned to: Nobody (None)
Summary: rubygems bin for windows changed intentionally?

Initial Comment:
The gem binaries were traditionally placed in the Ruby\bin folder, however that it not the case for Rubygems bundled with Ruby 1.9.3:

C:\>ruby -v
ruby 1.9.3dev (2011-01-28) [i386-mingw32]

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

>Comment By: V?t Ondruch (voxik)
Date: 2011-01-28 22:57

Message:
Hmm, looking again into this you are right. Strange ... so
it was probably Bundler issue, because Bundler has
apparently some troubles with newer rubygems.

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

Comment By: Luis Lavena (luislavena)
Date: 2011-01-28 22:41

Message:
Hello,

Can you be more specific? binaries for rubygems *are* inside Ruby/bin directory.


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

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

From noreply at rubyforge.org  Fri Jan 28 16:59:21 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 28 Jan 2011 16:59:21 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28891 ] rubygems bin for
	windows changed intentionally?
Message-ID: <20110128215921.5664118583B4@rubyforge.org>

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

Category: None
Group: None
>Status: Closed
>Resolution: Rejected
Priority: 3
Submitted By: V?t Ondruch (voxik)
Assigned to: Nobody (None)
Summary: rubygems bin for windows changed intentionally?

Initial Comment:
The gem binaries were traditionally placed in the Ruby\bin folder, however that it not the case for Rubygems bundled with Ruby 1.9.3:

C:\>ruby -v
ruby 1.9.3dev (2011-01-28) [i386-mingw32]

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

>Comment By: Luis Lavena (luislavena)
Date: 2011-01-28 18:59

Message:
That is soo true.

Try to update to bundler 1.0.9, I believe it fix some of the weird stuff.

Or use Isolate ;-)

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

Comment By: V?t Ondruch (voxik)
Date: 2011-01-28 18:57

Message:
Hmm, looking again into this you are right. Strange ... so
it was probably Bundler issue, because Bundler has
apparently some troubles with newer rubygems.

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

Comment By: Luis Lavena (luislavena)
Date: 2011-01-28 18:41

Message:
Hello,

Can you be more specific? binaries for rubygems *are* inside Ruby/bin directory.


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

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

From noreply at rubyforge.org  Fri Jan 28 17:05:59 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 28 Jan 2011 17:05:59 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28891 ] rubygems bin for
	windows changed intentionally?
Message-ID: <20110128220559.1E995167831F@rubyforge.org>

Bugs item #28891, was opened at 2011-01-28 22:04
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28891&group_id=126

Category: None
Group: None
Status: Closed
Resolution: Rejected
Priority: 3
Submitted By: V?t Ondruch (voxik)
Assigned to: Nobody (None)
Summary: rubygems bin for windows changed intentionally?

Initial Comment:
The gem binaries were traditionally placed in the Ruby\bin folder, however that it not the case for Rubygems bundled with Ruby 1.9.3:

C:\>ruby -v
ruby 1.9.3dev (2011-01-28) [i386-mingw32]

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

>Comment By: V?t Ondruch (voxik)
Date: 2011-01-28 23:05

Message:
I was using Bundler 1.0.9 ... I am just not sure whose fault
if was, because I met several times issue with not loaded
user_interaction.rb and that seems to me like change in
RubyGems ... not just Bundler is failing hard because of
that, also Rubygems itself are failing in format.rb

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

Comment By: Luis Lavena (luislavena)
Date: 2011-01-28 22:59

Message:
That is soo true.

Try to update to bundler 1.0.9, I believe it fix some of the weird stuff.

Or use Isolate ;-)

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

Comment By: V?t Ondruch (voxik)
Date: 2011-01-28 22:57

Message:
Hmm, looking again into this you are right. Strange ... so
it was probably Bundler issue, because Bundler has
apparently some troubles with newer rubygems.

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

Comment By: Luis Lavena (luislavena)
Date: 2011-01-28 22:41

Message:
Hello,

Can you be more specific? binaries for rubygems *are* inside Ruby/bin directory.


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

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

From noreply at rubyforge.org  Fri Jan 28 17:11:51 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 28 Jan 2011 17:11:51 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28891 ] rubygems bin for
	windows changed intentionally?
Message-ID: <20110128221151.21DC918583B6@rubyforge.org>

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

Category: None
Group: None
Status: Closed
Resolution: Rejected
Priority: 3
Submitted By: V?t Ondruch (voxik)
Assigned to: Nobody (None)
Summary: rubygems bin for windows changed intentionally?

Initial Comment:
The gem binaries were traditionally placed in the Ruby\bin folder, however that it not the case for Rubygems bundled with Ruby 1.9.3:

C:\>ruby -v
ruby 1.9.3dev (2011-01-28) [i386-mingw32]

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

>Comment By: Luis Lavena (luislavena)
Date: 2011-01-28 19:11

Message:
RubyGems bundled in Ruby trunk needs to be updated for that.. will ping Eric and Ryan.

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

Comment By: V?t Ondruch (voxik)
Date: 2011-01-28 19:05

Message:
I was using Bundler 1.0.9 ... I am just not sure whose fault
if was, because I met several times issue with not loaded
user_interaction.rb and that seems to me like change in
RubyGems ... not just Bundler is failing hard because of
that, also Rubygems itself are failing in format.rb

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

Comment By: Luis Lavena (luislavena)
Date: 2011-01-28 18:59

Message:
That is soo true.

Try to update to bundler 1.0.9, I believe it fix some of the weird stuff.

Or use Isolate ;-)

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

Comment By: V?t Ondruch (voxik)
Date: 2011-01-28 18:57

Message:
Hmm, looking again into this you are right. Strange ... so
it was probably Bundler issue, because Bundler has
apparently some troubles with newer rubygems.

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

Comment By: Luis Lavena (luislavena)
Date: 2011-01-28 18:41

Message:
Hello,

Can you be more specific? binaries for rubygems *are* inside Ruby/bin directory.


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

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

From ryand-ruby at zenspider.com  Fri Jan 28 18:02:21 2011
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Fri, 28 Jan 2011 15:02:21 -0800
Subject: [Rubygems-developers] Inability to use RubyGems against trunk
In-Reply-To: <AANLkTinnkT6WWAq33+83rTmfQG2_aoUdyhDEo-6UX16y@mail.gmail.com>
References: <AANLkTinnkT6WWAq33+83rTmfQG2_aoUdyhDEo-6UX16y@mail.gmail.com>
Message-ID: <11D61E1B-F47C-4E71-B0F5-760D213F70E5@zenspider.com>


On Jan 28, 2011, at 04:43 , Luis Lavena wrote:

> We are aiming at 1.5.0 release next week, and I'm having my doubts.

Fixed and pushed. Everyone pls poke on all platforms.


From noreply at rubyforge.org  Fri Jan 28 19:12:59 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 28 Jan 2011 19:12:59 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28890 ]
	rubygems/defaults/operating_system.rb not called?
Message-ID: <20110129001259.45119185835A@rubyforge.org>

Bugs item #28890, was opened at 2011-01-28 17:55
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28890&group_id=126

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: V?t Ondruch (voxik)
Assigned to: Nobody (None)
Summary: rubygems/defaults/operating_system.rb not called?

Initial Comment:
It appears that rubygems/defaults/operating_system.rb is not executed anymore. This file is used by Windows RubyInstaller for cooperation with DevKit.

C:\>gem --version
1.5.0

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

>Comment By: Luis Lavena (luislavena)
Date: 2011-01-28 21:12

Message:
Hello Vit,

Can you try this again against rubygems master and Ruby trunk?

We found another issue described at RubyGems devel list that could be the root issue.

Thank you.

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

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

From drbrain at segment7.net  Sat Jan 29 01:06:19 2011
From: drbrain at segment7.net (Eric Hodel)
Date: Fri, 28 Jan 2011 22:06:19 -0800
Subject: [Rubygems-developers] Inability to use RubyGems against trunk
In-Reply-To: <537DB504-8720-4913-917F-B14535ABA577@zenspider.com>
References: <AANLkTinnkT6WWAq33+83rTmfQG2_aoUdyhDEo-6UX16y@mail.gmail.com>
	<AANLkTiniWtKRKibkNhfpg7dGNFfzb=URQo1LM13CHPcY@mail.gmail.com>
	<537DB504-8720-4913-917F-B14535ABA577@zenspider.com>
Message-ID: <B105C9F6-CB96-445C-A657-F16226AB4C32@segment7.net>

On Jan 28, 2011, at 13:47, Ryan Davis wrote:
> But I've been seeing a lot of rdoc encoding problems.

I'll release RDoc 3.5 this weekend which should address the rest of the RDoc encoding problems.

> We need a better guard for rdoc before we ship 1.5.0.
> 
> I'm digging deeper into both the rdoc issue and into the activation issue at tip.

Gem::DocManager should be replaced with something that uses a post-install hook.  Using Gem::DocManager is too clumsy when installing gems.

From noreply at rubyforge.org  Sat Jan 29 07:21:31 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sat, 29 Jan 2011 07:21:31 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28890 ]
	rubygems/defaults/operating_system.rb not called?
Message-ID: <20110129122143.60E2E18583B4@rubyforge.org>

Bugs item #28890, was opened at 2011-01-28 21:55
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28890&group_id=126

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: V?t Ondruch (voxik)
Assigned to: Nobody (None)
Summary: rubygems/defaults/operating_system.rb not called?

Initial Comment:
It appears that rubygems/defaults/operating_system.rb is not executed anymore. This file is used by Windows RubyInstaller for cooperation with DevKit.

C:\>gem --version
1.5.0

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

>Comment By: V?t Ondruch (voxik)
Date: 2011-01-29 13:21

Message:
Rubygems master works for me.

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

Comment By: Luis Lavena (luislavena)
Date: 2011-01-29 01:12

Message:
Hello Vit,

Can you try this again against rubygems master and Ruby trunk?

We found another issue described at RubyGems devel list that could be the root issue.

Thank you.

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

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

From noreply at rubyforge.org  Sat Jan 29 13:16:42 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sat, 29 Jan 2011 13:16:42 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28890 ]
	rubygems/defaults/operating_system.rb not called?
Message-ID: <20110129181642.E1381167831F@rubyforge.org>

Bugs item #28890, was opened at 2011-01-28 17:55
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28890&group_id=126

Category: None
Group: None
>Status: Closed
>Resolution: Out of Date
Priority: 3
Submitted By: V?t Ondruch (voxik)
Assigned to: Nobody (None)
Summary: rubygems/defaults/operating_system.rb not called?

Initial Comment:
It appears that rubygems/defaults/operating_system.rb is not executed anymore. This file is used by Windows RubyInstaller for cooperation with DevKit.

C:\>gem --version
1.5.0

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

>Comment By: Luis Lavena (luislavena)
Date: 2011-01-29 15:16

Message:
Awesome, closing this now ;-)

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

Comment By: V?t Ondruch (voxik)
Date: 2011-01-29 09:21

Message:
Rubygems master works for me.

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

Comment By: Luis Lavena (luislavena)
Date: 2011-01-28 21:12

Message:
Hello Vit,

Can you try this again against rubygems master and Ruby trunk?

We found another issue described at RubyGems devel list that could be the root issue.

Thank you.

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

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

From noreply at rubyforge.org  Sat Jan 29 13:23:39 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sat, 29 Jan 2011 13:23:39 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28846 ]
	rubygems/userinteraction not included in key libraries
Message-ID: <20110129182340.0D0B91678323@rubyforge.org>

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

Category: other
Group: v1.4.x
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: Erik Hollensbe (erikh)
Assigned to: Nobody (None)
Summary: rubygems/userinteraction not included in key libraries

Initial Comment:
Gem::Installer and Gem::Format do not include this require, and therefore using them independently causes an explosion on 1.4.



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

Comment By: Eric Hodel (drbrain)
Date: 2011-01-21 00:37

Message:
Fixed, thanks!

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

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

From jon.forums at gmail.com  Sat Jan 29 13:24:34 2011
From: jon.forums at gmail.com (Jon)
Date: Sat, 29 Jan 2011 13:24:34 -0500
Subject: [Rubygems-developers] operating_system.rb behavior on ruby-core
	trunk@30653
In-Reply-To: <20110125120943.8ce19e25.jon.forums@gmail.com>
References: <20110125120943.8ce19e25.jon.forums@gmail.com>
Message-ID: <20110129132434.57de5e14.jon.forums@gmail.com>

> I use an operating_system.rb and a custom devkit.rb to enhance how "gem install my_native_gem" and "ruby -r devkit extconf.rb" behaves when building for Windows using RubyInstaller. As of ruby-core trunk at 30653 the operating_system.rb functionality appears to have stopped working. Things stil work on "ruby 1.9.2p160 (2011-01-16 revision 30579) [i386-mingw32]"
>
> ...SNIP...
> 
> === FAILING CASE ===
> 
> C:\Users\Jon\Documents>gem install rdiscount
> Building native extensions.  This could take a while...
> ERROR:  Error installing rdiscount:
>         ERROR: Failed to build gem native extension.


looks squashed...thank you.

C:\Users\Jon\Documents>ruby --version && gem --version
ruby 1.9.3dev (2011-01-30 trunk 30723) [i386-mingw32]
1.5.0

C:\Users\Jon\Documents>gem install rdiscount
Fetching: rdiscount-1.6.8.gem (100%)
Temporarily enhancing PATH to include DevKit...
Building native extensions.  This could take a while...
Successfully installed rdiscount-1.6.8
1 gem installed

C:\Users\Jon\Documents>ruby -e "require 'rdiscount'; puts RDiscount.new('**RubyGems 1.5.0**').to_html"
<p><strong>RubyGems 1.5.0</strong></p>


Jon

---
blog: http://jonforums.github.com/
twitter: @jonforums

From erik at hollensbe.org  Sun Jan 30 11:34:05 2011
From: erik at hollensbe.org (Erik Hollensbe)
Date: Sun, 30 Jan 2011 11:34:05 -0500
Subject: [Rubygems-developers] rubygems-test 0.3.0 released
Message-ID: <351C5A29-C8D4-47E7-A081-52DB92C7795E@hollensbe.org>

Major fixes to I/O operations and should run rake 'right'. Should also no longer require sudo if your gems are installed that way.

Please test on your favorite platform/interpreter combination! I sincerely want to support as many platforms as possible, and any help here would be greatly appreciated.

Thanks,

-Erik

From noreply at rubyforge.org  Sun Jan 30 14:30:01 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun, 30 Jan 2011 14:30:01 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28894 ] Add
	http://rubyforge.org/projects/rubygems to README
Message-ID: <20110130193001.5BF291858356@rubyforge.org>

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

Category: documentation
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Dr Nic Williams (nicwilliams)
Assigned to: Nobody (None)
Summary: Add http://rubyforge.org/projects/rubygems to README

Initial Comment:
I don't think the URL to the Issues Tracker is mentioned on the README. I accidentally created a ticket at http://help.rubygems.org.

Can we include http://rubyforge.org/projects/rubygems in the README?

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

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

From noreply at rubyforge.org  Sun Jan 30 14:52:48 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun, 30 Jan 2011 14:52:48 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28825 ] Add an url to this
	bug reporter to the readme, i needed to google it...
Message-ID: <20110130195248.773511858356@rubyforge.org>

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

Category: documentation
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: M G (grosser)
>Assigned to: Eric Hodel (drbrain)
Summary: Add an url to this bug reporter to the readme, i needed to google it...

Initial Comment:
message body is required

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

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

From noreply at rubyforge.org  Sun Jan 30 14:53:23 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun, 30 Jan 2011 14:53:23 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28894 ] Add
	http://rubyforge.org/projects/rubygems to README
Message-ID: <20110130195323.887621858356@rubyforge.org>

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

Category: documentation
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Dr Nic Williams (nicwilliams)
>Assigned to: Eric Hodel (drbrain)
Summary: Add http://rubyforge.org/projects/rubygems to README

Initial Comment:
I don't think the URL to the Issues Tracker is mentioned on the README. I accidentally created a ticket at http://help.rubygems.org.

Can we include http://rubyforge.org/projects/rubygems in the README?

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

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

From luislavena at gmail.com  Mon Jan 31 07:15:35 2011
From: luislavena at gmail.com (Luis Lavena)
Date: Mon, 31 Jan 2011 09:15:35 -0300
Subject: [Rubygems-developers] Revision r30734 of Ruby-trunk
Message-ID: <AANLkTi=1irGbR4jWZTGMCMnH-WciOzCDkc=Oc9HFqHFH@mail.gmail.com>

Hello,

I've just backported r30734 of Ruby trunk

https://github.com/ruby/ruby/commit/ce00071053d3d5957574c2d57d021f086991001c

-- 
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 Jan 31 07:17:15 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Mon, 31 Jan 2011 07:17:15 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28825 ] Add an url to this
	bug reporter to the readme, i needed to google it...
Message-ID: <20110131121715.8EDFA1858361@rubyforge.org>

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

Category: documentation
Group: None
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: M G (grosser)
>Assigned to: Luis Lavena (luislavena)
Summary: Add an url to this bug reporter to the readme, i needed to google it...

Initial Comment:
message body is required

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

>Comment By: Luis Lavena (luislavena)
Date: 2011-01-31 09:17

Message:
Added in commit c26d5a7

Thank you for your report.

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

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

From noreply at rubyforge.org  Mon Jan 31 07:18:10 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Mon, 31 Jan 2011 07:18:10 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28894 ] Add
	http://rubyforge.org/projects/rubygems to README
Message-ID: <20110131121810.8AE671858357@rubyforge.org>

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

Category: documentation
Group: None
>Status: Closed
>Resolution: Rejected
Priority: 3
Submitted By: Dr Nic Williams (nicwilliams)
Assigned to: Eric Hodel (drbrain)
Summary: Add http://rubyforge.org/projects/rubygems to README

Initial Comment:
I don't think the URL to the Issues Tracker is mentioned on the README. I accidentally created a ticket at http://help.rubygems.org.

Can we include http://rubyforge.org/projects/rubygems in the README?

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

>Comment By: Luis Lavena (luislavena)
Date: 2011-01-31 09:18

Message:
Duplicate of #28825, which has already been closed.

Thank you for your report.

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

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

From ryand-ruby at zenspider.com  Mon Jan 31 16:21:00 2011
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Mon, 31 Jan 2011 13:21:00 -0800
Subject: [Rubygems-developers] Release coming,
	but still no response on broken 1.9.x CI builds
In-Reply-To: <AANLkTinA7Y3Vm2NxfPNoHMneS0fvfpEbepMetn9Ega2O@mail.gmail.com>
References: <AANLkTi=dye+Q9JYUtghGaiB-+rGDisV9xUZPt8sBOQMK@mail.gmail.com>
	<300AF5C3-C708-436E-86E5-F83000C61DC2@segment7.net>
	<2C5AB12B-5171-4A2B-BD80-85AA15CF877E@zenspider.com>
	<AANLkTikL-Py6+x3xgBpW=tSL3E8J1GgWTvByT8GWYmnW@mail.gmail.com>
	<AANLkTinA7Y3Vm2NxfPNoHMneS0fvfpEbepMetn9Ega2O@mail.gmail.com>
Message-ID: <2007E31F-80D0-4808-BDCA-0D964F39F00C@zenspider.com>


On Jan 17, 2011, at 22:01 , Chad Woolley wrote:

> Here's the status:
> 
> 1.8.7-p330 - Green:
> http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_8_7-p330
> 
> 1.9.1-p378 - Red: (<"no such file to load -- io/console">)
> http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_1-p378
> 
> 1.9.2-p136 - Red (<"no such file to load -- io/console">):
> http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_2-p136

Well... these are finally running, but they're not running properly. We had a failure on the 20th and we didn't get notified about it:

http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_1-p378/48967276d584c52ec2e8b1a2ce9946fb3855766c

says:

Connection refused - connect(2) at /home/pivotal/ccrb/lib/smtp_tls.rb:76:in `initialize'


From drbrain at segment7.net  Mon Jan 31 20:47:52 2011
From: drbrain at segment7.net (Eric Hodel)
Date: Mon, 31 Jan 2011 17:47:52 -0800
Subject: [Rubygems-developers] [ANN] rubygems-update 1.5.0 Released
Message-ID: <F8A7E368-E255-413B-B256-A446EA166705@segment7.net>

rubygems-update version 1.5.0 has been released!

* <http://rubygems.org>
* <http://docs.rubygems.org>
* <http://help.rubygems.org>
* <http://github.com/rubygems>
* <http://rubyforge.org/projects/rubygems>

RubyGems is a package management framework for Ruby.

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

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

To upgrade to the latest RubyGems, run:

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

See UPGRADING.rdoc for more details and alternative instructions.

-----

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

* Download from: https://rubygems.org/pages/download
* Unpack into a directory and cd there
* Install with: ruby setup.rb  # you may need admin/root privilege

For more details and other options, see:

 ruby setup.rb --help

Changes:

### 1.5.0 / 2011-01-31

Major Enhancements:

* Finally fixed all known 1.9.x issues. Upgrading is now possible!
* Merged huge 1.3.7/ruby-core changes to master.

Minor Enhancements:

* Added UPGRADING.rdoc to help deal with 1.9 issues.
* Gem::Format now gives better errors for corrupt gem files and includes paths
* Pre-install hooks can now abort gem installation by returning false
* Move shareable TestCase classes to lib/ to help plugin authors with tests.
* Add post-build hooks that can cancel the gem install
* Always require custom_require now that require_gem is gone
* Added GemInstaller accessors for @options so plugins can reference them.
* Optimized Gem.find_files. ~10% faster than 1.4.2. ~40% faster than ruby 1.9.
* Gem::SilentUI now behaves like Gem::StreamUI for asking questions.  Patch by
 Erik Hollensbe.

Bug Fixes:

* `gem update` was implicitly doing --system.
* 1.9.3: Fixed encoding errors causing gem installs to die during rdoc phase.
* Add RubyForge URL to README. Closes #28825
* 1.9.3: Use chdir {} when building extensions to prevent warnings. Fixes #4337
* 1.9.2: Fix circular require warning.
* Make requiring openssl even lazier at request of NaHi
* `gem unpack` will now download the gem if it is not in the cache. Patch by
 Erik Hollensbe.
* rubygems-update lists its development dependencies again

From drbrain at segment7.net  Mon Jan 31 20:49:35 2011
From: drbrain at segment7.net (Eric Hodel)
Date: Mon, 31 Jan 2011 17:49:35 -0800
Subject: [Rubygems-developers] Release coming,
	but still no response on broken 1.9.x CI builds
In-Reply-To: <2007E31F-80D0-4808-BDCA-0D964F39F00C@zenspider.com>
References: <AANLkTi=dye+Q9JYUtghGaiB-+rGDisV9xUZPt8sBOQMK@mail.gmail.com>
	<300AF5C3-C708-436E-86E5-F83000C61DC2@segment7.net>
	<2C5AB12B-5171-4A2B-BD80-85AA15CF877E@zenspider.com>
	<AANLkTikL-Py6+x3xgBpW=tSL3E8J1GgWTvByT8GWYmnW@mail.gmail.com>
	<AANLkTinA7Y3Vm2NxfPNoHMneS0fvfpEbepMetn9Ega2O@mail.gmail.com>
	<2007E31F-80D0-4808-BDCA-0D964F39F00C@zenspider.com>
Message-ID: <A93F48C0-BD9D-46E0-975F-BD92E051F8CB@segment7.net>

On Jan 31, 2011, at 13:21, Ryan Davis wrote:
> On Jan 17, 2011, at 22:01 , Chad Woolley wrote:
>> Here's the status:
>> 
>> 1.8.7-p330 - Green:
>> http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_8_7-p330
>> 
>> 1.9.1-p378 - Red: (<"no such file to load -- io/console">)
>> http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_1-p378
>> 
>> 1.9.2-p136 - Red (<"no such file to load -- io/console">):
>> http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_2-p136
> 
> Well... these are finally running, but they're not running properly. We had a failure on the 20th and we didn't get notified about it:
> 
> http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_1-p378/48967276d584c52ec2e8b1a2ce9946fb3855766c
> 
> says:
> 
> Connection refused - connect(2) at /home/pivotal/ccrb/lib/smtp_tls.rb:76:in `initialize'

They all passed except 1.9.2 which couldn't upgrade to hoe 2.9.