All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Marcus Hoffmann via buildroot <buildroot@buildroot.org>
Cc: James Hilliard <james.hilliard1@gmail.com>,
	Marcus Hoffmann <buildroot@bubu1.eu>,
	Asaf Kahlon <asafka7@gmail.com>,
	Oli Vogt <oli.vogt.pub01@gmail.com>
Subject: Re: [Buildroot] [PATCH] package/python-django: security bump to 5.1.1
Date: Thu, 5 Sep 2024 21:45:51 +0200	[thread overview]
Message-ID: <20240905214551.06532f87@windsurf> (raw)
In-Reply-To: <20240904154417.168646-1-buildroot@bubu1.eu>

On Wed,  4 Sep 2024 17:44:16 +0200
Marcus Hoffmann via buildroot <buildroot@buildroot.org> wrote:

> Fixes:
> * CVE-2024-45230
> * CVE-2024-45231
> 
> Further changes: https://docs.djangoproject.com/en/5.1/releases/5.1.1/
> 
> Signed-off-by: Marcus Hoffmann <buildroot@bubu1.eu>
> ---
>  package/python-django/python-django.hash | 4 ++--
>  package/python-django/python-django.mk   | 4 ++--
>  2 files changed, 4 insertions(+), 4 deletions(-)

I've applied to next, because next had 5.1.0.

For master, which has 5.0.8, we need a bump to 5.0.9, which fixes those
security issues I believe (and 2024.02.x should also upgrade to 5.0.9).
Could you send a patch against master bumping to 5.0.9 ?

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-09-05 19:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-04 15:44 [Buildroot] [PATCH] package/python-django: security bump to 5.1.1 Marcus Hoffmann via buildroot
2024-09-05 19:45 ` Thomas Petazzoni via buildroot [this message]
2024-09-09 13:23   ` Marcus Hoffmann via buildroot
2024-09-14 15:15 ` Peter Korsgaard
2024-09-14 15:16   ` 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=20240905214551.06532f87@windsurf \
    --to=buildroot@buildroot.org \
    --cc=asafka7@gmail.com \
    --cc=buildroot@bubu1.eu \
    --cc=james.hilliard1@gmail.com \
    --cc=oli.vogt.pub01@gmail.com \
    --cc=thomas.petazzoni@bootlin.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.