Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: "Raphaël Mélotte" <raphael.melotte@mind.be>,
	"Asaf Kahlon" <asafka7@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/1] package/python-botocore: bump to version 1.31.20
Date: Mon, 7 Aug 2023 22:21:46 +0200	[thread overview]
Message-ID: <20230807222146.6e6ea019@windsurf> (raw)
In-Reply-To: <20230806220255.4099091-1-james.hilliard1@gmail.com>

On Sun,  6 Aug 2023 16:02:55 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:

> When we bumped urllib3 in 074bc42971181ee71d8ff5bd57641b7b7eb7580f
> we broke compatibility with python-botocore.
> 
> This compatibility error was fixed upstream in botocore 1.29.122:
> https://github.com/boto/botocore/commit/0a6d8e3c6325da395a04227599cfa292190d6841
> 
> Fixes:
>  - https://gitlab.com/buildroot.org/buildroot/-/jobs/4768561482
> 
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
> Changes v1 -> v2:
>   - add fixes info
> ---
>  package/python-botocore/python-botocore.hash | 4 ++--
>  package/python-botocore/python-botocore.mk   | 4 ++--
>  2 files changed, 4 insertions(+), 4 deletions(-)

Applied to master, thanks.

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

      parent reply	other threads:[~2023-08-07 20:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-06 22:02 [Buildroot] [PATCH v2 1/1] package/python-botocore: bump to version 1.31.20 James Hilliard
2023-08-06 22:14 ` Romain Naour
2023-08-07 20:21 ` Thomas Petazzoni 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=20230807222146.6e6ea019@windsurf \
    --to=buildroot@buildroot.org \
    --cc=asafka7@gmail.com \
    --cc=james.hilliard1@gmail.com \
    --cc=raphael.melotte@mind.be \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox