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 #164108
has caused the Debian Bug report #164108,
regarding exim: Purging exim leaves an empty /etc/exim
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.)
--
164108: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=164108
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: exim
Version: 3.36-3
Severity: minor
This patch removes /etc/exim if it's empty on purge. I hope this helps.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux ganymed 2.4.19 #1 Fri Aug 9 16:07:14 CEST 2002 i686
Locale: LANG=C, LC_CTYPE=de_DE
Versions of packages exim depends on:
ii cron 3.0pl1-72 management of regular background p
ii libc6 2.2.5-15 GNU C Library: Shared libraries an
ii libdb2 2:2.7.7.0-8 The Berkeley database routines (ru
ii libident 0.22-2 simple RFC1413 client library - ru
ii libldap2 2.0.23-14 OpenLDAP libraries (without TLS su
ii libpam0g 0.76-4 Pluggable Authentication Modules l
ii libpcre3 3.4-1.1 Philip Hazel's Perl Compatible Reg
-- no debconf information
--- exim.postrm.orig 2002-10-10 11:47:06.000000000 +0200
+++ exim.postrm 2002-10-10 11:48:47.000000000 +0200
@@ -29,6 +29,7 @@
# Remove logs, config file etc
rm -rf /var/log/exim /var/run/exim /etc/exim/exim.conf
+ rmdir /etc/exim 2>/dev/null || /bin/true
# Remove links from rc?.d.
update-rc.d -f exim remove >/dev/null
--- 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 ---
