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 handle better what it finds from first stage in such cases).
I kept the qemu-debootstrap task since if debootstrap develops something to be passed to second stage that needs modification of the second stage call that would have to be changed there. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
