Your message dated Sat, 14 Oct 2006 16:47:44 +0200
with message-id <[EMAIL PROTECTED]>
and subject line recovered file not present at location given in 
X-vi-recover-file
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
package: nvi
version: 1.79-22

kernal version 2.4.31-pre2
C library libc-2.2.5.so

Several recent reboots have resulted in my receiving a message, reporting
that a file has been saved for recovery (ie one identical message
each time the system reboots).  There is no file at the location given in
the message (and the X-vi-recover-file header), however - but there is a
binary containing an apparently unedited message (and other data) at the
location given by the X-vi-recover-path header.  Since I don't normally
use vi, and didn't find out about the recovered file until the system was
rebooted several weeks after the file was created, I'm unfortunately not
certain what I did to result in the recovery package's confusion.
My best guess is:

While part-way through reconfiguring mutt, I accidentally dropped myself
into vi, to create a message.  I then probably tried several of the more
commonly used escape/quit key-combinations before hitting on the correct
one.  This presumably resulted in a file which had (as far as vi was
concerned) been edited, but was still identical to the original unedited
version.

I can supply a copy of the binary and/or the recovery message if they
would be helpful.

Chris.


--- End Message ---
--- Begin Message ---
Hi,

if you don't mind, I'll close this report now. I've taken over the
package and am now scanning the bugtracker for old reports...


Regards,

Jan

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to