Dear Exim maintainers,

The following bug was filed for the release notes.
Can you review the attached proposed patch for the release notes.

On Tue, Mar 10, 2009 at 03:39:23PM +0100, Jutta Zalud wrote:
> 
> 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/exim-us...@exim.org/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.

I cut and pasted a paragraph from your NEWS file, so I guess this is
correct, but you may want to provide more information.

Thanks in advance,
-- 
Nekral
Index: en/issues.dbk
===================================================================
--- en/issues.dbk	(révision 6878)
+++ en/issues.dbk	(copie de travail)
@@ -441,6 +441,22 @@
   </para>
 </section>
 
+<section id="exim">
+  <title>Upgrading exim4</title>
+  <para>
+    It is necessary to either accept the offered configuration file change
+    for <systemitem role="package">exim4-config</systemitem> or to
+    manually check a manually changed exim configuration.  Exim will not
+    run if a configuration file of an older version is being used with a
+    more recent <systemitem role="package">exim4-config</systemitem>.
+  </para>
+  <para>
+    See the notes for version 4.67-4 in
+    <filename>/usr/share/doc/exim4-config/NEWS.Debian.gz</filename>
+    for more information.
+  </para>
+</section>
+
 <section id="nis">
 <title><acronym>NIS</acronym> and Network Manager</title>
 <indexterm><primary>NIS</primary></indexterm>

Reply via email to