Debian Bug report logs - #487204
ruby1.8: object allocation during garbage collection phase

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Blaz Lorger <blaz.lorger@triera.net>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: ruby1.8: object allocation during garbage collection phase

Date: Wed, 11 Jun 2008 08:32:08 +0200

Package: ruby1.8
Version: 1.8.7-2
Severity: important


My script is aborted after with following message after executing successfully for some time:
===
/usr/lib/ruby/1.8/xmltv/libxmltv.rb:150: [BUG] object allocation during
garbage collection phase
ruby 1.8.7 (2008-05-31 patchlevel 0) [x86_64-linux]

Aborted
===

Problem appeard after upgrade to version 1.8.7-2. Downgrade to version 1.8.6.114-2 solves the problem.

I have upgraded and downgraded following packages:
[UPGRADE] irb1.8 1.8.6.114-2 -> 1.8.7-2
[UPGRADE] libdbm-ruby1.8 1.8.6.114-2 -> 1.8.7-2
[UPGRADE] libgdbm-ruby1.8 1.8.6.114-2 -> 1.8.7-2
[UPGRADE] libopenssl-ruby1.8 1.8.6.114-2 -> 1.8.7-2
[UPGRADE] libreadline-ruby1.8 1.8.6.114-2 -> 1.8.7-2
[UPGRADE] libruby1.8 1.8.6.114-2 -> 1.8.7-2
[UPGRADE] libtcltk-ruby1.8 1.8.6.114-2 -> 1.8.7-2
[UPGRADE] rdoc1.8 1.8.6.114-2 -> 1.8.7-2
[UPGRADE] ri1.8 1.8.6.114-2 -> 1.8.7-2
[UPGRADE] ruby1.8 1.8.6.114-2 -> 1.8.7-2
[UPGRADE] ruby1.8-dev 1.8.6.114-2 -> 1.8.7-2
[UPGRADE] ruby1.8-examples 1.8.6.114-2 -> 1.8.7-2

This report was generated after downgrade to version 1.8.6.114-2, so
version of libruby1.8 in dependency list is version after downgrade.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages ruby1.8 depends on:
ii  libc6                        2.7-12      GNU C Library: Shared libraries
ii  libruby1.8                   1.8.6.114-2 Libraries necessary to run Ruby 1.

ruby1.8 recommends no packages.

-- no debconf information

Message #10 received at 485738@bugs.debian.org (full text, mbox, reply):

From: Lucas Nussbaum <lucas@lucas-nussbaum.net>

To: Blaz Lorger <blaz.lorger@triera.net>, 485738@bugs.debian.org

Subject: Re: Bug#485738: ruby1.8: object allocation during garbage collection phase

Date: Wed, 11 Jun 2008 09:52:31 +0200

On 11/06/08 at 08:32 +0200, Blaz Lorger wrote:
> Package: ruby1.8
> Version: 1.8.7-2
> Severity: important
> 
> 
> My script is aborted after with following message after executing successfully for some time:
> ===
> /usr/lib/ruby/1.8/xmltv/libxmltv.rb:150: [BUG] object allocation during
> garbage collection phase
> ruby 1.8.7 (2008-05-31 patchlevel 0) [x86_64-linux]
> 
> Aborted
> ===
> 
> Problem appeard after upgrade to version 1.8.7-2. Downgrade to version 1.8.6.114-2 solves the problem.
> 
> I have upgraded and downgraded following packages:
> [UPGRADE] irb1.8 1.8.6.114-2 -> 1.8.7-2
> [UPGRADE] libdbm-ruby1.8 1.8.6.114-2 -> 1.8.7-2
> [UPGRADE] libgdbm-ruby1.8 1.8.6.114-2 -> 1.8.7-2
> [UPGRADE] libopenssl-ruby1.8 1.8.6.114-2 -> 1.8.7-2
> [UPGRADE] libreadline-ruby1.8 1.8.6.114-2 -> 1.8.7-2
> [UPGRADE] libruby1.8 1.8.6.114-2 -> 1.8.7-2
> [UPGRADE] libtcltk-ruby1.8 1.8.6.114-2 -> 1.8.7-2
> [UPGRADE] rdoc1.8 1.8.6.114-2 -> 1.8.7-2
> [UPGRADE] ri1.8 1.8.6.114-2 -> 1.8.7-2
> [UPGRADE] ruby1.8 1.8.6.114-2 -> 1.8.7-2
> [UPGRADE] ruby1.8-dev 1.8.6.114-2 -> 1.8.7-2
> [UPGRADE] ruby1.8-examples 1.8.6.114-2 -> 1.8.7-2
> 
> This report was generated after downgrade to version 1.8.6.114-2, so
> version of libruby1.8 in dependency list is version after downgrade.

