I tried several combinations: $ sudo qemu-debootstrap --no-check-gpg --arch=armhf jessie ./test-root-jessie-raspian http://mirrordirector.raspbian.org/raspbian $ sudo qemu-debootstrap --no-check-gpg --arch=armhf jessie ./test-root-jessie $ sudo qemu-debootstrap --no-check-gpg --arch=armhf jessie ./test-root-jessie-mirrorset http://httpredir.debian.org/debian/ $ sudo qemu-debootstrap --no-check-gpg --arch=armhf trusty ./test-root-trusty
All jessie ones have deb http://httpredir.debian.org/debian jessie main The Trusty has deb http://ports.ubuntu.com/ubuntu-ports trusty main As far as I understood your report you'd have expected to see http://mirrordirector.raspbian.org/raspbian there right? AFAIK the distribution defines the keyring. And as you already pointed out: I: Keyring file not available at /usr/share/keyrings/debian-archive-keyring.gpg; switching to https mirror https://mirrors.kernel.org/debian Maybe that is it: $ sudo qemu-debootstrap --no-check-gpg --arch=armhf jessie ./test-root-jessie-raspian-keyset --keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg http://mirrordirector.raspbian.org/raspbian But then this is happening at --second-stage and since this is defined as: --second-stage Complete the bootstrapping process. Other arguments are generally not needed. It gets no further arguments when called e.g.: I: Running command: chroot ./test-root-jessie-raspian-keyset /debootstrap/debootstrap --second-stage I: Keyring file not available at /usr/share/keyrings/debian-archive-keyring.gpg; switching to https mirror https://mirrors.kernel.org/debian The failing check on key and fallback is in "/usr/share/debootstrap/functions". The one that is interesting is copied into $tgtdir)/deboostrap/ So modifying that for debugging a bit. Breaking that down: $ mkdir test-root-jessie-raspian-stepbystep $ debootstrap --arch armhf --foreign --no-check-gpg --keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg jessie ./test-root-jessie-raspian-stepbystep http://mirrordirector.raspbian.org/raspbian # modify for debugging $ sudo cp /usr/bin/qemu-arm-static ./test-root-jessie-raspian-stepbystep/usr/bin/ $ chroot ./test-root-jessie-raspian-keyset /debootstrap/debootstrap --second-stage Deconstructing whats going on there. - First of all the issue is reproducible there - Setting the keyring in stage 2 fails as that needs gpgv (intended to run in stage 1 only) - setting --no-check-gpg in stage 2 fails as well - the raspbian keyring only comes later when the respective file is installed (raspbian-archive-keyring) I also tried with a modified debootrap script for raspbian, but that failed me as well. I'm out of ideas - but I'm pretty much (>80%) convinced that this is far more a deboostrap bug than of the qemu-debootrap wrapper. Yet my debootrap-foo is limited, adding a proper bug task and look forward for deboostrap experts to do some magic. ** Also affects: debootstrap (Ubuntu) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670905 Title: qemu-debootstrap inserts debian repos into the chroot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1670905/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
