| 2007-03-26 09:29:44 |
Colin Watson |
ubiquity: statusexplanation |
|
It's not entirely clear why debconf failed to acquire the lock here. Perhaps another instance was running somewhere, or perhaps something else unclear went wrong.
This change (which was NOT in time for the Feisty beta release, but will be in all future releases, including Feisty final) fixes one major known cause of this problem, namely that if the attempt to lock the file was unlucky enough to be interrupted by delivery of a signal then it wouldn't be retried. Even if that wasn't the problem here, debconf will now print more information which may help to determine the real cause of the problem. Thus, I do still welcome reports of this bug from users of more recent versions of Feisty than the beta.
debconf (1.5.13ubuntu1) feisty; urgency=low
* Resynchronise with Debian. Remaining changes:
- Install Python confmodule for python2.5 as well.
* Retry flock() on EINTR. Failing that, print the errno if flock() fails
so that we have a better chance of working out why.
* Set Maintainer to me for DebianMaintainerField (even though I'm part of
the maintenance team upstream ...).
-- Colin Watson <cjwatson@ubuntu.com> Fri, 23 Mar 2007 10:16:04 +0000 |
|
