From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Badrikesh Prusty <badrikesh.prusty@siemens.com>,
isar-users@googlegroups.com
Cc: gokhan.cetin@siemens.com, alexander.heinisch@siemens.com
Subject: Re: [PATCH v3 0/1] image-postproc: ignore systemd preset failures
Date: Thu, 19 Feb 2026 18:52:24 +0100 [thread overview]
Message-ID: <2c47f23b-7944-40be-9721-0a0b88b9d78f@siemens.com> (raw)
In-Reply-To: <20260219044406.441933-1-badrikesh.prusty@siemens.com>
On 19.02.26 05:44, 'Badrikesh Prusty' via isar-users wrote:
> changes in v3:
> * Do not disable pre-population of enabled systemd services during build,
> as this is the correct default behavior. Downstream layers can disable
> it if needed.
> * Ignore failures from systemd preset only.
>
> changes in v2:
> * Disable populate-systemd-preset at build time by default due to service
> failures observed on some systems.
>
> Badrikesh Prusty (1):
> image-postproc: ignore systemd preset failures
>
> meta/classes-recipe/rootfs.bbclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Is this series aiming at these new warnings of Isar?
DEBUG: Executing shell function image_postprocess_disable_systemd_firstboot
/proc/ is not mounted. This is not a supported mode of operation. Please fix
your invocation environment to mount /proc/ and /sys/ properly. Proceeding anyway.
Your mileage may vary.
Created symlink '/etc/systemd/system/systemd-firstboot.service' → '/dev/null'.
WARNING: Your image is not configured completely according to systemd-firstboot.
WARNING: It prompted: ""
DEBUG: Shell function image_postprocess_disable_systemd_firstboot finished
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/2c47f23b-7944-40be-9721-0a0b88b9d78f%40siemens.com.
next prev parent reply other threads:[~2026-02-19 17:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 4:44 'Badrikesh Prusty' via isar-users
2026-02-19 4:44 ` [PATCH v3 1/1] " 'Badrikesh Prusty' via isar-users
2026-02-19 13:36 ` 'MOESSBAUER, Felix' via isar-users
2026-02-19 15:26 ` 'Prusty, Badrikesh' via isar-users
2026-02-19 17:52 ` 'Jan Kiszka' via isar-users [this message]
2026-02-19 19:10 ` [PATCH v3 0/1] " 'Jan Kiszka' via isar-users
2026-02-20 8:20 ` 'MOESSBAUER, Felix' via isar-users
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=2c47f23b-7944-40be-9721-0a0b88b9d78f@siemens.com \
--to=isar-users@googlegroups.com \
--cc=alexander.heinisch@siemens.com \
--cc=badrikesh.prusty@siemens.com \
--cc=gokhan.cetin@siemens.com \
--cc=jan.kiszka@siemens.com \
/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