b-vol wrote: >The problem seems to >be 'bin/update' which runs only on new installations (where there is not >already a mailing list configured).
The problem appeared when bin/update did "import md5", but if bin/update hadn't run, Mailman would have encountered the same problem in operation because the SecurityManager.py module also does "import md5" and this in turn is imported by the MailList.py module which is imported by anything that touches a list. Also, the only time bin/update doesn't run on a "make install" is when the install is to a "DESTDIR" as when making a package for distribution. In the normal case, it always runs, and since its purpose is to update an existing installation's data and lists as necessary for the newly installed version, it would make no sense if it only ran on a "new" installation where by definition, it has nothing to do. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
