Hi, looks like this has happened when changing the source of gnupg to gnupg2 with 2.2.4-1ubuntu1.
The old source svn://anonscm.debian.org/pkg-gnupg/gnupg/trunk/ contains the Package as important. The new source https://anonscm.debian.org/git/pkg-gnupg/gnupg2.git contains the Package as optional. gnupg2 was present before, but the did not build a gnupg-Package. Kind regards, ** Also affects: gnupg2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore Status in apt-setup package in Ubuntu: Confirmed Status in gnupg package in Ubuntu: New Status in gnupg2 package in Ubuntu: New Bug description: In di if the kernel is in a private PPA we seed di using d-i apt-setup/local0/key string http://keyserver.ubuntu.com:11371/pks/lookup?op=get&search=<key> this used to work in xenial, but in bionic this fails and therefore apt update fails in base-installer. May be because add-apt-key is not installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
