> DM> The standard way; config (as me) and "make install" (as root).
>
> Did you install over an existing Mailman 2.0.x installation, or did
> you do a fresh MM2.1 install and copy list directories over?
I've been running "latest CVS" for some time, so it was a previous revision
of 2.1a.
> >> Try using bin/dumpdb on both the (old) config.db value and the
> >> (new) config.pck value and check attributes like
> >> `data_version', and `delivery_status'.
>
> DM> Where do I find the old and new files?...the new ones are
> DM> obviously there, but the old ones aren't saved by upgrade, are
> DM> they?...it'd be nice if they were somewhere I'm missing,
> DM> because then I could manually fix the problem. (No, I don't
> DM> have backups.)
>
> All the files should be in lists/<listname>/config.{db,pck}{,.last}
>
> The upgrade procedure doesn't get rid of the .db files.
I thought "last" was the last time anything changed with a list setting?
It's got a very recent date.
There *is* "config.pck.backup.dec.30"; is that the one preserved by
upgrade/update?
_______________________________________________
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-developers
