[Piuparts-devel] Bug#466118: Bug#466118: Bug#466367: apache2.2-common: conffile question during upgrade

[Lars Wirzenius]

On ma, 2008-02-18 at 21:03 +0100, Stefan Fritsch wrote:
> On Monday 18 February 2008, Marc Haber wrote:
> > piuparts -d etch -d lenny fails when the package being tested pulls
> > in apache2, because dpkg issues a "conffile changed" question for
> > /etc/default/apache2 during apache2.2-common update, even if the
> > file was not changed since etch's apache2 was installed. This makes
> > the automated update fail.
> >
> > If you absolutely have to mess with your dpkg-conffiles, please do
> > it in a way that doesn't break an important test tool.
> 
> IMO apache2 is behaving perfectly sane and piuparts should handle this 
> corner case (e.g. by specifying --force-confnew).

Well, I disagree. I think every case where a package upgrade causes a
conffile change prompt from dpkg and the user has not, in fact,
themselves changed the conffile in question is a bug. piuparts finds the
bug.

Having piuparts ignore such problems would lessen its utility.

I'm not opposed to having an option in piuparts to add --force-confnew
in individual cases, but I am not going to enable it on archive wide
checks.