Re: Building a trixie image on a bookworm host / using sysvinit
Hello Roland,
thank you for the quick reply.
Am 28.04.25 um 15:26 schrieb Roland Clobus:
On 28/04/2025 13:20, Stefan Baur wrote:
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.
The 'lb config' command line was helpful.
My crystal ball suggested I should post it, so I did. ;))
By using chroot for nearly everything, it should be possible to build
any image on any system, so building trixie on bookworm should work.
For trixie, you might want to reduce --archive-areas to 'main non-free-
firmware' (removing non-free and contrib)
Oh? Will these repos be available once trixie is released, or are they
gone for good in trixie? What should I use instead, if I am pulling
packages from current non-free and/or contrib?
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:
...[snip]...
Until a patch is written, as a work-around you can add to 'lb config':
--debootstrap-options="--include=live-config-sysvinit"
Thank you! Do I need to/should I file a bug report in Debian?
The package 'systemd-sysv' gets installed already in the bootstrap
phase, and prevents the sysv version from being installed. That is
earlier than the moment the setting of '--initsystem' is activated.
Not all scenarios are tested regularly, and you found one :-)
Yeah, I seem to have a special talent for that ...
Kind Regards,
Stefan Baur
Reply to: