From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 1/4] diffoscope: upgrade 326 -> 327
Date: Sat, 8 Aug 2026 22:09:51 +0100 [thread overview]
Message-ID: <20260808210954.994064-1-richard.purdie@linuxfoundation.org> (raw)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
.../diffoscope/{diffoscope_326.bb => diffoscope_327.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-support/diffoscope/{diffoscope_326.bb => diffoscope_327.bb} (93%)
diff --git a/meta/recipes-support/diffoscope/diffoscope_326.bb b/meta/recipes-support/diffoscope/diffoscope_327.bb
similarity index 93%
rename from meta/recipes-support/diffoscope/diffoscope_326.bb
rename to meta/recipes-support/diffoscope/diffoscope_327.bb
index 3ab679f34f6..30d33732f6e 100644
--- a/meta/recipes-support/diffoscope/diffoscope_326.bb
+++ b/meta/recipes-support/diffoscope/diffoscope_327.bb
@@ -10,7 +10,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504"
inherit pypi setuptools3
-SRC_URI[sha256sum] = "21aaa977a9fbdf6e2b70b675a700ad1f80e878ac1dac59cf6fb0ba5f319616c7"
+SRC_URI[sha256sum] = "b5a398de17b180637cf091ba5c3c9fecde9dc8f5c2c80204ff8dd78e1b9d5358"
RDEPENDS:${PN} += "\
binutils \
next reply other threads:[~2026-08-08 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 21:09 Richard Purdie [this message]
2026-08-08 21:09 ` [PATCH 2/4] python3-pycairo: upgrade 1.29.0 -> 1.29.1 Richard Purdie
2026-08-08 21:09 ` [PATCH 3/4] python3-uv-build: upgrade 0.12.1 -> 0.12.3 Richard Purdie
2026-08-08 21:17 ` Patchtest results for " patchtest
2026-08-08 21:09 ` [PATCH 4/4] python3-vcs-versioning: upgrade 2.2.3 -> 2.2.4 Richard Purdie
2026-08-08 21:17 ` Patchtest results for [PATCH 1/4] diffoscope: upgrade 326 -> 327 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=20260808210954.994064-1-richard.purdie@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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