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

[Jason Heeris]

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 the
bright side, you can close it as fixed. And I can once again work on a
build procedure for live Raspbian images.

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

[Jason Heeris]

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:   Tue Nov 22 18:37:56 2016 +0100

Pass components to debootstrap --second-stage

Commit e24e4b in debootstrap fixed setup_available to work in the
--foreign case (iotw at the second stage). Unfortunately this breaks
things if components aren't passed to the second stage _and_ your main
component isn't called main.

To fix this, pass --components to both the first and second stage
debootstrap when needed.

Signed-off-by: Sjoerd Simons 

I will see if I can identify the offending change a little more
specifically.

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

[Jason Heeris]

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.