Hi,

Could you try to find a relatively simple script that reproduces the
problem?
-- 
| Lucas Nussbaum
| lucas@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr             GPG: 1024D/023B3F4F |

Message #15 received at 485738@bugs.debian.org (full text, mbox, reply):

From: Blaž Lorger <blaz.lorger@triera.net>

To: Lucas Nussbaum <lucas@lucas-nussbaum.net>

Cc: 485738@bugs.debian.org

Subject: reproduction

Date: Wed, 11 Jun 2008 15:17:44 +0200

[Message part 1 (text/plain, inline)]

Apparently it is sufficient to upgrade packages libruby1.8,  ruby1.8 and 
ruby1.8-dev to encounter the bug.

It is possible that bug is actually caused only when you use libxml-ruby1.8.
Maybe it is worth mentioning that original script used libxml, but didn't fail 
while using libxml (line in script).

Here is script that reproduces the bug:

#!/usr/bin/env ruby

require 'xml/libxml'

i = 0;
while true
	doc = XML::Document.new;
	doc.root = XML::Node.new('gc-bug');
	i += 1;
	puts "***************** #{i} *********" if i%100 == 0;
end


And output on my computer:
$ ./gcbug.rb
***************** 100 *********
***************** 200 *********
***************** 300 *********
***************** 400 *********
***************** 500 *********
***************** 600 *********
***************** 700 *********
***************** 800 *********
***************** 900 *********
***************** 1000 *********
***************** 1100 *********
***************** 1200 *********
./gcbug.rb:8: [BUG] object allocation during garbage collection phase
ruby 1.8.7 (2008-05-31 patchlevel 0) [x86_64-linux]

Aborted

[gcbug.rb (application/x-ruby, attachment)]

Message #20 received at 485738@bugs.debian.org (full text, mbox, reply):

From: Blaž Lorger <blaz.lorger@triera.net>

To: Lucas Nussbaum <lucas@lucas-nussbaum.net>

Cc: 485738@bugs.debian.org

Subject: Re: reproduction

Date: Wed, 11 Jun 2008 15:23:28 +0200

Correction, this is simplest script that reproduces bug:

#!/usr/bin/env ruby

require 'xml/libxml'

i = 0;
while true
	XML::Document.new;
	i += 1;
	puts "***************** #{i} *********" if i%100 == 0;
end

Message #25 received at 485738@bugs.debian.org (full text, mbox, reply):

From: James Healy <jimmy@deefa.com>

To: 485738@bugs.debian.org

Subject: Not just libxml

Date: Thu, 12 Jun 2008 23:45:48 +1000

The following script that uses the ruby cairo bindings produces the same
error for me using 1.8.7-2. Is it maybe an issue with c bindings in
general?

#!/usr/bin/env ruby

require 'cairo'
require 'stringio'

i = 0;
while true
  output = StringIO.new
  surface = Cairo::PDFSurface.new(output, 100, 100)
  context = Cairo::Context.new(surface)
  i += 1;
  puts "***************** #{i} *********" if i%100 == 0;
end

-- James Healy <jimmy-at-deefa-dot-com>  Thu, 12 Jun 2008 23:44:16 +1000

Message #30 received at 485738@bugs.debian.org (full text, mbox, reply):

From: Lucas Nussbaum <lucas@lucas-nussbaum.net>

To: James Healy <jimmy@deefa.com>, 485738@bugs.debian.org

Subject: Re: Bug#485738: Not just libxml

Date: Thu, 12 Jun 2008 16:47:34 +0200

On 12/06/08 at 23:45 +1000, James Healy wrote:
> The following script that uses the ruby cairo bindings produces the same
> error for me using 1.8.7-2. Is it maybe an issue with c bindings in
> general?

Hi James,

We are going to upload a new version of Ruby to unstable soon
(1.8.7.37-1). We are just waiting for a transition to finish. Let's see
if it's fixed with this version, and then we can try to contact
upstream.

