Your message dated Wed, 16 Apr 2008 17:40:43 -0400
with message-id <[EMAIL PROTECTED]>
and subject line exim has been removed from Debian, closing #316553
has caused the Debian Bug report #316553,
regarding apt upgrade message "db_upgrade: unrecognized file type"
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
316553: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=316553
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: exim
Version: 3.36-17
Severity: minor

Hi,

got a slightly older (~5 years) exim installation on Debian testing here.

During apt-get dist-upgrade I got:

Setting up exim (3.36-17) ...
db_upgrade: /var/spool/exim/db/retry.lockfile: unrecognized file type
db_upgrade: DB->upgrade: /var/spool/exim/db/retry.lockfile: Invalid argument

Setting up nmap...

[EMAIL PROTECTED]:/home/andi# ls -l /var/spool/exim/db/retry.lockfile
-rw-r-----  1 mail mail 0 Jul  4  2004 /var/spool/exim/db/retry.lockfile

[EMAIL PROTECTED]:/home/andi# ls -l /var/spool/exim/db/
total 48
-rw-r-----  1 mail mail 12288 Jun  9 14:41 retry
-rw-r-----  1 mail mail     0 Jul  4  2004 retry.lockfile
-rw-r-----  1 mail mail 24576 Jun  1 10:05 wait-local_smtp
-rw-r-----  1 mail mail     0 Jul  4  2004 wait-local_smtp.lockfile
-rw-r-----  1 mail mail 12288 Jul 29  2004 wait-remote_smtp
-rw-r-----  1 mail mail     0 Jul  4  2004 wait-remote_smtp.lockfile

Might be something to be fixed/cleaned up in that install, or not...

Thanks!

Andreas Mohr


--- End Message ---
--- Begin Message ---
Version: 3.36-18.2+rm

The exim package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.

For more information about this package's removal, read
http://bugs.debian.org/420191 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.

Don't hesitate to reply to this mail if you have any question.

Thank you for your contribution to Debian.
Barry deFreese


--- End Message ---

Reply via email to