Package: ftp.debian.org Severity: normal Before continuing, I must first say that I am a *user* making a request to remove the mixmaster package. The /reportbug/ app only offered these choices:
1 ANAIS Package removal - Architecture Not Allowed In Source. 2 ICE Package removal - Internal Compiler Error. 3 NBS Package removal - Not Built [by] Source. 4 NPOASR Package removal - Never Part Of A Stable Release. 5 NVIU Package removal - Newer Version In Unstable. 6 ROM Package removal - Request Of Maintainer. 7 ROP Package removal - Request of Porter. 8 RoQA Package removal - Requested by the QA team. 9 other Not a package removal request, report other problems. 10 override Change override request. So I selected 8 RoQA but I'm not on the QA team. However, this is something the QA team should discuss. Rationale: The mixmaster package is effectively unmaintained*, and has reached a state of mostly broken, ultimately it diluting the Debian brand. I could not find any rules or criteria on quality standards for packages that acquire placement in an official Debian repository, but if there are any such standards mixmaster has likely fallen short of them. Grave bug 824827 was essentially treated as WONTFIX, leaving the application in a state that fails more often than not. The app relies on the services of message forwarding nodes, some of which have transitioned to more secure 4k key size. The mixmaster app (which does not support the new key size) routes messages to nodes it's not compatible with, causing traffic to be silently dropped. (*) Or perhaps mixmaster is maintained, but the package maintainer has opted to deliberately hold the package in a disfunctional state.
