Re: [OE-core] [PATCHv5 1/2] systemd-systemctl-native: Install systemd-sysv-install

["Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>]

[-- Attachment #1.1: Type: text/plain, Size: 4445 bytes --]

On Thu Aug 21, 2025 at 5:11 PM CEST, Peter Kjellerstedt via lists.openembedded.org wrote:
>> -----Original Message-----
>> From: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
>> Sent: den 21 augusti 2025 08:38
>> To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>; openembedded-core@lists.openembedded.org
>> Subject: Re: [OE-core] [PATCHv5 1/2] systemd-systemctl-native: Install systemd-sysv-install
>> 
>> On Wed Aug 20, 2025 at 3:42 PM CEST, Peter Kjellerstedt via lists.openembedded.org wrote:
>> > It is needed when support for both systemd and sysvinit are enabled.
>> >
>> > This also adds a patch for systemctl to allow the path to
>> > systemd-sysv-install to be specified in runtime. This is needed because
>> > the hardcoded path that is built into systemctl does not match the path
>> > to where it will eventually be executed.
>> >
>> > Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
>> > ---
>> 
>> Hi Peter,
>> 
>> Sorry, but...
>> 
>> WARNING: core-image-full-cmdline-1.0-r0 do_rootfs: iptables.postinst returned 1, marking as unpacked only, configuration required on target.
>> WARNING: core-image-full-cmdline-1.0-r0 do_rootfs: openssh-sshd.postinst returned 1, marking as unpacked only, configuration required on target.
>> WARNING: core-image-full-cmdline-1.0-r0 do_rootfs: sysklogd.postinst returned 1, marking as unpacked only, configuration required on target.
>> WARNING: core-image-full-cmdline-1.0-r0 do_rootfs: ostinst returned 1, marking as unpacked only, configuration required on target.
>> WARNING: core-image-full-cmdline-1.0-r0 do_rootfs: at.postinst returned 1, marking as unpacked only, configuration required on target.
>> WARNING: core-image-full-cmdline-1.0-r0 do_rootfs: cronie.postinst returned 1, marking as unpacked only, configuration required on target.
>> WARNING: core-image-full-cmdline-1.0-r0 do_rootfs: logrotate.postinst returned 1, marking as unpacked only, configuration required on target.
>> WARNING: core-image-full-cmdline-1.0-r0 do_rootfs: nfs-utils-client.postinst returned 1, marking as unpacked only, configuration required on target.
>> WARNING: core-image-full-cmdline-1.0-r0 do_rootfs: nfs-utils.postinst returned 1, marking as unpacked only, configuration required on target.
>> WARNING: core-image-full-cmdline-1.0-r0 do_rootfs: run-postinsts.postinst returned 1, marking as unpacked only, configuration required on target.
>> ERROR: core-image-full-cmdline-1.0-r0 do_rootfs: Postinstall scriptlets of ['iptables', 'openssh-sshd', 'sysklogd', 'ostinst returned 1, marking as unpacked only, configuration required on target', 'at', 'cronie', 'logrotate', 'nfs-utils-client', 'nfs-utils', 'run-postinsts'] have failed. If the intention is to defer them to first boot,
>> then please place them into pkg_postinst_ontarget:${PN} ().
>> Deferring to first boot via 'exit 1' is no longer supported.
>> 
>> https://autobuilder.yoctoproject.org/valkyrie/#/builders/65/builds/2253
>> And lot of other builds in
>> https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/2246
>> 
>> 
>> Best regards,
>> Mathieu
>
> I have failed to reproduce this. I fetched 15c8343c10751f16248ac1b5b5d1cad34b4e4917 
> that is used in the above builds, and used this configuration in my 
> local.conf (to try to mimic the configuration used by the autobuilder):
>
> DISTRO ?= "poky-altcfg"
>
> EXTRA_IMAGE_FEATURES ?= "allow-empty-password empty-root-password allow-root-login"
>
> USER_CLASSES ?= "buildstats"
>
> MACHINE ?= "genericx86"
>
> INHERIT += "image-buildinfo"
> IMAGE_BUILDINFO_VARS:append = " IMAGE_BASENAME IMAGE_NAME"
>
> PACKAGE_CLASSES = "package_ipk package_rpm package_deb"
>
> IMAGE_ROOTFS_EXTRA_SPACE:append = "${@bb.utils.contains('IMAGE_FEATURES', 'package-management', ' + 262144', '', d)}"
>
> BB_HASHSERVE = "wss://hashserv-eu.yoctoproject.org/ws"
>
> Do you have the log.do_rootfs from the failed build? Maybe it can shed 
> some light on what went wrong...
>
> //Peter

I have to confess I'm having a hard time trying to reproduce this
locally. I will try again in the coming days.

I've saved data of the following build and I'm attaching the
log.do_rootfs.

https://autobuilder.yoctoproject.org/valkyrie/#/builders/93/builds/2263

Best regards,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


[-- Attachment #2: log.do_rootfs.1597395.bz2 --]
[-- Type: application/x-bzip, Size: 11798 bytes --]