[Mailman-Developers] Trouble upgrading from ancient version

[mjinks at uchicago.edu]

On Thu, Nov 20, 2003 at 04:56:45PM -0500, Barry Warsaw wrote:
> 
> If it works for you, I'll commit this to cvs.

Thanks much.

It did get me a different error, at least:

Updating mailing list: 1-readamericanren
Traceback (most recent call last):
  File "bin/update", line 570, in ?
    errors = main()
  File "bin/update", line 447, in main
    errors = errors + dolist(listname)
  File "bin/update", line 187, in dolist
    mlist = MailList.MailList(listname, lock=0)
  File "/opt/pkgs/mailman-2.1.3/Mailman/MailList.py", line 128, in
__init__
    self.Load()
  File "/opt/pkgs/mailman-2.1.3/Mailman/MailList.py", line 616, in Load
    self.CheckVersion(dict)
  File "/opt/pkgs/mailman-2.1.3/Mailman/MailList.py", line 639, in
CheckVersion
    Update(self, stored_state)
  File "/opt/pkgs/mailman-2.1.3/Mailman/versions.py", line 53, in Update
    NewRequestsDatabase(l)
  File "/opt/pkgs/mailman-2.1.3/Mailman/versions.py", line 476, in
NewRequestsDatabase
    msg = Message.OutgoingMessage(text)
AttributeError: 'module' object has no attribute 'OutgoingMessage'
*** Error code 1
make: Fatal error: Command failed for target `update'


If this one has an obvious fix I'd love to hear about it, but if not, it
probably isn't worth any sweat.  We're going to take a different tack
with this, shut down the production list server for a couple of hours
next week to get "non-active" copies of the existing lists for upgrade
testing, then again when actual switchover time comes.

Thanks again,
-mrj
-- 
Michael Jinks, ENSA, NSIT, University of Chicago
"I have seen the future, and it makes no sense."