Lucas

Message #35 received at 485738@bugs.debian.org (full text, mbox, reply):

From: James Healy <jimmy@deefa.com>

To: Lucas Nussbaum <lucas@lucas-nussbaum.net>

Cc: 485738@bugs.debian.org

Subject: Re: Bug#485738: Not just libxml

Date: Fri, 13 Jun 2008 00:21:57 +1000

Lucas Nussbaum wrote:
> We are going to upload a new version of Ruby to unstable soon
> (1.8.7.37-1). We are just waiting for a transition to finish. Let's see
> if it's fixed with this version, and then we can try to contact
> upstream.

No probs. I've downgraded to 1.8.6 for the moment, so I'll wait until I
see the new package enter unstable and give it a go.

-- James Healy <jimmy-at-deefa-dot-com>  Fri, 13 Jun 2008 00:20:37 +1000

Message #40 received at 485738@bugs.debian.org (full text, mbox, reply):

From: Lucas Nussbaum <lucas@lucas-nussbaum.net>

To: Blaž Lorger <blaz.lorger@triera.net>, 485738@bugs.debian.org

Cc: akira@debian.org, daigo@debian.org

Subject: Re: Bug#485738: reproduction

Date: Wed, 18 Jun 2008 09:58:05 +0200

On 11/06/08 at 15:23 +0200, Blaž Lorger wrote:
> Correction, this is simplest script that reproduces bug:
> 
> #!/usr/bin/env ruby
> 
> require 'xml/libxml'
> 
> i = 0;
> while true
> 	XML::Document.new;
> 	i += 1;
> 	puts "***************** #{i} *********" if i%100 == 0;
> end

Thanks for the testcase. I reproduced the problem with 1.8.7.17. Arg.
I also rebuilt libxml-ruby to make sure it wasn't caused by a subtle ABI
change, but the problem is still there with a freshly build libxml-ruby.

Akira-san, Daigo-san, could one of you raise the issue on ruby-dev? Or
should I raise it on ruby-core?
-- 
| Lucas Nussbaum
| lucas@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr             GPG: 1024D/023B3F4F |

Message #45 received at 485738@bugs.debian.org (full text, mbox, reply):

From: Daigo Moriwaki <daigo@debian.org>

To: Lucas Nussbaum <lucas@lucas-nussbaum.net>, 485738@bugs.debian.org

Cc: Blaž Lorger <blaz.lorger@triera.net>, akira@debian.org, daigo@debian.org

Subject: Re: Bug#485738: reproduction

Date: Wed, 18 Jun 2008 22:28:38 +0900

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

Lucas Nussbaum wrote:
> Akira-san, Daigo-san, could one of you raise the issue on ruby-dev? Or
> should I raise it on ruby-core?

I have just reported this issue to ruby-dev and wait for a reply.

Daigo

- --
Daigo Moriwaki
daigo at debian dot org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIWQ2GNcPj+ukc0lARAgw6AJ9sngCSyTxdrAz8rD4XjpmDb14S9ACfdjVL
4L4aJHdybhNO1+28YkZVU/8=
=7uNt
-----END PGP SIGNATURE-----

Message #50 received at 485738@bugs.debian.org (full text, mbox, reply):

From: Daigo Moriwaki <daigo@debian.org>

To: Daigo Moriwaki <daigo@debian.org>, 485738@bugs.debian.org

Cc: Lucas Nussbaum <lucas@lucas-nussbaum.net>, Blaž Lorger <blaz.lorger@triera.net>, akira@debian.org

Subject: Re: Bug#485738: reproduction

Date: Wed, 18 Jun 2008 23:24:27 +0900

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

Daigo Moriwaki wrote:
> Lucas Nussbaum wrote:
>> Akira-san, Daigo-san, could one of you raise the issue on ruby-dev? Or
>> should I raise it on ruby-core?
> 
> I have just reported this issue to ruby-dev and wait for a reply.

A guy I know replied. It is up to LibXml which is doing wrong. As the error
message says, object allocation by LibXml should not be performed during GC.

As of ruby 1.8.7, it exactly checks this issue and will report the bug message
if it finds.

Daigo

- --
Daigo Moriwaki
daigo at debian dot org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIWRqbNcPj+ukc0lARArGZAJ907oA2JHvpzeUwRQVNTa3k55B+QQCgwU/1
2fh/DpwvUNJJ5e0tglrfqaU=
=MXZd
-----END PGP SIGNATURE-----

