Hi,
On Thu, May 05, 2011 at 01:04:05PM +0200, Stefan Eriksson wrote:
> > The answer should be "no" here as I've set boolean false but it goes with
> yes and tries to configure the database which I dont want :(
> >
> > Is there a way through this problem? How do I autoconfigure it to say no to
> the dbconfig-common question in the installation script?
>
> This is known bug in dbconfig-common that it ignores preseed. See
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476946 for more
> information. Merging bug accordingly.
I haven't read the full reports, but I've gotten similar questions from
users before about this. I think the problem is that you shouldn't be
relying on debconf to do th work for you in the first place (i.e. "debconf
is not a registry"). dbconfig-common is internally stateless, so it goes
out of its way to always use the local config rather than the transient
data in the debconf cache.
Instead of (or in addition to, guess it wouldn't hurt...) pre-seeding
debconf, have you tried just plopping in a config file at
/etc/dbconfig-common/<pkg>.conf ? The rest of the process (creating
tables/users/custom config files) should then honor that configuration.
sean
--
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
