public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Gijs Peskens <gijs.peskens@munisense.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] Ubuntu 25.10: base-passwd fails to chown. (pseudo issue)
Date: Wed, 22 Oct 2025 18:06:47 +0200	[thread overview]
Message-ID: <e13e095b-3174-4f07-af32-b562ee3edc77@munisense.com> (raw)
In-Reply-To: <CANNYZj8WZ+hx_OvO+=m_JsayTZEB9GmC6ma4xEp-qPqXso=aog@mail.gmail.com>


On 10/22/25 13:11, Alexander Kanavin wrote:
> Thanks for the report. I was dreading the day this happens, and I'm
> sure others as well. Chances are, other distros will follow, and then
> Yocto project has a problem.
>
> Should we build C based native coreutils as early as possible, and
> then use only that? That might buy some time, but isn't a real
> solution, if GNU stops their development.
I'd guess that's the lowest energy approach, other routes would 
potentially involve writing the utils themselves with pseudo in mind and 
calling back into host utilities where needed. I don't believe GNU would 
stop development on coreutils anywhere in the near(ish) future, nor that 
the approach of building native coreutils would break since it should 
more or less only depend on the libC and kernel, things which aren't 
going away anytime soon.

Perhaps some magic right now inside bitbake that checks whether the 
host-utils are uutils and fails early would be nice (again: I'm aware 
I'm in unsupported land, energy shouldn't be wasted too much).

Gijs


  reply	other threads:[~2025-10-22 16:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-22  9:57 Ubuntu 25.10: base-passwd fails to chown. (pseudo issue) Gijs Peskens
2025-10-22 11:11 ` [OE-core] " Alexander Kanavin
2025-10-22 16:06   ` Gijs Peskens [this message]
2025-10-23 13:25     ` Ross Burton

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=e13e095b-3174-4f07-af32-b562ee3edc77@munisense.com \
    --to=gijs.peskens@munisense.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