On Fri, Jul 11, 2014 at 11:37:14PM +0200, Jonas Smedegaard wrote: > reopen 751367 > seen 751367 1.12.11 > thanks > > This bug also exist in stable - the following is from executing > http://parl.debian.net/desktop/script.sh (which installs a bunch of > packages) in a clean Wheezy pbuilder chroot: > > [...] > Setting up dictionaries-common (1.12.11) ... > update-default-wordlist: Question empty but elements installed for class > "wordlist" > dictionaries-common/default-wordlist: return code: "0", value: "" > Choices: , Manual symlink setting > shared/packages-wordlist: return code: "10" owners/error: > "shared/packages-wordlist doesn't exist" > Installed elements: english (Webster's Second International English > wordlist) > > Please see "/usr/share/doc/dictionaries-common/README.problems", section > "Debconf database corruption" for recovery info.
Hi, Jonas > Please consider applying the bugfix also to a stable point release. The underlying bug is debconf database corruption and it is not fixed by dictionaries-common (nor known to be caused by it). Previously, dictionaries-common complained loudly (as above) when noticing it, pointing users to fix debconf database corruption (and giving advice on that), so underlying bug can be fixed and have things working as expected again. What has recently been changed in dictionaries-common is that instead of complaining that loudly, issues a debconf note warning about the problem and prompts for default wordlist and ispell dictionaries if needed and they could not be extracted from saved info (this feature was recently added to stop having info being saved only to debconf). Users are expected to deal with debconf database corruption at their sites, but no error appears during upgrade proccess. That note is still tagged as untranslatable and its contents under review by the debian-l10n-english team. Once that happens, translation process will start, but now it still unfinished. Since those changes do not fix the real underlying problem (debconf database corruption), but only change the package complains about it, I do not think it is eligible for a stable point release. Do not know what stable release team would think about this. Regards, -- Agustin -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
