Comment 12 for bug 62986

I *believe* that I've finally got this fixed. However, I never could reproduce it myself, and the change to debconf-apt-progress verges on a rewrite of its main loop, so I would very much appreciate testing by anyone who could reproduce this. Tomorrow's daily build of Gutsy's alternate images, or Tribe 4 if you prefer, should include this fix.

debconf (1.5.14) unstable; urgency=low

[ Colin Watson ]
* Retry flock() on EINTR. Failing that, print the errno if flock() fails
so that we have a better chance of working out why.
* Install Python confmodule for python2.5 as well.
* Add confmodule bindings for the DATA command.
* Somebody looking at confmodule(3) probably actually wants
debconf-devel(7). Add a reference in SEE ALSO.
* Make sure that apt status commands and debconf protocol commands under
debconf-apt-progress are properly interleaved. Closes: #425397