…And, that was it. Reverting to an earlier backup that got the whole
thing solved the problem.
On Jul 22, 2014, at 11:17 AM, Mark Sapiro wrote:
> On 07/22/2014 11:09 AM, McGregor, Donald (Don) (CIV) wrote:
>>
>> So it looks like I’m missing the config.pck files on the lists
>> from the old hos
On 07/22/2014 11:09 AM, McGregor, Donald (Don) (CIV) wrote:
>
> So it looks like I’m missing the config.pck files on the lists
> from the old host. Did I get a bad backup? The disks eventually
> blew up on the old host so that’s plausible.
If the config.pck files are missing from your backups,
> Some systems put the configs and so on in a different place from the
> "standard" mailman install. I infer that you have the right place,
> but please confirm. On my Debian system, list configs look like
>
> /var/lib/mailman/lists/LISTNAME/config.pck
>
> and I've never seen a system that didn
On 07/21/2014 08:43 PM, Stephen J. Turnbull wrote:
>
> How old was the old Mailman? AFAIK old configs should automatically
> be upgraded if necessary when you upgrade Mailman, unless they're very
> very old (< 2.1.9 at a guess).
Way older than that. Even config.db files from Mailman 2.0.x will
Don:
> I’m attempting to bring it up on a new box with a yum-supplied copy
> of mailman rather than the old-fashioned hand install.
Some systems put the configs and so on in a different place from the
"standard" mailman install. I infer that you have the right place,
but please confirm. On my
I had a server blow up on me. It’s dead, Jim, but I have backups of the
/usr/local/mailman directory, and
I’m attempting to bring it up on a new box with a yum-supplied copy of mailman
rather than the
old-fashioned hand install.
I’ve got the yum-supplied version configured, and can create new li
