← Back to branch summary

~ubuntu-branches/ubuntu/jaunty/debconf/jaunty

« back to all changes in this revision

Viewing changes to debconf-apt-progress

  • Committer: Bazaar Package Importer
  • Author(s): Colin Watson
  • Date: 2009-03-21 00:43:56 UTC
  • Revision ID: james.westby@ubuntu.com-20090321004356-3z0j22obs50dlbzi
Tags: 1.5.26ubuntu2
https://launchpad.net/bugs/337306
debconf-apt-progress: If we didn't start the debconf frontend ourselves,
then it's unlikely that the passthrough child will be able to start
debconf normally, so tell it to use a pipe database in that case and
rely on passthrough to save answers (LP: #337306).

Show diffs side-by-side

added added

removed removed

Lines of Context:
debconf-apt-progress
274
274
                $ENV{DEBCONF_READFD} = 5;
275
275
                $ENV{DEBCONF_WRITEFD} = 6;
276
276
                $ENV{APT_LISTCHANGES_FRONTEND} = 'none';
 
277
                # If we already had a debconf frontend when we started, then
 
278
                # the passthrough child needs to use the same pipe-database
 
279
                # trick as we do. See start_debconf.
 
280
                if ($ENV{DEBCONF_APT_PROGRESS_HAD_FRONTEND}) {
 
281
                        $ENV{DEBCONF_DB_REPLACE} = 'configdb';
 
282
                        $ENV{DEBCONF_DB_OVERRIDE} = 'Pipe{infd:none outfd:none}';
 
283
                }
277
284
                exec @_;
278
285
        }
279
286