All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tim Orling" <ticotimo@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Tim Orling <timothy.t.orling@intel.com>
Subject: [RFC PATCH 09/10][dunfell] python3: upgrade 3.8.9 -> 3.8.10
Date: Mon, 21 Jun 2021 10:02:56 -0700	[thread overview]
Message-ID: <4f3d732b68925204fd63790f8ef69b6819fbc4fb.1624294059.git.timothy.t.orling@intel.com> (raw)
In-Reply-To: <cover.1624294059.git.timothy.t.orling@intel.com>

Release Date: May 3, 2021

This is the tenth and final regular maintenance release of Python 3.8

Note: The release you're looking at is Python 3.8.10, a bugfix release for the
legacy 3.8 series. Python 3.9 is now the latest feature release series of
Python 3.

FIXME:
AssertionError: Failed ptests:
{'python3': ['test_record_extensions', 'test_build_ext']}

References:
https://www.python.org/downloads/release/python-3810/
https://docs.python.org/release/3.8.10/whatsnew/changelog.html

Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
---
 .../python/{python3_3.8.9.bb => python3_3.8.10.bb}            | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-devtools/python/{python3_3.8.9.bb => python3_3.8.10.bb} (99%)

diff --git a/meta/recipes-devtools/python/python3_3.8.9.bb b/meta/recipes-devtools/python/python3_3.8.10.bb
similarity index 99%
rename from meta/recipes-devtools/python/python3_3.8.9.bb
rename to meta/recipes-devtools/python/python3_3.8.10.bb
index c6e7e593787..3e4386e57c8 100644
--- a/meta/recipes-devtools/python/python3_3.8.9.bb
+++ b/meta/recipes-devtools/python/python3_3.8.10.bb
@@ -42,8 +42,8 @@ SRC_URI_append_class-native = " \
            file://0001-Don-t-search-system-for-headers-libraries.patch \
            "
 
-SRC_URI[md5sum] = "51b5bbf2ab447e66d15af4883db1c133"
-SRC_URI[sha256sum] = "5e391f3ec45da2954419cab0beaefd8be38895ea5ce33577c3ec14940c4b9572"
+SRC_URI[md5sum] = "d9eee4b20155553830a2025e4dcaa7b3"
+SRC_URI[sha256sum] = "6af24a66093dd840bcccf371d4044a3027e655cf24591ce26e48022bc79219d9"
 
 # exclude pre-releases for both python 2.x and 3.x
 UPSTREAM_CHECK_REGEX = "[Pp]ython-(?P<pver>\d+(\.\d+)+).tar"
-- 
2.30.2


  parent reply	other threads:[~2021-06-21 17:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-21 17:02 [RFC PATCH 00/10][dunfell] python3 bugfix upgrades Tim Orling
2021-06-21 17:02 ` [RFC PATCH 01/10][dunfell] python3: upgrade 3.8.2 -> 3.8.3 Tim Orling
2021-06-21 17:02 ` [RFC PATCH 02/10][dunfell] python3: upgrade 3.8.3 -> 3.8.4 Tim Orling
2021-06-21 17:02 ` [RFC PATCH 03/10][dunfell] python3: upgrade 3.8.4 -> 3.8.5 Tim Orling
2021-06-21 17:02 ` [RFC PATCH 04/10][dunfell] python3: upgrade 3.8.5 -> 3.8.6 Tim Orling
2021-06-21 17:02 ` [RFC PATCH 05/10][dunfell] python3: upgrade 3.8.6 -> 3.8.7 Tim Orling
2021-06-21 17:02 ` [RFC PATCH 06/10][dunfell] python3: upgrade 3.8.7 -> 3.8.8 Tim Orling
2021-06-21 17:02 ` [RFC PATCH 07/10][dunfell] python3: skip tests requiring tools-sdk Tim Orling
2021-06-21 17:02 ` [RFC PATCH 08/10][dunfell] python3: upgrade 3.8.8 -> 3.8.9 Tim Orling
2021-06-21 17:02 ` Tim Orling [this message]
2021-06-21 17:02 ` [RFC PATCH 10/10][dunfell] python3-ptest: add newly discovered missing rdeps Tim Orling

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=4f3d732b68925204fd63790f8ef69b6819fbc4fb.1624294059.git.timothy.t.orling@intel.com \
    --to=ticotimo@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=timothy.t.orling@intel.com \
    /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.