From: Peter Korsgaard <peter@korsgaard.com>
To: Adam Duskett <adam.duskett@amarulasolutions.com>
Cc: James Hilliard <james.hilliard1@gmail.com>,
Oli Vogt <oli.vogt.pub01@gmail.com>,
Asaf Kahlon <asafka7@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/python-django: bump version to 4.2.6
Date: Wed, 25 Oct 2023 22:35:27 +0200 [thread overview]
Message-ID: <875y2uphio.fsf@48ers.dk> (raw)
In-Reply-To: <20231020082703.1610281-1-adam.duskett@amarulasolutions.com> (Adam Duskett's message of "Fri, 20 Oct 2023 10:27:03 +0200")
>>>>> "Adam" == Adam Duskett <adam.duskett@amarulasolutions.com> writes:
> Tested with tests.package.test_python_django.TestPythonPy3Django.test_run in
> Fedora 38 and Debian 11
> Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
Looking at
https://www.djangoproject.com/weblog/2023/oct/04/security-releases/,
Django 4.2.6 was a security release, so it should have been marked as
such (and ideally we would first have bumped to 4.1.12 for easier
backporting).
4.2.6 apparently also introduced a regression, so it would be good if
you could send a bump to 4.2.7:
https://docs.djangoproject.com/en/dev/releases/4.2.7/
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-10-25 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 8:27 [Buildroot] [PATCH 1/1] package/python-django: bump version to 4.2.6 Adam Duskett
2023-10-22 18:37 ` Yann E. MORIN
2023-10-25 20:35 ` Peter Korsgaard [this message]
2023-10-26 10:26 ` Adam Duskett
2023-10-26 11:26 ` Peter Korsgaard
2023-10-30 7:40 ` Peter Korsgaard
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=875y2uphio.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=adam.duskett@amarulasolutions.com \
--cc=asafka7@gmail.com \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=oli.vogt.pub01@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox