Oh, if it's trying to install amd64 when you're actually trying to build i386: 1) Did you previously try to build an amd64 image in this same directory? If so, the bootstrap stage gets cached, so you need to remove it (either by deleting cache/bootstrap, or executing lb clean --cache to purge the entire cache - probably best), before then doing lb config followed by lb build, if it is to build successfully, otherwise you'll have issues. However, when I stupidly did this very same thing when investigating the issues upiter and yourself are experiencing, this didn't manifest itself in those same issues, for me it was incorrectly building an amd64 image, then got confused when it couldn't find the i386 kernel to download. So perhaps this is not the case. 2) Make sure you're not only specifying the flavour as 686-pae, but also "--architectures i386". If you're building an i386 image on an amd64 host, and forgetting to set that, perhaps that might explain this, though I'm just throwing a possible idea out, I haven't checked the code.
Aside from this, read the big reply I just sent to upiter, and follow the instructions to replicate what I did. It would be good to userstand how on earth you two are ending up with both 3.2 and 3.16 instead of just 3.16. > and then live-build exits without creating an image. How is it getting 3.2.0-4 > and why does live-build appear to want to install linux-image-amd64 and the > one I specify in LB_LINUX_PACKAGES="linux-image-3.16.0-0.bpo.4"? > > Charles -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
