curtin is also busted in cases where the user provides a 'keyid', or
even a 'key' (data inline).
It seems we can/should probably make add_apt_key_raw write data to
/etc/apt/trusted.gpg.d ourselves rather than using apt-key.
** Also affects: curtin (Ubuntu)
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
apt-key leaves files in /dev open after exit
Status in apt package in Ubuntu:
Status in curtin package in Ubuntu:
Status in gnupg2 package in Ubuntu:
In Ubuntu 16.10, but not in 16.04, apt-key leaves /dev/null and
/dev/urandom open after exiting. Here's a procedure to replicate the
1. Install Ubuntu 16.10. (I used MAAS for this task.)
2. Install the "lsof" package (which is not installed by default).
3. Type "lsof | grep dev" to see open files.
4. Type "sudo apt-key adv --recv-keys --keyserver
5. Type "lsof | grep dev" again.
6. Compare the output of the two "lsof" commands.
I'm attaching two files, before.txt and after.txt, that show the
before and after results from "lsof | grep dev" in this scenario. Note
that the /dev/null and /dev/urandom files are both open after apt-key
is run, but not before. This problem does NOT occur with Ubuntu 16.04.
This problem is preventing us (the server certification team) from
importing keys in a custom MAAS preseed script; after installing
successfully, umounting the installed image fails because of the open
files on /dev.
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~touch-packages
Post to : email@example.com
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp