Hi Roland, sorry, it took me a while to answer this ...
On 2012-03-20 14:24, Roland Mas wrote: > I'm not sure there's a way to fix that without touching the packages > in stable; Touching stable is not an option, this needs to be fixed by the package in squeeze. > so, while I agree this bug is valid for the squeeze->wheezy > upgrade, it should be tagged as only concerning versions up to 5.1.1-2. > > What do you think? How does /etc/gforge/httpd.conf get created? Is there any local customization (like a hostname) by default or is it the sam efile in all installations (until customized)? If you can limit the possible files created by the package in squeeze just collect all possible md5sums of unmodified configuration files. Then in the preinst compute the md5sum of an existing /etc/gforge/httpd.conf and compare it to the list, move it aside it matching and delete the backup in postinst. This will allow installation of the clean new file without prompting. IIRC the initscripts and basefiles packages in sid do something similar for /etc/default/rcS and /etc/profile Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
