From: auh@auh.yoctoproject.org
To: Joshua Watt <JPEWhacker@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: [AUH] python3-pycryptodomex: upgrading to 3.9.9 SUCCEEDED [thread overview]
Message-ID: <MADEUP.16481067921EDB69.27635@lists.openembedded.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-pycryptodomex* to *3.9.9* has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-pycryptodomex-upgrade-3.9.8-3.9.9.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
[-- Attachment #2: 0001-python3-pycryptodomex-upgrade-3.9.8-3.9.9.patch --]
[-- Type: text/x-diff, Size: 1294 bytes --]
From 09cdda3af4411f8b7dfc12e53e64ea297e9f0bf4 Mon Sep 17 00:00:00 2001
From: Upgrade Helper <auh@auh.yoctoproject.org>
Date: Mon, 16 Nov 2020 14:40:05 +0000
Subject: [PATCH] python3-pycryptodomex: upgrade 3.9.8 -> 3.9.9
---
...n3-pycryptodomex_3.9.8.bb => python3-pycryptodomex_3.9.9.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-pycryptodomex_3.9.8.bb => python3-pycryptodomex_3.9.9.bb} (69%)
diff --git a/meta/recipes-devtools/python/python3-pycryptodomex_3.9.8.bb b/meta/recipes-devtools/python/python3-pycryptodomex_3.9.9.bb
similarity index 69%
rename from meta/recipes-devtools/python/python3-pycryptodomex_3.9.8.bb
rename to meta/recipes-devtools/python/python3-pycryptodomex_3.9.9.bb
index 035c7fa636..abff71efdd 100644
--- a/meta/recipes-devtools/python/python3-pycryptodomex_3.9.8.bb
+++ b/meta/recipes-devtools/python/python3-pycryptodomex_3.9.9.bb
@@ -1,7 +1,7 @@
require python-pycryptodome.inc
inherit setuptools3
-SRC_URI[sha256sum] = "48cc2cfc251f04a6142badeb666d1ff49ca6fdfc303fd72579f62b768aaa52b9"
+SRC_URI[sha256sum] = "7b5b7c5896f8172ea0beb283f7f9428e0ab88ec248ce0a5b8c98d73e26267d51"
FILES_${PN}-tests = " \
${PYTHON_SITEPACKAGES_DIR}/Cryptodome/SelfTest/ \
--
2.20.1
[-- Attachment #3: buildhistory-diff.txt --]
[-- Type: text/plain, Size: 222 bytes --]
Changes to packages/core2-32-poky-linux/python3-pycryptodomex (sysroot):
/usr/lib/python3.9/site-packages/pycryptodomex-3.9.8-py3.9.egg-info moved to /usr/lib/python3.9/site-packages/pycryptodomex-3.9.9-py3.9.egg-info
[-- Attachment #4: buildhistory-diff-full.txt --]
[-- Type: text/plain, Size: 2909 bytes --]
packages/core2-32-poky-linux/python3-pycryptodomex: PV changed from "3.9.8" to "3.9.9"
packages/core2-32-poky-linux/python3-pycryptodomex: SRC_URI changed from "https://files.pythonhosted.org/packages/source/p/pycryptodomex/pycryptodomex-3.9.8.tar.gz" to "https://files.pythonhosted.org/packages/source/p/pycryptodomex/pycryptodomex-3.9.9.tar.gz"
packages/core2-32-poky-linux/python3-pycryptodomex: PKGV changed from 3.9.8 [default] to 3.9.9 [default]
packages/core2-32-poky-linux/python3-pycryptodomex/python3-pycryptodomex-dbg: PV changed from "3.9.8" to "3.9.9"
packages/core2-32-poky-linux/python3-pycryptodomex/python3-pycryptodomex-dbg: PKGV changed from 3.9.8 [default] to 3.9.9 [default]
packages/core2-32-poky-linux/python3-pycryptodomex/python3-pycryptodomex-dev: PV changed from "3.9.8" to "3.9.9"
packages/core2-32-poky-linux/python3-pycryptodomex/python3-pycryptodomex-dev: PKGV changed from 3.9.8 [default] to 3.9.9 [default]
packages/core2-32-poky-linux/python3-pycryptodomex/python3-pycryptodomex-doc: PV changed from "3.9.8" to "3.9.9"
packages/core2-32-poky-linux/python3-pycryptodomex/python3-pycryptodomex-doc: PKGV changed from 3.9.8 [default] to 3.9.9 [default]
packages/core2-32-poky-linux/python3-pycryptodomex/python3-pycryptodomex-locale: PV changed from "3.9.8" to "3.9.9"
packages/core2-32-poky-linux/python3-pycryptodomex/python3-pycryptodomex-locale: PKGV changed from 3.9.8 [default] to 3.9.9 [default]
packages/core2-32-poky-linux/python3-pycryptodomex/python3-pycryptodomex-src: PV changed from "3.9.8" to "3.9.9"
packages/core2-32-poky-linux/python3-pycryptodomex/python3-pycryptodomex-src: PKGV changed from 3.9.8 [default] to 3.9.9 [default]
packages/core2-32-poky-linux/python3-pycryptodomex/python3-pycryptodomex-staticdev: PV changed from "3.9.8" to "3.9.9"
packages/core2-32-poky-linux/python3-pycryptodomex/python3-pycryptodomex-staticdev: PKGV changed from 3.9.8 [default] to 3.9.9 [default]
packages/core2-32-poky-linux/python3-pycryptodomex/python3-pycryptodomex-tests: PV changed from "3.9.8" to "3.9.9"
packages/core2-32-poky-linux/python3-pycryptodomex/python3-pycryptodomex-tests: PKGSIZE changed from 34085817 to 34085905 (+0%)
packages/core2-32-poky-linux/python3-pycryptodomex/python3-pycryptodomex-tests: PKGV changed from 3.9.8 [default] to 3.9.9 [default]
packages/core2-32-poky-linux/python3-pycryptodomex/python3-pycryptodomex: PV changed from "3.9.8" to "3.9.9"
packages/core2-32-poky-linux/python3-pycryptodomex/python3-pycryptodomex: PKGSIZE changed from 3057028 to 3057431 (+0%)
packages/core2-32-poky-linux/python3-pycryptodomex/python3-pycryptodomex: PKGV changed from 3.9.8 [default] to 3.9.9 [default]
Changes to packages/core2-32-poky-linux/python3-pycryptodomex (sysroot):
/usr/lib/python3.9/site-packages/pycryptodomex-3.9.8-py3.9.egg-info moved to /usr/lib/python3.9/site-packages/pycryptodomex-3.9.9-py3.9.egg-info
reply other threads:[~2020-11-16 18:28 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=MADEUP.16481067921EDB69.27635@lists.openembedded.org \
--to=auh@auh.yoctoproject.org \
--cc=JPEWhacker@gmail.com \
--cc=openembedded-core@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.