[Mailman-Users] What is really required to go from 2.0.x to 2.1.y?

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

Re: [Mailman-Users] What is really required to go from 2.0.x to 2.1.y?

Christopher Waltham wrote: process snipped, but it looks OK The problem is when I run bin/list_members on a list of whose membership I know well. Amazingly, when I run that command, I see list members from around 2-3 years ago; I do not see list members whom I absolutely know are on that

Re: [Mailman-Users] What is really required to go from 2.0.x to 2.1.y?

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? The

Re: [Mailman-Users] What is really required to go from 2.0.x to 2.1.y?

Christopher Waltham quoted me and wrote: A possibly viable alternative is to look at your 2.1.9 installation and just remove the config.pck and config.pck.last files from any lists/listname/ directory that has a config.db. Mailman will then convert the config.db the first time the list is