Your message dated Sat, 13 Oct 2012 16:09:35 +0100
with message-id
<CALkubT7+CrXoEiWD54J6xaOYDoQusmsjAvqaA89+Pk+AxD=-v...@mail.gmail.com>
and subject line
has caused the Debian Bug report #519111,
regarding release-notes: exim4-upgrade fails when choosing "N"
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.)
--
519111: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=519111
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release-notes
Severity: normal
-- System Information:
Debian Release: 5.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
During dist-upgrade the user is asked several times if they wish to
install new config-files provided by the maintainer of the packet, keep
their old config files, see both files to compare. The default answer
is "N" - i.e. keep the old config files, and this is usually save. But
users run into troubles, when they do not install the new config-files
for Exim4 4.69. They are left with a broken exim4 they cannot even
uninstall easyly.
see eg:
http://lists.alioth.debian.org/pipermail/pkg-exim4-users/2009-March/001587.html
http://www.mail-archive.com/[email protected]/msg25245.html
http://lists.debian.org/debian-user-german/2009/02/msg01318.html
So I suggest that some warning be included into the Release notes,
that exim4-users should choose the new config-files unless they really
know what they are doing.
Best regards,
jutta
--- End Message ---
--- Begin Message ---
Thanks for reporting! since lenny is now obsolete this bug will now be closed
We are sorry it could not make it to lenny :(
--- End Message ---
