Bug#876257: libwebkit2gtk-4.0-37: blocks upgrade path for libgstreamer-plugins-bad1.0-0 1.12.3

2017-09-20 Thread Alberto Garcia
On Wed, Sep 20, 2017 at 01:04:20PM +0300, Sebastian Dröge wrote:

> > > libgstreamer-plugins-bad1.0-0 (>= 1.12.2), libgstreamer-plugins-bad1.0-0 
> > > (<< 1.12.3)

> > 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))"
> > 
> > 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.

I see, thanks. This particular instance is alreay being dealt with
(#876227) so no hurries here. I think it's fine if the version
contraints in gstreamer are updated in the next upload.

Thanks!!

Berto



Bug#876257: libwebkit2gtk-4.0-37: blocks upgrade path for libgstreamer-plugins-bad1.0-0 1.12.3

2017-09-20 Thread Sebastian Dröge
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


Bug#876257: libwebkit2gtk-4.0-37: blocks upgrade path for libgstreamer-plugins-bad1.0-0 1.12.3

2017-09-20 Thread Alberto Garcia
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?

Berto



Bug#876257: libwebkit2gtk-4.0-37: blocks upgrade path for libgstreamer-plugins-bad1.0-0 1.12.3

2017-09-20 Thread Antonio Ospite
Package: libwebkit2gtk-4.0-37
Version: 2.18.0-2
Severity: important

Dear Maintainer,

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.

Thanks,
   Antonio

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (500, 'unstable-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 4.12.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8), 
LANGUAGE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libwebkit2gtk-4.0-37 depends on:
ii  libatk1.0-0 2.26.0-2
ii  libc6   2.24-17
ii  libcairo2   1.14.10-1
ii  libegl1 0.2.999+git20170802-4
ii  libenchant1c2a  1.6.0-11+b2
ii  libfontconfig1  2.12.3-0.2
ii  libfreetype62.8-0.2
ii  libgcc1 1:7.2.0-5
ii  libgcrypt20 1.7.9-1
ii  libgdk-pixbuf2.0-0  2.36.10-1
ii  libgl1  0.2.999+git20170802-4
ii  libglib2.0-02.54.0-1
ii  libgstreamer-plugins-bad1.0-0   1.12.2-1+b1
ii  libgstreamer-plugins-base1.0-0  1.12.3-1
ii  libgstreamer1.0-0   1.12.3-1
ii  libgtk-3-0  3.22.21-1
ii  libharfbuzz-icu01.4.2-1
ii  libharfbuzz0b   1.4.2-1
ii  libhyphen0  2.8.8-5
ii  libicu5757.1-6
ii  libjavascriptcoregtk-4.0-18 2.18.0-2
ii  libjpeg62-turbo 1:1.5.2-2
ii  libnotify4  0.7.7-2
ii  libpango-1.0-0  1.40.12-1
ii  libpng16-16 1.6.32-1
ii  libsecret-1-0   0.18.5-3.1
ii  libsoup2.4-12.60.0-1
ii  libsqlite3-03.20.1-1
ii  libstdc++6  7.2.0-5
ii  libtasn1-6  4.12-2.1
ii  libwayland-client0  1.14.0-1
ii  libwayland-egl1-mesa [libwayland-egl1]  17.2.1-1
ii  libwayland-server0  1.14.0-1
ii  libwebp60.6.0-3
ii  libx11-62:1.6.4-3
ii  libxcomposite1  1:0.4.4-2
ii  libxdamage1 1:1.1.4-3
ii  libxml2 2.9.4+dfsg1-4
ii  libxslt1.1  1.1.29-2.1
ii  zlib1g  1:1.2.8.dfsg-5

Versions of packages libwebkit2gtk-4.0-37 recommends:
ii  gstreamer1.0-plugins-base  1.12.3-1
ii  gstreamer1.0-plugins-good  1.12.3-1
ii  libgl1-mesa-dri17.2.1-1

Versions of packages libwebkit2gtk-4.0-37 suggests:
ii  libwebkit2gtk-4.0-37-gtk2  2.18.0-2

-- no debconf information
-- 
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?