group.of.nepali.translators team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

** Also affects: curtin (Ubuntu Zesty)
   Importance: Undecided
       Status: Fix Released

** Also affects: curtin (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: curtin (Ubuntu Xenial)
       Status: New => Fix Released

** Changed in: curtin (Ubuntu Xenial)
       Status: Fix Released => Confirmed

** Changed in: curtin (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: curtin (Ubuntu Xenial)
       Status: Confirmed => Triaged

** Changed in: curtin (Ubuntu Zesty)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1645680

Title:
  apt feature broken on >=Yakkety due to new gpg agent

Status in curtin:
  Confirmed
Status in GnuPG:
  Incomplete
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Xenial:
  Triaged
Status in curtin source package in Yakkety:
  Triaged
Status in curtin source package in Zesty:
  Fix Released

Bug description:
  Hi,
  while testing I found that when running apt feature related to add-apt-repository like:

  apt:
    sources:
      ignored1:
        source: "ppa:paelzer/yourppa"

  Or in fact any sort of add-apt-repository (also unrelated to the apt feature itself) like:
  late_commands:
   01_install_ppa: ['curtin', 'in-target --', 'add-apt-repository --yes ppa:paelzer/bug-1645274-multipath-merge']

  Then the installation fails.

  Both use the chroot to execute in target, but recent add-apt-
  repository seems so cause daemons to spawn which then let the umount
  fail.

  Failure is usually around something like:
  "umount: /tmp/tmptmucmfm0/target/dev: target is busy"

  
  Here an excerpt from a lsof +fg afterwards.
  dirmngr   6771             root    1r   CHR            LG,0x80000    1,9      0t0   11 /tmp/tmptmucmfm0/target/dev/urandom
  dirmngr   6771             root    2w   CHR                  W,LG    1,3      0t0    6 /tmp/tmptmucmfm0/target/dev/null
  gpg-agent 6776             root    0r   CHR                    LG    1,3      0t0    6 /tmp/tmptmucmfm0/target/dev/null
  gpg-agent 6776             root    1w   CHR                  W,LG    1,3      0t0    6 /tmp/tmptmucmfm0/target/dev/null
  gpg-agent 6776             root    2w   CHR                  W,LG    1,3      0t0    6 /tmp/tmptmucmfm0/target/dev/null

  One of them could be shut down by:
  gpg-connect-agent --verbose KILLAGENT
  But not dirmngr, that has to be killed.
  Actually killing them seems ok (does not seem to create and later fallout).

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1645680/+subscriptions