Bug#749560: transition: miniupnpc

[Thomas Goirand <zigo@debian.org>]

On 07/13/2014 11:02 PM, Thomas Goirand wrote:
> On 07/05/2014 11:59 PM, Emilio Pozuelo Monfort wrote:
>> On 05/07/14 17:45, Thomas Goirand wrote:
>>> So, is the next course of action to upload miniupnpc to Sid now, then
>>> raise the severity of #751225 and #751229 to RC, then upload fixes to
>>> DELAYED/2?
>>
>> Yes please.
> 
> Bugs #751225 and #751229 where closed, so NMU wont be needed. Everything
> should then rebuild fine now.
> 
>>> I'm guessing that later, I should request for binNMUs for all reverse
>>> dependencies, right?
>>
>> Aye.
> 
> I just did that (see #754708).

As Jcristau advised on IRC, I shouldn't have opened a new bug, so I'm
closing it, and copying it's content here:

I have uploaded miniupnpc version 1.9.20140610-2 to Unstable. This means
packages that were linking against the shared library libminiupnpc8 now
need to link against the new libminiupnpc10.

A binNMU needs to happen for the following source packages (I have
re-checked again this list using apt-rdepends -r, and it's still correct):

- 0ad
- bitcoin
- eiskaltdcpp
- litecoin
- megaglest
- sushi
- transmission
- warzone2100

I believe we shall proceed with the binNMU once libminiupnpc10 reaches
all buildd mirrors.

Note that, unless this has changed since my last rebuild tests, and if I
trust that bugs #751224 (for 0ad), #751225 (for megaglest) and #751229
(for warzone2100) were addressed correctly, all of the above should
build just fine with the new miniupnpc.

Thanks to Emilio Pozuelo Monfort for helping me with the transition
process for this new miniupnpc,

Cheers,

Thomas Goirand (zigo)