librmagick-ruby1.8: librmagick-ruby unusable after upgrade to imagemagick-6.0.7.1

[Debian Bug Importer]

Automatically imported from Debian bug report #271673 http://bugs.debian.org/271673

[Mike Williams (mdub)]

A rebuild is required to fix the problem.

librmagick-ruby_1.6.0-2 is available at

    http://www.dogbiscuit.org/mdub/software/debian/unstable/

and is waiting for sponsor upload.

[Steve Langasek (vorlon)]

Mike,

This is not a bug that should be swept under the rug by rebuilding
librmagick-ruby. If newer versions of imagemagick do not provide the
same binary interface as earlier versions, this is a grave bug in
imagemagick that needs to be looked into, lest we release sarge with
subtly-broken packages that go unnoticed.

Which was the last version of imagemagick you had installed that *did*
work with the librmagick-ruby currently in the archive?

Thanks,
--
Steve Langasek
postmodern programmer

[Daniel Kobras (kobras)]

reassign 271673 libmagick6,librmagick-ruby1.8
thanks

On Tue, Sep 14, 2004 at 04:14:19PM -0700, Steve Langasek wrote:
> This is not a bug that should be swept under the rug by rebuilding
> librmagick-ruby. If newer versions of imagemagick do not provide the
> same binary interface as earlier versions, this is a grave bug in
> imagemagick that needs to be looked into, lest we release sarge with
> subtly-broken packages that go unnoticed.
>
> Which was the last version of imagemagick you had installed that *did*
> work with the librmagick-ruby currently in the archive?

[Mentioned most of it on irc already, but let's keep it on record in the
 BTS as well.]

The breakage was caused by the progress_meter changes that make up the
biggest part of the differences between 6.0.6.2 and 6.0.7.1. New member
variables were added to the Image and ImageInfo structs, so offsets
changes for all members declared later on. Please do not upload a new
librmagick-ruby--the mess is in imagemagick itself, and that where we'll
have to clean it up. I'm leaving the bug co-assigned to librmagick-ruby
in an attempt to avoid duplicate reports about the breakage.

Regards,

Daniel.

[Debian Bug Importer (debzilla)]

Automatically imported from Debian bug report #271673 http://bugs.debian.org/271673

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Tue, 14 Sep 2004 23:26:00 +1000
From: Mike Williams <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: librmagick-ruby1.8: librmagick-ruby unusable after upgrade to
 imagemagick-6.0.7.1

Package: librmagick-ruby1.8
Version: 1.6.0-1
Severity: grave
Justification: renders package unusable

The upgrade to imagemagick-6.0.7.1-1 has made RMagick unusable; it appears
to chop the first four characters off image filenames when attempting to
load them:

$ ruby -rRMagick -e 'Magick::Image.read("apple-red.png")'
-e:1:in `read': unable to open image `e-red.png': No such file or directory:
(Magick::ImageMagickError)

$ ruby -rRMagick -e 'Magick::Image.read("banana.png")'
-e:1:in `read': unable to open image `na.png': No such file or directory:
(Magick::ImageMagickError)

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.6
Locale: LANG=C, LC_CTYPE=C

Versions of packages librmagick-ruby1.8 depends on:
ii libbz2-1.0 1.0.2-1 A high-quality block-sorting file
ii libc6 2.3.2.ds1-16 GNU C Library: Shared libraries an
ii libdps1 4.3.0.dfsg.1-6 Display PostScript (DPS) client li
ii libfreetype6 2.1.7-2.2 FreeType 2 font engine, shared lib
ii libice6 4.3.0.dfsg.1-6 Inter-Client Exchange library
ii libjasper-1.701-1 1.701.0-2 The JasPer JPEG-2000 runtime libra
ii libjpeg62 6b-9 The Independent JPEG Group's JPEG
ii liblcms1 1.12-2.1 Color management library
ii libmagick6 5:6.0.7.1-1 Image manipulation library
ii libpng12-0 1.2.5.0-7 PNG library - runtime
ii libruby1.8 1.8.1+1.8.2pre2-3 Libraries necessary to run the Rub
ii libsm6 4.3.0.dfsg.1-6 X Window System Session Management
ii libtiff4 3.6.1-1.1 Tag Image File Format library
ii libx11-6 4.3.0.dfsg.1-6 X Window System protocol client li
ii libxext6 4.3.0.dfsg.1-6 X Window System miscellaneous exte
ii libxml2 2.6.11-3 GNOME XML library
ii libxt6 4.3.0.dfsg.1-6 X Toolkit Intrinsics
ii xlibs 4.3.0.dfsg.1-6 X Window System client libraries m
ii zlib1g 1:1.2.1.1-7 compression library - runtime

