From: "Thomas Roos" <roosesweb@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Thomas Roos <thomas@roosesweb.de>
Subject: [meta-python][PATCH 1/6] python3-pika: build the 1.4.4 release
Date: Sun, 8 Nov 2026 20:25:44 +0100 [thread overview]
Message-ID: <20261108192549.1082715-2-thomas@roosesweb.de> (raw)
In-Reply-To: <20261108192549.1082715-1-thomas@roosesweb.de>
The upgrade to 1.4.4 only changed SRC_URI[sha256sum], which is unused
since the recipe fetches from git, so SRCREV still pointed at a 1.4.2
era commit and the package installed pika 1.4.2 under version 1.4.4.
Point SRCREV at the 1.4.4 tag commit and drop the unused checksum. Add
tag=${PV} to SRC_URI so that the fetcher checks that SRCREV is the
commit of the release tag.
AI-Generated: Claude Code, Claude Opus 5.5
Signed-off-by: Thomas Roos <thomas@roosesweb.de>
---
meta-python/recipes-devtools/python/python3-pika_1.4.4.bb | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/meta-python/recipes-devtools/python/python3-pika_1.4.4.bb b/meta-python/recipes-devtools/python/python3-pika_1.4.4.bb
index 2c18659eab..c4c1bae8fe 100644
--- a/meta-python/recipes-devtools/python/python3-pika_1.4.4.bb
+++ b/meta-python/recipes-devtools/python/python3-pika_1.4.4.bb
@@ -8,13 +8,11 @@ HOMEPAGE = "https://pika.readthedocs.io"
LICENSE = "BSD-3-Clause"
LIC_FILES_CHKSUM = "file://LICENSE;md5=678ec81495ba50edf81e84e4f1aa69f3"
-SRC_URI[sha256sum] = "8cfc8b33a5cb16e733bd60cffca9732c0d1d761ecd80a89f34ed7df2cd38d6d6"
-
# The PyPI package omits some files for testing like tests/__init__.py
# so use the GitHub source instead.
-SRCREV = "3c9b50d4167e436c73cecae8127e3c5b266b2fce"
+SRCREV = "60fee4203a30d5dfa0500857cea6a65ef571d46c"
SRC_URI = "\
- git://github.com/pika/pika;branch=1.4.x;protocol=https \
+ git://github.com/pika/pika;branch=1.4.x;protocol=https;tag=${PV} \
file://run-ptest \
"
--
2.56.0
next prev parent reply other threads:[~2026-11-08 19:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 19:25 [meta-python][PATCH 0/6] Fixes for pika, pint, haversine and httpx2 Thomas Roos
2026-11-08 19:25 ` Thomas Roos [this message]
2026-11-08 19:25 ` [meta-python][PATCH 2/6] python3-pint: add missing runtime dependencies Thomas Roos
2026-11-08 19:25 ` [meta-python][PATCH 3/6] python3-haversine: keep working when numba fails to import Thomas Roos
2026-11-08 19:25 ` [meta-python][PATCH 4/6] python3-truststore: add recipe Thomas Roos
2026-11-08 19:25 ` [meta-python][PATCH 5/6] python3-httpcore2: " Thomas Roos
2026-11-08 19:25 ` [meta-python][PATCH 6/6] python3-httpx2: add missing runtime dependencies Thomas Roos
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=20261108192549.1082715-2-thomas@roosesweb.de \
--to=roosesweb@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=thomas@roosesweb.de \
/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