[Debconf-devel] Bug#577632: Can't locate filetest.pm in @INC ... dpkg: error processing debconf

[Joey Hess]

Joey Hess wrote:
> I'd suggest this patch as the cleanest fix. Only problem is that
> DbDriver::Stack can fail if the topmost DbDriver in a stack is readonly,
> and this can turn DbDrivers that were at least apparently not readonly
> into readonly ones. I think, but am not sure, that the stack dbdriver
> would fail only if the file dbdriver would have failed before.

Actually, Stack doesn't fail here, it only debugs a complaint. So
my patch does not lead to new failures. 

It may lead to debconf *not* failing when it would have before. For
example, if a user runs debconf, and changes the db, with my change,
Stack will absorb the change that it cannot make, while before File
would at the end try to write to the database and fail with an error.
So, Stack probably should to remember write errors and propigate them at
the end, to mirror that behavior.

Also, note that the fix for #577299 did not address other DbDrivers,
particularly Directory, which also require write access to the db
when started readonly. So it needs the same kind of change to degrade
to readonly mode if it cannot write to its lock file.

-- 
see shy jo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 828 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/debconf-devel/attachments/20100413/01a9ee67/attachment.pgp>