debootstrap on Xenial creates broken install for Bionic related to gnupg1/gnupg2 apt-key dependencies

Bug #1767319 reported by Roman Fiedler on 2018-04-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
debootstrap (Ubuntu)
Undecided
Unassigned

Bug Description

"debootstrap bionic" run on Ubuntu Xenial will create a bootstrap installation missing any gnupg (not gpgv) tools. Thus continuing installation from the bootstrapped installation using own debian package archives will fail, as that would require adding of public keys for the private repository. Due to "apt-key" needing gnupg for internal operation, adding keys and thus installation will fail.

Reproduce: run debootstrap and check if "apt-key list" works or "gpg" is installed afterwards.

Expected behaviour: Debootstrap installation can be used as template for further setup or as LXC guest without additional modifications.

This bug could also be seen as a missing dependency on "apt" package, but not sure if it was omitted on purpose.

$ lsb_release -rd
Description: Ubuntu 16.04.4 LTS
Release: 16.04

$ apt-cache policy debootstrap
debootstrap:
  Installed: 1.0.78+nmu1ubuntu1.5
  Candidate: 1.0.78+nmu1ubuntu1.5
  Version table:
 *** 1.0.78+nmu1ubuntu1.5 500
        500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     1.0.78+nmu1ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

The same thing happens when debootstrap is used under Debian 9.

A workaround for this is using: --include=gnupg2

If you are using "lb build" you can configure it like this:
 lb config --debootstrap-options="--include=gnupg2"

I think that the correct package to use must be gnupg2 according to this wiki:
  https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes#Other_base_system_changes_since_16.04_LTS

Best regards!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers