Package: release.debian.org Severity: normal User: release.debian....@packages.debian.org Usertags: transition
The GUPnP stack has been released in a new major upstream versions and the two base components (gssdp & gupnp) have bumped their sonames "now that we're breaking API/ABI"[1][2]. The new stack has been uploaded to experimental, with gssdp and gupnp currently stuck in NEW. I've compared the dpkg-gensymbols generated symbols files and no symbols are missing in the new library version. I see some changes related to improving the situation for bindings, so I guess some data structures might have changed that broke the ABI. I don't see any reasons why reverse dependencies should have any problems building against the new versions, but I've only tested a few random ones (like gupnp-igd, bickley, ...). One exception is rygel, which has (too) strict configure checks and will need a sourceful upload, but I'll handle that being the maintainer for it as well. [1] http://git.gnome.org/browse/gssdp/commit/?id=e937ef0b688b4764a4db7d23f8cd3ff7fb72affb [2] http://git.gnome.org/browse/gupnp/commit/?id=71a93a7b116ed0bef725a88cedc3bb1414cb1d5a -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (300, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
