Closed
Bug 457376
Opened 16 years ago
Closed 16 years ago
Upgrade mailman to 2.1.11
Categories
(mozilla.org Graveyard :: Server Operations, task)
mozilla.org Graveyard
Server Operations
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: reed, Assigned: reed)
References
Details
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+
Comment 1•16 years ago
|
||
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)
Comment 2•16 years ago
|
||
This is done right?
Assignee | ||
Comment 3•16 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 | ||
Comment 4•16 years ago
|
||
dm-mailman01 has been upgraded.
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Whiteboard: Done for notorious; still need to do dm-mailman01
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•