Your message dated Thu, 1 Dec 2016 00:22:09 +0100
with message-id
<cae2spabcnmk6m+ncrientvtmg5hjccyxw0_w74rwgubnmb_...@mail.gmail.com>
and subject line Re: [Pkg-gmagick-im-team] Bug#846385: imagemagick: Potential
ABI break upstream (without SONAME change)
has caused the Debian Bug report #846385,
regarding imagemagick: Potential ABI break upstream (without SONAME change)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
846385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846385
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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 ruby-rmagick, it seems like (possibly) upstream made an ABI
change without bumping the SONAME for libmagickcore, and ruby-rmagick
ends up pulling in the wrong dependency
(https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/armhf/r/ruby-rmagick/20161130_032804_d2177@/log.gz).
More specifically, we are building against imagemagick
8:6.9.6.6+dfsg-1ubuntu2:
https://launchpadlibrarian.net/295470626/buildlog_ubuntu-zesty-arm64.ruby-rmagick_2.15.4+dfsg-2build1_BUILDING.txt.gz.
During the build, the tests pass succesfully (using the above version of
imagemagick), but you can see that the the resulting binary package has
dependencies that are more relaxed than that specific version:
Depends: ruby (>= 1:2.3~0), libc6 (>= 2.17), libmagickcore-6.q16-2 (>=
8:6.8.8.9), libruby2.3 (>= 2.3.0~preview2)
Therefore, when the autopkgtest runs:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/armhf/r/ruby-rmagick/20161130_032804_d2177@/log.gz,
imagemagick 8:6.8.9.9-7ubuntu9 is used, and a segmentation fault occurs.
Thanks to Marc Deslauriers' research, it seems like there might have
been at least one ABI breakage upsream in libmagickcore:
https://abi-laboratory.pro/tracker/compat_report/imagemagick/6.9.1-10/6.9.2-10/67f2f/abi_compat_report.html,
which might be related.
What is your opinion on this as the Debian maintainer? Should the SONAME
be bumped and symbols files be updated?
Thanks for your time!
-Nish
--
Nishanth Aravamudan
Ubuntu Server
Canonical Ltd
--- End Message ---
--- Begin Message ---
reason: does not affect debian
On Wed, Nov 30, 2016 at 9:34 PM, Nishanth Aravamudan
<[email protected]> 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 ruby-rmagick and php-imagick with this
> version (note that Debian is seeing similar failures).
>
> At least for ruby-rmagick, it seems like (possibly) upstream made an ABI
> change without bumping the SONAME for libmagickcore, and ruby-rmagick
> ends up pulling in the wrong dependency
> (https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/armhf/r/ruby-rmagick/20161130_032804_d2177@/log.gz).
>
> More specifically, we are building against imagemagick
> 8:6.9.6.6+dfsg-1ubuntu2:
> https://launchpadlibrarian.net/295470626/buildlog_ubuntu-zesty-arm64.ruby-rmagick_2.15.4+dfsg-2build1_BUILDING.txt.gz.
>
> During the build, the tests pass succesfully (using the above version of
> imagemagick), but you can see that the the resulting binary package has
> dependencies that are more relaxed than that specific version:
>
> Depends: ruby (>= 1:2.3~0), libc6 (>= 2.17), libmagickcore-6.q16-2 (>=
> 8:6.8.8.9), libruby2.3 (>= 2.3.0~preview2)
>
> Therefore, when the autopkgtest runs:
> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/armhf/r/ruby-rmagick/20161130_032804_d2177@/log.gz,
> imagemagick 8:6.8.9.9-7ubuntu9 is used, and a segmentation fault occurs.
>
> Thanks to Marc Deslauriers' research, it seems like there might have
> been at least one ABI breakage upsream in libmagickcore:
> https://abi-laboratory.pro/tracker/compat_report/imagemagick/6.9.1-10/6.9.2-10/67f2f/abi_compat_report.html,
> which might be related.
>
> What is your opinion on this as the Debian maintainer? Should the SONAME
> be bumped and symbols files be updated?
>
> Thanks for your time!
Debian do a so bump for 6.9.5-8. I think it is safer to do the same on ubuntu
Bastien
>
> -Nish
>
> --
> Nishanth Aravamudan
> Ubuntu Server
> Canonical Ltd
>
> _______________________________________________
> Pkg-gmagick-im-team mailing list
> [email protected]
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-gmagick-im-team
--- End Message ---
