public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <Qi.Chen@windriver.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH V3 2/2] systemd: upgrade from 257.8 to 258
Date: Sat, 18 Oct 2025 15:49:45 +0200	[thread overview]
Message-ID: <DDLHVDCXIV53.3EI69FW87CCB8@bootlin.com> (raw)
In-Reply-To: <DDKQEKP5R8RA.185ZCAGQ6EA07@bootlin.com>

On Fri Oct 17, 2025 at 6:18 PM CEST, Mathieu Dubois-Briand wrote:
> On Thu Oct 16, 2025 at 10:47 AM CEST, Chen Qi via lists.openembedded.org wrote:
>> From: Chen Qi <Qi.Chen@windriver.com>
>>
>> 258 Release Changes:
>> https://github.com/systemd/systemd/releases/tag/v258
>>
>> The 'runlevel', 'initctl', 'telinit' related contents are removed
>> because they are offically removed in v258.
>>
>> Disable tests explicitly. This is because we're not installing any
>> tests. There's no point building them out. And this puts extra burden
>> on making things compile for musl.
>>
>> gcrypt and gnutls PACKAGECONFIGs are removed as "OpenSSL is now the only
>> supported cryptography backend for systemd-resolved and systemd-importd."
>>
>> musl changes:
>> 1. This version has big changes in musl patches. The goal is to
>>    help maintenance. I want patches to be more easily applied
>>    to new versions. The count of files modified by musl specific
>>    patches decreased from 113 (v257) to 34 (v258).
>> 2. All patches are re-evaluated.
>>    This version of systemd introduces big changes in header
>>    files and other places. So the previous musl patches are
>>    re-evaluated one by one. Those that are dropped are considered not
>>    needed. A few new ones are added. There are some notable ones.
>>    0012-do-not-disable-buffer-in-writing-files.patch is dropped because
>>    there is not runtime error.
>>    0016-Fix-the-segfault-for-glob-related-codes-and-define-d.patch is
>>    added because this version of systemd uses strv_free to free gl_pathv
>>    instead of relying on globfree provided by libc.
>>
>> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
>> ---
>
> Hi Chen,
>
> Thanks for the new version. Still, we get some errors with post install
> scripts:
>
> ERROR: core-image-sato-1.0-r0 do_rootfs: Postinstall scriptlets of ['bluez5', 'ofono', 'connman', 'xserver-nodm-init', 'avahi-daemon', 'rpcbind', '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.
> Details of the failure are in /srv/pokybuild/yocto-worker/qa-extras2/build/build/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0/temp/log.do_rootfs.
> ERROR: Logfile of failure stored in: /srv/pokybuild/yocto-worker/qa-extras2/build/build/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0/temp/log.do_rootfs.2882514
> NOTE: recipe core-image-sato-1.0-r0: task do_rootfs: Failed
> ERROR: Task (/srv/pokybuild/yocto-worker/qa-extras2/build/layers/openembedded-core/meta/recipes-sato/images/core-image-sato.bb:do_rootfs) failed with exit code '1'
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/26/builds/2590
>
> Can you have a look at these, please?
>
> Thanks,
> Mathieu

Sorry, another issue that I've just identified, during image tests:

Traceback (most recent call last):
  File "/srv/pokybuild/yocto-worker/qemuarm-alt/build/layers/openembedded-core/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/srv/pokybuild/yocto-worker/qemuarm-alt/build/layers/openembedded-core/meta/lib/oeqa/runtime/cases/parselogs.py", line 185, in test_parselogs
    self.assertEqual(errcount, 0, msg=self.msg)
AssertionError: 1 != 0 : Log: /srv/pokybuild/yocto-worker/qemuarm-alt/build/build/tmp/work/qemuarm-poky-linux-gnueabi/core-image-sato/1.0/target_logs/Xorg.0.log
-----------------------
Central error: [    27.402] failed to find screen to remove
***********************
[    26.897] (**) Option "Device" "/dev/input/event1"
[    26.955] (II) event1  - QEMU QEMU USB Keyboard: is tagged by udev as: Keyboard
[    26.956] (II) event1  - QEMU QEMU USB Keyboard: device is a keyboard
[    26.959] (II) event1  - QEMU QEMU USB Keyboard: device removed
[    26.991] (**) Option "config_info" "udev:/sys/devices/platform/3f000000.pcie/pci0000:00/0000:00:02.0/usb1/1-2/1-2:1.0/0003:0627:0001.0002/input/input1/event1"
[    26.991] (II) XINPUT: Adding extended input device "QEMU QEMU USB Keyboard" (type: KEYBOARD, id 7)
[    27.049] (II) event1  - QEMU QEMU USB Keyboard: is tagged by udev as: Keyboard
[    27.051] (II) event1  - QEMU QEMU USB Keyboard: device is a keyboard
[    27.401] (II) config/udev: removing GPU device /sys/devices/platform/3f000000.pcie/pci0000:00/0000:00:03.0/drm/card0 /dev/dri/card0
[    27.402] xf86: remove device 0 /sys/devices/platform/3f000000.pcie/pci0000:00/0000:00:03.0/drm/card0
[    27.402] failed to find screen to remove
[    27.428] (II) config/udev: removing device QEMU QEMU USB Keyboard
[    27.431] (II) event1  - QEMU QEMU USB Keyboard: device removed
[    27.472] (II) UnloadModule: "libinput"
[    27.508] (II) config/udev: Adding input device QEMU QEMU USB Keyboard (/dev/input/event1)
[    27.509] (**) QEMU QEMU USB Keyboard: Applying InputClass "libinput keyboard catchall"
[    27.509] (II) Using input driver 'libinput' for 'QEMU QEMU USB Keyboard'
[    27.509] (**) QEMU QEMU USB Keyboard: always reports core events
[    27.509] (**) Option "Device" "/dev/input/event1"
[    27.567] (II) event1  - QEMU QEMU USB Keyboard: is tagged by udev as: Keyboard
[    27.568] (II) event1  - QEMU QEMU USB Keyboard: device is a keyboard

***********************
1 errors found in logs.

https://autobuilder.yoctoproject.org/valkyrie/#/builders/74/builds/2588

Thanks,
Mathieu

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



  reply	other threads:[~2025-10-18 13:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-16  8:46 [OE-core][PATCH V3 1/2] base-passwd: add clock group Qi.Chen
2025-10-16  8:47 ` [OE-core][PATCH V3 2/2] systemd: upgrade from 257.8 to 258 Qi.Chen
2025-10-17 16:18   ` Mathieu Dubois-Briand
2025-10-18 13:49     ` Mathieu Dubois-Briand [this message]
2025-10-20  4:37       ` ChenQi
2025-10-22  3:28       ` ChenQi
2025-10-23  8:29         ` Mathieu Dubois-Briand
2025-10-23 13:49         ` Mathieu Dubois-Briand
2025-10-24  2:42           ` ChenQi
2025-10-27  5:07           ` ChenQi
2025-10-16  9:49 ` [OE-core][PATCH V3 1/2] base-passwd: add clock group Peter Kjellerstedt
2025-10-17  2:56   ` ChenQi
2025-10-17 18:22     ` Alexander Kanavin
2025-10-20  5:14       ` ChenQi
2025-10-20 11:59         ` Alexander Kanavin
2025-10-20 14:29           ` Peter Kjellerstedt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DDLHVDCXIV53.3EI69FW87CCB8@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=Qi.Chen@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox