On Fri, Jun 13, 2014 at 12:25:19AM +0200, Adam Borowski wrote:
> On Thu, Jun 12, 2014 at 06:24:09PM +0200, Agustin Martin wrote:
> > On Thu, Jun 12, 2014 at 05:40:17PM +0200, Adam Borowski wrote:
> > > > Debconf database corruption might have happened for other reasons, and
> > > > I'd expect it to have affected more packages.
> 
> When testing on a quite large set of packages, only dictionaries-common
> seems to be affected.

dictionaries-common is the only one that complains about that, not
necessarily the one causing the corruption.

However that heavy complaint was intended to appear only when no reasonable
workaround was possible. However, for not simple corruptions this seems not
the case.

> > Note that this debconf database corruption is unlikely to have its origin
> > in dictionaries-common, it is probably caused by the combination of a
> > package and special circumstances. If dictionaries-common was to blame I
> > would have received a flood of bug reports about this.
> 
> Here's a reproducer:
> * install wheezy
> * install dictionaries-common
> * rm -rf /var/cache/*
> * dist-upgrade to jessie

In that case, you cannot expect your system to behave normally again without
a litte help. For selected values you can save them outside debconf, but for
things like shared questions you only save the selections, but not the
shared questions. Unless you regenerate the database, at least debconf
shared questions will not behave sanely.

I trusted owners of a debconf shared question to provide info about available
possibilities, and this will not work in such a big corruption. Fortunately,
once package is unpacked dictionaries-common has access to the same info
provided by the shared question, so I am changing code run in postinst to
use it. 

Current code for checking defaults is run at config and at that stage only
debconf info is expected to be available, this is why it was not working as
expected in this case.

Expect an upload soon with the above changes, once I test things a bit more. 
This should show a saner behavior.

Thanks for your feedback,

Regards,

-- 
Agustin


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to