From: auh@moto-timo.dev
To: openembedded-devel@lists.openembedded.org
Subject: [AUH] python3-sqlalchemy: upgrading to 2.0.18 SUCCEEDED
Date: Wed, 12 Jul 2023 05:31:50 +0000 (UTC) [thread overview]
Message-ID: <20230712053150.6925EEB64D9@smtp.lore.kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2334 bytes --]
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-sqlalchemy* to *2.0.18* has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-sqlalchemy-upgrade-2.0.15-2.0.18.patch
- check the changes to upstream patches and summarize them in the commit message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update failures.
Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
From 6e2a69a8645818b127c46156cc673088a682d370 Mon Sep 17 00:00:00 2001
From: Upgrade Helper <auh@moto-timo.dev>
Date: Tue, 11 Jul 2023 22:58:37 -0500
Subject: [PATCH] python3-sqlalchemy: upgrade 2.0.15 -> 2.0.18
---
...ython3-sqlalchemy_2.0.15.bb => python3-sqlalchemy_2.0.18.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-python/recipes-devtools/python/{python3-sqlalchemy_2.0.15.bb => python3-sqlalchemy_2.0.18.bb} (87%)
diff --git a/meta-python/recipes-devtools/python/python3-sqlalchemy_2.0.15.bb b/meta-python/recipes-devtools/python/python3-sqlalchemy_2.0.18.bb
similarity index 87%
rename from meta-python/recipes-devtools/python/python3-sqlalchemy_2.0.15.bb
rename to meta-python/recipes-devtools/python/python3-sqlalchemy_2.0.18.bb
index e6f0d6429..770d558d2 100644
--- a/meta-python/recipes-devtools/python/python3-sqlalchemy_2.0.15.bb
+++ b/meta-python/recipes-devtools/python/python3-sqlalchemy_2.0.18.bb
@@ -4,7 +4,7 @@ HOMEPAGE = "http://www.sqlalchemy.org/"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE;md5=b707d50badb798e1d897f2c8f649382d"
-SRC_URI[sha256sum] = "2e940a8659ef870ae10e0d9e2a6d5aaddf0ff6e91f7d0d7732afc9e8c4be9bbc"
+SRC_URI[sha256sum] = "1fb792051db66e09c200e7bc3bda3b1eb18a5b8eb153d2cedb2b14b56a68b8cb"
PYPI_PACKAGE = "SQLAlchemy"
inherit pypi setuptools3
--
2.25.1
[-- Attachment #2: 0001-python3-sqlalchemy-upgrade-2.0.15-2.0.18.patch --]
[-- Type: text/x-diff, Size: 1340 bytes --]
From 6e2a69a8645818b127c46156cc673088a682d370 Mon Sep 17 00:00:00 2001
From: Upgrade Helper <auh@moto-timo.dev>
Date: Tue, 11 Jul 2023 22:58:37 -0500
Subject: [PATCH] python3-sqlalchemy: upgrade 2.0.15 -> 2.0.18
---
...ython3-sqlalchemy_2.0.15.bb => python3-sqlalchemy_2.0.18.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-python/recipes-devtools/python/{python3-sqlalchemy_2.0.15.bb => python3-sqlalchemy_2.0.18.bb} (87%)
diff --git a/meta-python/recipes-devtools/python/python3-sqlalchemy_2.0.15.bb b/meta-python/recipes-devtools/python/python3-sqlalchemy_2.0.18.bb
similarity index 87%
rename from meta-python/recipes-devtools/python/python3-sqlalchemy_2.0.15.bb
rename to meta-python/recipes-devtools/python/python3-sqlalchemy_2.0.18.bb
index e6f0d6429..770d558d2 100644
--- a/meta-python/recipes-devtools/python/python3-sqlalchemy_2.0.15.bb
+++ b/meta-python/recipes-devtools/python/python3-sqlalchemy_2.0.18.bb
@@ -4,7 +4,7 @@ HOMEPAGE = "http://www.sqlalchemy.org/"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE;md5=b707d50badb798e1d897f2c8f649382d"
-SRC_URI[sha256sum] = "2e940a8659ef870ae10e0d9e2a6d5aaddf0ff6e91f7d0d7732afc9e8c4be9bbc"
+SRC_URI[sha256sum] = "1fb792051db66e09c200e7bc3bda3b1eb18a5b8eb153d2cedb2b14b56a68b8cb"
PYPI_PACKAGE = "SQLAlchemy"
inherit pypi setuptools3
--
2.25.1
reply other threads:[~2023-07-12 5:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230712053150.6925EEB64D9@smtp.lore.kernel.org \
--to=auh@moto-timo.dev \
--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