public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: ChenQi <Qi.Chen@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH V4 1/3] base-passwd: add clock group
Date: Fri, 31 Oct 2025 10:58:54 +0800	[thread overview]
Message-ID: <8c6216e2-59fc-4807-a1ce-ae86c22a2bf2@windriver.com> (raw)
In-Reply-To: <CANNYZj-a7AVDtX4R4VDSfgmTOFd7XpxeCrbmnaskrw-QPigvrQ@mail.gmail.com>

On 10/29/25 18:50, Alexander Kanavin wrote:
> On Wed, 29 Oct 2025 at 05:55, Chen Qi via lists.openembedded.org
> <Qi.Chen=windriver.com@lists.openembedded.org> wrote:
>> +Subject: [PATCH] Add clock group
>> +
>> +The clock group is needed to "to enable applications like linuxptp
>> +to open clocks without root privileges". See the link below:
>> +https://github.com/systemd/systemd/commit/af96ccfc24bc4803078a46b4ef2cdeb5decdfbcd
>> +
>> +Note that this group is needed as long as people use udev from
>> +systemd because 50-udev-default.rules needs it. See the above
>> +commit.
>> +
>> +Upstream-Status: Inappropriate [oe specific]
>> +[
>> +  MR: https://salsa.debian.org/debian/base-passwd/-/merge_requests/17
>> +  It was rejected by upstream. See details in MR's comments.
>> +]
> Thanks for engaging with upstream. The upstream-status should be
> Denied [link] in this case.
>
> Which brings the point that (I think?) has already been made: as this
> group is systemd-specific, it should probably be handled in that
> recipe.
>
> Alex

Hi Alex,

Debian is using sysusers to handle common groups. You can see that sgx 
and kvm groups are also handled in this way: 
https://salsa.debian.org/systemd-team/systemd/-/commit/7aab0da57c0df18bf552aae58076500081f93e01

But in Yocto, we are not relying on sysusers. So we have to use 
base-passwd. sgx and kvm are also added to base-passwd via oe-specific 
patches.

I'll correct the Upstream-Status and send out V5.

Regards,
Qi



      reply	other threads:[~2025-10-31  2:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-29  4:55 [OE-core][PATCH V4 1/3] base-passwd: add clock group Qi.Chen
2025-10-29  4:55 ` [OE-core][PATCH V4 2/3] systemd: upgrade from 257.8 to 258.1 Qi.Chen
2025-10-29  4:55 ` [OE-core][PATCH V4 3/3] parselogs: ignore error on qemuarm as a workaround Qi.Chen
2025-10-29 10:50 ` [OE-core][PATCH V4 1/3] base-passwd: add clock group Alexander Kanavin
2025-10-31  2:58   ` ChenQi [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=8c6216e2-59fc-4807-a1ce-ae86c22a2bf2@windriver.com \
    --to=qi.chen@windriver.com \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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