Message #55 received at 485738@bugs.debian.org (full text, mbox, reply):

From: Lucas Nussbaum <lucas@lucas-nussbaum.net>

To: Daigo Moriwaki <daigo@debian.org>

Cc: 485738@bugs.debian.org, Blaž Lorger <blaz.lorger@triera.net>, akira@debian.org

Subject: Re: Bug#485738: reproduction

Date: Wed, 18 Jun 2008 16:40:18 +0200

On 18/06/08 at 23:24 +0900, Daigo Moriwaki wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Daigo Moriwaki wrote:
> > Lucas Nussbaum wrote:
> >> Akira-san, Daigo-san, could one of you raise the issue on ruby-dev? Or
> >> should I raise it on ruby-core?
> > 
> > I have just reported this issue to ruby-dev and wait for a reply.
> 
> A guy I know replied. It is up to LibXml which is doing wrong. As the error
> message says, object allocation by LibXml should not be performed during GC.
> 
> As of ruby 1.8.7, it exactly checks this issue and will report the bug message
> if it finds.

Apparently the cairo bindings have the same problem....

I hope it's limited to cairo + libxml!
-- 
| Lucas Nussbaum
| lucas@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr             GPG: 1024D/023B3F4F |

Message #60 received at 485738@bugs.debian.org (full text, mbox, reply):

From: James Healy <jimmy@deefa.com>

To: Lucas Nussbaum <lucas@lucas-nussbaum.net>, 485738@bugs.debian.org

Subject: Re: Bug#485738: reproduction

Date: Thu, 19 Jun 2008 15:59:59 +1000

Lucas Nussbaum wrote:
> > A guy I know replied. It is up to LibXml which is doing wrong. As the error
> > message says, object allocation by LibXml should not be performed during GC.
> > 
> > As of ruby 1.8.7, it exactly checks this issue and will report the bug message
> > if it finds.
> 
> Apparently the cairo bindings have the same problem....
> 
> I hope it's limited to cairo + libxml!

OK. Annoying in some ways, but nice to have narrowed the source down
somewhat. I'll see if I can get in touch with the rcairo developer.

My b.d.o foo is weak, otherwise I'd clone the bug and reassign it to the
right packages. Sorry!

-- James Healy <jimmy-at-deefa-dot-com>  Thu, 19 Jun 2008 15:56:44 +1000

Message #65 received at 485738@bugs.debian.org (full text, mbox, reply):

From: James Healy <jimmy@deefa.com>

To: Lucas Nussbaum <lucas@lucas-nussbaum.net>, 485738@bugs.debian.org

Subject: Re: Bug#485738: reproduction

Date: Thu, 19 Jun 2008 17:31:55 +1000

Lucas Nussbaum wrote:
> > A guy I know replied. It is up to LibXml which is doing wrong. As the error
> > message says, object allocation by LibXml should not be performed during GC.
> > 
> > As of ruby 1.8.7, it exactly checks this issue and will report the bug message
> > if it finds.
> 
> Apparently the cairo bindings have the same problem....
> 
> I hope it's limited to cairo + libxml!

For anyone doing further research, here's the bug on rubyforge that
prompted the addition of the check in 1.8.7:

http://rubyforge.org/tracker/index.php?func=detail&aid=11859&group_id=426&atid=1698

-- James Healy <jimmy-at-deefa-dot-com>  Thu, 19 Jun 2008 17:28:00 +1000

Message #78 received at 487204@bugs.debian.org (full text, mbox, reply):

From: James Healy <jimmy@deefa.com>

To: 487204@bugs.debian.org

Subject: Upstream

Date: Fri, 20 Jun 2008 16:39:06 +1000

I've been in touch with the upstream maintainer about this, and it has
been fixed in CVS HEAD. Unfortunately, he hasn't indicated when he plans
to cut a new release.

This bug affects anyone who renders a cairo surface to an object in
memory (like a StringIO), and on 1.8.7.

-- James Healy <jimmy-at-deefa-dot-com>  Fri, 20 Jun 2008 16:27:17 +1000

Message #83 received at 487204@bugs.debian.org (full text, mbox, reply):

From: Lucas Nussbaum <lucas@lucas-nussbaum.net>

