All users were logged out of Bugzilla on October 13th, 2018

Upgrade mailman to 2.1.11

RESOLVED FIXED

Status

RESOLVED FIXED
10 years ago
4 years ago

People

(Reporter: reed, Assigned: reed)

Tracking

Dependency tree / graph
Bug Flags:
needs-downtime +

Details

(Assignee)

Description

10 years ago
RPM all built and ready to go at im-pkgdev02:/usr/src/redhat/RPMS/i386/mailman-2.1.11-3mozilla0.i386.rpm.

Need to schedule time for this for next week. Note that dm-mailman01 and notorious will both need RHEL5 upgrades before this, of course.
Flags: needs-downtime+
(Assignee)

Updated

10 years ago
Blocks: 459262
We also need to either rebuild Majordomo2 or migrate those lists to mailman after the upgrade, too.

Migrating will probably be painful, I still haven't figured out the archive import stuff to move the archives into pipermail or whatever mailman is using for archives these days.

We should chkconfig postfix off prior to the upgrade to make sure it stays off after booting into rhel5, and make sure the individual upgrades to mailman and majordomo are in place prior to turning it back on.  (maybe httpd too, for good measure)
(Assignee)

Updated

10 years ago
No longer blocks: 458894

Comment 2

10 years ago
This is done right?
(Assignee)

Comment 3

10 years ago
(In reply to comment #2)
> This is done right?

Only on notorious. We can't do dm-mailman01 right now.
Whiteboard: Done for notorious; still need to do dm-mailman01
(Assignee)

Updated

10 years ago
Blocks: 460825
(Assignee)

Comment 4

10 years ago
dm-mailman01 has been upgraded.
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Whiteboard: Done for notorious; still need to do dm-mailman01
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.