From: auh@moto-timo.dev
To: openembedded-devel@lists.openembedded.org
Subject: [AUH] python3-bandit: upgrading to 1.7.5 SUCCEEDED
Date: Wed, 12 Jul 2023 05:30:00 +0000 (UTC) [thread overview]
Message-ID: <20230712053000.64C00EB64DA@smtp.lore.kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2355 bytes --]
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-bandit* to *1.7.5* has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-bandit-upgrade-1.7.4-1.7.5.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 402fc96d7b589d9e22aca46789f0320134cf223b Mon Sep 17 00:00:00 2001
From: Upgrade Helper <auh@moto-timo.dev>
Date: Tue, 11 Jul 2023 17:05:58 -0500
Subject: [PATCH] python3-bandit: upgrade 1.7.4 -> 1.7.5
---
.../python/{python3-bandit_1.7.4.bb => python3-bandit_1.7.5.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-python/recipes-devtools/python/{python3-bandit_1.7.4.bb => python3-bandit_1.7.5.bb} (82%)
diff --git a/meta-python/recipes-devtools/python/python3-bandit_1.7.4.bb b/meta-python/recipes-devtools/python/python3-bandit_1.7.5.bb
similarity index 82%
rename from meta-python/recipes-devtools/python/python3-bandit_1.7.4.bb
rename to meta-python/recipes-devtools/python/python3-bandit_1.7.5.bb
index cfdbde968..5e2a7e8bc 100644
--- a/meta-python/recipes-devtools/python/python3-bandit_1.7.4.bb
+++ b/meta-python/recipes-devtools/python/python3-bandit_1.7.5.bb
@@ -2,7 +2,7 @@ SUMMARY = "Security oriented static analyser for python code."
LICENSE = "Apache-2.0"
LIC_FILES_CHKSUM = "file://LICENSE;md5=34400b68072d710fecd0a2940a0d1658"
-SRC_URI[sha256sum] = "2d63a8c573417bae338962d4b9b06fbc6080f74ecd955a092849e1e65c717bd2"
+SRC_URI[sha256sum] = "bdfc739baa03b880c2d15d0431b31c658ffc348e907fe197e54e0389dd59e11e"
DEPENDS = "python3-pbr-native python3-git python3-pbr python3-pyyaml python3-six python3-stevedore"
--
2.25.1
[-- Attachment #2: 0001-python3-bandit-upgrade-1.7.4-1.7.5.patch --]
[-- Type: text/x-diff, Size: 1372 bytes --]
From 402fc96d7b589d9e22aca46789f0320134cf223b Mon Sep 17 00:00:00 2001
From: Upgrade Helper <auh@moto-timo.dev>
Date: Tue, 11 Jul 2023 17:05:58 -0500
Subject: [PATCH] python3-bandit: upgrade 1.7.4 -> 1.7.5
---
.../python/{python3-bandit_1.7.4.bb => python3-bandit_1.7.5.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-python/recipes-devtools/python/{python3-bandit_1.7.4.bb => python3-bandit_1.7.5.bb} (82%)
diff --git a/meta-python/recipes-devtools/python/python3-bandit_1.7.4.bb b/meta-python/recipes-devtools/python/python3-bandit_1.7.5.bb
similarity index 82%
rename from meta-python/recipes-devtools/python/python3-bandit_1.7.4.bb
rename to meta-python/recipes-devtools/python/python3-bandit_1.7.5.bb
index cfdbde968..5e2a7e8bc 100644
--- a/meta-python/recipes-devtools/python/python3-bandit_1.7.4.bb
+++ b/meta-python/recipes-devtools/python/python3-bandit_1.7.5.bb
@@ -2,7 +2,7 @@ SUMMARY = "Security oriented static analyser for python code."
LICENSE = "Apache-2.0"
LIC_FILES_CHKSUM = "file://LICENSE;md5=34400b68072d710fecd0a2940a0d1658"
-SRC_URI[sha256sum] = "2d63a8c573417bae338962d4b9b06fbc6080f74ecd955a092849e1e65c717bd2"
+SRC_URI[sha256sum] = "bdfc739baa03b880c2d15d0431b31c658ffc348e907fe197e54e0389dd59e11e"
DEPENDS = "python3-pbr-native python3-git python3-pbr python3-pyyaml python3-six python3-stevedore"
--
2.25.1
reply other threads:[~2023-07-12 5:30 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=20230712053000.64C00EB64DA@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