Bug#907767: time to go, then
Control: clone -1 -2
Control: retitle -2 RM: mozplugger -- RoQA; useless; dead upstream
Control: reassign -2 ftp.debian.org
In Sep 2018, Adrian Bunk wrote:
> As far as I can see, not a single one of the 15 (sic) browser packages
> in the dependencies does both still exist in unstable and still work
> with mozplugger.
So what's the reason to keep it?
I happen to know a group of guys (11 humans, 1 cat/god) who are good at
dealing with "package X exists when it shouldn't". Have at it!
drill -t any mozplugger.mozdev.org
→ NXDOMAIN
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can.
⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener.
⠈⠳⣄⠀⠀⠀⠀ A master species delegates.
Reply to: