On Tue, 2005-11-22 at 11:09 +1100, James Bunton wrote:
> Looks like you somehow got that upgrade routine to run on an already
> updated spool dir.
>
> Any idea how?
>
> That should only get run when migrating from PyMSNt 0.9.3 and lower.
>
> Did you delete the notes_to_myself file?
The file system got full somehow over the weekend. After cleaning up,
and restarting the services, the notes_to_myself file was there, but
empty.
From [EMAIL PROTECTED] Tue Nov 22 11:02:13 2005
From: [EMAIL PROTECTED] (James Bunton)
Date: Tue Nov 22 11:02:39 2005
Subject: [py-transports] PyMSN 0.10.2 spool error
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
On 22/11/2005, at 6:41 PM, Vladimir Vrzic wrote:
> On Tue, 2005-11-22 at 11:09 +1100, James Bunton wrote:
>> Looks like you somehow got that upgrade routine to run on an already
>> updated spool dir.
>>
>> Any idea how?
>>
>> That should only get run when migrating from PyMSNt 0.9.3 and lower.
>>
>> Did you delete the notes_to_myself file?
>
> The file system got full somehow over the weekend. After cleaning up,
> and restarting the services, the notes_to_myself file was there, but
> empty.
Ah.
You need to put these two lines in it
doSpoolPrepCheck
doHashDirUpgrade
---
James
