#563774 localepurge: config script forgets that user wanted to purge all locales

#563774#5
Date:
2010-01-04 16:26:30 UTC
From:
To:
Local changes to /etc/locale.nopurge are not preserved on upgrade. To
add insult to injury, they are not preserved even if the file was
generated by maintainer scripts: on each upgrade debconf proposes me to
keep all the installed locales (which is different form the set
I decided to keep last time).

#563774#10
Date:
2010-01-05 03:00:08 UTC
From:
To:
Hello Jakub,

i am unable to reproduce this behavior, and i think you should
definitely abstain from manually editing this configuration file.
You are not supposed to touch any configuration file which is handled
via debconf.

Please try to purge the package from your system, and then reinstall and
reconfigure it via the standard debconf way. Does this solve the issue?

Thanks a lot in advance!
P. *8^)

#563774#15
Date:
2010-01-05 03:00:08 UTC
From:
To:
Hello Jakub,

i am unable to reproduce this behavior, and i think you should
definitely abstain from manually editing this configuration file.
You are not supposed to touch any configuration file which is handled
via debconf.

Please try to purge the package from your system, and then reinstall and
reconfigure it via the standard debconf way. Does this solve the issue?

Thanks a lot in advance!
P. *8^)

#563774#20
Date:
2010-01-05 09:44:40 UTC
From:
To:
clone 563683 -1
severity -1 normal
retitle -1 localepurge: config script forgets that user wanted to purge all locales
thanks

* Paul Seelig <pseelig@debian.org>, 2010-01-05, 04:00:

It turns out that this happens only if I select no locales to keep.
Sorry for inadvertently reporting two issues in a single bugreport.

On the contrary, your package should abstain from violating Debian
Policy 10.7.3. ;) No, seriously.

Yes, I am, and your package is obliged to keep my modifications. Really.
Let me quote debconf-is-not-registry 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.