#1611 upgrade mailman3 stack for django 4.x
Closed: Fixed a month ago by arrfab. Opened a month ago by arrfab.

Actually deployment was done on pkg imported from epel9 , including django3 (what we tested) but epel9 rebased to django4 so we have to :

  • carefully import needed packages and dependencies into tags (candidate and testing)
  • verify if we need to modify ansible-role-mailman3
  • verify that mailman3 still works in .stg. and that we have all we need
  • promote to -release tag and update prod instance

Metadata Update from @arrfab:
- Issue assigned to arrfab

a month ago

Metadata Update from @arrfab:
- Issue tagged with: centos-common-infra, high-gain, high-trouble, investigation

a month ago

django4.2 was added into cbs infra tags but logic in that .spec doesn't even upgrade nor obsoletes python3-django3.
So a workaround was applied to ansible mailman3 role
and role was then applied to staging : https://lists.stg.centos.org is now ugpraded to django4.2

We'll merge back into main branch soon and upgrade prod instance after some validation tests

Merged into main branch and applied by ansible so closing

Metadata Update from @arrfab:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

a month ago

Log in to comment on this ticket.

Metadata