[#35027] [Ruby 1.9-Bug#4352][Open] [patch] Fix eval(s, b) backtrace; make eval(s, b) consistent with eval(s) — "James M. Lawrence" <redmine@...>

Bug #4352: [patch] Fix eval(s, b) backtrace; make eval(s, b) consistent with eval(s)

16 messages 2011/02/01

[#35114] [Ruby 1.9-Bug#4373][Open] http.rb:677: [BUG] Segmentation fault — Christian Fazzini <redmine@...>

Bug #4373: http.rb:677: [BUG] Segmentation fault

59 messages 2011/02/06

[#35171] [Ruby 1.9-Bug#4386][Open] encoding: directive does not affect regex expressions — mathew murphy <redmine@...>

Bug #4386: encoding: directive does not affect regex expressions

9 messages 2011/02/09

[#35237] [Ruby 1.9-Bug#4400][Open] nested at_exit hooks run in strange order — Suraj Kurapati <redmine@...>

Bug #4400: nested at_exit hooks run in strange order

12 messages 2011/02/15

[ruby-core:35166] Re: undefined class/module YAML::PrivateType - Error

From: Luis Lavena <luislavena@...>
Date: 2011-02-09 13:56:13 UTC
List: ruby-core #35166
On Wed, Feb 9, 2011 at 10:51 AM, Bernard Lambeau <blambeau@gmail.com> wrote:
> Not yet and瀛t seems that many people are currently observing similar
> behavior:濾ttp://help.rubygems.org/discussions/problems/483-gems-built-with-rubygems-150-ruby-192-do-not-install-properly-with-150-187
> I've put ruby-core members in copy, to draw their attention on the problem.
> I don't know how I can make better...

This has already been fixed in RubyGems:
https://github.com/rubygems/rubygems/commit/6a896f356ef325d0357051fa962b6e3a835c04d2

http://help.rubygems.org is not meant to report bugs, is for support
around rubygems.org itself. For that is RubyGems bug tracker:

http://rubyforge.org/projects/rubygems

-- 
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駻y

In This Thread

Prev Next