Hi folks, I have been tasked with moving a Mailman 2.0.12 installation from a Solaris (SPARC) server to a Linux (x86) server. The Linux server will be receiving a copy of Mailman 2.1.9, so obviously I am making the 2.0.x -> 2.1.x jump in there. Also, on Solaris, Mailman lives in / home/mailman but on Linux I will be putting it in /blender/mailman (and thus using move_list to update archives, fix_url, etc.)
What makes this migration slightly tricky is that the server hosts around 840 lists. Therefore, going through each list pre- and post- migration by hand would be a little time-consuming for me, so I want to avoid that where possible :-)I noticed that, when doing a "make update" when installing 2.1.9, a couple of lists from 2.0.12 failed the update process and I had to Control-C them for the process to continue. I'm not sure what the exact problem was, hence I'm wondering if there is any kind of check that I can run in a FOR loop to verify a list's integrity. And, yes, I've run check_db and check_perms and neither report problems, this just seems to be a handful of lists out of the 800-odd that seem a little flaky. Thanks, Chris ------------------------------------------------------ Mailman-Users mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
