Hi there, On Wednesday 13 January 2010, you wrote: > during a test with piuparts I noticed your package failed the piuparts > upgrade test because dpkg detected a conffile as being modified and then > prompted the user for an action. As there is no user input, this fails. But > this is not the real problem, the real problem is that this prompt shows up > in the first place, as there was nobody modifying this conffile at all, the > package has just been installed and upgraded...
looking into the changelog and the preinst it seems, its the following change:
* Rename config file to apt-proxy.conf instead of apt-proxy-v2.conf.
install|upgrade)
if [ -n "$PREV" ] && dpkg --compare-versions "$PREV" lt "1.9.37" ;
then
# This is NOT a fresh install, a previous version of the
package is either installed
# or configured (i.e. previous package deinstalled but not
purged).
if [ -r /etc/apt-proxy/apt-proxy-v2.conf ]; then
mv /etc/apt-proxy/apt-proxy-v2.conf /etc/apt-
proxy/apt-proxy.conf
fi
fi
;;
Is there a special reason for doing this?
"/etc/apt-proxy/apt-proxy-v2.conf" is shipped with the package in Lenny, so it
should exist on upgrade. Overwriting the existing config unconditionaly seems
suboptimal (so the configfile is changed in any case).
Thanks and with kind regards, Jan.
--
Never write mail to <w...@spamfalle.info>, you have been warned!
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GIT d-- s+: a C+++ UL++++ P+ L+++ E--- W+++ N+++ o++ K++ w--- O M V- PS PE Y++
PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h---- r+++ y++++
------END GEEK CODE BLOCK------
signature.asc
Description: This is a digitally signed message part.
