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 [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
