[Mailman-Users] Anything to look out for in a 2.1.9 to 2.1.14-1upgrade?

[Mark Sapiro]

Steve Burling wrote:

>Short version:
>
>Are there any gotchas in upgrading from 2.1.9 to 2.1.14-1 that I need to
>look out for?  I am, as usual in these cases, looking for the most expedient
>way to fix a problem I've brought on myself.


There are no gotcha's in upgrading from 2.1.9 to 2.1.14-1, but there
are gotcha's in upgrading a RedHat rpm installation from a source
distribution.

See the FAQ at <http://wiki.list.org/x/KYCB> and the patch in the
mailman-developers post linked from that FAQ.

But, see below.


[...]
>Yesterday, we replaced the web server hardware with a 64-bit Red Hat 6
>machine, which has python 2.6.6, and the web interface stopped working.
>Delivery to lists is working just fine.  In the mailman error log, I see the
>following:
>
>Jan 16 09:53:30 2012 admin(13467):
>@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
>admin(13467): [----- Mailman Version: 2.1.9 -----]
>admin(13467): [----- Traceback ------]
>admin(13467): Traceback (most recent call last):
>admin(13467):   File "/opt/mailman/scripts/driver", line 94, in run_main
>admin(13467):     pkg = __import__('Mailman.Cgi', globals(), locals(),
>[scriptname])
>admin(13467):   File "/opt/mailman/Mailman/Cgi/listinfo.py", line 27, in
><module>
>admin(13467):     from Mailman import MailList
>admin(13467):   File "/opt/mailman/Mailman/MailList.py", line 51, in
><module>
>admin(13467):     from Mailman.Archiver import Archiver
>admin(13467):   File "/opt/mailman/Mailman/Archiver/__init__.py", line 17,
>in <module>
>admin(13467):     from Archiver import *
>admin(13467):   File "/opt/mailman/Mailman/Archiver/Archiver.py", line 32,
>in <module>
>admin(13467):     from Mailman import Mailbox
>admin(13467):   File "/opt/mailman/Mailman/Mailbox.py", line 21, in <module>
>admin(13467):     import mailbox
>admin(13467):   File "/usr/lib64/python2.6/mailbox.py", line 18, in <module>
>admin(13467):     import email.message
>admin(13467): ImportError: No module named message
>
>I'm trying to figure out if there's an easy way to fix this, that *won't*
>break delivery to the lists.  Any hints much appreciated. 


You can fix this by removing the email directory from
/usr/lib/mailman/pythonlib so that Mailman will use the Python 2.6
email package instead of Mailman's which is not compatible, but this
won't fix all the Mailman 2.1.9/Python 2.6.x incompatibilities.

However, I have other questions.

Is RedHat distributing Mailman 2.1.9 with Python 2.6.6? If so, this is
bad, and see <http://wiki.list.org/x/OIDD>. If not, perhaps there is a
RedHat RPM you can use to upgrade.

OTOH, from the paths I see in the traceback above (prefix =
/opt/mailman), it seems your current Mailman may have been installed
from source rather than a RedHat RPM. If this is the case, just
configure Mailman 2.1.14-1 with the same options you used for 2.1.9,
stop mailman, make install and start mailman and you should be OK.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan