Quoting Agustin Martin (2014-07-15 18:11:06) > On Fri, Jul 11, 2014 at 11:37:14PM +0200, Jonas Smedegaard wrote: >> 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.
Uhm, please correct me if I'm wrong, but my experience is that dictionaries-common not only "complains loudly" but *fails*, which causes the whole package upgrade to fail. Seems that _this_ bug is not about the underlying corruption but how "loudly" as you call it it is treated by dictionaries-common (why else close it for newer package releases without the underlying issue fixed?). [snip] > 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. I believe the issue of dictionaries-common failing - thereby interrupting upgrade of upnrelated packages - is in itself serious enough for a stable fix, even if underlying issue is still unfixed. Since you seem to understand the underlying issue (I don't) did you file appropriate bugreport about that? If so, please mention bug number here, for others stumbling across this bugreport and (unlike me) interested concerned not about package upgrade interruption but the underlying corruption issue. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
