public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>,
	Quirin Gylstorff <quirin.gylstorff@siemens.com>
Subject: Re: [PATCH] image-account-extension: Also rebuild roots on GROUP_* changes
Date: Wed, 16 Jul 2025 21:51:54 +0200	[thread overview]
Message-ID: <76ea2330-5b4b-46ab-9d35-3bc9c64ea6a5@siemens.com> (raw)
In-Reply-To: <9e54c21f-63df-4a0c-bdca-711dc8079380@siemens.com>

On 18.06.25 08:57, 'Jan Kiszka' via isar-users wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
> 
> Unlike what 3330e1ca2bca what assumed, also certain changes to groups
> can invalidate previous runs of the account extensions against the
> cached rootfs.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
>  meta/classes/image-account-extension.bbclass | 9 ++++-----
>  1 file changed, 4 insertions(+), 5 deletions(-)
> 
> diff --git a/meta/classes/image-account-extension.bbclass b/meta/classes/image-account-extension.bbclass
> index 3c461b1a..5039adab 100644
> --- a/meta/classes/image-account-extension.bbclass
> +++ b/meta/classes/image-account-extension.bbclass
> @@ -8,21 +8,20 @@
>  USERS ??= ""
>  GROUPS ??= ""
>  
> -# rebuild rootfs on change of USERS as homes might be moved / created
> -# no need to depend on GROUPS as they don't create directories
> -# groups need to be created before users, hence do not move the user creation into
> -# the do_rootfs_install task but only add a dependency
> +# rebuild rootfs on change of USERS or GROUPS as homes might be created, moved
> +# or given different IDs.
>  python() {
>      for entry in (d.getVar("GROUPS") or "").split():
>          group_entry = "GROUP_{}".format(entry)
>          d.appendVarFlag("image_postprocess_accounts", "vardeps", " {}".format(group_entry))
> +        d.appendVarFlag("do_rootfs_install", "vardeps", " {}".format(group_entry))
>  
>      for entry in (d.getVar("USERS") or "").split():
>          user_entry = "USER_{}".format(entry)
>          d.appendVarFlag("image_postprocess_accounts", "vardeps", " {}".format(user_entry))
>          d.appendVarFlag("do_rootfs_install", "vardeps", " {}".format(user_entry))
>  }
> -do_rootfs_install[vardeps] += "USERS"
> +do_rootfs_install[vardeps] += "GROUPS USERS"
>  
>  def image_create_groups(d: "DataSmart") -> None:
>      """Creates the groups defined in the ``GROUPS`` bitbake variable.

This seems to have been forgotten.

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/76ea2330-5b4b-46ab-9d35-3bc9c64ea6a5%40siemens.com.

  reply	other threads:[~2025-07-16 19:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-18  6:57 'Jan Kiszka' via isar-users
2025-07-16 19:51 ` 'Jan Kiszka' via isar-users [this message]
2025-07-17  8:44   ` 'MOESSBAUER, Felix' via isar-users
2025-07-17 10:30   ` Baurzhan Ismagulov

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=76ea2330-5b4b-46ab-9d35-3bc9c64ea6a5@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=jan.kiszka@siemens.com \
    --cc=quirin.gylstorff@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