To: James Healy <jimmy@deefa.com>, 487204@bugs.debian.org

Subject: Re: [DRE-maint] Bug#487204: Upstream

Date: Fri, 20 Jun 2008 09:24:11 +0200

On 20/06/08 at 16:39 +1000, James Healy wrote:
> I've been in touch with the upstream maintainer about this, and it has
> been fixed in CVS HEAD. Unfortunately, he hasn't indicated when he plans
> to cut a new release.

Actually, we don't need a new release, just a patch :-)
-- 
| Lucas Nussbaum
| lucas@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr             GPG: 1024D/023B3F4F |

Message #88 received at 487204@bugs.debian.org (full text, mbox, reply):

From: Antonio Terceiro <terceiro@softwarelivre.org>

To: Lucas Nussbaum <lucas@lucas-nussbaum.net>

Cc: James Healy <jimmy@deefa.com>, 487204@bugs.debian.org

Subject: libcairo-ruby: backported fix from upstream CVS (was "Bug#487204: Upstream")

Date: Sun, 3 Aug 2008 20:48:38 -0300

[Message part 1 (text/plain, inline)]

Lucas Nussbaum escreveu isso aí:
> On 20/06/08 at 16:39 +1000, James Healy wrote:
> > I've been in touch with the upstream maintainer about this, and it has
> > been fixed in CVS HEAD. Unfortunately, he hasn't indicated when he plans
> > to cut a new release.
> 
> Actually, we don't need a new release, just a patch :-)

Since Lenny is frozen, by now we should not upload a new release,
either. I backported the upstream fix from CVS, and created a branch off
1.5.1-1 in pkg-ruby-extras team's repository
(packages/libcairo-ruby/branches/1.5.1-1+bug487204).

I tested with two applications that depend on libcairo-ruby1.8, packages
treil and edit-json (this one depends indirectly on libcairo-ruby1.8
through libgtk2-ruby1.8), and they seemed to work ok. The script that
demonstrated the problem also run ok, despite the infinite loop. ;)

Lucas, could you please check the package? It's here:

http://svn.debian.org/wsvn/pkg-ruby-extras/packages/libcairo-ruby/branches/1.5.1-1+bug487204/

-- 
Antonio Terceiro <terceiro@softwarelivre.org>
http://people.softwarelivre.org/~terceiro/
GnuPG ID: 0F9CB28F

[signature.asc (application/pgp-signature, inline)]

Message #95 received at 487204-done@bugs.debian.org (full text, mbox, reply):

From: Paul van Tilburg <paulvt@debian.org>

To: 487204-done@bugs.debian.org

Subject: fixed in libcairo-ruby 1.6.3-1

Date: Sun, 10 Aug 2008 15:46:12 +0200

Source: libcairo-ruby
Source-Version: 1.6.3-1

This bug was fixed by new upstream release 1.6.3 targetted towards
fixing precisely this bug.  I consider it closed by the upload of 1.6.3.

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

Format: 1.8
Date: Sun, 10 Aug 2008 15:24:03 +0200
Source: libcairo-ruby
Binary: libcairo-ruby libcairo-ruby1.8 libcairo-ruby1.9
Architecture: source all amd64
Version: 1.6.3-1
Distribution: unstable
Urgency: low
Maintainer: Paul van Tilburg <paulvt@debian.org>
Changed-By: Paul van Tilburg <paulvt@debian.org>
Description: 
 libcairo-ruby - Cairo bindings for the Ruby language
 libcairo-ruby1.8 - Cairo bindings for the Ruby language
 libcairo-ruby1.9 - Cairo bindings for the Ruby language
Changes: 
 libcairo-ruby (1.6.3-1) unstable; urgency=low
 .
   [ Paul van Tilburg ]
   * New upstream release.
   * Dropped patch 01_fix-ftools-extconf: fixed upsteam.
   * Added patch 01_fix-st.h-ruby1.9-paths.
   * Bumped build-dependancy on libcairo2 to >= 1.6.0.
   * Fixed the too long line in debian/copyright.
   * Bumped standards version to 3.8.0; no changes required.
 .
   [ Lucas Nussbaum ]
   * Build-depend on r-p-t >= 0.14, to fix the ruby1.9
     libs install problem.
