Bug#846385: imagemagick: Potential ABI break upstream (without SONAME change)

BTW feel free to NMU imagemagick during a short break I take in the next two days. Bastien

Bug#846385: imagemagick: Potential ABI break upstream (without SONAME change)

On Tue, Dec 20, 2016 at 4:22 PM, roucaries bastien wrote: > On Wed, Dec 14, 2016 at 1:29 PM, roucaries bastien > wrote: >> On Wed, Dec 14, 2016 at 1:28 PM, roucaries bastien >> wrote: >>>

Bug#846385: imagemagick: Potential ABI break upstream (without SONAME change)

On Wed, Dec 14, 2016 at 1:29 PM, roucaries bastien wrote: > On Wed, Dec 14, 2016 at 1:28 PM, roucaries bastien > wrote: >> On Tue, Dec 13, 2016 at 12:21 AM, Emilio Pozuelo Monfort >> wrote: >>> On 09/12/16

Bug#846385: imagemagick: Potential ABI break upstream (without SONAME change)

On Tue, Dec 13, 2016 at 12:21 AM, Emilio Pozuelo Monfort wrote: > On 09/12/16 22:37, roucaries bastien wrote: >> control: forwarded -1 https://github.com/ImageMagick/ImageMagick/issues/320 >> >> Dear realease team, >> >> What is the next step? > > In which version was the ABI

Bug#846385: imagemagick: Potential ABI break upstream (without SONAME change)

On Wed, Dec 14, 2016 at 1:28 PM, roucaries bastien wrote: > On Tue, Dec 13, 2016 at 12:21 AM, Emilio Pozuelo Monfort > wrote: >> On 09/12/16 22:37, roucaries bastien wrote: >>> control: forwarded -1

Bug#846385: imagemagick: Potential ABI break upstream (without SONAME change)

On 09/12/16 22:37, roucaries bastien wrote: > control: forwarded -1 https://github.com/ImageMagick/ImageMagick/issues/320 > > Dear realease team, > > What is the next step? In which version was the ABI break introduced? In general I would prefer the change to be reverted, but depending on how

Bug#846385: imagemagick: Potential ABI break upstream (without SONAME change)

control: forwarded -1 https://github.com/ImageMagick/ImageMagick/issues/320 Dear realease team, What is the next step? Thank you On Tue, Dec 6, 2016 at 8:23 PM, Simon McVittie wrote: > Control: reopen 846385 > Control: severity 846385 serious > > tl;dr: yes, this is clearly

Bug#846385: imagemagick: Potential ABI break upstream (without SONAME change)

Control: reopen 846385 Control: severity 846385 serious tl;dr: yes, this is clearly an ABI break. On Thu, 01 Dec 2016 at 15:55:02 +0100, roucaries bastien wrote: > * struct _DrawInfo (1) is not a problem from a C point of view because > it should be set and destry by API function. It is a opaque

Bug#846385: Fwd: [Pkg-gmagick-im-team] Bug#846385: imagemagick: Potential ABI break upstream (without SONAME change)

-- Forwarded message -- From: Antonio Terceiro <terce...@debian.org> Date: Sun, Dec 4, 2016 at 1:08 AM Subject: Re: [Pkg-gmagick-im-team] Bug#846385: imagemagick: Potential ABI break upstream (without SONAME change) To: roucaries bastien <roucaries.bastien+deb...@gmail.com>

Bug#846385: [Pkg-gmagick-im-team] Bug#846385: imagemagick: Potential ABI break upstream (without SONAME change)

On Thu, Dec 01, 2016 at 03:55:02PM +0100, roucaries bastien wrote: > On Wed, Nov 30, 2016 at 9:34 PM, Nishanth Aravamudan > wrote: > > Package: imagemagick > > Version: 6.9.9.6+dfsg-1 > > Severity: normal > > > > Dear Maintainer, > > > > We recently merged

Bug#846385: [Pkg-gmagick-im-team] Bug#846385: imagemagick: Potential ABI break upstream (without SONAME change)

On Wed, Nov 30, 2016 at 9:34 PM, Nishanth Aravamudan wrote: > Package: imagemagick > Version: 6.9.9.6+dfsg-1 > Severity: normal > > Dear Maintainer, > > We recently merged imagemagick 6.9.9.6+dfsg-1 in Ubuntu 17.04; however > we see autopkgtest failures in

Bug#846385: imagemagick: Potential ABI break upstream (without SONAME change)

Package: imagemagick Version: 6.9.9.6+dfsg-1 Severity: normal Dear Maintainer, We recently merged imagemagick 6.9.9.6+dfsg-1 in Ubuntu 17.04; however we see autopkgtest failures in ruby-rmagick and php-imagick with this version (note that Debian is seeing similar failures). At least for