From: Luis Felipe <sirgazil@zoho.com>
To: guix-devel@gnu.org
Subject: Adding Django 4.2 LTS
Date: Wed, 21 Jun 2023 18:36:22 +0000 [thread overview]
Message-ID: <8087a7ce-d17d-3005-f548-4562576aa82d@zoho.com> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1231 bytes --]
Hi,
I've been using Django 4.2.2 from my personal Guix channel for a couple
of days and it seems to work alright, so I'd like to send a patch to
include it in Guix, although I have some questions first.
1. python-asgiref >= 3.6.0 and < 4 is a requirement for Django 4.2 LTS
series, there is a patch for it already
(https://issues.guix.gnu.org/61543), it builds, doesn't appear to have
known vulnerabilities and Django 4.2.2 works with it. Would it be okay
to add it to Guix until someone else packages the latest version (3.7.2,
but it currently fails to build for me: sanity-check
DistributionNotFound or something)?
2. "guix lint python-django@4.2.2" says this version of DJango might be
vulnerable to CVE-2023-31047 but reading the CVE description version
4.2.2 doesn't seem to be affected. Is there anything I should do
regarding this warning?
3. Guix currently distributes versions of Django that no longer receive
security updates or bug fixes. For example, python-django@4.0.7,
python-django@3.1.14, python-django@2.2.28 (see
https://www.djangoproject.com/download/). Should they be removed?
Thanks in advance,
--
Luis Felipe López Acevedo
https://luis-felipe.gitlab.io/
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2881 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next reply other threads:[~2023-06-21 18:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 18:36 Luis Felipe [this message]
2023-07-31 2:13 ` Adding Django 4.2 LTS Maxim Cournoyer
2023-07-31 15:24 ` ngraves--- via Development of GNU Guix and the GNU System distribution.
2023-07-31 15:25 ` ngraves--- via Development of GNU Guix and the GNU System distribution.
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=8087a7ce-d17d-3005-f548-4562576aa82d@zoho.com \
--to=sirgazil@zoho.com \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.