Checksums-Sha1: 
 70b5f295b4c3aa8c84b029c33bbb74f0224aefc0 1437 libcairo-ruby_1.6.3-1.dsc
 4d158b2650fd46c4b766b9a9167b6086cb7773ed 222796 libcairo-ruby_1.6.3.orig.tar.gz
 6e1b7fb47c78c47f70a72b83f27036ce09e6e276 4494 libcairo-ruby_1.6.3-1.diff.gz
 775b57cb98eabd4c1f85985cd78543660facdfe6 23112 libcairo-ruby_1.6.3-1_all.deb
 630a02ccb74fb398197f72c3a64bdaf8a7c246dc 75890
libcairo-ruby1.8_1.6.3-1_amd64.deb
 1c876eb037b09eadceeaa9c66adbd3c5c306a921 76768
libcairo-ruby1.9_1.6.3-1_amd64.deb
Checksums-Sha256: 
 d30dc16d39a585e964cc886fef22df9d55c057e026d61fce935a4c86d337aa67 1437
libcairo-ruby_1.6.3-1.dsc
 c4b7f82b7b0e6109b3b906ae1d8ac82b2b183b2ed25369d374e2fa4b1242a8f8 222796
libcairo-ruby_1.6.3.orig.tar.gz
 3626130f8ef712aab61414adf32af998abaffb8dbf121c54ab0ac84c88c7b2e6 4494
libcairo-ruby_1.6.3-1.diff.gz
 e967890ed392ae83febdfc84168a975880c413ddba03ff182462022cb8797a17 23112
libcairo-ruby_1.6.3-1_all.deb
 3bb3f087d8a7b1251fd825b572329a2a3a086ac8b73e9e31c1c4433bce5c594d 75890
libcairo-ruby1.8_1.6.3-1_amd64.deb
 5c98b5b89f2413d9b069b4428570710bc8a711e14f0eb433c846ef2be0138c7c 76768
libcairo-ruby1.9_1.6.3-1_amd64.deb
Files: 
 2675ded761e25e46e53a4e206f4f1892 1437 libs optional libcairo-ruby_1.6.3-1.dsc
 d7f798ab145f417e734d9d47f5adeb7e 222796 libs optional
libcairo-ruby_1.6.3.orig.tar.gz
 9797cf501cad579e79d3b1311febc6cd 4494 libs optional
libcairo-ruby_1.6.3-1.diff.gz
 ff94579ccd9aeaf835d7714652832e3b 23112 libs optional
libcairo-ruby_1.6.3-1_all.deb
 8bc2b956cbfd997e2684378ba607856a 75890 libs optional
libcairo-ruby1.8_1.6.3-1_amd64.deb
 1183225704842fe592022a22968ac9bb 76768 libs optional
libcairo-ruby1.9_1.6.3-1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkie7TYACgkQJBBhylAGQYFgeACfSi+6OJJYggDOSV5OkTHUUp4N
b20An1zYbUekiWxt2JCpbScem0NdFukS
=BvPw
-----END PGP SIGNATURE-----

Message #100 received at 487204-close@bugs.debian.org (full text, mbox, reply):

From: Michael Schutte <m.schutte.jr@gmail.com>

To: 487204-close@bugs.debian.org

Subject: Bug#487204: fixed in libcairo-ruby 1.5.1-1+lenny1

Date: Tue, 26 Aug 2008 21:02:40 +0000

Source: libcairo-ruby
Source-Version: 1.5.1-1+lenny1

We believe that the bug you reported is fixed in the latest version of
libcairo-ruby, which is due to be installed in the Debian FTP archive:

libcairo-ruby1.8_1.5.1-1+lenny1_amd64.deb
  to pool/main/libc/libcairo-ruby/libcairo-ruby1.8_1.5.1-1+lenny1_amd64.deb
libcairo-ruby1.9_1.5.1-1+lenny1_amd64.deb
  to pool/main/libc/libcairo-ruby/libcairo-ruby1.9_1.5.1-1+lenny1_amd64.deb
libcairo-ruby_1.5.1-1+lenny1.diff.gz
  to pool/main/libc/libcairo-ruby/libcairo-ruby_1.5.1-1+lenny1.diff.gz
libcairo-ruby_1.5.1-1+lenny1.dsc
  to pool/main/libc/libcairo-ruby/libcairo-ruby_1.5.1-1+lenny1.dsc
