Hello again, I don't really have an opinion if this should be solved by - changing the priority of gnupg or gnupg2 (if that wasn't only another unrelated side effect of the change described in Comment #7) - adding a dependency to gnupg2 | gnupg to apt-setup-udeb if that would be possible. - using the patch from Comment #12
As far as I can see there was no progress in the upstream bug ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851774 ), yet. But they're not releasing on April 26th 2018. ;-) This might be a bug affecting only advanced admins using depoyment via preseed, but it will IMHO affect everyone of them. If they haven't deactivated key verification at all. ;-) Kind regards Lars -- 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: Confirmed Status in gnupg2 package in Ubuntu: Confirmed 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
