Bug#503667: request-tracker3.6 - Use debconf as registry

2008-10-27 Thread Bastian Blank
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. Bastian -- Each kiss is as the first. --

Bug#503667: request-tracker3.6 - Use debconf as registry

2008-10-27 Thread Dominic Hargreaves
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

Bug#503667: [request-tracker-maintainers] Bug#503667: request-tracker3.6 - Use debconf as registry

2008-10-27 Thread Dominic Hargreaves
On Mon, Oct 27, 2008 at 12:26:18PM +, Dominic Hargreaves wrote: I propose to change debian/config to just check whether the rt3.6-db-* packages are installed to determine whether to support these packages (and then remove the db4.6-db-* config/postinst scripts altogether). Does this

Bug#503667: [request-tracker-maintainers] Bug#503667: request-tracker3.6 - Use debconf as registry

2008-10-27 Thread Niko Tyni
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

Bug#503667: [request-tracker-maintainers] Bug#503667: request-tracker3.6 - Use debconf as registry

2008-10-27 Thread Niko Tyni
On Mon, Oct 27, 2008 at 02:50:15PM +0200, Niko Tyni wrote: 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