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

[roucaries bastien]

On Tue, Dec 20, 2016 at 4:22 PM, roucaries bastien
<roucaries.bastien+debian at gmail.com> wrote:
> On Wed, Dec 14, 2016 at 1:29 PM, roucaries bastien
> <roucaries.bastien+debian at gmail.com> wrote:
>> On Wed, Dec 14, 2016 at 1:28 PM, roucaries bastien
>> <roucaries.bastien+debian at gmail.com> wrote:
>>> On Tue, Dec 13, 2016 at 12:21 AM, Emilio Pozuelo Monfort
>>> <pochu at debian.org> 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 break introduced?
>>>
>>> It was introduced more than 2 years ago ( 6.9.2-10). One version after
>>> jessie what lie in unstable before jessie release.
>>>>
>>>> In general I would prefer the change to be reverted, but depending on how long
>>>> this has been in the archive, and in order to stay up to date for security
>>>> fixes, it may be best to do the soname bump.
>>>
>>> From a security point of view, I prefer recent version. I do not want
>>> to keep jessie version with huge patch queue for
>>>>
>>>> Can you check if your rdeps build fine against a new imagemagick?
>
> libmagick++ rdeps build fine except traficserver due to a sphinx error
> (unreleated to imagemagick)
> libmagickwand rdeps build fine except rss-glx due to unreleated build
> conflict (#838800)
> libmagickcore rdeps build fine except dx due to missing .mak file
> (unlikely imagemagick)

trafficserver is - #848800
dx #848894

>
> Will rebuild traficserver and dx under sid chroot and report FTBFS.
>
> Seems it is ok
>
> Bastien
>>>
>>> What i will do i will set on unstable the newer version with so dump
>>> and will begin to rebuilt on pbuilder. Normally it will be fine.
>>
>> s/unstable/experimental/g
>>>
>>> I wish to have abi checker on the debian side
>>>
>>> Bastien
>>>>
>>>> Emilio