Bug#639871: gupnp transition also needs to include newer gupnp-igd
Hello!
On Fri, Dec 16, 2011 at 10:24:39AM +0100, Niels Thykier wrote:
[...]
> So far we have recorded the following SONAME/package name changes:
>
> libgssdp-1.0-2 => libgssdp-1.0-3
> libgupnp-1.0-3 => libgupnp-1.0-4
> libgupnp-igd-1.0-3 => libgupnp-igd-1.0-4
>
>
> And new one all appear to be ready in experimental already. However, in
> the previous email, the following -dev packages were also mentioned:
>
> - libgupnp-av-1.0-dev
> - Has a new version in experimental, but no SONAME change?
yes
>
> - libgupnp-dlna-1.0-dev
> - Nothing new in experimental
build-dependencies already satisfied in unstable.
>
> So, will there be a sourceful upload of gupnp-av and gupnp-dlna bumping
> their SONAME?
no
>
> If not, I believe the tracker is curently up to date[1] and we should be
> ready to start.
Uploaded: gssdp, gupnp, gupnp-av, gupnp-vala, rygel ...
(and gupnp-tools as a bonus while at it. new upstream release + IMHO no need
to hold back gtk2 -> gtk3 switch anymore, so to unstable it went.)
Still pending: gupnp-igd
bigon didn't feel confortable enough with the testing of the new version yet.
Please do *not* binNMU gupnp-igd even if it might seem possible by looking
at dependencies, since runtime breakage has been mentioned by upstream....
Other binNMUs should be able to start as soon as the buildds have caught up
with what was just uploaded....
--
Andreas Henriksson
Reply to: