Mark Sapiro said the following on 2006/09/15 04:42 PM: > I don't know why your installations were not all upgraded to email > 2.5.8 when you upgraded to 2.1.9, but they should have been.
I'm just as puzzled ;-) > Yes. In each installation there are copies of paths.py in the bin, > cron, scripts and tests directories. Each of these contains the > following section <snip useful solution - thanks muchly> > but the real issue is why didn't your 2.1.9 upgrade process install the > right email library in pythonlib in the first place. I don't know. I shut down each installation of mailman via the /etc/init.d/mailman.$domain init script before doing the `make && make install` after specific configuration options for each install. I suppose it's possible a stray process was still running? Anyway, the problem is sorted for now and I have some additional info for a single source of the pythonlibs. Now just to make sure a future upgrade path isn't compromised by opting for this. -- | Bretton Vine | 083 633 8475 | [EMAIL PROTECTED] | | GPG: http://bretton.hivemind.net/bretton_vine.asc | "If I work incessantly to the last, nature owes me another form of existence when the present one collapses." - Goethe, 1829 ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org 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
