[Bug 1999197] Re: mailman3 package missing in jammy, however mailman3 package from Debian 11 works with the other mailman3 packages from Jammy

Fri Sep 29 23:12:34 UTC 2023

Hello AlainKnaff, or anyone else affected,

Accepted mailman3 into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mailman3/3.3.8-1ubuntu1~22.04.1 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: mailman3 (Ubuntu Jammy)
       Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1999197

Title:
  mailman3 package missing in jammy, however mailman3 package from
  Debian 11 works with the other mailman3 packages from Jammy

Status in mailman3 package in Ubuntu:
  Invalid
Status in mailman3 source package in Jammy:
  Fix Committed

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 at ubuntu22:~# lsb_release -rd
  Description:    Ubuntu 22.04.1 LTS
  Release:        22.04

  2)
  root at 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/dpkg/status

  (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/mailman.cfg
  needs to be copied to MAILMAN_REST_API_PASS in /etc/mailman3/mailman-
  web.py).

  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/mailman3/web/mailman-web.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/postorius/lists/ => generated 8958 bytes in 56 msecs (HTTP/1.1 200) 7 headers in 220 bytes (1 switches on core 0)
  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/python3/dist-packages/django/core/handlers/base.py", line 181, in _get_response
      response = wrapped_callback(request, *callback_args, **callback_kwargs)
    File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 70, in view
      return self.dispatch(request, *args, **kwargs)
    File "/usr/lib/python3/dist-packages/postorius/views/generic.py", line 74, in dispatch
      return super(MailingListView, self).dispatch(request, *args, **kwargs)
    File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 98, in dispatch
      return handler(request, *args, **kwargs)
    File "/usr/lib/python3/dist-packages/postorius/views/list.py", line 301, in get
      primary_email = set_preferred(request.user, mm_user)
    File "/usr/lib/python3/dist-packages/postorius/utils.py", line 77, in set_preferred
      mm_user.preferred_address = primary_email.email
    File "/usr/lib/python3/dist-packages/mailmanclient/restobjects/user.py", line 57, in __setattr__
      super(User, self).__setattr__(name, value)
    File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py", line 131, in __setattr__
      return super(RESTObject, self).__setattr__(name, value)
    File "/usr/lib/python3/dist-packages/mailmanclient/restobjects/user.py", line 145, in preferred_address
      response, content = self._connection.call(url, {'email': email})
    File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 160, in call
      raise HTTPError(params.get('url'), response.status_code,
  urllib.error.HTTPError: HTTP Error 404: {"title": "404 Not Found"}
  WARNING 2022-12-09 00:21:25,569 749 django.request Not Found: /mailman3/postorius/lists/lilux-info.lilux.lu/
  WARNING 2022-12-09 00:21:25,569 749 django.request Not Found: /mailman3/postorius/lists/lilux-info.lilux.lu/
  [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/postorius/lists/lilux-info.lilux.lu/ => generated 6374 bytes in 192 msecs (HTTP/1.1 404) 7 headers in 227 bytes (1 switches on core 1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mailman3/+bug/1999197/+subscriptions