-- no debconf information

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 15 Sep 2004 00:15:01 +1000
From: Mike Williams <email address hidden>
To: <email address hidden>
Subject: librmagick-ruby_1.6.0-2 available

A rebuild is required to fix the problem.

librmagick-ruby_1.6.0-2 is available at

    http://www.dogbiscuit.org/mdub/software/debian/unstable/

and is waiting for sponsor upload.

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Tue, 14 Sep 2004 16:14:19 -0700
From: Steve Langasek <email address hidden>
To: <email address hidden>
Subject: Re: librmagick-ruby1.8: librmagick-ruby unusable after upgrade to imagemagick-6.0.7.1

--udcq9yAoWb9A4FsZ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Mike,

This is not a bug that should be swept under the rug by rebuilding
librmagick-ruby. If newer versions of imagemagick do not provide the
same binary interface as earlier versions, this is a grave bug in
imagemagick that needs to be looked into, lest we release sarge with
subtly-broken packages that go unnoticed.

Which was the last version of imagemagick you had installed that *did*
work with the librmagick-ruby currently in the archive?

Thanks,
--=20
Steve Langasek
postmodern programmer

--udcq9yAoWb9A4FsZ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

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

iD8DBQFBR3tIKN6ufymYLloRAqD6AKCUVgrV4nxgwdVVPfMzrsKNc69yhgCguKgT
Wi0/3N6k7/jlupT9X8AgQu4=
=/NtS
-----END PGP SIGNATURE-----

--udcq9yAoWb9A4FsZ--

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 15 Sep 2004 02:59:46 +0200
From: Daniel Kobras <email address hidden>
To: <email address hidden>
Cc: Steve Langasek <email address hidden>
Subject: Re: librmagick-ruby1.8: librmagick-ruby unusable after upgrade to imagemagick-6.0.7.1

reassign 271673 libmagick6,librmagick-ruby1.8
thanks

On Tue, Sep 14, 2004 at 04:14:19PM -0700, Steve Langasek wrote:
> This is not a bug that should be swept under the rug by rebuilding
> librmagick-ruby. If newer versions of imagemagick do not provide the
> same binary interface as earlier versions, this is a grave bug in
> imagemagick that needs to be looked into, lest we release sarge with
> subtly-broken packages that go unnoticed.
>
> Which was the last version of imagemagick you had installed that *did*
> work with the librmagick-ruby currently in the archive?

[Mentioned most of it on irc already, but let's keep it on record in the
 BTS as well.]

The breakage was caused by the progress_meter changes that make up the
biggest part of the differences between 6.0.6.2 and 6.0.7.1. New member
variables were added to the Image and ImageInfo structs, so offsets
changes for all members declared later on. Please do not upload a new
librmagick-ruby--the mess is in imagemagick itself, and that where we'll
have to clean it up. I'm leaving the bug co-assigned to librmagick-ruby
in an attempt to avoid duplicate reports about the breakage.

Regards,

Daniel.

[Thom May (thombot)]

We only have libmagick 6.0.2.5, so we can ignore this.

[Mike Williams (mdub)]

Daniel Kobras wrote:

>The breakage was caused by the progress_meter changes that make up the
>biggest part of the differences between 6.0.6.2 and 6.0.7.1. New member
>variables were added to the Image and ImageInfo structs, so offsets
>changes for all members declared later on. Please do not upload a new
>librmagick-ruby--the mess is in imagemagick itself, and that where we'll
>have to clean it up. I'm leaving the bug co-assigned to librmagick-ruby
>in an attempt to avoid duplicate reports about the breakage.
>
>
Daniel, Steve, thanks for your input. I'll hold off uploading another
librmagick-ruby, as you say.

Tim Hunter (RMagick author) echoes your comment:

In this particular case, the ImageMagick folks changed a structure that is
shared between IM and C applications that link with IM. Probably they
shouldn't have but there's no stopping them. I have to test against every
release of IM to see if some API has changed since the last release. And
Christy will change the API on any release boundary. They had this under
control for a while but since 6.0.0 they've gone back to their old bad
habits.

--
cheers, MikeW http://www.dogbiscuit.org/mdub/

[Mike Williams (mdub)]

Steve Langasek wrote:

>Which was the last version of imagemagick you had installed that *did*
>work with the librmagick-ruby currently in the archive?
>
>
imagemagick_6.0.6.2-1 + librmagick-ruby_1.6.0-1 works fine.

I haven't tested with imagemagick_6.0.6.2-1.2.

--
cheers, MikeW

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 15 Sep 2004 19:21:10 +1000
From: Mike Williams <email address hidden>
To: Daniel Kobras <email address hidden>, <email address hidden>
Cc: Steve Langasek <email address hidden>,
 Tim Hunter <email address hidden>
