On Sat, Jan 24, 2009 at 5:36 PM, Luis Lavena <luislav...@gmail.com> wrote: > On Sat, Jan 24, 2009 at 5:28 PM, Chad Woolley <thewoolley...@gmail.com> wrote: >> On Sat, Jan 24, 2009 at 12:14 PM, Luis Lavena <luislav...@gmail.com> wrote: >>> http://pastie.org/369729 >> >> Here's the only change I made: >> >> http://rubyforge.org/tracker/?func=detail&atid=575&aid=23210&group_id=126 >> >> Doesn't seem like it could have caused any of these errors... > > Hello Chad, I saw that change, but is not the one raising failures. > > I've just reverted to 1918 (previous the commits related to > pre-release gems) and it worked: > > 696 tests, 2149 assertions, 0 failures, 0 errors, 0 skips > > I'll move up until found the first one introducing these errors. >
revision 1943 introduced the issues: Make Gem::Dependency#=~ to work with Gem::Specification > What worries me is that it fails on MinGW, but not VC6 build of Ruby. > http://pastie.org/369758 Again, the errors only show on MinGW. Will check linux and see what happens. -- Luis Lavena AREA 17 - Perfection in design is achieved not when there is nothing more to add, but rather when there is nothing more to take away. Antoine de Saint-Exupéry _______________________________________________ Rubygems-developers mailing list Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
