From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: jaipaul.cheernam@est.tech, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] systemtap: Upgrade 5.5 -> 5.6
Date: Sat, 19 Sep 2026 22:49:27 +0100 [thread overview]
Message-ID: <3dbfaacd3f9ee5656a5005daba1fa57b01419a12.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260919140957.80166-1-jaipaul.cheernam@est.tech>
On Sat, 2026-09-19 at 16:09 +0200, Jaipaul Cheernam via lists.openembedded.org wrote:
> NEWS: https://sourceware.org/git/?p=systemtap.git;a=blob;f=NEWS;hb=release-5.6
>
> - Clean up python2 support in recipe and clean up obsoloute patch
> More details [1], [2]
>
> - Added pip/wheel native to the python3-probes PACKAGECONFIG — the new build uses pip/wheel
>
> - Added two patches to keep do_package_qa passing. The generated
> tapset/python3.stpm recorded the recipe-sysroot path of libpython,
> since it comes from sysconfig's LIBDIR and python3targetconfig points
> that at ${STAGING_LIBDIR}; @cast module names are resolved verbatim
> with no --sysroot translation, so that path also made python3 probes
> unresolvable on the target. The pip-installed HelperSDT module shipped
> __pycache__/*.pyc naming ${D} and a dist-info/direct_url.json naming
> the wheel in ${B}, both artifacts of "pip install --root".
> Reported upstream as PR34652 [3], patches posted to the systemtap
> list [4].
>
> [1] https://sourceware.org/git/?p=systemtap.git;a=commit;h=3c9c8a8163e0a9c77bf9a3a7f87ceaf2d3de98b5
> [2] https://sourceware.org/git/?p=systemtap.git;a=commit;h=55a0168613e765f6be5257b0c4fb97678292716f
> [3] https://sourceware.org/bugzilla/show_bug.cgi?id=34652
> [4] https://inbox.sourceware.org/systemtap/20260919135744.78642-1-jaipaul.cheernam@est.tech/
>
> Signed-off-by: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
I think there may be a reproducibilty issue in there:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/5022
https://valkyrie.yocto.io/pub/repro-fail/oe-reproducible-20260919-l3njlk0p/packages/diff-html/
Cheers,
Richard
next prev parent reply other threads:[~2026-09-19 21:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 14:09 [PATCH] systemtap: Upgrade 5.5 -> 5.6 Jaipaul Cheernam
2026-09-19 14:16 ` Patchtest results for " patchtest
2026-09-19 21:49 ` Richard Purdie [this message]
2026-09-20 8:26 ` [PATCH v2] " Jaipaul Cheernam
2026-09-20 8:31 ` Patchtest results for " patchtest
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=3dbfaacd3f9ee5656a5005daba1fa57b01419a12.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=jaipaul.cheernam@est.tech \
--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