Building a trixie image on a bookworm host - is this supported? And why is systemd getting pulled in even though --initsystem sysvinit is set?
Hi list,
I wanted to see if my custom image works under trixie as well, so I
changed all bookworm references to trixie and ran the lb config and lb
build commands with my usual parameters.
Since my custom image is rather small and serves a limited, dedicated
purpose, I prefer to use sysvinit instead of systemd.
That is why, amongst other things, lb config is called with
--initsystem sysvinit (both for the bookworm and the trixie build).
Bookworm builds just fine, trixie throws:
Solving dependencies...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
systemd-sysv : Conflicts: initscripts but 3.14-4 is to be installed
Conflicts: insserv but 1.26.0-1 is to be installed
Conflicts: startpar but 0.66-1 is to be installed
Conflicts: sysv-rc but 3.14-4 is to be installed
Conflicts: sysvinit-core but 3.14-4 is to be installed
sysvinit-core : Conflicts: systemd-sysv but 257.5-2 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be
caused by held packages.
E: The following information from --solver 3.0 may provide additional
context:
Unable to satisfy dependencies. Reached two conflicting decisions:
1. systemd-sysv:amd64 is selected for install
2. systemd-sysv:amd64 is selected for removal because:
1. sysvinit-core:amd64=3.14-4 is selected for install
2. systemd-sysv:amd64 Conflicts sysvinit-core
E: An unexpected failure occurred, exiting...
P: Begin unmounting filesystems...
P: Saving caches...
Now I'm not sure if the version of live-build in bookworm has a bug that
might be fixable by upgrading the host to trixie before trying to build
trixie images (in the past, I've had trouble trying to build bookworm
images on a bullseye host, when the exact same config worked just fine
with the newer live-build version on a boomworm host), or if one of the
packages in my package lists is suddenly pulling in a hard dependency on
systemd-sysv.
Is this a known problem, and if not, what's the best way to determine
the package(s) in my custom package lists causing the breakage? Since
multiple packages might be at fault, I guess I can't just split the
package files in half, see if it still errors out, then try the other
half, etc. Short of a better method, I'd probably have to empty my
package lists and fill them one by one, triggering a build after each
add. That sounds ... painful.
On the other hand, if this problem will go away by itself once trixie
becomes stable, I can just wait it out.
The following is basically the lb config call I'm using, I've only
edited out identifying information and boot parameters that are picked
up by my custom scripts (as these would only become relevant once a
build succeeds and I try to boot it).
lb config -a amd64 -k amd64 --apt-indices false --apt-recommends false
--cache false --checksums none --firmware-binary false --memtest none
--win32-loader false --backports false --firmware-chroot true
--initsystem sysvinit --security true --updates true --bootloaders
syslinux --distribution trixie syslinux --config GIT_URI_HERE
--binary-images netboot --archive-areas main contrib non-free
non-free-firmware --bootappend-live boot=live components net.ifnames=0
biosdevname=0 hostname=localhost lang=de_DE.UTF-8 vconsole.keymap=de
keyboard-layouts=de locales=de_DE.UTF-8 timezone=Europe/Berlin
timezone=Europe/Berlin
If there's any log/debug output that might be helpful, just let me know
and I'll post it.
Kind Regards,
Stefan Baur
Reply to: