public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Schaffner, Tobias" <tobias.schaffner@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH v2 0/4] Rewrite the image-account-extension in python
Date: Mon, 22 May 2023 06:52:31 +0000	[thread overview]
Message-ID: <3a6f9713-852e-b877-8222-6c0a61cd568c@siemens.com> (raw)
In-Reply-To: <d8b71a1b15185911533d93e78dc49aba5cf55cb2.camel@ilbers.de>

On 22.05.23 06:57, Uladzimir Bely wrote:
> On Mon, 2023-05-22 at 07:41 +0300, Uladzimir Bely wrote:
>>
>>
>> While testing this in CI, got the following error while building any
>> targets:
>>
>> /usr/sbin/groupmod: unrecognized option '--system'
>>
>> I didn't deeply debug why exactly this arg comes to gropmod. The
>> strange thing is that there are no visible errors in
>> do_image_postprocess log, while build in general fails. See the
>> attachments.
>>
> 
> P.S. It seems, `groupadd` has "--system" option, since `groupmod`
> doesn't have it. I guess, this should be handled in the new version of
> the patch.

Good catch. Thanks!

      reply	other threads:[~2023-05-22  6:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09  7:44 T. Schaffner
2023-05-09  7:44 ` [PATCH v2 1/4] simplify image-account-extension T. Schaffner
2023-05-09  7:44 ` [PATCH v2 2/4] create a minimal python unittest infrastructure T. Schaffner
2023-05-09  7:44 ` [PATCH v2 3/4] add unittests for the image-account-extension T. Schaffner
2023-05-09  7:44 ` [PATCH v2 4/4] set minimal python version in user_manual to 3.5 T. Schaffner
2023-05-22  4:41 ` [PATCH v2 0/4] Rewrite the image-account-extension in python Uladzimir Bely
2023-05-22  4:57   ` Uladzimir Bely
2023-05-22  6:52     ` Schaffner, Tobias [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=3a6f9713-852e-b877-8222-6c0a61cd568c@siemens.com \
    --to=tobias.schaffner@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=ubely@ilbers.de \
    /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