Hi Alberto, On Wed, 2017-09-20 at 11:19 +0200, Alberto Garcia wrote: > On Wed, Sep 20, 2017 at 10:53:07AM +0200, Antonio Ospite wrote: > > it looks like libwebkit2gtk-4.0-37 is blocking the upgrade path > > for libgstreamer-plugins-bad1.0-0 1.12.3, looking at the package > > dependencies I spotted these constraints: > > > > libgstreamer-plugins-bad1.0-0 (>= 1.12.2), libgstreamer-plugins-bad1.0-0 > > (<< 1.12.3) > > > > which explain the issue. > > > > However I am not sure about why both constraints are there. > > That's gst-plugins-bad: > > DEB_DH_MAKESHLIBS_ARGS_libgstreamer-plugins-bad$(gst_deb_abi) += -V > "libgstreamer-plugins-bad$(gst_deb_abi) (>= $(gst_version)), > libgstreamer-plugins-bad$(gst_deb_abi) (<< $(gst_version_next))" > > From its changelog: > > + Split the libraries into their own package and add a -dev package. > The API of the library is not guaranteed to be stable and as such > the shlibs of the library package are very strict and will require > dependant libraries to get a rebuild after every new upstream version. > > I understand that its rdeps need to be rebuilt each time there's a new > upstream version, or how is that supposed to work? Sebastian?
That's correct. The API and ABI of the libraries in gst-plugins-bad is not stable and can change every release. However only every new minor release, not micro release. So >= 1.12 < 1.13 would be sufficient here and probably would solve most of the headaches. Feel free to send me a patch or NMU directly for that, otherwise I'll get it done with the next upload.
signature.asc
Description: This is a digitally signed message part
