Re: libruby1.8 breaks raggle?

[Michael Ablassmeier <abi@grinser.de>]

hi Mauricio,

On Fri, Dec 17, 2004 at 12:10:39PM +0100, Mauricio Fernández wrote:
> On Fri, Dec 17, 2004 at 10:36:53AM +0100, Michael Ablassmeier wrote:
> > If rebuilding ruby1.8 (-2) without 101_cvs_updates.patch, raggle works nicely,
> > if the patch is applied it stops updating the feeds with:
> >     
> >  Feed Thread Reap Error: "temporal locking already locked string".
> [...]
> 
> I think it's caused by
> 
> Thu Nov  4 03:11:33 2004  Yukihiro Matsumoto  <matz@ruby-lang.org>
> 
>         * string.c (str_gsub): lock strings temporarily.  [ruby-dev:24687]
> 
> http://tinyurl.com/5p9qt

hm, well, As far as i can see this patch was already applied in -1, at least,
debian/changelog tells:

ruby1.8 (1.8.1+1.8.2pre3-1) unstable; urgency=high 
  [..]
    - (urgency high) String#gsub! dumps core again.  [ruby-dev:24687]
  [..]

raggle works well with libruby1.8 (1.8.1+1.8.2pre3-1).

> It should be fairly easy to locate the faulty gsub.

bye,
    - michael