public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Yoann Congal <yoann.congal@smile.fr>,
	Mark Hatle <mark.hatle@kernel.crashing.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v2] pseudo: Update to 1.9.3 release
Date: Tue, 20 Jan 2026 10:31:25 +0000	[thread overview]
Message-ID: <83cb39fb9474846d054baa83925e63cb4bdef32c.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAMSfU+5Xyi8RZFaC4q4b9B9DGGB7=AjbKkvn2s+WtJKcsBVRKA@mail.gmail.com>

On Tue, 2026-01-20 at 09:59 +0100, Yoann Congal wrote:
> Le mar. 20 janv. 2026 à 09:52, Richard Purdie via
> lists.openembedded.org
> <richard.purdie=linuxfoundation.org@lists.openembedded.org> a écrit :
> > Pulls in the following changes:
> > 
> >   Makefile.in: Bump version to 1.9.3
> >   configure: Minor code quality changes
> >   pseudo: code quality scan - resolved various potential issues
> >   makewrappers: improve error handling and robustness
> >   Update COPYRIGHT files
> >   ports/linux/pseudo_wrappers.c: Call the wrappers where possible
> >   ports/linux/pseudo_wrappers.c: Workaround compile error on Debian
> > 11
> >   ports/linux/pseudo_wrappers.c: Reorder the syscall operations
> >   ports/unix/guts/realpath.c: Fix indents
> >   pseudo_util.c: Skip realpath like expansion for /proc on Linux
> >   test/test-proc-pipe.sh: Add test case for proc pipes
> >   ports/unix/guts/realpath.c: realpath fails if the resolved path
> > doesn't exist
> > 
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> 
> Do you think I should take this for stable inclusion? (leaning toward
> yes)

Good question. Copying Mark.

I suspect it will be easier all around if we did take it. There are a
lot of fixes in here and it is hard to know which ones any given user
might need or run into. There isn't any real feature work, just various
fixes for new glibc calls or existing code. The failure modes for
pseudo are problematic for end users who wouldn't understand many of
them. The realpath/proc fixes are the most invasive piece.

I would suggest we wait a little bit before taking it, just so we can
test things with master and ensure there is are no regressions. 

You would need to take the dpkg ADMINDIR change as well as the pseudo
changes won't work without that.

I'm open to other thoughts either way...

Cheers,

Richard


  reply	other threads:[~2026-01-20 10:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20  8:52 [PATCH v2] pseudo: Update to 1.9.3 release Richard Purdie
2026-01-20  8:59 ` [OE-core] " Yoann Congal
2026-01-20 10:31   ` Richard Purdie [this message]
2026-01-20 15:01     ` Mark Hatle

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=83cb39fb9474846d054baa83925e63cb4bdef32c.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=mark.hatle@kernel.crashing.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=yoann.congal@smile.fr \
    /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