On Mon, Oct 27, 2008 at 12:52:57PM +0100, Bastian Blank wrote: > Package: request-tracker3.6 > Version: 3.6.7-3 > Severity: serious > > request-tracker3.6 uses debconf as a registry to detect which db > informations are available. The debconf data is volatile and therefor > not possible to be used in this way.
The debconf information (rt3.6-db-*/available) is only used on new installations or upgrades with an unmodified /etc/request-tracker3.6/RT_SiteConfig.pm. The aim was (of course) to aid the administrator by offering only the possible database choices. This is particularly hard to do otherwise in the preconfiguration case, where there is no other information source available because the rt3.6-db-* packages are usually not installed yet, only preconfigured. I suppose it would be enough if the rt3.6-db-* postinst scripts stored the debconf setting somewhere under /var and the config scripts then parsed those in. Thanks for the bug. -- Niko Tyni [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
