From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Andreas Naumann <anaumann@emlix.com>, isar-users@googlegroups.com
Subject: Re: [PATCH 1/1] postproc: Correct typo to image_postprocess_disable_systemd_firstboot
Date: Wed, 17 Dec 2025 12:12:14 +0100 [thread overview]
Message-ID: <e1839ccb-cd32-4b5e-b032-f15b595d8fdf@siemens.com> (raw)
In-Reply-To: <3aaadf14-45d1-4142-ac30-e8f92aa710d5@emlix.com>
On 17.12.25 11:05, Andreas Naumann wrote:
> Hello Jan,
>
> Am 17.12.25 um 09:51 schrieb Jan Kiszka:
>> A sentence here that this typo had no functional impact would have been
>> nice.
>
> Good point, should i resend?
>
If you already have the editor open... :)
Jan
> Andreas
>
>>
>> On 17.12.25 09:39, 'Andreas Naumann' via isar-users wrote:
>>> Signed-off-by: Andreas Naumann <anaumann@emlix.com>
>>> ---
>>> meta/classes-recipe/image-postproc-extension.bbclass | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/meta/classes-recipe/image-postproc-extension.bbclass b/
>>> meta/classes-recipe/image-postproc-extension.bbclass
>>> index b332e826..1aba2ec5 100644
>>> --- a/meta/classes-recipe/image-postproc-extension.bbclass
>>> +++ b/meta/classes-recipe/image-postproc-extension.bbclass
>>> @@ -80,8 +80,8 @@ image_postprocess_sshd_key_regen() {
>>> fi
>>> }
>>> -ROOTFS_POSTPROCESS_COMMAND =+
>>> "image_posprocess_disable_systemd_firstboot"
>>> -image_posprocess_disable_systemd_firstboot() {
>>> +ROOTFS_POSTPROCESS_COMMAND =+
>>> "image_postprocess_disable_systemd_firstboot"
>>> +image_postprocess_disable_systemd_firstboot() {
>>> SYSTEMD_VERSION=$(sudo chroot '${ROOTFSDIR}' dpkg-query \
>>> --showformat='${source:Upstream-Version}' \
>>> --show systemd || echo "0" )
>> Reviewed-by: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> Jan
>>
> Andreas Naumann
>
--
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/e1839ccb-cd32-4b5e-b032-f15b595d8fdf%40siemens.com.
prev parent reply other threads:[~2025-12-17 11:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 8:39 'Andreas Naumann' via isar-users
2025-12-17 8:51 ` 'Jan Kiszka' via isar-users
2025-12-17 10:05 ` 'Andreas Naumann' via isar-users
2025-12-17 11:12 ` 'Jan Kiszka' via isar-users [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=e1839ccb-cd32-4b5e-b032-f15b595d8fdf@siemens.com \
--to=isar-users@googlegroups.com \
--cc=anaumann@emlix.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