mailman3 package missing in jammy, however mailman3 package from Debian 11 works with the other mailman3 packages from Jammy
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| mailman-hyperkitty (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
| Jammy |
In Progress
|
Undecided
|
Unassigned | ||
| mailman3 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
| Jammy |
Fix Committed
|
Undecided
|
Unassigned | ||
Bug Description
[ Impact ]
There is currently no version of Mailman in Ubuntu 22.04, meaning that people who depend on its functionality have limited options:
i) Stay on an older version of Ubuntu, but miss out on other update packages.
ii) Use a non-LTS Ubuntu release, but this results in a less stable experience and Mailman is principally a server package.
iii) Manually install the Debian package, but this requires manually updating it.
[ Test Plan ]
mailman3 should be available in Jammy with all DEP-8 tests passing.
[ Where problems could occur ]
Several packages are still present in Jammy, such as mailman3-web, despite mailman3 being removed. They will also have to be tested and potentially updated to be compatible with the version backported from Lunar.
[Original description]
1)
root@ubuntu22:~# lsb_release -rd
Description: Ubuntu 22.04.1 LTS
Release: 22.04
2)
root@ubuntu22:~# apt-cache policy mailman3
mailman3:
Installed: 3.2.2-1
Candidate: 3.2.2-1
Version table:
*** 3.2.2-1 100
100 /var/lib/
(shows version held from focal, see below)
3) I expect Jammy (22.04.1) to have a mailman3 versions to go along with the supplied mailman3-web package
4) What happened: mailman3 package missing in jammy, and mailman3-web supplied but incompatible with mailman3 version held over from focal.
When upgrading from Ubuntu 20.04.05 (focal) to 22.04.01 (jammy), mailman3 and mailman3-full packages are de-installed during upgrade. Strangely enough mailman3-web still makes it.
Of course, this results in a non-functional mailman3 installation (just a front-end without the backend).
Adding back the focal repositories and manually reinstalling mailman3 and mailman3-full 3.2.2-1 from focal into jammy gets mailman3 mostly up and running again (i.e. correctly distributes mails to lists).
Rest API password (i.e. admin_pass from /etc/mailman3/
After doing this, front end *mostly* works.
However, lists cannot be viewed when logged in as admin, instead the following error is displayed:
Something went wrong
HTTP Error 404: {"title": "404 Not Found"}
Event downgrading mailman3-web from 0+20200530-2 to 0+20180916-10 and then rebooting does not help.
When this happens, the following is logged to /var/log/
[pid: 749|app: 0|req: 9/9] 127.0.0.1 () {60 vars in 1359 bytes} [Fri Dec 9 00:21:22 2022] GET /mailman3/
ERROR 2022-12-09 00:21:25,565 749 postorius Un-handled exception: HTTP Error 404: {"title": "404 Not Found"}
Traceback (most recent call last):
File "/usr/lib/
response = wrapped_
File "/usr/lib/
return self.dispatch(
File "/usr/lib/
return super(MailingLi
File "/usr/lib/
return handler(request, *args, **kwargs)
File "/usr/lib/
primary_email = set_preferred(
File "/usr/lib/
mm_
File "/usr/lib/
super(User, self)._
File "/usr/lib/
return super(RESTObject, self)._
File "/usr/lib/
response, content = self._connectio
File "/usr/lib/
raise HTTPError(
urllib.
WARNING 2022-12-09 00:21:25,569 749 django.request Not Found: /mailman3/
WARNING 2022-12-09 00:21:25,569 749 django.request Not Found: /mailman3/
[pid: 749|app: 0|req: 10/10] 127.0.0.1 () {60 vars in 1399 bytes} [Fri Dec 9 00:21:25 2022] GET /mailman3/
| AlainKnaff (kubuntu-misc) wrote | #1 |
| summary: |
- mailman3 package missing in jammy + mailman3 package missing in jammy, and keeping focal version causes HTTP + Error 404: {"title": "404 Not Found"} |
| AlainKnaff (kubuntu-misc) wrote Re: mailman3 package missing in jammy, but mailman3-web supplied but incompatible with mailman3 held over from focal | #2 |
| description: | updated |
| summary: |
- mailman3 package missing in jammy, and keeping focal version causes HTTP - Error 404: {"title": "404 Not Found"} + mailman3 package missing in jammy, but mailman3-web supplied but + incompatible with mailman3 held over from focal |
| AlainKnaff (kubuntu-misc) wrote | #3 |
| summary: |
- mailman3 package missing in jammy, but mailman3-web supplied but - incompatible with mailman3 held over from focal + mailman3 package missing in jammy, however mailman3 package from Debian + 11 works with the other mailman3 packages from Jammy |
| Launchpad Janitor (janitor) wrote | #4 |
| Changed in mailman3 (Ubuntu): | |
| status: | New → Confirmed |
| Claus-Justus Heine (rotatingdrop) wrote | #5 |
| Dave Moskovitz (dave-thinktank) wrote | #6 |
| Jeremy Gregson (jrggv) wrote | #7 |
| information type: | Public → Public Security |
| information type: | Public Security → Public |
| Loeka Rogge (exur00) wrote | #8 |
| description: | updated |
| Changed in mailman3 (Ubuntu): | |
| status: | Confirmed → Invalid |
| Changed in mailman3 (Ubuntu Jammy): | |
| status: | New → Triaged |
| Lucas Kanashiro (lucaskanashiro) wrote | #9 |
| Steve Langasek (vorlon) wrote Please test proposed package | #10 |
| Changed in mailman3 (Ubuntu Jammy): | |
| status: | Triaged → Fix Committed |
| tags: | added: verification-needed verification-needed-jammy |
| Ubuntu SRU Bot (ubuntu-sru-bot) wrote Autopkgtest regression report (mailman3/3.3.8-1ubuntu1~22.04.1) | #11 |
| AlainKnaff (kubuntu-misc) wrote | #12 |
| AlainKnaff (kubuntu-misc) wrote | #13 |
| Lucas Kanashiro (lucaskanashiro) wrote | #14 |
| Changed in mailman-hyperkitty (Ubuntu): | |
| status: | New → Invalid |
| Changed in mailman-hyperkitty (Ubuntu Jammy): | |
| status: | New → In Progress |
| Bert Van de Poel (bhack) wrote | #15 |
Just "holding" the mailman3 and mailman3-full packages (using apt-mark hold) before upgrading from focal to jammy prevents them from being uninstalled. So no need to reinstall them and synchronize the REST password. However, the problem with list administration still happens:
Something went wrong
HTTP Error 404: {"title": "404 Not Found"}