From: nmali <narpat.mali@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Cc: <hari.gpillai@windriver.com>
Subject: [meta-python][kirkstone][PATCH 1/1] python3-django: upgrade 4.0.2 -> 4.2.1
Date: Wed, 31 May 2023 10:02:57 +0000 [thread overview]
Message-ID: <20230531100257.3467702-1-narpat.mali@windriver.com> (raw)
From: Narpat Mali <narpat.mali@windriver.com>
Django 4.2* is designated as a long-term support release. It will receive
security updates for at least three years after its release.
The delta between 4.0.2 and 4.2.1 contain numerous CVEs and other
bugfixes.
Release Notes: https://docs.djangoproject.com/en/dev/releases/
Signed-off-by: Narpat Mali <narpat.mali@windriver.com>
---
.../python/{python3-django_4.0.2.bb => python3-django_4.2.1.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-python/recipes-devtools/python/{python3-django_4.0.2.bb => python3-django_4.2.1.bb} (77%)
diff --git a/meta-python/recipes-devtools/python/python3-django_4.0.2.bb b/meta-python/recipes-devtools/python/python3-django_4.2.1.bb
similarity index 77%
rename from meta-python/recipes-devtools/python/python3-django_4.0.2.bb
rename to meta-python/recipes-devtools/python/python3-django_4.2.1.bb
index 690b9809dc..4daca65eb5 100644
--- a/meta-python/recipes-devtools/python/python3-django_4.0.2.bb
+++ b/meta-python/recipes-devtools/python/python3-django_4.2.1.bb
@@ -1,7 +1,7 @@
require python-django.inc
inherit setuptools3
-SRC_URI[sha256sum] = "110fb58fb12eca59e072ad59fc42d771cd642dd7a2f2416582aa9da7a8ef954a"
+SRC_URI[sha256sum] = "7efa6b1f781a6119a10ac94b4794ded90db8accbe7802281cd26f8664ffed59c"
RDEPENDS:${PN} += "\
${PYTHON_PN}-sqlparse \
--
2.40.0
next reply other threads:[~2023-05-31 10:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 10:02 nmali [this message]
2023-06-01 15:51 ` [oe] [meta-python][kirkstone][PATCH 1/1] python3-django: upgrade 4.0.2 -> 4.2.1 Randy MacLeod
2023-06-01 23:55 ` Tim Orling
2023-06-02 15:49 ` Mali, Narpat
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=20230531100257.3467702-1-narpat.mali@windriver.com \
--to=narpat.mali@windriver.com \
--cc=hari.gpillai@windriver.com \
--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;
as well as URLs for NNTP newsgroup(s).