From: Yoann Congal <yoann.congal@smile.fr>
To: bitbake-devel@lists.openembedded.org
Subject: [bitbake][wrynose][2.18][PATCH 0/3] Patch review
Date: Wed, 20 May 2026 01:33:43 +0200 [thread overview]
Message-ID: <cover.1779233514.git.yoann.congal@smile.fr> (raw)
Please review this set of changes for 2.18/wrynose and have comments back by
end of day Thursday, May 21.
Passed a-full on autobuilder with some AB-INT issues:
* https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/3846
* check-layer https://autobuilder.yoctoproject.org/valkyrie/#/builders/27/builds/3851
Failed due to 16285 – AB-INT: check-layer: unexplained changed signatures
retried as https://autobuilder.yoctoproject.org/valkyrie/#/builders/27/builds/3852
* qemux86-64-ptest https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/3688
Failed due to 16279 – AB-INT: groff error: couldn't exec preconv: No such file or directory
retried as https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/3689
* qemuriscv64-ptest https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/1610
Failed due to 16215 – AB-INT PTEST RISCV64: libpng ptest failure
Retried as https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/1611
* oe-selftest-debian https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/3878
retried as https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/3879
git.openembedded.org hung up a HTTP git clone connection
* oe-selftest-fedora https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/3740
retried as https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/3741
git.yoctoproject.org hung up a HTTP git clone connection
I attribute the last 2 to the current situation with bot scrappers.
A new build is running here:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/3847
The following changes since commit 0415a00658b59f66bdab22a3558794f238c42973:
fetch/git: Improve temporary directory handling (2026-05-13 17:50:24 +0100)
are available in the Git repository at:
https://git.openembedded.org/bitbake-contrib stable/2.18-nut
https://git.openembedded.org/bitbake-contrib/log/?h=stable/2.18-nut
for you to fetch changes up to 22021758e66737bcf68dfd2b74adc6a0cb1d42d9:
README: Add "2.18" subject-prefix to git-send-email suggestion (2026-05-19 11:08:15 +0200)
----------------------------------------------------------------
Alexander Kanavin (1):
fetch/wget: in upstream version checks, match versioned directories
exactly
Yoann Congal (2):
b4-config: add send-prefixes for 2.18/wrynose
README: Add "2.18" subject-prefix to git-send-email suggestion
.b4-config | 1 +
README | 4 ++--
lib/bb/fetch2/wget.py | 2 +-
3 files changed, 4 insertions(+), 3 deletions(-)
next reply other threads:[~2026-05-19 23:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 23:33 Yoann Congal [this message]
2026-05-19 23:33 ` [bitbake][wrynose][2.18][PATCH 1/3] fetch/wget: in upstream version checks, match versioned directories exactly Yoann Congal
2026-05-19 23:33 ` [bitbake][wrynose][2.18][PATCH 2/3] b4-config: add send-prefixes for 2.18/wrynose Yoann Congal
2026-05-19 23:33 ` [bitbake][wrynose][2.18][PATCH 3/3] README: Add "2.18" subject-prefix to git-send-email suggestion Yoann Congal
-- strict thread matches above, loose matches on Subject: below --
2026-05-08 7:13 [bitbake][wrynose][2.18][PATCH 0/3] Patch review Yoann Congal
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=cover.1779233514.git.yoann.congal@smile.fr \
--to=yoann.congal@smile.fr \
--cc=bitbake-devel@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