From: auh@auh.yoctoproject.org
To: Joshua Watt <JPEWhacker@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: [AUH] python3-libarchive-c: upgrading to 3.1 SUCCEEDED [thread overview]
Message-ID: <MADEUP.16860E22AE3CEB48.23614@lists.openembedded.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-libarchive-c* to *3.1* has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-libarchive-c-upgrade-3.0-3.1.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-libarchive-c-upgrade-3.0-3.1.patch --]
[-- Type: text/x-diff, Size: 1282 bytes --]
From a286b32e963cefd54b1c14b3ad795d279a19313c Mon Sep 17 00:00:00 2001
From: Upgrade Helper <auh@auh.yoctoproject.org>
Date: Sun, 6 Jun 2021 09:11:26 +0000
Subject: [PATCH] python3-libarchive-c: upgrade 3.0 -> 3.1
---
...python3-libarchive-c_3.0.bb => python3-libarchive-c_3.1.bb} | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
rename meta/recipes-devtools/python/{python3-libarchive-c_3.0.bb => python3-libarchive-c_3.1.bb} (78%)
diff --git a/meta/recipes-devtools/python/python3-libarchive-c_3.0.bb b/meta/recipes-devtools/python/python3-libarchive-c_3.1.bb
similarity index 78%
rename from meta/recipes-devtools/python/python3-libarchive-c_3.0.bb
rename to meta/recipes-devtools/python/python3-libarchive-c_3.1.bb
index d29195545f..5e0f461271 100644
--- a/meta/recipes-devtools/python/python3-libarchive-c_3.0.bb
+++ b/meta/recipes-devtools/python/python3-libarchive-c_3.1.bb
@@ -9,8 +9,7 @@ PYPI_PACKAGE = "libarchive-c"
inherit pypi setuptools3
-SRC_URI[md5sum] = "920885f5910aa8245e30896996e0415b"
-SRC_URI[sha256sum] = "6f12fa9cf0e44579e5f45bbf11aa455a930fbfdb13ea0ce3c3dfe7b9b9a452ba"
+SRC_URI[sha256sum] = "618a7ecfbfb58ca15e11e3138d4a636498da3b6bc212811af158298530fbb87e"
RDEPENDS_${PN} += "\
libarchive \
--
2.17.1
[-- Attachment #3: buildhistory-diff.txt --]
[-- Type: text/plain, Size: 215 bytes --]
Changes to packages/core2-32-poky-linux/python3-libarchive-c (sysroot):
/usr/lib/python3.9/site-packages/libarchive_c-3.0-py3.9.egg-info moved to /usr/lib/python3.9/site-packages/libarchive_c-3.1-py3.9.egg-info
[-- Attachment #4: buildhistory-diff-full.txt --]
[-- Type: text/plain, Size: 2414 bytes --]
packages/core2-32-poky-linux/python3-libarchive-c: PKGV changed from 3.0 [default] to 3.1 [default]
packages/core2-32-poky-linux/python3-libarchive-c: PV changed from "3.0" to "3.1"
packages/core2-32-poky-linux/python3-libarchive-c: SRC_URI changed from "https://files.pythonhosted.org/packages/source/l/libarchive-c/libarchive-c-3.0.tar.gz" to "https://files.pythonhosted.org/packages/source/l/libarchive-c/libarchive-c-3.1.tar.gz"
packages/core2-32-poky-linux/python3-libarchive-c/python3-libarchive-c-dbg: PKGV changed from 3.0 [default] to 3.1 [default]
packages/core2-32-poky-linux/python3-libarchive-c/python3-libarchive-c-dbg: PV changed from "3.0" to "3.1"
packages/core2-32-poky-linux/python3-libarchive-c/python3-libarchive-c-dev: PKGV changed from 3.0 [default] to 3.1 [default]
packages/core2-32-poky-linux/python3-libarchive-c/python3-libarchive-c-dev: PV changed from "3.0" to "3.1"
packages/core2-32-poky-linux/python3-libarchive-c/python3-libarchive-c-doc: PKGV changed from 3.0 [default] to 3.1 [default]
packages/core2-32-poky-linux/python3-libarchive-c/python3-libarchive-c-doc: PV changed from "3.0" to "3.1"
packages/core2-32-poky-linux/python3-libarchive-c/python3-libarchive-c-locale: PKGV changed from 3.0 [default] to 3.1 [default]
packages/core2-32-poky-linux/python3-libarchive-c/python3-libarchive-c-locale: PV changed from "3.0" to "3.1"
packages/core2-32-poky-linux/python3-libarchive-c/python3-libarchive-c-src: PKGV changed from 3.0 [default] to 3.1 [default]
packages/core2-32-poky-linux/python3-libarchive-c/python3-libarchive-c-src: PV changed from "3.0" to "3.1"
packages/core2-32-poky-linux/python3-libarchive-c/python3-libarchive-c-staticdev: PKGV changed from 3.0 [default] to 3.1 [default]
packages/core2-32-poky-linux/python3-libarchive-c/python3-libarchive-c-staticdev: PV changed from "3.0" to "3.1"
packages/core2-32-poky-linux/python3-libarchive-c/python3-libarchive-c: PKGV changed from 3.0 [default] to 3.1 [default]
packages/core2-32-poky-linux/python3-libarchive-c/python3-libarchive-c: PKGSIZE changed from 68818 to 67758 (-2%)
packages/core2-32-poky-linux/python3-libarchive-c/python3-libarchive-c: PV changed from "3.0" to "3.1"
Changes to packages/core2-32-poky-linux/python3-libarchive-c (sysroot):
/usr/lib/python3.9/site-packages/libarchive_c-3.0-py3.9.egg-info moved to /usr/lib/python3.9/site-packages/libarchive_c-3.1-py3.9.egg-info
next reply other threads:[~2021-06-06 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 17:24 auh [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-03 1:24 [AUH] python3-libarchive-c: upgrading to 3.1 SUCCEEDED auh
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.16860E22AE3CEB48.23614@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox