This bug was fixed in the package ubuntu-keyring - 2016.09.19
ubuntu-keyring (2016.09.19) yakkety; urgency=medium
* Ship each active key in a separate keyring in /etc/apt/trusted.gpg.d/
as conffiles for simpler usage of apt-secure(8).
* Remove all active keys from /etc/apt/trusted.gpg as they are shipped
now as fragment files.
* Depend on gpgv and only recommend gnupg.
* Stop calling apt-key update LP: #1619444
* Generate SHA512SUMS.txt.asc file, signed by me, and verified against
debian-keyring at build time as a weak consistency check.
-- Dimitri John Ledkov <x...@ubuntu.com> Fri, 16 Sep 2016 14:36:10
** Changed in: ubuntu-keyring (Ubuntu)
Status: New => Fix Released
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu.
apt-key should not be used in scripts
Status in ubuntu-keyring package in Ubuntu:
Got that comment while upgrading ubuntu-keyring:
Setting up ubuntu-keyring (2016.09.01) ...
Warning: apt-key should not be used in scripts (called from postinst
maintainerscript of the package ubuntu-keyring)
Warning: 'apt-key update' is deprecated and should not be used anymore!
DistroRelease: Ubuntu 16.10
Package: ubuntu-keyring 2016.09.01
ProcVersionSignature: Ubuntu 4.8.0-5.6-generic 4.8.0-rc4
Uname: Linux 4.8.0-5-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Date: Thu Sep 1 21:42:35 2016
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~touch-packages
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp