Bug#656088: gforge-web-apache2: prompting due to modified conffiles which where not modified by the user
Andreas Beckmann, 2012-07-05 15:30:37 +0200 : > On 2012-07-05 15:15, Roland Mas wrote: >> I can't limit that a posteriori, I'm afraid. Even for users who >> installed the very minimal set of packages and didn't customize >> anything, there's still at least the variability of the hostname. > > Well, you can extract the hostname and check, whether it was modified. > and you can remove the line with the hostname before running md5sum or > replace it with some placeholder first: I think that adding code that's only going to work in very specific conditions (ie. piuparts) but not in real-life scenarios, to a package that doesn't have a version in stable, isn't really something I want to spend much time on, as I feel there's not much call for it. I'm therefore going to downgrade the severity of this bug report; not closing, in case someone wants to do the necessary work. Thanks for detecting it in the first place anyway (and thanks for the other piuparts checks, they're much appreciated). Roland. -- Roland Mas 'And what would humans be without love?' RARE, said Death. -- in Sourcery (Terry Pratchett) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#656088: gforge-web-apache2: prompting due to modified conffiles which where not modified by the user
On 2012-07-05 15:15, Roland Mas wrote: > I can't limit that a posteriori, I'm afraid. Even for users who > installed the very minimal set of packages and didn't customize > anything, there's still at least the variability of the hostname. Well, you can extract the hostname and check, whether it was modified. and you can remove the line with the hostname before running md5sum or replace it with some placeholder first: sed -e "s/^HoStNaMe: $the_local_hostname/HoStNaMe: GENERIC.DEFAU.LT/" /etc/gforge/httpd.conf| md5sum Or can you just regenerate the httpd.conf in the preinst script on upgrades from pre-conffile and place it in a temporary location and compare that to the version in /etc? Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#656088: gforge-web-apache2: prompting due to modified conffiles which where not modified by the user
Andreas Beckmann, 2012-07-05 13:34:52 +0200 : > Hi Roland, Hi, > 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)? In 5.1 and 5.2 and beyond (ie. for wheezy), it's a standard conffile which will very rarely change from the shipped version. In 5.0 and older (ie. up until squeeze), it was generated from templates with variables filled in (including at the very least the hostname to be used by Apache for its virtual hosts). The list of templates itself was variable, since plugins could provide snippets of files that would be used when generating /etc/gforge/httpd.conf. > If you can limit the possible files created by the package in squeeze > just collect all possible md5sums of unmodified configuration files. I can't limit that a posteriori, I'm afraid. Even for users who installed the very minimal set of packages and didn't customize anything, there's still at least the variability of the hostname. Roland. -- Roland Mas Le weblog entièrement nu -- http://roland.entierement.nu/ Le photoblog entièrement net -- http://roland.entierement.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#656088: gforge-web-apache2: prompting due to modified conffiles which where not modified by the user
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
Bug#656088: gforge-web-apache2: prompting due to modified conffiles which where not modified by the user
Andreas Beckmann, 2012-03-19 18:23:27 +0100 : > Package: gforge-web-apache2 > Version: 5.1.1-3 > Followup-For: Bug #656088 > > Hi, > > the prompting due to modified /etc/gforge/httpd.conf has not been fixed > in 5.1.1-3: > > Setting up gforge-web-apache2 (5.1.1-3) ... > > Configuration file `/etc/gforge/httpd.conf' >==> File on system created by you or by a script. Hi, I'm trying to reproduce the error with a local piuparts, but apparently it lacks some of the magic you have (--allow-database, in particular :-) Nevertheless, I believe this particular problem is not really a problem in 5.1.1-* (wheezy/sid), but in 5.0.2-5 (squeeze) only. More precisely, the configuration scripts in 5.0.2-5 always regenerate this httpd.conf file from a template and fill some blanks with host names and IP addresses. So this file will always appear as locally modified on upgrades from 5.0. The 5.1 series replaces that large file with a single operative line (an Include directive for a set of smaller files), with no need for automated changes, so the "locally modified" thing should no longer happen. I'm not sure there's a way to fix that without touching the packages in stable; 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? Roland. -- Roland Mas Why did the tachyon cross the road? Because it was on the other side. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
