|Open||Security||None||T181803 Stop storing Mailman passwords in plain text|
|Open||None||T118641 Implement proper AAA for lists.wikimedia.org (mailman)|
|Open||None||T190054 List archives on lists.wikimedia.org is not mobile friendly|
|Open||None||T115329 "From" at start of line becomes ">From" in pipermail|
|Open||None||T52864 Upgrade GNU Mailman from 2.1 to Mailman3|
|Resolved||Legoktm||T256541 Fix the problem with gravatar and mailman3|
|Declined||Ladsgroup||T276687 Backport hyperkitty 1.3.4 for buster|
You want to be running Debian Buster/testing/unstable, because that has all the tooling available (you can also do this in a container). apt-get install build-essential git-buildpackage devscripts dh-python
Then you want to set up a buster chroot so your package builds are clean, see https://wiki.debian.org/git-pbuilder
gbp clone https://salsa.debian.org/mailman-team/hyperkitty You can checkout the debian/1.3.4-2 tag and create a buster-wikimedia branch.
Create a new entry in debian/changelog, see https://gerrit.wikimedia.org/r/plugins/gitiles/operations/debs/pygments/+/refs/heads/debian/buster-wikimedia/debian/changelog for example. The version'll be something like 1.3.4-2~bpo10+1~wmf1
Then try to build it with gbp buildpackage. If you're lucky, it'll just work and you'll have debs in the parent directory that you can test.
Otherwise you'll need to go through the failures and see if you need a different dependency (listed in debian/control) or need to patch stuff. See https://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.patches.html
Depending on how extensive your changes are, we can copy the git repo into Gerrit and host a fork with the backport changes...if it's just a changelog entry we don't need to go through all that hassle.