Bug#884635: transition: libupnp

[Niels Thykier <niels@thykier.net>]

Uwe Kleine-König:
> Hello,
> 
> adding Marcelo (upstream for libupnp) to recipents.
> 
> On 09/30/2018 10:09 AM, Sebastian Ramacher wrote:
>> On 2017-12-22 22:38:23, Uwe Kleine-König wrote:
>>> Hello,
>>>
>>> On Sun, Dec 17, 2017 at 10:07:16PM +0100, Uwe Kleine-König wrote:
>>>> Currently there are two versions of libupnp in the archive:
>>>>
>>>>  - src:libupnp providing the 1.6.x branch of libupnp which is considered
>>>>    legacy by upstream
>>>>  - src:pupnp-1.8 providing the 1.8.x branch of libupnp
>>>>
>>>> I want to get rid of libupnp6 converting all rdeps to the newer libupnp
>>>> package.
>>>
>>> ...
>>
>> The list of open issues is down to:
>>
>>>  - amule
>>>    - FTBFS #884996 (patch)
>>>  - djmount
>>>    - FTBFS #884243
>>>  - gmrender-resurrect
>>>    - FTBFS #884246
>>>  - linphone
>>>    - FTBFS #884247
>>
>> Those still fail to build.
>>
>>>  - gmediaserver
>>>    - FTBFS #884245
>>
>> RM requested.
> (RM = Request to remove the package from testing)
> 
>> Considering that those packages had over 9 months to get fixed, I think we
>> should start the transition and RM the unfixed packages from testing.
> 
> The bug for gmrender-resurrect is tagged "help". I didn't look into that
> but I think it would be fair to check this one at least before starting
> to remove packages. I'll give it a bump in my todo list.
> 
> @Marcelo: Do you care to look into https://bugs.debian.org/884246 ?
> 
> Best regards
> Uwe
> 

Hi,

Before this transition can start, we will need a solution for amule,
djmount, gmrender-resurrect and linphone (which is either RM or upload
with a fix).

Removing all of them leads to the following collateral damage[1]:

"""
Checking reverse dependencies...
# Broken Depends:
kopete: kopete
libosmo-abis: libosmotrau2

# Broken Build-Depends:
kopete: libmediastreamer-dev (>= 3.6)
        libortp-dev (>= 0.13)
libosmo-abis: libortp-dev
libosmo-netif: libortp-dev
osmo-bts: libortp-dev

Dependency problem found.
"""
(I have not researched exactly which package causes what to break; that
is an exercise left for the reader)

Accordingly, if we plan on removing these packages, their dependencies
are now also a part of the transition (having to move away from the
packages being removed or being removed themselves - the latter leading
to a rinse-and-repeat effect).

So:

 * Which of amule, djmount, gmrender-resurrect, linphone are going to
   be fixed/removed?

 * What is and how do we handle the collateral (if any) from any
  removals?

Thanks,
~Niels


[1]:
dak rm -nR -s testing amule djmount gmrender-resurrect \
  linphone gmediaserver

Can be run from respighi.debian.org, which is DD-accessible.