On 2013-09-24 14:12, Steven Shiau wrote: > > > [...] >> > Hi Niels,
Hi, > Thanks for the quick response. Actually I can reproduce the problem in > the bootstrap chroot environment. Here is how I reproduce the problem: > [...] Thanks for the step-by-step guide. > > The value is still "en_US.UTF-8", which I expect it should be > "ca_ES.UTF-8, de_DE.UTF-8". > > I also ran steps 5-6 again, and the step 7 step still showed me "Value: > en_US.UTF-8" > > Any suggestion or idea? > Thanks. > > Steven. > > [...] What happens is that the results of your debconf-communicate session is overridden the moment you run "dpkg-reconfigure localepurge" or upgrade localepurge. I have to either treat the config file or the debconf database as the canonical data source. localepurge/0.7.2 used the debconf database, but that was considered a bug. Jakub Wilk from #563774 (quoting the description of a Lintian tag): > | In the Unix tradition, Debian packages should have human-readable and > | human-editable configuration files. […] Typically, packages should use > | debconf-supplied information to generate configuration files, and — to > | avoid losing configuration information on upgrades — should parse > | these configuration files in the config script if it is necessary to > | ask the user for changes. So now it uses the generated config file (if available) to (re)seed the debconf database before asking requestions so the default is to generate the same config file you already have[1]. You may want to read the bugs #691431 and #563774 for more information as they are the reason the behaviour has changed (and why I believe I cannot change it back). ~Niels [1] With the exception of the "purge all"-case which is still broken. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
