Debian Bug report logs - #625544
transition: imagemagick4

Toggle useless messages

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

From: Bastien ROUCARIES <roucaries.bastien@gmail.com>

To: submit@bugs.debian.org

Subject: [release.debian.org] Transition: libmagickcore4, libmagick++4, libmagickwand4

Date: Wed, 4 May 2011 12:27:14 +0200

Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition

Hi,

We would like to perform the transition from  libmagickcore3, libmagick++3, libmagickwand3 to libmagickcore4, libmagick++4, 
libmagickwand4

This transition will requires sourcefull uploads as there is a (minimal) API change.

Package are in experimental

grep-dctrl -F Build-Depends "libmagick-dev" -s Package /var/lib/apt/lists/*_Sources
Package: ale
Package: dx
Package: gnuift
Package: imview
Package: kismet
Package: nip2
Package: psiconv
Package: rss-glx
Package: vips
Package: xine-lib
Package: drawtiming
Package: gnuift
Package: kismet
Package: nip2
Package: vips
Package: xine-lib
Package: drawtiming
Package: gnuift
Package: kismet
Package: nip2
Package: vips
Package: xine-lib

grep-dctrl -F Build-Depends "libmagick++-dev" -s Package /var/lib/apt/lists/*_Sources
Package: drawtiming
Package: dvdauthor
Package: labplot
Package: dvdauthor
Package: gem
Package: gmic
Package: gnudatalanguage
Package: k3d
Package: kxstitch
Package: labplot
Package: pfstools
Package: pstoedit
Package: pythonmagick
Package: synfig
Package: vdr-plugin-skinenigmang
Package: zbar
Package: dvdauthor
Package: gem
Package: gmic
Package: gnudatalanguage
Package: inkscape
Package: k3d
Package: pfstools
Package: player
Package: pstoedit
Package: pythonmagick
Package: vdr-plugin-skinenigmang
Package: zbar

grep-dctrl -F Build-Depends "libmagickwand-dev" -s Package /var/lib/apt/lists/*_Sources
Package: xine-lib
Package: calibre
Package: dx
Package: libdmtx
Package: librmagick-ruby
Package: obex-data-server
Package: php-imagick
Package: rss-glx
Package: virtuoso-opensource
Package: calibre
Package: dx
Package: libdmtx
Package: librmagick-ruby
Package: obex-data-server
Package: php-imagick
Package: rss-glx
Package: virtuoso-opensource

Thanks

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

From: Cyril Brulebois <kibi@debian.org>

To: Bastien ROUCARIES <roucaries.bastien@gmail.com>, 625544@bugs.debian.org

Subject: Re: Bug#625544: [release.debian.org] Transition: libmagickcore4, libmagick++4, libmagickwand4

Date: Wed, 4 May 2011 12:44:03 +0200

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

(Just passing by, not directly involved with the release team.)

Bastien ROUCARIES <roucaries.bastien@gmail.com> (04/05/2011):
> This transition will requires sourcefull uploads as there is a
> (minimal) API change.

It might help to mention the packages which will be OK with a binNMU,
and those which will need a sourceful upload; for the latter, I guess
bugs were opened already, possibly with patches; mentioning those
might help figure out when packages/maintainers are ready.

Mraw,
KiBi.

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

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

From: Bastien ROUCARIES <roucaries.bastien@gmail.com>

To: 625544@bugs.debian.org

Subject: Binnmu

Date: Wed, 4 May 2011 16:25:15 +0200

php5-magick is ready and will only need a binnmu

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

From: Julien Cristau <jcristau@debian.org>

To: Bastien ROUCARIES <roucaries.bastien@gmail.com>, 625544@bugs.debian.org

Subject: Re: Bug#625544: [release.debian.org] Transition: libmagickcore4, libmagick++4, libmagickwand4

Date: Wed, 4 May 2011 20:52:07 +0200

tag 625544 moreinfo
kthxbye

On Wed, May  4, 2011 at 12:27:14 +0200, Bastien ROUCARIES wrote:

> We would like to perform the transition from  libmagickcore3, libmagick++3, libmagickwand3 to libmagickcore4, libmagick++4, 
> libmagickwand4
> 
> This transition will requires sourcefull uploads as there is a (minimal) API change.

A minimal API change that affects *all* reverse dependencies?  That
doesn't sound minimal at all.

Also, please don't change the names of the -dev packages.

Cheers,
Julien

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

From: Julien Cristau <julien@cristau.org>

To: Bastien ROUCARIES <roucaries.bastien@gmail.com>, 625544@bugs.debian.org

Cc: Laurent Fousse <lfousse@debian.org>

Subject: Re: Bug#625544: [release.debian.org] Transition: libmagickcore4, libmagick++4, libmagickwand4

Date: Wed, 25 May 2011 14:24:28 +0200

On Wed, May  4, 2011 at 20:52:07 +0200, Julien Cristau wrote:

> tag 625544 moreinfo
> kthxbye
> 
> On Wed, May  4, 2011 at 12:27:14 +0200, Bastien ROUCARIES wrote:
> 
> > We would like to perform the transition from  libmagickcore3, libmagick++3, libmagickwand3 to libmagickcore4, libmagick++4, 
> > libmagickwand4
> > 
> > This transition will requires sourcefull uploads as there is a (minimal) API change.
> 
> A minimal API change that affects *all* reverse dependencies?  That
> doesn't sound minimal at all.
> 
> Also, please don't change the names of the -dev packages.
> 
So apparently you didn't bother to reply, but uploaded anyway?  WTF?

Cheers,
Julien

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

From: Bastien ROUCARIES <roucaries.bastien@gmail.com>

To: 625544@bugs.debian.org

Subject: Asking for binnmu

Date: Wed, 25 May 2011 14:24:28 +0200

Could I ask for binnmu of reverse depends. Libruby break but it was
broken before this upgrade nevertheless.

Bastien

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

From: Bastien ROUCARIES <roucaries.bastien@gmail.com>

To: Julien Cristau <julien@cristau.org>

Cc: 625544@bugs.debian.org, Laurent Fousse <lfousse@debian.org>

Subject: Re: Bug#625544: [release.debian.org] Transition: libmagickcore4, libmagick++4, libmagickwand4

Date: Wed, 25 May 2011 15:49:18 +0200

n Wed, May 25, 2011 at 2:24 PM, Julien Cristau <julien@cristau.org> wrote:
> On Wed, May  4, 2011 at 20:52:07 +0200, Julien Cristau wrote:
>
>> tag 625544 moreinfo
>> kthxbye
>>
>> On Wed, May  4, 2011 at 12:27:14 +0200, Bastien ROUCARIES wrote:
>>
>> > We would like to perform the transition from  libmagickcore3, libmagick++3, libmagickwand3 to libmagickcore4, libmagick++4,
>> > libmagickwand4
>> >
>> > This transition will requires sourcefull uploads as there is a (minimal) API change.
>>
>> A minimal API change that affects *all* reverse dependencies?  That
>> doesn't sound minimal at all.
>>
>> Also, please don't change the names of the -dev packages.
>>
> So apparently you didn't bother to reply, but uploaded anyway?  WTF?

Upstream break ABI and not API

Bastien

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

From: Martin Pitt <mpitt@debian.org>

To: 625544-close@bugs.debian.org

Subject: Bug#625544: fixed in calibre 0.8.2+dfsg-1

Date: Tue, 31 May 2011 06:02:21 +0000

Source: calibre
Source-Version: 0.8.2+dfsg-1

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

calibre-bin_0.8.2+dfsg-1_amd64.deb
  to main/c/calibre/calibre-bin_0.8.2+dfsg-1_amd64.deb
calibre_0.8.2+dfsg-1.debian.tar.gz
  to main/c/calibre/calibre_0.8.2+dfsg-1.debian.tar.gz
calibre_0.8.2+dfsg-1.dsc
  to main/c/calibre/calibre_0.8.2+dfsg-1.dsc
calibre_0.8.2+dfsg-1_all.deb
  to main/c/calibre/calibre_0.8.2+dfsg-1_all.deb
calibre_0.8.2+dfsg.orig.tar.gz
  to main/c/calibre/calibre_0.8.2+dfsg.orig.tar.gz



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 625544@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Martin Pitt <mpitt@debian.org> (supplier of updated calibre 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: SHA256

Format: 1.8
Date: Tue, 31 May 2011 07:38:22 +0200
Source: calibre
Binary: calibre calibre-bin
Architecture: source all amd64
Version: 0.8.2+dfsg-1
Distribution: unstable
Urgency: low
Maintainer: Miriam Ruiz <little_miry@yahoo.es>
Changed-By: Martin Pitt <mpitt@debian.org>
Description: 
 calibre    - e-book converter and library management
 calibre-bin - e-book converter and library management
Closes: 625544 628640
Changes: 
 calibre (0.8.2+dfsg-1) unstable; urgency=low
 .
   * Rebuild against libmagick 4. (Closes: #625544)
   * debian/watch: Update for new location on sourceforge.
   * Drop kfreebsd.patch, fixed upstream.
   * Unfuzz the other two patches.
   * debian/control: Change build dependency to unversioned libboost-dev.
   * debian/rules: Drop fixing recipes permissions, they are installed as a zip
     file now.
   * debian/rules: Rewrite weird "env python2" style hashbang lines to use
     standard /usr/bin/python.
   * debian/control, debian/rules: Force usage of python2.7 for now, as long as
     it is not the default yet. The new upstream version requires it now.
   * debian/control: Remove unnecessary python-pythonmagick dependency.
     (Closes: #628640)
Checksums-Sha1: 
 cea04a1570b21aa6c0d4f80d012106aefaf307e8 2333 calibre_0.8.2+dfsg-1.dsc
 b486495014d51a73894b2196954038756652c1c7 27703040 calibre_0.8.2+dfsg.orig.tar.gz
 bdaca85f4de7bf076f1f7c14083577080fa5c24c 18879 calibre_0.8.2+dfsg-1.debian.tar.gz
 b994d08deda98982f0c70957f08aecc2526a8570 12469022 calibre_0.8.2+dfsg-1_all.deb
 97d18770fee2c2ecc61a30eccfb1fb4fec5833fc 204020 calibre-bin_0.8.2+dfsg-1_amd64.deb
Checksums-Sha256: 
 16243f67db8c7cfcf4968aae7af924f53907041418df338669bf917fca77154c 2333 calibre_0.8.2+dfsg-1.dsc
 f4f25eb149d3b61a6881857a2185231690779241ca9b6649aa02e594a8611926 27703040 calibre_0.8.2+dfsg.orig.tar.gz
 f3a05b4e0e16b7f0e41060c18648fffa57ed3165c5430b327f177155b8463b0a 18879 calibre_0.8.2+dfsg-1.debian.tar.gz
 e107590f1705c037ddceeeda6f66bf0aaf14f240fc8f8f46a78d48081991b3b3 12469022 calibre_0.8.2+dfsg-1_all.deb
 9618782d227950aec85b3baaafd31955afc612a6f066ced90d7cfc15b3c8d825 204020 calibre-bin_0.8.2+dfsg-1_amd64.deb
Files: 
 b94bfaa3534dd46e7d0d0dbf1a626bd6 2333 text extra calibre_0.8.2+dfsg-1.dsc
 207be742c8c834d1c358f752a6fc07b8 27703040 text extra calibre_0.8.2+dfsg.orig.tar.gz
 8cb63c77345404e7e079bf1f637b052d 18879 text extra calibre_0.8.2+dfsg-1.debian.tar.gz
 0fead21c9874ee9f3d1feff34a99fd7c 12469022 text extra calibre_0.8.2+dfsg-1_all.deb
 9b0bcccc4ee2b88674f7c40faf29d465 204020 text extra calibre-bin_0.8.2+dfsg-1_amd64.deb

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

iQIcBAEBCAAGBQJN5H+wAAoJEPmIJawmtHufFt8P/imVzWrSU2k0ynlrQoHaw6sk
j/bn3QGfDC59VzlXOh/5zrYKS4hPeKTD45dF2YJTXsKF2fGpcGb4mvrNZ5mpjsuk
QFsPkx0NxECNYa0NcaqKJ1shtu/VqYCrU2guS/Ph5puQ1/A7B9ux30ubd1v6KIGO
cEao+QCNWN2SwGpbU88D4kF6QTXmdRPYRv/zQJZCVW6X2yVixYxvgOxT7hvhXIJT
jKTRyxBrq1Ud1TrAFV20JyU9CIfl23N08sKkFnBUoJxgqt5N7F5qAoD7TJUrpQFa
7FmznCPMyB/0kOaxlN2TGWagbhj02uq8DxS5UObCRLOnlS6tVZujXM+ycd821H/J
YcKJEVTfx6SwSa/RyHArirlemRT7kAnYCkIAFgcMc71lRovWhzStLbHzdsCH2C6F
qCBikIvSzt3bt3WqTAjrI+k7mWDAXF2lShxDrrYngpkJB6+imPylEwCcF+TGE5E0
rNddeKmr62VvzK+5VaMw7zjz5LaIB/QK71RmLrGnBm/rSH39cQ172MMNqHty0ngF
maRNhWoWTcCYE5/9yI1d6VpiTUIcgsAmCSD1r19Eh9m+eL8H77y04eO5wOsy2BmT
nlX/flrspsetHinLgsHpQdWD/gLj2IPBl1Zs7u2Zo9DN7dOzFwdZaVG0JZIrCNCd
6VBjjFV24koXcrK9T6/s
=JXss
-----END PGP SIGNATURE-----

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

From: Julien Cristau <jcristau@debian.org>

To: Martin Pitt <mpitt@debian.org>

Cc: 625544@bugs.debian.org

Subject: Re: Bug#625544: fixed in calibre 0.8.2+dfsg-1

Date: Tue, 31 May 2011 08:21:26 +0200

reopen 625544
kthxbye

On Tue, May 31, 2011 at 06:02:21 +0000, Martin Pitt wrote:

>  calibre (0.8.2+dfsg-1) unstable; urgency=low
>  .
>    * Rebuild against libmagick 4. (Closes: #625544)

Err, no.  #625544 is against release.debian.org, not calibre.

Cheers,
Julien

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

From: Vincent Fourmond <fourmond@debian.org>

To: 625544@bugs.debian.org, Bastien ROUCARIES <roucaries.bastien@gmail.com>, control@bugs.debian.org

Subject: Imagemagick transition: closer ?

Date: Sat, 11 Jun 2011 00:01:11 +0200

block 625544 by 630014
thanks

  Dear Release Team,

  It seems to me that the Imagemagick transition is well under way
now. There are only a few problems remaining, as far as I can tell:

  * we have a (rather stupid ;-)...) RC bug against imagemagick
itself, which should be fixed quite soon (an upload is planned either
tonight or tomorrow)
  * nip2 FTBS due to obsolete dependencies in libvips-dev, see #630014;
  * libfprint FTBS but maintainer is taking care of that (see #629788);
  * pythonmagick FTBS.

  For the latter, there seem to be no choice but uploading a new
upstream version. What is worrying me is that pythonmagick is somehow
tied to the python transition. For now, it only builds with python2.6.
Is this fine ?

  Cheers,

      Vincent

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

From: Mehdi Dogguy <mehdi@dogguy.org>

To: Vincent Fourmond <fourmond@debian.org>, 625544@bugs.debian.org

Cc: Bastien ROUCARIES <roucaries.bastien@gmail.com>

Subject: Re: Bug#625544: Imagemagick transition: closer ?

Date: Sat, 11 Jun 2011 09:57:17 +0200

On 06/11/2011 12:01 AM, Vincent Fourmond wrote:
> 
>   It seems to me that the Imagemagick transition is well under way
> now. There are only a few problems remaining, as far as I can tell:
> 
>   * we have a (rather stupid ;-)...) RC bug against imagemagick
> itself, which should be fixed quite soon (an upload is planned either
> tonight or tomorrow)
>   * nip2 FTBS due to obsolete dependencies in libvips-dev, see #630014;
>   * libfprint FTBS but maintainer is taking care of that (see #629788);
>   * pythonmagick FTBS.
> 
>   For the latter, there seem to be no choice but uploading a new
> upstream version. What is worrying me is that pythonmagick is somehow
> tied to the python transition. For now, it only builds with python2.6.

I intend to remove pythonmagick from testing to get it out our way.
Once imagemagick fixed and performous/libtuxcap/kismet/autotrace built
and signed on all architectures, imagemagick will be able to migrate.

The status can be seen on:

	http://release.debian.org/transitions/html/imagemagick4.html

(updated hourly).

Regards,

-- 
Mehdi Dogguy مهدي الدڤي
http://dogguy.org/

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

From: Mehdi Dogguy <mehdi@dogguy.org>

To: Mehdi Dogguy <mehdi@dogguy.org>, 625544-done@bugs.debian.org

Cc: Vincent Fourmond <fourmond@debian.org>, Bastien ROUCARIES <roucaries.bastien@gmail.com>

Subject: Re: Bug#625544: Imagemagick transition: closer ?

Date: Tue, 28 Jun 2011 10:54:53 +0200

On 06/11/2011 09:57 AM, Mehdi Dogguy wrote:
> On 06/11/2011 12:01 AM, Vincent Fourmond wrote:
>>
>>    It seems to me that the Imagemagick transition is well under way
>> now. There are only a few problems remaining, as far as I can tell:
>>
>>    * we have a (rather stupid ;-)...) RC bug against imagemagick
>> itself, which should be fixed quite soon (an upload is planned either
>> tonight or tomorrow)
>>    * nip2 FTBS due to obsolete dependencies in libvips-dev, see #630014;
>>    * libfprint FTBS but maintainer is taking care of that (see #629788);
>>    * pythonmagick FTBS.
>>
>>    For the latter, there seem to be no choice but uploading a new
>> upstream version. What is worrying me is that pythonmagick is somehow
>> tied to the python transition. For now, it only builds with python2.6.
>
> I intend to remove pythonmagick from testing to get it out our way.
> Once imagemagick fixed and performous/libtuxcap/kismet/autotrace built
> and signed on all architectures, imagemagick will be able to migrate.
>
> The status can be seen on:
>
> 	http://release.debian.org/transitions/html/imagemagick4.html
>
> (updated hourly).
>

ImageMagick migrated during yesteday's Britney run. Closing…

Regards,

-- 
Mehdi Dogguy مهدي الدڤي
http://dogguy.org/

Send a report that this bug log contains spam.