Chances are that this was fixed by partitioner changes since Dapper,
such as avoiding the mad scheme where partman was left running during
the summary page, or the introduction of the new advanced partitioner in
Feisty. Failing that ...
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 <[EMAIL PROTECTED]> Fri, 23 Mar 2007 10:16:04 +0000
** Changed in: ubiquity (Ubuntu)
Assignee: (unassigned) => Colin Watson
Status: Confirmed => Fix Released
--
two debconf frontends active at partman_commit
https://launchpad.net/bugs/47670
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
