Package: live-build Version: 1:20161216 I configure with: lb config --debian-installer live -d stretch --archive-areas main contrib non-free upstream restricted --linux-packages `dpkg-query -f '${binary:Package}\n' -W` This configures the target for the same packages as those installed on the build host. It seems to correctly configure: P: Creating config tree for a debian/stretch/amd64 system P: Symlinking hooks... Now whenever a build (lb build) is attempted it fails in the same way. The build chugs along retrieving/verifying/unpacking packages. So far so good. But the build eventually fails with: Reading package lists... Done Building dependency tree Reading state information... Done [2016-12-31 14:30:15] lb chroot_install-packages install P: Begin installing packages (install pass)... Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package a2ps-amd64 P: Begin unmounting filesystems... P: Saving caches... Reading package lists... Done Building dependency tree Reading state information... Done Note E: Unable to locate package a2ps-amd64 a2ps happens to be the first package in my package list. It doesn't matter which package is first - the build appends the suffix "-amd64" to create an illegal package name (no such package exists). As there are no options for either "lb config" or "lb build" which affect this behavior I'm concluding this is a bug. I've scoured all the documentation such as https://debian-live.alioth.debian.org/live-manual/stable/manual/html/live-manual.en.html and spent hours googling for answers or workarounds without success. Please advise. Build host: uname -a Linux nehalem 4.1.17 #2 SMP Sun Feb 14 22:42:14 CST 2016 x86_64 GNU/Linux |