From drbrain at segment7.net Thu Nov 3 14:08:36 2011 From: drbrain at segment7.net (Eric Hodel) Date: Thu, 3 Nov 2011 11:08:36 -0700 Subject: Ruby 1.9.3 is out, where is RubyGems 1.8.11? In-Reply-To: References: Message-ID: On Oct 30, 2011, at 4:59 PM, Luis Lavena wrote: > Hello, > > I noticed there is no packages for RubyGems 1.8.11 at RubyForge: > http://rubyforge.org/frs/?group_id=126&release_id=46225 Whoops! They're up now From luislavena at gmail.com Thu Nov 3 14:28:24 2011 From: luislavena at gmail.com (Luis Lavena) Date: Thu, 3 Nov 2011 15:28:24 -0300 Subject: Ruby 1.9.3 is out, where is RubyGems 1.8.11? In-Reply-To: References: Message-ID: On Thu, Nov 3, 2011 at 3:08 PM, Eric Hodel wrote: > On Oct 30, 2011, at 4:59 PM, Luis Lavena wrote: >> Hello, >> >> I noticed there is no packages for RubyGems 1.8.11 at RubyForge: >> http://rubyforge.org/frs/?group_id=126&release_id=46225 > > Whoops! > > They're up now Thank you Eric, needed this to update the recipes for other RubyInstallers (beyond 1.9.3) -- Luis Lavena AREA 17 - Perfection in design is achieved not when there is nothing more to add, but rather when there is nothing more to take away. Antoine de Saint-Exup?ry From noreply at rubyforge.org Wed Nov 9 03:33:11 2011 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 9 Nov 2011 03:33:11 -0500 (EST) Subject: [ rubygems-Bugs-29420 ] I distribute my ruby script using Ocra but when executing my exe file i get this errors Message-ID: <20111109083311.A54711858361@rubyforge.org> Bugs item #29420, was opened at 09/11/2011 09:33 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=29420&group_id=126 Category: None Group: v0.9.2 Status: Open Resolution: None Priority: 3 Submitted By: Khalid MOBARKI (ktemax) Assigned to: Nobody (None) Summary: I distribute my ruby script using Ocra but when executing my exe file i get this errors Initial Comment: C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in `to_spec s': Could not find hoe (>= 1.3.0) amongst [commonwatir-2.0.2, ffi-1.0.9-x86-ming w32, firewatir-1.9.4, nokogiri-1.5.0-x86-mingw32, ocra-1.3.0, rautomation-0.6.3, s4t-utils-1.0.4, safariwatir-0.3.8, user-choices-1.1.6.1, watir-2.0.2, win32-ap i-1.4.8, win32-process-0.6.5, windows-api-0.3.0, windows-pr-1.2.1, xml-simple-1. 1.0] (Gem::LoadError) from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb :761:in `block in activate_dependencies' from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb :758:in `each' from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb :758:in `activate_dependencies' from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb :742:in `activate' from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb :764:in `block in activate_dependencies' from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb :758:in `each' from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb :758:in `activate_dependencies' from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb :742:in `activate' from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb :764:in `block in activate_dependencies' from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb :758:in `each' from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb :758:in `activate_dependencies' from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb :742:in `activate' from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems.rb:209:in `rescu e in try_activate' from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems.rb:206:in `try_a ctivate' from :218:in `try_activate' from :32:in `rescue in require' from :29:in `require' from C:/Tmp/ocr77.tmp/src/hello.rb:3:in `
' ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=29420&group_id=126 From noreply at rubyforge.org Wed Nov 9 06:22:38 2011 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 9 Nov 2011 06:22:38 -0500 (EST) Subject: [ rubygems-Bugs-29316 ] ruby_code case not handled: Regexp Message-ID: <20111109112238.F2DB21858361@rubyforge.org> Bugs item #29316, was opened at 2011-07-13 10:54 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=29316&group_id=126 Category: `gem install` command Group: None >Status: Closed >Resolution: Rejected Priority: 3 Submitted By: Gonzalo Garramuno (gga) Assigned to: Nobody (None) Summary: ruby_code case not handled: Regexp Initial Comment: ERROR: While executing gem ... (Gem::Exception) ruby_code case not handled: Regexp When installing the ifmapper gem in rubygems.org in ubuntu's ruby-1.9.1-full. Trying to build the gem with the same gem1.9 (-v 1.8.5), I obtain a gem that when installed reports: ERROR: While executing gem ... (Gem::Package::FormatError) corrupt gem (Gem::Package::TarInvalidError: tar is corrupt, name contains null byte) in /media/Linux/src/bin/ifmapper/ifmapper-1.1.4/ifmapper-1.1.4.gem ---------------------------------------------------------------------- Comment By: Ryan Davis (zenspider) Date: 2011-11-09 03:22 Message: I'm closing this ticket as we've moved to github issues for all issue tracking. Please refile this ticket there if you think it is still valid. https://github.com/rubygems/rubygems/issues Thanks, The RubyGems Team ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2011-07-13 11:18 Message: Hello, Please report this to GitHub, the tracker is not even linked on RubyForge page anymore. ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2011-07-13 11:17 Message: Hi! Believe it or not, we're moving to github's issue tracker! The pressure to move has been loud and clear, but for the longest time it didn't support the way we worked. Now that it has freeform labels it can support our workflow adequately. There is just one problem: Your bug is here and we don't want to lose you! What we'd like you to do is fairly painless and should only take a few minutes: Please file the _exact_ same ticket on github and provide a link back to this crufty old ticket so we can refer to any previous discussion that occurred. Once the new ticket is made, put a forwarding link to it here and close this ticket out. In a couple weeks, we'll track down the old tickets that are still open and decide what to do with them. We could have done this fairly automatically, but we really want you to do it so you're attached to the ticket and we can still communicate with you and keep a record of it. https://github.com/rubygems/rubygems/issues Thanks, The RubyGems Team ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=29316&group_id=126 From noreply at rubyforge.org Wed Nov 9 06:22:39 2011 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 9 Nov 2011 06:22:39 -0500 (EST) Subject: [ rubygems-Bugs-29420 ] I distribute my ruby script using Ocra but when executing my exe file i get this errors Message-ID: <20111109112239.25A341858363@rubyforge.org> Bugs item #29420, was opened at 2011-11-09 00:33 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=29420&group_id=126 Category: None Group: v0.9.2 >Status: Closed >Resolution: Rejected Priority: 3 Submitted By: Khalid MOBARKI (ktemax) Assigned to: Nobody (None) Summary: I distribute my ruby script using Ocra but when executing my exe file i get this errors Initial Comment: C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in `to_spec s': Could not find hoe (>= 1.3.0) amongst [commonwatir-2.0.2, ffi-1.0.9-x86-ming w32, firewatir-1.9.4, nokogiri-1.5.0-x86-mingw32, ocra-1.3.0, rautomation-0.6.3, s4t-utils-1.0.4, safariwatir-0.3.8, user-choices-1.1.6.1, watir-2.0.2, win32-ap i-1.4.8, win32-process-0.6.5, windows-api-0.3.0, windows-pr-1.2.1, xml-simple-1. 1.0] (Gem::LoadError) from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb :761:in `block in activate_dependencies' from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb :758:in `each' from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb :758:in `activate_dependencies' from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb :742:in `activate' from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb :764:in `block in activate_dependencies' from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb :758:in `each' from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb :758:in `activate_dependencies' from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb :742:in `activate' from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb :764:in `block in activate_dependencies' from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb :758:in `each' from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb :758:in `activate_dependencies' from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb :742:in `activate' from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems.rb:209:in `rescu e in try_activate' from C:/Tmp/ocr77.tmp/lib/ruby/site_ruby/1.9.1/rubygems.rb:206:in `try_a ctivate' from :218:in `try_activate' from :32:in `rescue in require' from :29:in `require' from C:/Tmp/ocr77.tmp/src/hello.rb:3:in `
' ---------------------------------------------------------------------- Comment By: Ryan Davis (zenspider) Date: 2011-11-09 03:22 Message: I'm closing this ticket as we've moved to github issues for all issue tracking. Please refile this ticket there if you think it is still valid. https://github.com/rubygems/rubygems/issues Thanks, The RubyGems Team ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=29420&group_id=126 From ryand-ruby at zenspider.com Mon Nov 28 17:56:51 2011 From: ryand-ruby at zenspider.com (Ryan Davis) Date: Mon, 28 Nov 2011 14:56:51 -0800 Subject: Code Reviews - aka "oh god... he's at it again..." Message-ID: <26F5EEEA-F259-4C79-96BF-ABFD6DB807ED@zenspider.com> I'd like to get rubygems moving again. Specifically, rubygems codebase is a crufty mess and we need to fix it. First, we need to know what to fix. I'd like to see us do a full set of code reviews across the entire codebase with comment tags put in where the pain points are (detailed below). That way we can prioritize our pain and start to address it. This effort is intended to go towards a 2.0 release, NOT a 1.x release. It is meant to rejuvenate the codebase and get us pointed in the right direction. We've got 95 files in lib with ~20k lines in them. Every file should have at least one set of eyeballs on every line them with certain files having MANY sets of eyeballs on them. We've got 94 files in test with ~17k lines in them. They're just as important (if not more) as the files in lib. I'd like to get people to step up and schedule code reviews over the next 2-4 weeks. Who's in? Let me know here that you're interested and how much you think you'd like to do. ## Tagging: Nothing complex... I standardize on the following (examples): # FIX: xxx is wrong # HACK: should have done xxx instead # TODO: xxx needs yyy # DOC # REFACTOR: duplicated from xxx # RETIRE: replaced by xxx # WARN: xxx is scary I have a script that shows all of these in a clean way. Here is the summary of specification.rb: Occurances: 32: TODO 2: FIX 1: REFACTOR 1: HACK So you can use that as the basic idea that I'm going for. From nick at quaran.to Mon Nov 28 18:41:54 2011 From: nick at quaran.to (Nick Quaranto) Date: Mon, 28 Nov 2011 18:41:54 -0500 Subject: Code Reviews - aka "oh god... he's at it again..." In-Reply-To: <26F5EEEA-F259-4C79-96BF-ABFD6DB807ED@zenspider.com> References: <26F5EEEA-F259-4C79-96BF-ABFD6DB807ED@zenspider.com> Message-ID: May I suggest we do this in a branch instead of master? Just in case we need to cut a new release and we can go bananas in a separate branch and merge it in once we're happy. On Mon, Nov 28, 2011 at 5:56 PM, Ryan Davis wrote: > I'd like to get rubygems moving again. > > Specifically, rubygems codebase is a crufty mess and we need to fix it. > First, we need to know what to fix. I'd like to see us do a full set of > code reviews across the entire codebase with comment tags put in where the > pain points are (detailed below). That way we can prioritize our pain and > start to address it. > > This effort is intended to go towards a 2.0 release, NOT a 1.x release. It > is meant to rejuvenate the codebase and get us pointed in the right > direction. > > We've got 95 files in lib with ~20k lines in them. Every file should have > at least one set of eyeballs on every line them with certain files having > MANY sets of eyeballs on them. We've got 94 files in test with ~17k lines > in them. They're just as important (if not more) as the files in lib. > > I'd like to get people to step up and schedule code reviews over the next > 2-4 weeks. Who's in? Let me know here that you're interested and how much > you think you'd like to do. > > ## Tagging: > > Nothing complex... I standardize on the following (examples): > > # FIX: xxx is wrong > # HACK: should have done xxx instead > # TODO: xxx needs yyy > # DOC > # REFACTOR: duplicated from xxx > # RETIRE: replaced by xxx > # WARN: xxx is scary > > I have a script that shows all of these in a clean way. Here is the > summary of specification.rb: > > Occurances: > 32: TODO > 2: FIX > 1: REFACTOR > 1: HACK > > So you can use that as the basic idea that I'm going for. > > _______________________________________________ > RubyGems-Developers mailing list > http://rubyforge.org/projects/rubygems > RubyGems-Developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubygems-developers > From steve at steveklabnik.com Mon Nov 28 20:30:06 2011 From: steve at steveklabnik.com (Steve Klabnik) Date: Mon, 28 Nov 2011 20:30:06 -0500 Subject: Code Reviews - aka "oh god... he's at it again..." In-Reply-To: <26F5EEEA-F259-4C79-96BF-ABFD6DB807ED@zenspider.com> References: <26F5EEEA-F259-4C79-96BF-ABFD6DB807ED@zenspider.com> Message-ID: I've never looked at any of the RubyGems code, so if there's a part that would particularly be helped out by an extra pair of brand new eyes, I wouldn't mind pitching in a few hours. From ryand-ruby at zenspider.com Mon Nov 28 20:31:52 2011 From: ryand-ruby at zenspider.com (Ryan Davis) Date: Mon, 28 Nov 2011 17:31:52 -0800 Subject: Code Reviews - aka "oh god... he's at it again..." In-Reply-To: References: <26F5EEEA-F259-4C79-96BF-ABFD6DB807ED@zenspider.com> Message-ID: On Nov 28, 2011, at 15:41 , Nick Quaranto wrote: > May I suggest we do this in a branch instead of master? Just in case we > need to cut a new release and we can go bananas in a separate branch and > merge it in once we're happy. We're currently doing the opposite. 1.8.x is released from the 1.8 branch. From luislavena at gmail.com Mon Nov 28 20:55:28 2011 From: luislavena at gmail.com (Luis Lavena) Date: Mon, 28 Nov 2011 22:55:28 -0300 Subject: Code Reviews - aka "oh god... he's at it again..." In-Reply-To: <26F5EEEA-F259-4C79-96BF-ABFD6DB807ED@zenspider.com> References: <26F5EEEA-F259-4C79-96BF-ABFD6DB807ED@zenspider.com> Message-ID: On Mon, Nov 28, 2011 at 7:56 PM, Ryan Davis wrote: > I'd like to get rubygems moving again. > /me wants a better remote fetcher, perhaps API driven one instead of massive marshalled data? -- Luis Lavena AREA 17 - Perfection in design is achieved not when there is nothing more to add, but rather when there is nothing more to take away. Antoine de Saint-Exup?ry From ryand-ruby at zenspider.com Tue Nov 29 05:36:17 2011 From: ryand-ruby at zenspider.com (Ryan Davis) Date: Tue, 29 Nov 2011 02:36:17 -0800 Subject: Code Reviews - aka "oh god... he's at it again..." In-Reply-To: References: <26F5EEEA-F259-4C79-96BF-ABFD6DB807ED@zenspider.com> Message-ID: <5D145CDA-0095-4EBD-856C-189E56C5888C@zenspider.com> On Nov 28, 2011, at 17:55 , Luis Lavena wrote: > On Mon, Nov 28, 2011 at 7:56 PM, Ryan Davis wrote: >> I'd like to get rubygems moving again. >> > > /me wants a better remote fetcher, perhaps API driven one instead of > massive marshalled data? /me too :P Can you make sure there is a ticket for that? From ryand-ruby at zenspider.com Tue Nov 29 05:40:10 2011 From: ryand-ruby at zenspider.com (Ryan Davis) Date: Tue, 29 Nov 2011 02:40:10 -0800 Subject: Code Reviews - aka "oh god... he's at it again..." In-Reply-To: References: <26F5EEEA-F259-4C79-96BF-ABFD6DB807ED@zenspider.com> Message-ID: <6209D901-5EE0-4467-9E6F-7B11763FB286@zenspider.com> On Nov 28, 2011, at 17:30 , Steve Klabnik wrote: > I've never looked at any of the RubyGems code, so if there's a part > that would particularly be helped out by an extra pair of brand new > eyes, I wouldn't mind pitching in a few hours. Awesome Steve. Thanks! Any amount of eyeballs that we can get on rubygems.rb and specification.rb will help. Granted, there's plenty more too... but those two files contain most of the functionality/risk/ugly. I'd like to continue slimming down rubygems.rb because it has been a grab-bag of crap for many years now. Functionality in there should move the the actual responsible class. Most of the work I did this year was moving stuff from there (and other places) to specification since most of the work of rubygems has to do with specifications.