public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: Martin Bachmann <martin.bachmann@designwerk.com>
Cc: Thomas Perale <thomas.perale@mind.be>,
	Martin Bachmann via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v1 1/1] package/python-multipart: bump to version 0.0.22
Date: Fri,  6 Mar 2026 20:53:05 +0100	[thread overview]
Message-ID: <20260306195305.7486-1-thomas.perale@mind.be> (raw)
In-Reply-To: <ZR0P278MB0869C41190C47D5811F1A6758B75A@ZR0P278MB0869.CHEP278.PROD.OUTLOOK.COM>

In reply of:
> This will fix CVE-2026-24486
> 
> Signed-off-by: Martin Bachmann <martin.bachmann@designwerk.com>

Applied to 2025.02.x & 2025.11.x. Thanks

> ---
>  package/python-multipart/python-multipart.hash | 4 ++--
>  package/python-multipart/python-multipart.mk   | 4 ++--
>  2 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/package/python-multipart/python-multipart.hash b/package/python-multipart/python-multipart.hash
> index ed01763cd7..a5bc988b02 100644
> --- a/package/python-multipart/python-multipart.hash
> +++ b/package/python-multipart/python-multipart.hash
> @@ -1,5 +1,5 @@
>  # md5, sha256 from https://pypi.org/pypi/python_multipart/json
> -md5  fd24645f1b328d5d328e8b10bc2c596c  python_multipart-0.0.21.tar.gz
> -sha256  7137ebd4d3bbf70ea1622998f902b97a29434a9e8dc40eb203bbcf7c2a2cba92  python_multipart-0.0.21.tar.gz
> +md5  0debb97a2b5d68f8dd5119bd200f4010  python_multipart-0.0.22.tar.gz
> +sha256  7340bef99a7e0032613f56dc36027b959fd3b30a787ed62d310e951f7c3a3a58  python_multipart-0.0.22.tar.gz
>  # Locally computed sha256 checksums
>  sha256  a8e833176cd617daf00b9d6d39fa15ca8edebc6d1643079cd2f4893c0c289be2  LICENSE.txt
> diff --git a/package/python-multipart/python-multipart.mk b/package/python-multipart/python-multipart.mk
> index 6921d935eb..cdaae6ef67 100644
> --- a/package/python-multipart/python-multipart.mk
> +++ b/package/python-multipart/python-multipart.mk
> @@ -4,9 +4,9 @@
>  #
>  ################################################################################
>  
> -PYTHON_MULTIPART_VERSION = 0.0.21
> +PYTHON_MULTIPART_VERSION = 0.0.22
>  PYTHON_MULTIPART_SOURCE = python_multipart-$(PYTHON_MULTIPART_VERSION).tar.gz
> -PYTHON_MULTIPART_SITE = https://files.pythonhosted.org/packages/78/96/804520d0850c7db98e5ccb70282e29208723f0964e88ffd9d0da2f52ea09
> +PYTHON_MULTIPART_SITE = https://files.pythonhosted.org/packages/94/01/979e98d542a70714b0cb2b6728ed0b7c46792b695e3eaec3e20711271ca3
>  PYTHON_MULTIPART_SETUP_TYPE = hatch
>  PYTHON_MULTIPART_LICENSE = Apache-2.0
>  PYTHON_MULTIPART_LICENSE_FILES = LICENSE.txt
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2026-03-06 19:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25 12:49 [Buildroot] [PATCH v1 1/1] package/python-multipart: bump to version 0.0.22 Martin Bachmann via buildroot
2026-03-01 18:49 ` Julien Olivain via buildroot
2026-03-06 19:53 ` Thomas Perale via buildroot [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=20260306195305.7486-1-thomas.perale@mind.be \
    --to=buildroot@buildroot.org \
    --cc=martin.bachmann@designwerk.com \
    --cc=thomas.perale@mind.be \
    /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