libcairo-ruby_1.5.1-1+lenny1_all.deb
  to pool/main/libc/libcairo-ruby/libcairo-ruby_1.5.1-1+lenny1_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 487204@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Schutte <m.schutte.jr@gmail.com> (supplier of updated libcairo-ruby package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


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

Format: 1.8
Date: Wed, 20 Aug 2008 12:06:59 +0200
Source: libcairo-ruby
Binary: libcairo-ruby libcairo-ruby1.8 libcairo-ruby1.9
Architecture: source all amd64
Version: 1.5.1-1+lenny1
Distribution: testing-proposed-updates
Urgency: low
Maintainer: Paul van Tilburg <paulvt@debian.org>
Changed-By: Michael Schutte <m.schutte.jr@gmail.com>
Description: 
 libcairo-ruby - Cairo bindings for the Ruby language
 libcairo-ruby1.8 - Cairo bindings for the Ruby language
 libcairo-ruby1.9 - Cairo bindings for the Ruby language
Closes: 487204
Changes: 
 libcairo-ruby (1.5.1-1+lenny1) testing-proposed-updates; urgency=low
 .
   [ Antonio Terceiro ]
   * Backported change from CVS (r1.32-> r1.33, src/rb_cairo_surface.rb) to fix
     object allocation during garbage collection phase. (Closes: #487204).
 .
   [ Michael Schutte ]
   * Prepare upload to testing-proposed-updates.
   * Bump Standards-Version to 3.8.0, no changes needed.
   * Build-depend on r-p-t >= 0.14, to fix the ruby1.9 libs install problem.
   * Add myself to Uploaders.
Checksums-Sha1: 
 6a04183a08466c092c419808316e52b0fa5b03c1 1550 libcairo-ruby_1.5.1-1+lenny1.dsc
 0c45665dab117fb1c35027f802a11f14d2391c66 5150 libcairo-ruby_1.5.1-1+lenny1.diff.gz
 8fe5a09978309e090685f81490a66f69038bcb60 20990 libcairo-ruby_1.5.1-1+lenny1_all.deb
 f1b8ec9fc283d897828b53f77aefc17b94d66ce9 69418 libcairo-ruby1.8_1.5.1-1+lenny1_amd64.deb
 8dd84c38235cbfd8ebcdedb4e58599946545424f 70184 libcairo-ruby1.9_1.5.1-1+lenny1_amd64.deb
Checksums-Sha256: 
 8ce978f319e53bc1f78a7e0b0954797c5200e5818160896a564fde39ed173171 1550 libcairo-ruby_1.5.1-1+lenny1.dsc
 62f37f6bb6f3021f3a4b88172ef4f99ce3204e0a974dd7fb3d7c2a7c0883792e 5150 libcairo-ruby_1.5.1-1+lenny1.diff.gz
 88b80ac1af43fdaa1b9fdbdf992048287ccdb3ac4ca93f9af4034fcb92009429 20990 libcairo-ruby_1.5.1-1+lenny1_all.deb
 835081c44f627a786122c61f359f3c726f7948046296bffd83ee38a239a6a94f 69418 libcairo-ruby1.8_1.5.1-1+lenny1_amd64.deb
 7f9792f60b4b410c374e3c671f8ee45ddd53010d82e52a2099a8c9f8535b39b9 70184 libcairo-ruby1.9_1.5.1-1+lenny1_amd64.deb
Files: 
 6ccd06a82756e07c8ea1bb27446b1732 1550 libs optional libcairo-ruby_1.5.1-1+lenny1.dsc
 ab8ce169e0b1e12874d329152c56ea5f 5150 libs optional libcairo-ruby_1.5.1-1+lenny1.diff.gz
 7e594994bf51f2e70dc93c4cef508c51 20990 libs optional libcairo-ruby_1.5.1-1+lenny1_all.deb
 537a4ef17bebe8d434e4d30a01234631 69418 libs optional libcairo-ruby1.8_1.5.1-1+lenny1_amd64.deb
 49572e0a7596192a0cd5335023453bef 70184 libs optional libcairo-ruby1.9_1.5.1-1+lenny1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAki0ZLYACgkQ2A7zWou1J69NbwCfQnXoXkJr9jlrCsbWHqGVp6jS
uNUAn3mQNRoKINUphZSwtCtXU1DrE6iQ
=vTZ+
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.