Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <rs@ti.com>, <raj.khem@gmail.com>,
	<richard.purdie@linuxfoundation.org>, <alex@linutronix.de>,
	<otavio@ossystems.com.br>, <kexin.hao@windriver.com>
Cc: <afd@ti.com>, <detheridge@ti.com>, <denis@denix.org>,
	<reatmon@ti.com>, <openembedded-core@lists.openembedded.org>,
	<vijayp@ti.com>
Subject: Re: [oe-core][PATCHv3] xuser-account: convert to standard-user-account
Date: Sat, 20 Jun 2026 14:51:20 +0200	[thread overview]
Message-ID: <DJDW23PH3DPO.1NMHFSM6HL150@bootlin.com> (raw)
In-Reply-To: <20260618190003.3266810-1-rs@ti.com>

On Thu Jun 18, 2026 at 9:00 PM CEST, rs wrote:
> From: Randolph Sapp <rs@ti.com>
>
> Change this single xuser account template into a generic
> standard-user-account that uses distro level variables for
> configuration.
>
> This allows for seamless configuration of multiple out-of-box scripts
> and tests across layers without having to implicitly hope that the
> username or groups haven't been changed by a bbappend or recipe
> override.
>
> This also adds a class and a variable to allow recipes to assert that
> the user is in requested groups.
>
> This was proposed specifically to remove some issues highlighted in:
> https://lists.openembedded.org/g/openembedded-core/message/230665
>
> Signed-off-by: Randolph Sapp <rs@ti.com>
> ---
> v2:
> 	- Add seat to the default STANDARD_USER_SYSTEM_GROUPS var
> v3:
> 	- Add STANDARD_USER_GROUPS_EXPECT to indicate what groups are
> 	  expected to be provided by other projects
> 	- Set user UID and GID as 1000 in the static tracking files
> 	- Update the weston test's user name
> ---

Hi Randolph,

Thanks for the new version.

I believe we still have some failure:

2026-06-20 11:01:50,077 - oe-selftest - INFO - incompatible_lic.NoGPL3InImagesTests.test_core_image_full_cmdline_weston (subunit.RemotedTestCase)
2026-06-20 11:01:50,080 - oe-selftest - INFO -  ... FAIL
...
ERROR: weston-init-1.0-r0 do_package_write_rpm: File /srv/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-4070494/tmp/work/qemux86_64-poky-linux/weston-init/1.0/recipe-sysroot/etc/passwd doesn't exist in sysroot!
ERROR: weston-init-1.0-r0 do_package_write_rpm: Error executing a python function in exec_func_python() autogenerated:
...
Exception: KeyError: 'getpwuid(): uid not found: 1000'

https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/4105
https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/3936

Can you have a look at the issue?

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2026-06-20 12:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-18 19:00 [oe-core][PATCHv3] xuser-account: convert to standard-user-account rs
2026-06-20 12:51 ` Mathieu Dubois-Briand [this message]
2026-06-20 12:54   ` Mathieu Dubois-Briand

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=DJDW23PH3DPO.1NMHFSM6HL150@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=afd@ti.com \
    --cc=alex@linutronix.de \
    --cc=denis@denix.org \
    --cc=detheridge@ti.com \
    --cc=kexin.hao@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    --cc=raj.khem@gmail.com \
    --cc=reatmon@ti.com \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=rs@ti.com \
    --cc=vijayp@ti.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