Bug#433422: exim4: complains inappropriately about DEBCONFsomethingDEBCONF on upgrade

[Reid Priedhorsky]

Marc Haber wrote:
> On Tue, Jul 17, 2007 at 09:30:08AM -0500, Reid Priedhorsky wrote:
>> The point is that I think the check for DEBCONFsomethingDEBCONF 
>> overreaches: all the DEBCONF strings under /etc/exim4 that I could see 
>> appeared in ~ or .dpkg-old files, none of which are config files.
> 
> They might be. How do I know which include directives the local admin
> uses? I did not intend to write an exim config parser in shell, so I
> decided to err on the safe side and to offer a possibility to silence
> the warnings.
> 
>> I'm not sure if you intended it, but I was insulted by your reply.
> 
> And I am continuously insulted by people who require me to re-iterate
> things that are already in the BTS (this issue, three times) _AND_ in
> the docs.

Marc,

I do think there is a real bug here. Removing the files in question 
makes the error message go away:

reidster:/etc/exim4# /etc/init.d/exim4 restart
Stopping MTA for restart:DEBCONFsomethingDEBCONF found in exim 
configuration. This is most probably
caused by you upgrading to exim4 4.67-3 or later without accepting the
suggested conffile changes. Please read
/usr/share/doc/exim4-config/NEWS.Debian.gz for 4.67-2 and 4.67-4
  exim4_listener.
Restarting MTA: exim4.
reidster:/etc/exim4# find . -name '*~' -exec rm {} \;
reidster:/etc/exim4# find . -name '*.dpkg-old' -exec rm {} \;
reidster:/etc/exim4# find . -xtype f -exec grep -H DEBCONF {} \;
reidster:/etc/exim4# /etc/init.d/exim4 restart
Stopping MTA for restart: exim4_listener.
Restarting MTA: exim4.

I don't understand why it makes sense for your searching code to look 
for DEBCONF in those files -- no sane configuration would ever include 
them, and they are easy to generate in the process of normal admin tasks.

Thanks,

Reid