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). The old version creates a config file dynamically depending on system configuration and the new version converts this file into a conffile managed by dpkg. In general, it is not correct to do this without asking the user if he wants to keep his automatically created version. Though in this case the config file is trivial and the change is described in NEWS.Debian, so it would probably not hurt too much to suppress the question. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