Subject: Re: Bug#271673: librmagick-ruby1.8: librmagick-ruby unusable after
 upgrade to imagemagick-6.0.7.1

Daniel Kobras wrote:

>The breakage was caused by the progress_meter changes that make up the
>biggest part of the differences between 6.0.6.2 and 6.0.7.1. New member
>variables were added to the Image and ImageInfo structs, so offsets
>changes for all members declared later on. Please do not upload a new
>librmagick-ruby--the mess is in imagemagick itself, and that where we'll
>have to clean it up. I'm leaving the bug co-assigned to librmagick-ruby
>in an attempt to avoid duplicate reports about the breakage.
>
>
Daniel, Steve, thanks for your input. I'll hold off uploading another
librmagick-ruby, as you say.

Tim Hunter (RMagick author) echoes your comment:

In this particular case, the ImageMagick folks changed a structure that is
shared between IM and C applications that link with IM. Probably they
shouldn't have but there's no stopping them. I have to test against every
release of IM to see if some API has changed since the last release. And
Christy will change the API on any release boundary. They had this under
control for a while but since 6.0.0 they've gone back to their old bad
habits.

--
cheers, MikeW http://www.dogbiscuit.org/mdub/

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 15 Sep 2004 19:26:47 +1000
From: Mike Williams <email address hidden>
To: Steve Langasek <email address hidden>, <email address hidden>
Subject: Re: Bug#271673: librmagick-ruby1.8: librmagick-ruby unusable after
 upgrade to imagemagick-6.0.7.1

Steve Langasek wrote:

>Which was the last version of imagemagick you had installed that *did*
>work with the librmagick-ruby currently in the archive?
>
>
imagemagick_6.0.6.2-1 + librmagick-ruby_1.6.0-1 works fine.

I haven't tested with imagemagick_6.0.6.2-1.2.

--
cheers, MikeW

[Daniel Kobras (kobras)]

On Wed, Sep 15, 2004 at 02:59:46AM +0200, Daniel Kobras wrote:
> On Tue, Sep 14, 2004 at 04:14:19PM -0700, Steve Langasek wrote:
> > This is not a bug that should be swept under the rug by rebuilding
> > librmagick-ruby. If newer versions of imagemagick do not provide the
> > same binary interface as earlier versions, this is a grave bug in
> > imagemagick that needs to be looked into, lest we release sarge with
> > subtly-broken packages that go unnoticed.
>
> The breakage was caused by the progress_meter changes that make up the
> biggest part of the differences between 6.0.6.2 and 6.0.7.1. New member
> variables were added to the Image and ImageInfo structs, so offsets
> changes for all members declared later on. Please do not upload a new
> librmagick-ruby--the mess is in imagemagick itself, and that where we'll
> have to clean it up. I'm leaving the bug co-assigned to librmagick-ruby
> in an attempt to avoid duplicate reports about the breakage.

Ryuici, sorry for yet-again stepping on your toes, but this issue needs
to be addressed urgently. Otherwise we end up with packages compiled
against binary incompatible versions of imagemagick in the archive. I
have therefore prepared an NMU roughly the same way I did last December
when we faced a similar situation: I'll re-upload version 6.0.6.2 with a
bumped epoch, based on the last known-good 6.0.6.2-1.2. Some bugs were
fixed in 6.0.7.1, so in order not to cause regressions, I've selectively
pulled a handful of bugfixes from 6.0.7.1 and included them in the
Debian diff. Judging from the upstream changelog, I must have missed a
few fixes in the backport that I couldn't clearly identify, and I only
applied changes that looked safe enough as to not introduce new
breakage. (I've also removed the file magick/-MP that seems to have
slipped into the previous Debian diffs by mistake.) A full diff of the
changes I performed is attached. To keep it small, it's diffed against
6.0.6.2-1.2 rather than 6.0.7.1-1.

It's important that the new upload makes it into sarge as soon as
possible. Upstream has announced a new 6.0.8 release with bumped soname
to fix this error. This would require a rebuild of all packages that
depend on imagemagick, so please do not upload this version right away.
Please hold it back until 6.0.6.2-1.3 makes it into testing, or even
better until after sarge has been released.

Regards,

Daniel.

[Daniel Kobras (kobras)]

tag 271673 + fixed

quit

This message was generated automatically in response to a
non-maintainer upload. The .changes file follows.

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

