Hi Thomas, (adding the bug to CC as there's no reason to contact me personally).
On Thu, Mar 15, 2012 at 08:38:56PM +0800, Thomas Goirand wrote: > I am very concerned by #476946. It's affecting a lot of packages: > - phpmyadmin > - roundcube > - keystone > - etc. > > I had a look, and I can't really find how dbconfig works. As I > understand, everything is in dpkg/*, right? But then, how does it work? > Can you describe it a bit, so that I can find faster where the issue is? > Or maybe you can try to find the reason why there is #476946? For starters, I suggest you read through the documentation. There is a design document shipped in the package :) The problem in this case is that, by design, dbconfig-common is nuking all debconf settings before each run because "Debconf is not a registry", and Really Bad Things can happen to other people who are *not* pre-seeding if we allow the debconf settings to persist between installs/upgrades/etc. If you want to make pre-seeding work, without dropping the files in place ahead of time (which seemed to have unrelated problems, though my memory is pretty hazy on this topic by now), I think you'll have to patch dbconfig-common to: * accept a new debconf flag (let's call it "dbconfig-common/debconf_is_a_registry"). * find the portions of the code where the debconf settings are nuked, and; * make it conditional based on this new debconf value. * nuke the value of this new debconf setting immediately afterwards. * add mention of this behavior to the design document. * add mention of this feature to the developer "using" guide. If you or someone else is feeling particularly adventurous I'm happy to review a proposed change that does the above (or if you can motivate a better way to do it by all means be my guest). If you want bonus l33t points, there is a shunit based test framework which could use a test case for the same, though I wouldn't be so mean as to force you to figure that out as a pre-condition :) sean -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org