public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
	isar-users@googlegroups.com
Cc: tobias.schaffner@siemens.com
Subject: Re: [PATCH v2 1/2] fix group splitting in user creation
Date: Thu, 03 Aug 2023 00:31:37 +0300	[thread overview]
Message-ID: <dc6aca1c117eb78e02a1d7e1c4b8d134a6aeeb31.camel@ilbers.de> (raw)
In-Reply-To: <20230727032415.3366650-1-felix.moessbauer@siemens.com>

On Thu, 2023-07-27 at 03:24 +0000, 'Felix Moessbauer' via isar-users
wrote:
> There is a bug when converting the USER_<foo>[groups] configuration
> from the bitbake format (space separated) to the format useradd
> expects (comma separated). We cannot simply replace spaces with
> commas,
> as then multiple spaces in a row would create multiple commas.
> Instead,
> we need to split it first into the tokens and then join these tokens
> by
> comma.
> 
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
>  meta/classes/image-account-extension.bbclass | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/meta/classes/image-account-extension.bbclass
> b/meta/classes/image-account-extension.bbclass
> index e783c135..6f67f459 100644
> --- a/meta/classes/image-account-extension.bbclass
> +++ b/meta/classes/image-account-extension.bbclass
> @@ -98,10 +98,10 @@ def image_create_users(d: "DataSmart") -> None:
>          add_user_option("--comment", "comment")
>          add_user_option("--shell", "shell")
>  
> -        groups = d.getVarFlag(user_entry, "groups") or ""
> +        groups = (d.getVarFlag(user_entry, "groups") or "").split()
>          if groups:
>              args.append("--groups")
> -            args.append(groups.replace(' ', ','))
> +            args.append(','.join(groups))
>  
>          flags = (d.getVarFlag(user_entry, "flags") or "").split()
>  
> -- 
> 2.34.1
> 

Series applied to next, thanks.

      parent reply	other threads:[~2023-08-02 21:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27  3:24 Felix Moessbauer
2023-07-27  3:24 ` [PATCH v2 2/2] add unit test for user creation with groups Felix Moessbauer
2023-08-01  7:21 ` [PATCH v2 1/2] fix group splitting in user creation Schaffner, Tobias
2023-08-02 21:31 ` Uladzimir Bely [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=dc6aca1c117eb78e02a1d7e1c4b8d134a6aeeb31.camel@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=felix.moessbauer@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=tobias.schaffner@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