Format: 1.7
Date: Wed, 15 Sep 2004 18:25:50 +0200
Source: imagemagick
Binary: perlmagick libmagick++6-dev libmagick6-dev libmagick6 imagemagick libmagick++6
Architecture: source i386
Version: 6:6.0.6.2-1.3
Distribution: unstable
Urgency: high
Maintainer: Daniel Kobras <email address hidden>
Changed-By: Daniel Kobras <email address hidden>
Description:
 imagemagick - Image manipulation programs
 libmagick++6 - The object-oriented C++ API to the ImageMagick library
 libmagick++6-dev - The object-oriented C++ API to the ImageMagick library--developme
 libmagick6 - Image manipulation library
 libmagick6-dev - Image manipulation library -- development
 perlmagick - A perl interface to the libMagick graphics routines
Closes: 271673
Changes:
 imagemagick (6:6.0.6.2-1.3) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Raise epoch and revert back to 6.0.6.2 because the progress_meter
     changes in 6.0.7.1 broke binary compatibility by mistake.
     Closes: #271673
   * Retain maintainer changes from 6.0.7.1-1 upload.
   * Retain select bugfixes from 6.0.7.1 version:
     + PerlMagick/Magick.xs: Fix crashes in Profile if name option is unset.
     + utilities/miff.4: Fix header information in man page.
     + magick/annotate.c: Proper exception handling.
     + magick/blob.c: Do not crash when syncing a bogus file.
     + magick/error.h: Remove bogus format attribute from ExceptionType to
       silence compiler warnings.
     + magick/locale.c: Handle NULL locale data.
   * debian/README.Debian: Remove obsolete comment about lzw availability.
Files:
 882e50bbbf11946ef8feae016e3e1178 878 graphics optional imagemagick_6.0.6.2-1.3.dsc
 477a361ba0154cc2423726fab4a3f57c 6824001 graphics optional imagemagick_6.0.6.2.orig.tar.gz
 643d6198308be66071ce131b587e67cc 135472 graphics optional imagemagick_6.0.6.2-1.3.diff.gz
 76d80befec92e120bcdceb2ba62299a5 1464030 graphics optional imagemagick_6.0.6.2-1.3_i386.deb
 6667979bac7b07413d67946983369554 1167696 libs optional libmagick6_6.0.6.2-1.3_i386.deb
 6f66ca63368290c5a3e7c4665f121de7 1502088 libdevel optional libmagick6-dev_6.0.6.2-1.3_i386.deb
 078d6c9eb3e28367c4e7b2fe66717439 163474 libs optional libmagick++6_6.0.6.2-1.3_i386.deb
 1d831c6c3637a89847c0ce698bb1c2f1 207512 libdevel optional libmagick++6-dev_6.0.6.2-1.3_i386.deb
 b37619cdeaa8c0c6685f3febed0be150 141676 perl optional perlmagick_6.0.6.2-1.3_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFBSHg/pOKIA4m/fisRAk2GAKCzwpms5aIsS8w7UvzZlKy5Bi7A3ACgvQmO
Notnf8tk6BYAU70fllQUvEs=
=ZRYK
-----END PGP SIGNATURE-----

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 15 Sep 2004 19:06:32 +0200
From: Daniel Kobras <email address hidden>
To: <email address hidden>, Steve Langasek <email address hidden>
Subject: Re: librmagick-ruby1.8: librmagick-ruby unusable after upgrade to imagemagick-6.0.7.1

--C7zPtVaVf+AK4Oqc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Wed, Sep 15, 2004 at 02:59:46AM +0200, Daniel Kobras wrote:
> On Tue, Sep 14, 2004 at 04:14:19PM -0700, Steve Langasek wrote:
> > This is not a bug that should be swept under the rug by rebuilding
> > librmagick-ruby. If newer versions of imagemagick do not provide the
> > same binary interface as earlier versions, this is a grave bug in
> > imagemagick that needs to be looked into, lest we release sarge with
> > subtly-broken packages that go unnoticed.
>
> The breakage was caused by the progress_meter changes that make up the
> biggest part of the differences between 6.0.6.2 and 6.0.7.1. New member
> variables were added to the Image and ImageInfo structs, so offsets
> changes for all members declared later on. Please do not upload a new
> librmagick-ruby--the mess is in imagemagick itself, and that where we'll
> have to clean it up. I'm leaving the bug co-assigned to librmagick-ruby
> in an attempt to avoid duplicate reports about the breakage.

Ryuici, sorry for yet-again stepping on your toes, but this issue needs
to be addressed urgently. Otherwise we end up with packages compiled
against binary incompatible versions of imagemagick in the archive. I
have therefore prepared an NMU roughly the same way I did last December
when we faced a similar situation: I'll re-upload version 6.0.6.2 with a
bumped epoch, based on the last known-good 6.0.6.2-1.2. Some bugs were
fixed in 6.0.7.1, so in order not to cause regressions, I've selectively
pulled a handful of bugfixes from 6.0.7.1 and included them in the
Debian diff. Judging from the upstream changelog, I must have missed a
few fixes in the backport that I couldn't clearly identify, and I only
applied changes that looked safe enough as to not introduce new
breakage. (I've also removed the file magick/-MP that seems to have
slipped into the previous Debian diffs by mistake.) A full diff of the
changes I performed is attached. To keep it small, it's diffed against
6.0.6.2-1.2 rather than 6.0.7.1-1.

