Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: debootstrap (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:
Was there a bug filed upstream and if so, can you please share the ticket
number/link to ticket?
Couldn't really find a corresponding bug at
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=qemu-user-static.
Thanks.
--
You received this bug notification because you are a
Hi Alistair,
yes that matches 100% what I have found and is the reason I added a bug task
for debootstrap.
Sorry if I didn't sum it up so well, but yeah - I agree that the root cause is
the lack of an ability to pass such info to second stage (or alternatively that
second stage knows how to
Thinking about it, it actually wouldn't make too much sense to fix that
in the Ubuntu Delta of the two packages.
This bug is present in Debian too. So it would be best fixed in Debian,
and then Ubuntu will pick it up on the next merge.
Would you mind filing bug(s) with Debian please?
Mention
Yes, I expected the chroot to end up with the mirror I asked for in the
sources.list. This is the behaviour with a normal debbotstrap
invocation.
This doesn't actually have anything to do with the keyring file at all.
The reason this happens is because there is no mechanism for the first
stage
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
