From: Tom Geelen <t.f.g.geelen@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Tom Geelen <t.f.g.geelen@gmail.com>
Subject: [meta-python][PATCH 3/3] python3-sqlalchemy: upgrade 2.0.27 -> 2.0.29
Date: Mon, 15 Apr 2024 19:49:33 +0000 [thread overview]
Message-ID: <20240415194929.2315308-3-t.f.g.geelen@gmail.com> (raw)
In-Reply-To: <20240415194929.2315308-1-t.f.g.geelen@gmail.com>
---
...ython3-sqlalchemy_2.0.27.bb => python3-sqlalchemy_2.0.29.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-python/recipes-devtools/python/{python3-sqlalchemy_2.0.27.bb => python3-sqlalchemy_2.0.29.bb} (87%)
diff --git a/meta-python/recipes-devtools/python/python3-sqlalchemy_2.0.27.bb b/meta-python/recipes-devtools/python/python3-sqlalchemy_2.0.29.bb
similarity index 87%
rename from meta-python/recipes-devtools/python/python3-sqlalchemy_2.0.27.bb
rename to meta-python/recipes-devtools/python/python3-sqlalchemy_2.0.29.bb
index e5a837659..e646bd0d9 100644
--- a/meta-python/recipes-devtools/python/python3-sqlalchemy_2.0.27.bb
+++ b/meta-python/recipes-devtools/python/python3-sqlalchemy_2.0.29.bb
@@ -4,7 +4,7 @@ HOMEPAGE = "http://www.sqlalchemy.org/"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE;md5=c78b979ae6c20775a28a287d32092cbb"
-SRC_URI[sha256sum] = "86a6ed69a71fe6b88bf9331594fa390a2adda4a49b5c06f98e47bf0d392534f8"
+SRC_URI[sha256sum] = "bd9566b8e58cabd700bc367b60e90d9349cd16f0984973f98a9a09f9c64e86f0"
PYPI_PACKAGE = "SQLAlchemy"
inherit pypi setuptools3
--
2.34.1
prev parent reply other threads:[~2024-04-15 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 19:49 [meta-python][PATCH 1/3] python3-pychromecast: upgrade 14.0.0 -> 14.0.1 Tom Geelen
2024-04-15 19:49 ` [meta-python][PATCH 2/3] python3-zeroconf: upgrade 0.131.0 -> 0.132.0 Tom Geelen
2024-04-15 19:49 ` Tom Geelen [this message]
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=20240415194929.2315308-3-t.f.g.geelen@gmail.com \
--to=t.f.g.geelen@gmail.com \
--cc=openembedded-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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).