Bug#870936: mediatomb: should mediatomb be removed from unstable?

James Cowgill jcowgill at debian.org
Tue Nov 21 15:31:10 UTC 2017

Control: reassign -1 ftp.debain.org
Control: retitle -1 RM: mediatomb -- RoM; dead upstream, obsoleted by gerbera


On 06/08/17 19:00, James Cowgill wrote:
> On 06/08/17 09:50, Lucas Nussbaum wrote:
>> Source: mediatomb
>> User: debian-qa at lists.debian.org
>> Usertags: qa-removals-post-stretch
>> Hi,
>> Following a discussion[1] on the debian-qa@ mailing list on packages that
>> missed both jessie and stretch, I am proposing the removal of this package from
>> unstable, because:
>>   it was in unstable at the time of the stretch freeze
>>     but wasn't part of stretch
>> AND
>>   it was in unstable at the time of the jessie freeze
>>     but it wasn't part of jessie
>> AND
>>   it is still not in testing
>> AND
>>   it was not uploaded since the beginning of 2017.
> The answer is: yes it definitely should be removed.
> However, there is a replacement fork called gerbera (which I haven't
> finished packaging yet) and I don't want to lose all the open bugs
> against mediatomb which may also apply to gerbera. I'm going to try and
> finish it some time during DebConf so hopefully this won't be an issue...

gerbera is now in unstable, and I've reassigned all of mediatomb's bugs
to it. I therefore think mediatomb can be removed now.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20171121/dbd69882/attachment-0001.sig>

More information about the pkg-multimedia-maintainers mailing list