On Sep 18, 2008, at 11:18 PM, Mark Sapiro wrote:
Christopher Waltham wrote:
Bug in Mailman version 2.1.10
We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing
of
traceback and other system information has been explicitly inhibited
I have a server with 873 lists (yes really!), but only one seems to be
misbehaving. Specifically, when you go to the admin web interface and
click on Membership Management, I get an error saying:
Bug in Mailman version 2.1.10
We're sorry, we hit a bug!
Please inform the webmaster for this
I am almost hesitant to post this email at all, because I am so amazingly
confused at what is going on I half-think I'm imagining it.
I have a Mailman 2.0.12 instance (not 2.0.5 as I previously thought, sorry
Mark) running on a Solaris 8 SPARC server, which I'd planned to move onto a
Linux
Again, apologies for the way Exchange Webmail quotes messages.
-Original Message-
From: Mark Sapiro [mailto:[EMAIL PROTECTED]
Sent: Fri 3/14/2008 1:37 PM
To: Christopher Waltham; mailman-users@python.org
Subject: Re: [Mailman-Users] What is really required to go from 2.0.x to 2.1.y
I just migrated a Mailman installation (~800 lists, ~5000 users) from 2.1.5 on
SPARC Solaris to 2.1.9 on Linux x86. In the process, it looks like existing
list passwords have become corrupted.
Is there an easy way to migrate those passwords across? I can't find anything
in the FAQs, and
I just migrated a Mailman installation (~800 lists, ~5000 users) from 2.1.5
on SPARC Solaris to 2.1.9 on Linux x86. In the process, it looks like
existing list passwords have become corrupted.
Is there an easy way to migrate those passwords across? I can't find anything
in the FAQs, and really
