* debconf-apt-progress: DEBIAN_HAS_FRONTEND is always set here at some
point, even if only on the second run after starting debconf, so we need
to invert our handling of the check for whether we started the debconf
frontend ourselves (LP: #347648).
-- Colin Watson <email address hidden> Tue, 24 Mar 2009 03:22:29 +0000
This bug was fixed in the package debconf - 1.5.26ubuntu3
---------------
debconf (1.5.26ubuntu3) jaunty; urgency=low
* debconf- apt-progress: DEBIAN_HAS_FRONTEND is always set here at some
point, even if only on the second run after starting debconf, so we need
to invert our handling of the check for whether we started the debconf
frontend ourselves (LP: #347648).
-- Colin Watson <email address hidden> Tue, 24 Mar 2009 03:22:29 +0000