It's important that the new upload makes it into sarge as soon as
possible. Upstream has announced a new 6.0.8 release with bumped soname
to fix this error. This would require a rebuild of all packages that
depend on imagemagick, so please do not upload this version right away.
Please hold it back until 6.0.6.2-1.3 makes it into testing, or even
better until after sarge has been released.

Regards,

Daniel.

--C7zPtVaVf+AK4Oqc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline; filename="nmu.diff"

diff -u imagemagick-6.0.6.2/magick/error.h imagemagick-6.0.6.2/magick/error.h
--- imagemagick-6.0.6.2/magick/error.h
+++ imagemagick-6.0.6.2/magick/error.h
@@ -82,8 +82,7 @@
   SetExceptionInfo(ExceptionInfo *,ExceptionType),
   ThrowException(ExceptionInfo *,const ExceptionType,const c...

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Wed, 15 Sep 2004 13:32:08 -0400
From: Daniel Kobras <email address hidden>
To: <email address hidden>
Cc: Daniel Kobras <email address hidden>
Subject: Fixed in NMU of imagemagick 6:6.0.6.2-1.3

tag 271673 + fixed

quit

This message was generated automatically in response to a
non-maintainer upload. The .changes file follows.

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

Format: 1.7
Date: Wed, 15 Sep 2004 18:25:50 +0200
Source: imagemagick
Binary: perlmagick libmagick++6-dev libmagick6-dev libmagick6 imagemagick libmagick++6
Architecture: source i386
Version: 6:6.0.6.2-1.3
Distribution: unstable
Urgency: high
Maintainer: Daniel Kobras <email address hidden>
Changed-By: Daniel Kobras <email address hidden>
Description:
 imagemagick - Image manipulation programs
 libmagick++6 - The object-oriented C++ API to the ImageMagick library
 libmagick++6-dev - The object-oriented C++ API to the ImageMagick library--developme
 libmagick6 - Image manipulation library
 libmagick6-dev - Image manipulation library -- development
 perlmagick - A perl interface to the libMagick graphics routines
Closes: 271673
Changes:
 imagemagick (6:6.0.6.2-1.3) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Raise epoch and revert back to 6.0.6.2 because the progress_meter
     changes in 6.0.7.1 broke binary compatibility by mistake.
     Closes: #271673
   * Retain maintainer changes from 6.0.7.1-1 upload.
   * Retain select bugfixes from 6.0.7.1 version:
     + PerlMagick/Magick.xs: Fix crashes in Profile if name option is unset.
     + utilities/miff.4: Fix header information in man page.
     + magick/annotate.c: Proper exception handling.
     + magick/blob.c: Do not crash when syncing a bogus file.
     + magick/error.h: Remove bogus format attribute from ExceptionType to
       silence compiler warnings.
     + magick/locale.c: Handle NULL locale data.
   * debian/README.Debian: Remove obsolete comment about lzw availability.
Files:
 882e50bbbf11946ef8feae016e3e1178 878 graphics optional imagemagick_6.0.6.2-1.3.dsc
 477a361ba0154cc2423726fab4a3f57c 6824001 graphics optional imagemagick_6.0.6.2.orig.tar.gz
 643d6198308be66071ce131b587e67cc 135472 graphics optional imagemagick_6.0.6.2-1.3.diff.gz
 76d80befec92e120bcdceb2ba62299a5 1464030 graphics optional imagemagick_6.0.6.2-1.3_i386.deb
 6667979bac7b07413d67946983369554 1167696 libs optional libmagick6_6.0.6.2-1.3_i386.deb
 6f66ca63368290c5a3e7c4665f121de7 1502088 libdevel optional libmagick6-dev_6.0.6.2-1.3_i386.deb
 078d6c9eb3e28367c4e7b2fe66717439 163474 libs optional libmagick++6_6.0.6.2-1.3_i386.deb
 1d831c6c3637a89847c0ce698bb1c2f1 207512 libdevel optional libmagick++6-dev_6.0.6.2-1.3_i386.deb
 b37619cdeaa8c0c6685f3febed0be150 141676 perl optional perlmagick_6.0.6.2-1.3_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFBSHg/pOKIA4m/fisRAk2GAKCzwpms5aIsS8w7UvzZlKy5Bi7A3ACgvQmO
Notnf8tk6BYAU70fllQUvEs=
=ZRYK
-----END PGP SIGNATURE-----

[Daniel Kobras (kobras)]

tag 271673 - fixed
tag 271673 + sarge
thanks

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Thu, 16 Sep 2004 00:17:39 +0200
From: Daniel Kobras <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: Bug still unfixed in sarge.

tag 271673 - fixed
tag 271673 + sarge
thanks

[Daniel Kobras (kobras)]

tag 271673 + sid
thanks

On Wed, Sep 15, 2004 at 07:06:32PM +0200, Daniel Kobras wrote:
> [ABI breakage in imagemagick] needs to be addressed urgently.
> Otherwise we end up with packages compiled against binary incompatible
> versions of imagemagick in the archive. I have therefore prepared an
> NMU roughly the same way I did last December when we faced a similar
> situation: I'll re-upload version 6.0.6.2 with a bumped epoch, based
> on the last known-good 6.0.6.2-1.2.
(...)
> It's important that the new upload makes it into sarge as soon as
> possible.

Unfortunately, getting the fixed imagemagick in is taking a few days
longer than I had been hoping[1]. I'm Ccing -release because we need to
watch out and re-upload each package that has meanwhile been built with
the broken imagemagick 6.0.7.1. Otherwise, those packages will most
likely contain subtle and hard to identify bugs. There's no simple,
automated way to tell whether a package was built with the buggy
version. We'll have to go by date, instead, so a delay of a few days
might matter. So far, Steve has identified only k3d as a package that
will need to be rebuilt. I'll start checking for others once the new
imagemagick finally makes sid on all archs. And hope that maintainers
hand-build their uploads on uptodate systems only... (If someone has
nifty scripts at hand to simplify the search, that would be very
welcome.)

Regards,

Daniel.

[1] Here's why: I've reverted imagemagick to an earlier upstream version
    and included the old orig.tar.gz in the upload. The orig.tar.gz was
    still present in the pool, though, so katie accepted the upload,
    but discarded my orig.tar.gz. When the buildds tried to fetch the
    sources, they failed because the orig.tar.gz is neither in incoming,
    nor referenced in sid's Sources file. So imagemagick is stalled in
    Needs_Build until the i386 upload is moved into the archive, and the
    Sources file gets updated. Duh!
    Summary: Emergency-reverting to the previous upstream version will
    usually involve a one-day delay at least.

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Thu, 16 Sep 2004 19:28:06 +0200
From: Daniel Kobras <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#271673: librmagick-ruby1.8: librmagick-ruby unusable after upgrade to
 imagemagick-6.0.7.1

tag 271673 + sid
thanks

On Wed, Sep 15, 2004 at 07:06:32PM +0200, Daniel Kobras wrote:
> [ABI breakage in imagemagick] needs to be addressed urgently.
> Otherwise we end up with packages compiled against binary incompatible
> versions of imagemagick in the archive. I have therefore prepared an
> NMU roughly the same way I did last December when we faced a similar
> situation: I'll re-upload version 6.0.6.2 with a bumped epoch, based
> on the last known-good 6.0.6.2-1.2.
(...)
> It's important that the new upload makes it into sarge as soon as
> possible.

Unfortunately, getting the fixed imagemagick in is taking a few days
longer than I had been hoping[1]. I'm Ccing -release because we need to
watch out and re-upload each package that has meanwhile been built with
the broken imagemagick 6.0.7.1. Otherwise, those packages will most
likely contain subtle and hard to identify bugs. There's no simple,
automated way to tell whether a package was built with the buggy
version. We'll have to go by date, instead, so a delay of a few days
might matter. So far, Steve has identified only k3d as a package that
will need to be rebuilt. I'll start checking for others once the new
imagemagick finally makes sid on all archs. And hope that maintainers
hand-build their uploads on uptodate systems only... (If someone has
nifty scripts at hand to simplify the search, that would be very
welcome.)

Regards,

Daniel.

[1] Here's why: I've reverted imagemagick to an earlier upstream version
    and included the old orig.tar.gz in the upload. The orig.tar.gz was
    still present in the pool, though, so katie accepted the upload,
    but discarded my orig.tar.gz. When the buildds tried to fetch the
    sources, they failed because the orig.tar.gz is neither in incoming,
    nor referenced in sid's Sources file. So imagemagick is stalled in
    Needs_Build until the i386 upload is moved into the archive, and the
    Sources file gets updated. Duh!
    Summary: Emergency-reverting to the previous upstream version will
    usually involve a one-day delay at least.

[Steve Langasek (vorlon)]

On Thu, Sep 16, 2004 at 07:28:06PM +0200, Daniel Kobras wrote:
> tag 271673 + sid
> thanks

> On Wed, Sep 15, 2004 at 07:06:32PM +0200, Daniel Kobras wrote:
> > [ABI breakage in imagemagick] needs to be addressed urgently.
> > Otherwise we end up with packages compiled against binary incompatible
> > versions of imagemagick in the archive. I have therefore prepared an
> > NMU roughly the same way I did last December when we faced a similar
> > situation: I'll re-upload version 6.0.6.2 with a bumped epoch, based
> > on the last known-good 6.0.6.2-1.2.
> (...)
> > It's important that the new upload makes it into sarge as soon as
> > possible.

> Unfortunately, getting the fixed imagemagick in is taking a few days
> longer than I had been hoping[1]. I'm Ccing -release because we need to
> watch out and re-upload each package that has meanwhile been built with
> the broken imagemagick 6.0.7.1. Otherwise, those packages will most
> likely contain subtle and hard to identify bugs. There's no simple,
> automated way to tell whether a package was built with the buggy
> version. We'll have to go by date, instead, so a delay of a few days
> might matter.

> So far, Steve has identified only k3d as a package that will need to
> be rebuilt. I'll start checking for others once the new imagemagick
> finally makes sid on all archs.

You can add imgseek to this list; it was uploaded today.

As for scripts, checking whether packages build-depending on
libmagick6-dev or libmagick++6-dev have new files in the archive seems
easiest.

$ find a/ale a/animal a/autotrace d/drip d/dvdauthor d/dx g/gnuift \
  k/kismet libr/librmagick-ruby p/php3 p/php4-imagick/ r/rss-glx \
  r/rubymagick x/xastir g/guikachu i/imgseek k/k3d k/koffice p/prestimel \
  p/pstoedit -mtime -11

--
Steve Langasek
postmodern programmer

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Thu, 16 Sep 2004 13:22:46 -0700
From: Steve Langasek <email address hidden>
To: <email address hidden>, <email address hidden>
Subject: Re: Bug#271673: librmagick-ruby1.8: librmagick-ruby unusable after upgrade to
 imagemagick-6.0.7.1

--J2SCkAp4GZ/dPZZf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Sep 16, 2004 at 07:28:06PM +0200, Daniel Kobras wrote:
> tag 271673 + sid
> thanks

> On Wed, Sep 15, 2004 at 07:06:32PM +0200, Daniel Kobras wrote:
> > [ABI breakage in imagemagick] needs to be addressed urgently.
> > Otherwise we end up with packages compiled against binary incompatible
> > versions of imagemagick in the archive. I have therefore prepared an
> > NMU roughly the same way I did last December when we faced a similar
> > situation: I'll re-upload version 6.0.6.2 with a bumped epoch, based
> > on the last known-good 6.0.6.2-1.2.=20
> (...)
> > It's important that the new upload makes it into sarge as soon as
> > possible.

> Unfortunately, getting the fixed imagemagick in is taking a few days
> longer than I had been hoping[1]. I'm Ccing -release because we need to
> watch out and re-upload each package that has meanwhile been built with
> the broken imagemagick 6.0.7.1. Otherwise, those packages will most
> likely contain subtle and hard to identify bugs. There's no simple,
> automated way to tell whether a package was built with the buggy
> version. We'll have to go by date, instead, so a delay of a few days
> might matter.

> So far, Steve has identified only k3d as a package that will need to
> be rebuilt. I'll start checking for others once the new imagemagick
> finally makes sid on all archs.

You can add imgseek to this list; it was uploaded today.

As for scripts, checking whether packages build-depending on
libmagick6-dev or libmagick++6-dev have new files in the archive seems
easiest.

$ find a/ale a/animal a/autotrace d/drip d/dvdauthor d/dx g/gnuift \
  k/kismet libr/librmagick-ruby p/php3 p/php4-imagick/ r/rss-glx \
  r/rubymagick x/xastir g/guikachu i/imgseek k/k3d k/koffice p/prestimel \
  p/pstoedit -mtime -11

--=20
Steve Langasek
postmodern programmer

--J2SCkAp4GZ/dPZZf
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

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

iD8DBQFBSfYSKN6ufymYLloRAtnjAJ9JSDqUXm48mUMUpC6SmOAPtdmAKACgxA5H
P615/D/a2EiOXtmQmwXmFbs=
=tp3N
-----END PGP SIGNATURE-----

--J2SCkAp4GZ/dPZZf--

[Steve Langasek (vorlon)]

reassign 271673 libmagick6
tags 271673 fixed
thanks

The NMU of imagemagick addresses this bug in libmagick6, and that
version of the package should soon propagate to testing; there is no
further bug in librmagick-ruby1.8.

--
Steve Langasek
postmodern programmer

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 20 Sep 2004 23:56:49 -0700
From: Steve Langasek <email address hidden>
To: <email address hidden>
Subject: Re: librmagick-ruby1.8: librmagick-ruby unusable after upgrade to imagemagick-6.0.7.1

--UUBKWyapWpFAak7q
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

reassign 271673 libmagick6
tags 271673 fixed
thanks

The NMU of imagemagick addresses this bug in libmagick6, and that
version of the package should soon propagate to testing; there is no
further bug in librmagick-ruby1.8.

--=20
Steve Langasek
postmodern programmer

--UUBKWyapWpFAak7q
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

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

iD8DBQFBT9CvKN6ufymYLloRAhWdAJwMGmzhYCWqvvuBKDEk2uPUlgI5kQCgkI58
bM4rlxiLxich515B80LafUY=
=qWvO
-----END PGP SIGNATURE-----

--UUBKWyapWpFAak7q--

[Adam D. Barratt (debian-bts-adam-barratt)]

# Hi,
#
# These bugs were fixed in an NMU, but have not been acknowledged by the
# maintainers. With version tracking in the Debian BTS, it is important
# to know which version of a package fixes each bug so that they can be
# tracked for release status, so I'm closing these bugs with the
#relevant version information now

close 271146 2.10c-3.1
close 271221 0.9.14-1.1
close 273411 0.9.14-1.1
close 271673 6:6.0.6.2-1.3
close 271956 1.0-7.1
close 272245 2.04-11.2
close 273043 5.0.13-0.1
close 273338 1.2-4.2
close 273357 0.16.14-1.2
close 271221 0.9.14-1.1
close 273411 0.9.14-1.1
close 273613 1.0.5-1.1
close 273800 1.3-0.1
close 274087 2.1.19-1.2
close 275431 2.1.19-1.2
close 274106 1:19970918-12.2
close 274501 0.99.16-1.1
close 274503 0.99.17-2.1
close 274507 0.4-9.1
close 274955 0.3.35.1
close 275432 1.5.28-6.2
close 276637 2.1.19-1.4
close 276825 3.8.3-4.1
close 276851 0.61-6.1
close 278001 0.99.17-2.2
close 279483 6.1
close 279484 1.1
close 280309 1.5-9.1
close 212905 1.5-9.1
close 235681 1.5-9.1
close 236463 1.5-9.1
close 280337 3.2.0.115-7.1
close 356855 3.2.0.115-7.1
close 281282 0.9.3-2
close 282879 2.04-11.1
close 300174 1.0.0b-4.1
close 283756 0.63-1.2
close 284741 0.1.18-1.2
close 284872 0.70-pre20031121-2.1
close 284925 1.1.2-2.1
close 285058 1.2-7.1
close 347152 0.9.7.1+cvs20050803-1.1
close 285528 2.3.11-1.1
close 322368 2.3.11-1.1
close 285605 2.1.19-1.6
close 285628 0.8.3-1.1
close 285762 0.94-7woody4
close 289464 0.94-7woody4
close 285889 0.98.38-1.1
close 285902 20050625-0.1
close 285918 3.06-9.1
close 288966 3.06-9.1
close 326367 3.06-9.1
close 346671 3.06-9.1
close 286309 1:0.5.0-1.1
close 286633 1:0.5.0-1.1
close 286492 2.5.7-3
close 329499 2.5.7-3
close 287059 2.0.12-1.1
close 287066 2.1.1-3.1
close 314008 2.1.1-3.1
close 327992 2.1.1-3.1
close 287190 1.99.11-1.1
close 287628 0.6-10.1
close 323728 0.6-10.1
close 287629 2.0b3-13.1
close 287639 0.6.2-2.1
close 287677 1.4.8-9.1
close 206905 0.7-7.1
close 221950 0.7-7.1
close 287749 0.7-7.1
close 296526 0.7-7.1
close 317259 0.7-7.1
close 287886 0.4.2+cvs.2004.02.20-1.1
close 336046 0.4.2+cvs.2004.02.20-1.1
close 287891 2.1.8-2.1
close 326106 2.1.8-2.1
close 275651 0.6.0-8.1
close 287923 0.6.0-8.1
close 313937 0.6.0-8.1
close 324839 0.6.0-8.1
close 288158 200300506-1.1
close 288441 1.0.8-1.1
close 336944 1.0.8-1.1
close 288536 0.0.7E6F3-4.1
close 290390 0.0.7E6F3-4.1
close 295080 0.0.7E6F3-4.1
close 318375 0.0.7E6F3-4.1
close 288819 0.1.5.9+cvs.2004.02.07-3.2
close 288834 0.2.1-1.1
close 307036 0.2.1-1.1
close 322985 0.2.1-1.1
close 322993 0.2.1-1.1
close 288925 0.9.5+really0.9.6pre4-1.1