From: auh@moto-timo.dev
To: openembedded-devel@lists.openembedded.org
Subject: [AUH] python3-tox: upgrading to 4.6.4 SUCCEEDED
Date: Wed, 12 Jul 2023 05:32:00 +0000 (UTC) [thread overview]
Message-ID: <20230712053200.7B18EC001DC@smtp.lore.kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2257 bytes --]
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-tox* to *4.6.4* has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-tox-upgrade-4.6.3-4.6.4.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 555adea530747f842b1585dc7e89c66a0b60df32 Mon Sep 17 00:00:00 2001
From: Upgrade Helper <auh@moto-timo.dev>
Date: Tue, 11 Jul 2023 23:15:10 -0500
Subject: [PATCH] python3-tox: upgrade 4.6.3 -> 4.6.4
---
.../python/{python3-tox_4.6.3.bb => python3-tox_4.6.4.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-python/recipes-devtools/python/{python3-tox_4.6.3.bb => python3-tox_4.6.4.bb} (92%)
diff --git a/meta-python/recipes-devtools/python/python3-tox_4.6.3.bb b/meta-python/recipes-devtools/python/python3-tox_4.6.4.bb
similarity index 92%
rename from meta-python/recipes-devtools/python/python3-tox_4.6.3.bb
rename to meta-python/recipes-devtools/python/python3-tox_4.6.4.bb
index ed8fc38b2..a8215a91b 100644
--- a/meta-python/recipes-devtools/python/python3-tox_4.6.3.bb
+++ b/meta-python/recipes-devtools/python/python3-tox_4.6.4.bb
@@ -6,7 +6,7 @@ HOMEPAGE = "http://tox.readthedocs.org/"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE;md5=11610a9d8fd95649cf8159be12b98cb7"
-SRC_URI[sha256sum] = "9e2c5091a117d03b583c57c4c40aecd068099c17d40520e7b165e85c19334534"
+SRC_URI[sha256sum] = "5e2ad8845764706170d3dcaac171704513cc8a725655219acb62fe4380bdadda"
BBCLASSEXTEND = "native nativesdk"
inherit pypi python_hatchling
--
2.25.1
[-- Attachment #2: 0001-python3-tox-upgrade-4.6.3-4.6.4.patch --]
[-- Type: text/x-diff, Size: 1280 bytes --]
From 555adea530747f842b1585dc7e89c66a0b60df32 Mon Sep 17 00:00:00 2001
From: Upgrade Helper <auh@moto-timo.dev>
Date: Tue, 11 Jul 2023 23:15:10 -0500
Subject: [PATCH] python3-tox: upgrade 4.6.3 -> 4.6.4
---
.../python/{python3-tox_4.6.3.bb => python3-tox_4.6.4.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-python/recipes-devtools/python/{python3-tox_4.6.3.bb => python3-tox_4.6.4.bb} (92%)
diff --git a/meta-python/recipes-devtools/python/python3-tox_4.6.3.bb b/meta-python/recipes-devtools/python/python3-tox_4.6.4.bb
similarity index 92%
rename from meta-python/recipes-devtools/python/python3-tox_4.6.3.bb
rename to meta-python/recipes-devtools/python/python3-tox_4.6.4.bb
index ed8fc38b2..a8215a91b 100644
--- a/meta-python/recipes-devtools/python/python3-tox_4.6.3.bb
+++ b/meta-python/recipes-devtools/python/python3-tox_4.6.4.bb
@@ -6,7 +6,7 @@ HOMEPAGE = "http://tox.readthedocs.org/"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE;md5=11610a9d8fd95649cf8159be12b98cb7"
-SRC_URI[sha256sum] = "9e2c5091a117d03b583c57c4c40aecd068099c17d40520e7b165e85c19334534"
+SRC_URI[sha256sum] = "5e2ad8845764706170d3dcaac171704513cc8a725655219acb62fe4380bdadda"
BBCLASSEXTEND = "native nativesdk"
inherit pypi python_hatchling
--
2.25.1
reply other threads:[~2023-07-12 5:32 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=20230712053200.7B18EC001DC@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