On 07/11/2018 12:03, Uwe Kleine-König wrote: > Hello James, > > On 11/5/18 6:58 PM, James Cowgill wrote: >> Hi, >> >> On 05/11/2018 17:28, Uwe Kleine-König wrote: >>> Hello Emilio, >>> >>> [adding jcowgill to recipients] >>> >>> On 11/05/2018 04:37 PM, Emilio Pozuelo Monfort wrote: >>>> Please get this started, and bump the bug severities to serious. >>> >>> I never did a transition before, so I'm not entirely clear what should >>> happen now. >>> >>> The following steps should be done: >>> >>> a) upload pupnp-1.8 providing libupnp-dev to unstable >>> b) rebuild reverse dependencies of libupnp-dev >>> c) remove src:libupnp from unstable >>> d) remove src:libupnp from testing >>> e) remove the binary packages of src:libupnp from unstable >>> f) remove the binary packages of src:libupnp from testing >>> g) for b in 884243 884996 912066 885025; do bts severity $b serious;done >>> h) remove djmount and linux-igd from unstable and testing >>> i) apply patch from 884996 to amule and upload to unstable >> >> Yeah we can start this transition now that 1.8.4 was released (which >> resolved the ABI related issues). I'll upload it soon. >> >> The order is this: >> >> a) I upload pupnp-1.8 (which "hijacks" libupnp-dev from src:libupnp) >> g) Update bug severities > > Given that a) and g) is done now ... > >> b) binNMU all rdeps of libupnp-dev > > do we need to do anything here by hand?
binNMUs scheduled. > Note that > > https://release.debian.org/transitions/html/libupnp.html > > lists linphone as dependency, but the version in unstable doesn't depend > on libupnp (at least not via an explicit B-D). That should be because of the old cruft packages. You can ignore it. gmrender-resurrect and gerbera need to update their build-dep to libupnp-dev Cheers, Emilio
