I was just about to report this, so here goes...
On Fri, 2003-10-17 at 18:41, Barry Warsaw wrote:
> On Fri, 2003-10-17 at 12:34, Marc MERLIN wrote:
>
> > Oops, forgot the most important.
> > I upgraded to cvs (2.2a0) and the problem was still there.
> >
> > The patch applied to 2.2a0 and fixed the problem
>
> Okay, that's bad. ;)
>
> BTW, I should mention that if you're running your production servers
> from CVS, I /highly/ recommend you move to the Release_2_1-maint branch
Unfortunately, there is a bug when upgrading lists (at least from MM
2.1.2) to the Release_2_1-maint branch.
It seems to be caused by the latest SYNC_AFTER_WRITE patch:
Upgrading from version 0x20102f0 to 0x20103f0
getting rid of old source files
Updating mailing list: kpf
Updating the held requests database.
- updating old private mbox file
- updating old public mbox file
Traceback (most recent call last):
File "bin/update", line 570, in ?
errors = main()
File "bin/update", line 447, in main
errors = errors + dolist(listname)
File "bin/update", line 334, in dolist
mlist.Save()
File "/home/mailman/Mailman/MailList.py", line 522, in Save
self.__save(dict)
File "/home/mailman/Mailman/MailList.py", line 481, in __save
if mm_cfg.SYNC_AFTER_WRITE:
AttributeError: 'module' object has no attribute 'SYNC_AFTER_WRITE'
make: *** [update] Error 1
After upgrading to Release_2_1-maint, none of my lists would save, so I
had to use the Release_2_1_3 branch instead. :)
> instead of the HEAD. 2.2a0 (CVS HEAD) will likely see increased
> instability as I start to work on the code.
>
> -Barry
>
-Daniel
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
