public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Zhihang Wei <wzh@ilbers.de>
To: alexander.heinisch@siemens.com, isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com, felix.moessbauer@siemens.com,
	cedric.hombourger@siemens.com
Subject: Re: [PATCH v4 0/2] Enable systemd units based on systemd presets
Date: Tue, 4 Nov 2025 15:15:28 +0100	[thread overview]
Message-ID: <a1327d27-1f89-4588-8744-508e083be6c3@ilbers.de> (raw)
In-Reply-To: <20251030113332.1809425-1-alexander.heinisch@siemens.com>

Applied to next, thanks.

Bets regards,
Zhihang

On 10/30/25 12:33, alexander.heinisch@siemens.com wrote:
> From: Alexander Heinisch <alexander.heinisch@siemens.com>
>
> By default population of the presets is automatically done by systemd
> on first-boot.
>
> There were several issues with that:
>
> 1. The rootfs we get as a build artifact does not reflect the actual
> system running in the field.
>
> 2. For setups without writeable /etc this fails. With that addition
> it happens already at build time.
>
> Note: Additional services are enabled only. Services already enabled
> during the package installation won't be changed.
>
> Opt-out: `ROOTFS_FEATURES:remove = "populate-systemd-preset"`
>
> Changes since v1:
>    - Documented changes in RECIPE-API-CHANGELOG.md
>
> Changes since v2:
>    - Enable postprocessing to populate systemd presets via ROOTFS_FEATURES
>
> Changes since v3:
>    - Check if systemctl is installed on the target rootfs before invoking it.
>
>      => Tests fixed:
>      ```
>      $ avocado run citest.py:DevTest.test_dev --max-parallel-tasks=1
>      JOB ID     : 131df887f543d582a4e23d18759ef4d908a13485
>      JOB LOG    : /tmp/tmpaj335w6s/avocado/job-results/job-2025-10-30T10.32-131df88/job.log
>       (1/6) citest.py:DevTest.test_dev: STARTED
>       (1/6) citest.py:DevTest.test_dev: PASS (611.18 s)
>       (2/6) citest.py:DevTest.test_dev_apps: STARTED
>       (2/6) citest.py:DevTest.test_dev_apps: PASS (625.95 s)
>       (3/6) citest.py:DevTest.test_dev_rebuild: STARTED
>       (3/6) citest.py:DevTest.test_dev_rebuild: PASS (243.81 s)
>       (4/6) citest.py:DevTest.test_dev_run_amd64_bookworm: STARTED
>       (4/6) citest.py:DevTest.test_dev_run_amd64_bookworm: PASS (72.85 s)
>       (5/6) citest.py:DevTest.test_dev_run_arm64_bookworm: STARTED
>       (5/6) citest.py:DevTest.test_dev_run_arm64_bookworm: PASS (35.98 s)
>       (6/6) citest.py:DevTest.test_dev_run_arm_bookworm: STARTED
>       (6/6) citest.py:DevTest.test_dev_run_arm_bookworm: PASS (40.02 s)
>      RESULTS    : PASS 6 | ERROR 0 | FAIL 0 | SKIP 0 | WARN 0 | INTERRUPT 0 | CANCEL 0
>      JOB TIME   : 1634.63 s
>      ```
>
> Alexander Heinisch (2):
>    Minor cleanup: Refactor ROOTFS_FEATURES assignment for image to make
>      upcoming changes more easily trackable.
>    classes/image-postproc: Enable systemd units based on systemd presets
>
>   RECIPE-API-CHANGELOG.md     | 20 +++++++++++++++++++-
>   meta/classes/image.bbclass  | 10 +++++++++-
>   meta/classes/rootfs.bbclass | 12 ++++++++++++
>   3 files changed, 40 insertions(+), 2 deletions(-)
>
> --
> 2.39.5
>

-- 
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/a1327d27-1f89-4588-8744-508e083be6c3%40ilbers.de.

      parent reply	other threads:[~2025-11-04 14:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-30 11:33 alexander.heinisch via isar-users
2025-10-30 11:33 ` [PATCH v4 1/2] Minor cleanup: Refactor ROOTFS_FEATURES assignment for image to make upcoming changes more easily trackable alexander.heinisch via isar-users
2025-10-30 11:33 ` [PATCH v4 2/2] classes/image-postproc: Enable systemd units based on systemd presets alexander.heinisch via isar-users
2025-11-04 14:15 ` Zhihang Wei [this message]

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=a1327d27-1f89-4588-8744-508e083be6c3@ilbers.de \
    --to=wzh@ilbers.de \
    --cc=alexander.heinisch@siemens.com \
    --cc=cedric.hombourger@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=isar-users@googlegroups.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