[Pkg-mailman-hackers] Bug#746592: Upgrade/backport mailman as package has been made unusable by DMARC

[Faidon Liambotis]

On Thu, May 01, 2014 at 07:21:27PM +0100, juichenieder-debbie at yahoo.co.uk wrote:
> http://wiki.list.org/display/DEV/DMARC

The way I see it, this bug report is for two different things:

1) Package a new upstream release. The current one is 2.1.18, a minor
update to 2.1.16 (released on October, 2013; followed by 2.1.17 in the
meantime) that unstable currently has. 

2.1.18 provides a better solution to the DMARC problem, a problem that
affects the vast majority of the mailman users running public mailing
lists (as they're bound to have e.g. Yahoo! subscribers) and is going to
affect even more of them as the time passes.

The package update seems trivial and the fact that it hasn't been
done since November 2013 (2.1.17 release date) suggests to me to that
the package is poorly maintained. Dear maintainer, have you thought
about RFHing the package? Would you be okay with me NMUing the package
outside the regular NMU rules to update to a new upstream release?

2) A backport of the current jessie version to wheezy-backports. As far
as I know, it's highly unusual for backport requests to be tracked in
the main BTS, but if the maintainer doesn't mind, I won't :)

Anyone can do the backport, as long the maintainer is okay with it. I'd
be happy to do it, but I'd like to see (1) done first as to not waste my
time with backporting an 9-month old piece of software.

Thanks,
Faidon