All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Adam Duskett <adam.duskett@amarulasolutions.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/python-django: security bump to 4.2.7
Date: Wed, 08 Nov 2023 19:10:20 +0100	[thread overview]
Message-ID: <87pm0kqfoz.fsf@48ers.dk> (raw)
In-Reply-To: <20231103184428.1029306-1-adam.duskett@amarulasolutions.com> (Adam Duskett's message of "Fri, 3 Nov 2023 12:44:28 -0600")

>>>>> "Adam" == Adam Duskett <adam.duskett@amarulasolutions.com> writes:

 >  - Fixed a regression in Django 4.2 that caused a crash of QuerySet.aggregate()
 >    with aggregates referencing expressions containing subqueries (#34798).

 >  - Restored, following a regression in Django 4.2, creating
 >    varchar/text_pattern_ops indexes on CharField and TextField with
 >    deterministic collations on PostgreSQL (#34932).

 > Tested on Fedora 39 with:
 > ./support/testing/run-tests tests.package.test_python_django

 > Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>

While this indeed is a security fix, it seems to be for a Windows-only
issue:

https://www.djangoproject.com/weblog/2023/nov/01/security-releases/

Anyway, for 2023.02.x and 2023.08.x I have instead bumped to 4.1.13,
which contains the same fix.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2023-11-08 18:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03 18:44 [Buildroot] [PATCH 1/1] package/python-django: security bump to 4.2.7 Adam Duskett
2023-11-03 19:54 ` Thomas Petazzoni via buildroot
2023-11-08 18:10 ` Peter Korsgaard [this message]

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=87pm0kqfoz.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=adam.duskett@amarulasolutions.com \
    --cc=buildroot@buildroot.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 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.