public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Gijs Peskens <gijs.peskens@munisense.com>
To: openembedded-core@lists.openembedded.org
Subject: Ubuntu 25.10: base-passwd fails to chown. (pseudo issue)
Date: Wed, 22 Oct 2025 11:57:08 +0200	[thread overview]
Message-ID: <567bf317-620c-4f00-827c-50a511d431c7@munisense.com> (raw)

I'm just posting this here as a reference so others who run into this 
can hopefully find it, as it took me a while to figure out what was 
happening ;)

Ubuntu 25.10 obviously isn't supported, so I'm aware I'm on my own....

On Ubuntu 25.10 packages will fail to chown, this is due to Ubuntu 
having moved away from gnu coreutils to the rust based uutils coreutils. 
I'm presuming that Pseudo works by overriding libC provided functions, 
and thus intercepting the syscalls, and that the rust based coreutils do 
their syscalls directly (without a libC), which breaks pseudo and will 
result in failure to chown errors (and possibly other errors as well).

As a work-around, on 25.10, it's still possible to switch back to 
gnu-coreutils:
sudo apt-get remove --allow-remove-essential coreutils-from-uutils

(at your own risk)

Hope it helps others who run into this! :)

(and perhaps some thought must be given to this before 26.04 comes out, 
if the intention is to support that LTS).

Gijs Peskens



             reply	other threads:[~2025-10-22  9:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-22  9:57 Gijs Peskens [this message]
2025-10-22 11:11 ` [OE-core] Ubuntu 25.10: base-passwd fails to chown. (pseudo issue) Alexander Kanavin
2025-10-22 16:06   ` Gijs Peskens
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=567bf317-620c-4f00-827c-50a511d431c7@munisense.com \
    --to=gijs.peskens@munisense.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