Re: [Mailman-Users] mailman upgrade -> bug

2005-02-18 Thread Brad Knowles
At 11:46 AM +0100 2005-02-18, Olivier Nibart wrote: - run dpkg-reconfigure mailman : this will force python to 'recompile' the file (there is probably a more elegant way to do it, but this one works). Simply updating the .py file and stopping/restarting Mailman should cause Python to recompile

Re: [Mailman-Users] mailman upgrade -> bug

2005-02-18 Thread Olivier Nibart
Hi, I've sent a mail to the package maintener 3 days ago, with no answer for the moment. As Brad said, they mis-applied the patch. Ax the system saiys, the problem comes from the SLASH variable that is not set : admin(20327): parts = [x for x in path.split(SLASH) if x not in ('.', '..')]admi

Re: [Mailman-Users] mailman upgrade -> bug

2005-02-17 Thread Brad Knowles
At 12:26 AM +0100 2005-02-15, denis wrote: I have made the security upgrade on debian to mailman version 2.1.5-6. And now, i have a bug in all the archives. Is it possible to fix that ? Looks like someone mis-applied the patch at . Try re-applying it co

[Mailman-Users] mailman upgrade -> bug

2005-02-17 Thread denis
Hi, I have made the security upgrade on debian to mailman version 2.1.5-6. And now, i have a bug in all the archives. Is it possible to fix that ? Thanks Denis admin(20327): [- Mailman Version: 2.1.5 -] admin(20327): [- Traceback --] admin(20327): Traceback (most recent call l