[Bug 1260297] Re: status_update not sent any more, causes eternal hang on conffile prompts in aptdaemon

[Michael Vogt]

On Thu, Dec 12, 2013 at 01:49:46PM -0000, Martin Pitt wrote:
> Michael, btw, if you upload this please note that apt currently fails
> its autopkgtest. Primarily it produces a lot of stderr and fails to
> build during the test, but when I do that manually in a VM I also get
> one test case failure.
> 
> But this autopkgtest doesn't help much in the first place: it only tests
> the build tree, but it must test the actually installed apt (i. e.
> /usr/bin/). Can you run the tests against the installed package?

Indeed, sorry for that. I disabled autopkgtest for the last upload
again and prepared a branch that redirects stderr to a file (output is
mostly noise) and test the installed files instead of the build file.

One question - whats the best practise here, should the test also
check against the build tree? Or is it better to run the tests against
the build tree during the package build? I guess the later but would
be nice if you could confirm :)

Cheers,
 Michael

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1260297

Title:
  status_update not sent any more, causes eternal hang on conffile
  prompts in aptdaemon

Status in “apt” package in Ubuntu:
  Fix Released
Status in “apt” source package in Trusty:
  Fix Released

Bug description:
  On November 23, aptdaemon started to fail its tests [1]. In
  particular, it now eternally hangs in the conffile tests, which is
  reproducible locally perfectly well (on current trusty):

  $ PYTHONPATH=. python3 tests/test_configfileprompt.py ConfigFilePromptTestCase.test_keep
  [...]
  13:04:03 AptDaemon.Trans [DEBUG]: Emitting PropertyChanged: StatusDetails, silly-config wird konfiguriert
  13:04:03 AptDaemon.Worker.Terminal [DEBUG]: Setting up silly-config (0.1-0) ...
  13:04:03 AptDaemon.Worker.Terminal [DEBUG]: 
  13:04:03 AptDaemon.Worker.Terminal [DEBUG]: Configuration file `/etc/silly-packages.cfg' (actually `/tmp/tmp8q_w7btmp/etc/silly-packages.cfg')
  13:04:03 AptDaemon.Worker.Terminal [DEBUG]:  ==> File on system created by you or by a script.
  13:04:03 AptDaemon.Worker.Terminal [DEBUG]:  ==> File also in package provided by package maintainer.
  13:04:03 AptDaemon.Worker.Terminal [DEBUG]:    What would you like to do about it ?  Your options are:
  13:04:03 AptDaemon.Worker.Terminal [DEBUG]:     Y or I  : install the package maintainer's version
  13:04:03 AptDaemon.Worker.Terminal [DEBUG]:     N or O  : keep your currently-installed version
  13:04:03 AptDaemon.Worker.Terminal [DEBUG]:       D     : show the differences between the versions
  13:04:03 AptDaemon.Worker.Terminal [DEBUG]:       Z     : start a shell to examine the situation
  13:04:03 AptDaemon.Worker.Terminal [DEBUG]:  The default action is to keep your current version.

  After that it hangs eternally, you need to run "killall dpkg" to
  finish this.

  This coincides with the large apt update from  0.9.9.1~ubuntu5 to
  0.9.13~exp1ubuntu1 [2]; dpkg or aptdaemon itself haven't been uploaded
  in a while, so I'm fairly certain that either this is a regression in
  apt, or some deliberate new behaviour for which aptdaemon needs to be
  updated.

  I already ensured that the fix for bug 1254696 (Apt::Keep-Fds) does
  not help, and apparently aptdaemon does not even use that.

  [1] https://jenkins.qa.ubuntu.com/job/trusty-adt-aptdaemon/?
  [2] https://launchpad.net/ubuntu/+source/apt/0.9.13~exp1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1260297/+subscriptions