Ok, my bad. But there are plenty of
examples oqn the web of specifying pacmgkages via the "lb config"
command such as:
http://www.debianuserforums.orrg/viewtopic.php?f=9&t=185
The --packages option shown there and in other examples isn't
available in my version of live-build:
lb config [--apt apt|aptitude]
[--apt-ftp-proxy URL]
[--apt-http-proxy URL]
[--apt-indices true|false]
[--apt-options OPTION|"OPTIONS"]
[--aptitude-options OPTION|"OPTIONS"]
[--apt-pipeline DEPTH]
[--apt-recommends true|false]
[--apt-secure true|false]
[--apt-source-archives true|false]
[-a|--architectures ARCHITECTURE]
[-b|--binary-images iso|iso-hybrid|netboot|tar|hdd]
[--binary-filesystem fat16|fat32|ext2|ext3|ext4|ntfs]
[--bootappend-install PARAMETER|"PARAMETERS"]
[--bootappend-live PARAMETER|"PARAMETERS"]
[--bootappend-live-failsafe PARAMETER|"PARAMETERS"]
[--bootloaders grub-legacy|grub-pc|syslinux|grub-efi]
[--cache true|false]
[--cache-indices true|false]
[--cache-packages true|false]
[--cache-stages STAGE|"STAGES"]
[--checksums md5|sha1|sha256|sha512|none]
[--compression bzip2|gzip|lzip|xz|none]
[--config GIT_URL::GIT_BRANCH]
[--zsync true|false]
[--build-with-chroot true|false]
[--chroot-filesystem
ext2|ext3|ext4|squashfs|jffs2|none]
[--clean
[-c|--conffile FILE]
[--debconf-frontend
dialog|editor|noninteractive|readline]
[--debconf-priority low|medium|high|critical]
[--debian-installer
true|cdrom|netinst|netboot|businesscard|live|false]
[--debian-installer-distribution daily|CODENAME]
[--debian-installer-preseedfile FILE|URL]
[--debian-installer-gui true|false]
[--debootstrap-options OPTIONS]
[--debootstrap-script SCRIPT]
[--debug]
[-d|--distribution CODENAME]
[--parent-distribution CODENAME]
[--parent-debian-installer-distribution CODENAME]
[--dump]
[--fdisk fdisk|fdisk.dist]
[--force]
[--grub-splash FILE]
[--gzip-options OPTION|"OPTIONS"]
[--ignore-system-defaults]
[--initramfs auto|none|live-boot]
[--initramfs-compression bzip2|gzip|lzma]
[--initsystem sysvinit|systemd|none]
[--image-name [NAME]
[--interactive shell]
[--isohybrid-options OPTION|"OPTIONS"]
[--hdd-label LABEL]
[--hdd-size MB]
[--hdd-partition-start [parted unit, e.g. 63s]
[--iso-application NAME]
[--iso-preparer NAME]
[--iso-publisher NAME]
[--iso-volume NAME]
[--jffs2-eraseblock SIZE]
[--keyring-packages PACKAGE|"PACKAGES"]
[-k|--linux-flavours FLAVOUR|"FLAVOURS"]
[--linux-packages "PACKAGES"]
[--losetup losetup|losetup.orig]
[--memtest memtest86+|memtest86|none]
[-m|--parent-mirror-bootstrap URL]
[--parent-mirror-chroot URL]
[--parent-mirror-chroot-security URL]
[--parent-mirror-binary URL]
[--parent-mirror-binary-security URL]
[--parent-mirror-debian-installer URL]
[--mirror-bootstrap URL]
[--mirror-chroot URL]
[--mirror-chroot-security URL]
[--mirror-binary URL]
[--mirror-binary-security URL]
[--mirror-debian-installer URL]
[--mode debian]
[--system live|normal]
[--net-root-filesystem nfs|cfs]
[--net-root-mountoptions OPTIONS]
[--net-root-path PATH]
[--net-root-server IP|HOSTNAME]
[--net-cow-filesystem nfs|cfs]
[--net-cow-mountoptions OPTIONS]
[--net-cow-path PATH]
[--net-cow-server IP|HOSTNAME]
[--net-tarball true|false]
[--quiet]
[--archive-areas ARCHIVE_AREA|"ARCHIVE_AREAS"]
[--parent-archive-areas ARCHIVE_AREA|"ARCHIVE_AREAS"]
[--security true|false]
[--source true|false]
[-s|--source-images iso|netboot|tar|hdd]
[--firmware-binary true|false]
[--firmware-chroot true|false]
[--swap-file-path PATH]
[--swap-file-size MB]
[--tasksel apt|aptitude|tasksel]
[--updates true|false]
[--backports true|false]
[--verbose]
[--loadlin true|false]
[--win32-loader true|false]
[--bootstrap-qemu-exclude PACKAGES]
[--bootstrap-qemu-static PATH]
[--bootstrap-qemu-arch ARCH]
I'm only seeing --linux-packages as a possible option for
specifying configuration PACKAGES. Is there another option in this
list that's appropriate?
As for what's in that manual - it's nearly incomprehensible. Is
there a step-by-step HOWTO available somewhere?
Thanks.
On 12/31/16 15:45, Ben Armstrong wrote:
You are misusing
the
--linux-packages option which is only to specify kernel and
kernel modules.
See live-manual and use package lists instead.
Ben
On
December 31, 2016 4:45:26 PM "Peter.Stein"
<peter.stein@comcast.net> wrote:
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