Bug#940632: marked as done (nmu: mupdf_1.15.0+ds1-1+b1)
Your message dated Wed, 18 Sep 2019 12:01:04 +0200
with message-id <20190918100104.GA27926@jcristau-z4>
and subject line Re: Bug#940632: nmu: mupdf_1.15.0+ds1-1+b1
has caused the Debian Bug report #940632,
regarding nmu: mupdf_1.15.0+ds1-1+b1
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 owner@bugs.debian.org
immediately.)
--
940632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940632
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi release team,
Due to libjbig2dec0 upstream API being unstable, and a new release of
libjbig2dec0 introduced a new symbol, mupdf needs a bunNMU to catch up.
libjbig2dec0 tracks symbols changes, so a simple rebuild should properly
tighten dependency to only the new API.
Please rebuild mupdf against libjbig2dec0 0.16+20190905-2 to bump its
dependency on libjbig2dec0.
nmu mupdf_1.15.0+ds1-1+b1 . ANY . unstable . -m "Rebuild against libjbig2dec0 to correct dependency"
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl2BzTYACgkQLHwxRsGg
ASHWFg//abNUxllNBJ1Y3srHCddAlIiZ89nZx3dPOFJIptNBUWJM+07ggrChzNJC
6PPel6F5jQ8i7wDt6SRCrkfZMgve6T4vFm0nMiOSm2lWlojGfRuMqtxhX+YmdBFt
o8piYgvvQ1K2Eg2P0hJ74O435bgrIIt1+TkyOWu6OHOBGPlbFDaOeqoZnAeygFpm
NqHJBkuqWJNtoTMEYWnU4n+sbHFCg7OIIRq6HOMCT66ZmKNj0dg6Mx39/EX1YTMz
TuaZ+uBkLtx26NBZdngE7HxyKv2/MeQGIHJKGh5maNnv0oB5WNGOedgNM7mPwu3C
UmQTqc4+28HBk0NFrdImt+BTPPKHkzaNb3AZZ3mPzE0FmOwPDl0XhEIt90D07nTF
lrMiC3li3tNx8UfAIIiJv9B1n3p1g964/sejnGjBCXNhPwsZoQhJxgmWAHjNEfAB
tK1odp6b5CGIT67/pGfat23/IECsKQXPrrLVWscGtmkJSh/s5Zfx65wT6xPRlnRq
mOJ0NMGUgJk/Cu/2fmGa7vAH9b51nu/fXqArOdS8kxla6tW2gIB+mdTidue3zlSn
/iMYuuQEYYzZD8v7IIBpYf7Nd/0z2U1vrNYH4BpxWEDq3JBjte06k4ZgZt/Dk5f0
LnSpowUV4ETHhzNJi8QN3K4DCYczGPf3Q9Slul435Xc83b63p58=
=f6Tn
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Control: severity 940605 serious
Control: retitle 940605 jbig2dec: ABI breakage without SONAME and package name change
On Wed, Sep 18, 2019 at 08:22:49AM +0200, Jonas Smedegaard wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: binnmu
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> Hi release team,
>
> Due to libjbig2dec0 upstream API being unstable, and a new release of
> libjbig2dec0 introduced a new symbol, mupdf needs a bunNMU to catch up.
> libjbig2dec0 tracks symbols changes, so a simple rebuild should properly
> tighten dependency to only the new API.
>
> Please rebuild mupdf against libjbig2dec0 0.16+20190905-2 to bump its
> dependency on libjbig2dec0.
>
NAK. jbig2dec's symbols file diff includes this gem:
- jbig2_ctx_new@Base 0.11
This is broken. It means jbig2_ctx_new, previously part of the ABI
surface, is no longer exported. That needs to be fixed, either by
bringing it back or by bumping SONAME and library package name.
Closing the binNMU bug as invalid, and bumping severity on #940605.
Cheers,
Julien
--- End Message ---
Reply to: