Bug#851554: Bug#851524: Building armhf image fwith qemu fails at bootstrapping stage if firmware section enabled

Well, I could've saved myself a couple of hours if I'd remembered to do a git pull. This is fixed in master, and the fixing commit was 952ac834 (Rohan Garg, "Simplify bootstrapping of foreign architectures with qemu-debootstrap"). Thanks Rohan! Sorry everyone else for the noise on this report! On

Bug#851554: Bug#851524: Building armhf image fwith qemu fails at bootstrapping stage if firmware section enabled

Just did a git-bisect on the live-build code in the anonscm repo, and apparently this is the first commit with the issue: c12f7d715eda1dec63d035362630d11ea0cc1f8e is the first bad commit commit c12f7d715eda1dec63d035362630d11ea0cc1f8e Author: Sjoerd Simons Date:

Bug#851554: Bug#851524: Building armhf image fwith qemu fails at bootstrapping stage if firmware section enabled

Just an FYI, I recently revisited this project and the issue is still present with live-build 1:20170213. If I have time I'll try to identify the problem.

Bug#851524: Building armhf image fwith qemu fails at bootstrapping stage if firmware section enabled

I'm going to try to dig into this and see if I can fix it. But if anyone knows off the top of their head where a likely place to start looking would be, please let me know. Otherwise I'll start with the bootstrap scripts. - Jason

Bug#851524: Building armhf image fwith qemu fails at bootstrapping stage if firmware section enabled

Thanks to everyone who pointed me to the Snapshot repo. I've managed to narrow down the problem now. I updated the makefile to only do up to the bootstrap stage, because that's where it fails. I changed the version of the live-build package that was installed, and *only* live-build, and tested it

Bug#851524: Building armhf image fwith qemu fails at bootstrapping stage if firmware section enabled

> Incidentally, if anyone *has* a link to the old deb package > for 1:20151215 so I could verify this, that'd help. Jason, have a look at http://snapshot.debian.org/ Cheers Daniel signature.asc Description: OpenPGP digital signature

Bug#851524: Building armhf image fwith qemu fails at bootstrapping stage if firmware section enabled

Okay, after clearing caches, cleaning up env vars, etc. I'm able to reliably reproduce the problem. I've attached two makefiles, one that works (in that, it builds an image, I don't care about running the image yet). The other fails to build with the aforementioned error. In the last version of

Bug#851524: Building armhf image fwith qemu fails at bootstrapping stage if firmware section enabled

On 16 January 2017 at 14:35, Jason Heeris wrote: > On 16 January 2017 at 14:20, Michael . wrote: > > If you are building a Raspbian image your initial config should work > I will try again and see if removing the firmware section makes a difference

Bug#851524: Building armhf image fwith qemu fails at bootstrapping stage if firmware section enabled

On 16 January 2017 at 14:20, Michael . wrote: > If you are building a Raspbian image your initial config should work But that's the problem, it doesn't. See: https://gist.github.com/detly/109b8201e7c81417af3a8f455f415a6d I will try again and see if removing the firmware

Bug#851524: Building armhf image fwith qemu fails at bootstrapping stage if firmware section enabled

If you are building a Raspbian image your initial config should work, if you are not building a Raspbian image it won't work and will fail simply because it is unable to find something you are telling it to look for. On 16 January 2017 at 14:08, Jason Heeris wrote: >

Bug#851524: Building armhf image fwith qemu fails at bootstrapping stage if firmware section enabled

On 16 January 2017 at 14:08, Jason Heeris wrote: > Here's a command to try building from a Raspbian image. s/ from// - Jason

Bug#851524: Building armhf image fwith qemu fails at bootstrapping stage if firmware section enabled

Here's a command to try building from a Raspbian image. env DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" lb config \ --archive-areas 'main firmware non-free' \ --distribution jessie \ --chroot-filesystem squashfs \ --architectures armhf \

Bug#851524: Building armhf image fwith qemu fails at bootstrapping stage if firmware section enabled

On 16 January 2017 at 10:21, Ben Armstrong wrote: > > I can't see how --archive-areas 'main firmware' would've ever worked, since 'firmware' is not valid. Hmm. It was left over from my original project which was a Raspbian live build, which suddenly started failing

Bug#851524: Building armhf image fwith qemu fails at bootstrapping stage if firmware section enabled

On January 15, 2017 6:39:27 PM Jason Heeris wrote: If I change the line: --archive-areas 'main firmware' Firmware is not a valid archive area in the Debian archive. Perhaps you meant non-free, where non-free firmwares are kept? ...to... --archive-areas 'main'

Bug#851524: Building armhf image fwith qemu fails at bootstrapping stage if firmware section enabled

Forgot to mention: this looks a lot like bugs #813232 and #571136. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571136 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813232 - Jason

Bug#851524: Building armhf image fwith qemu fails at bootstrapping stage if firmware section enabled

Package: live-build Version: 1:20161216 These two commands: lb config \ --archive-areas 'main firmware' \ --distribution jessie \ --architectures armhf \ --bootstrap-qemu-arch armhf \ --bootstrap-qemu-static /usr/bin/qemu-arm-static sudo lb build 2>&1 build.log ...result in a build