From: Peter Korsgaard <peter@korsgaard.com>
To: Marcus Hoffmann via buildroot <buildroot@buildroot.org>,
James Hilliard <james.hilliard1@gmail.com>
Cc: Marcus Hoffmann <buildroot@bubu1.eu>
Subject: Re: [Buildroot] [PATCH 1/1] package/python-starlette: bump to version 0.34.0
Date: Mon, 05 Feb 2024 15:58:07 +0100 [thread overview]
Message-ID: <87il33rm9s.fsf@48ers.dk> (raw)
In-Reply-To: <42594955-dcd4-4161-9a84-879f096d49f7@bubu1.eu> (Marcus Hoffmann via buildroot's message of "Mon, 5 Feb 2024 14:34:05 +0100")
>>>>> "Marcus" == Marcus Hoffmann via buildroot <buildroot@buildroot.org> writes:
> Hi Peter,
> On 05.02.24 12:15, Peter Korsgaard wrote:
>>>>>>> "James" == James Hilliard <james.hilliard1@gmail.com> writes:
>> > Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
>> Committed, thanks.
>>
> We currently have fastapi 0.105.0 in buildroot which depends on
> starlette < 0.28.0.
> There's a pending patch by James that bumps it to 0.108.0, which
> unfortunately is also not compatible with starlette 0.34.0 [1] :-/
> In fact there's no fastapi release that is compatible with starlette
> 0.34.0 (newer fastapi releases require even newer starlette
> versions...)
Argh :(
> I guess I'll send a series that bumps *both* again to compatible versions?
Yes please!
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-02-05 14:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 7:29 [Buildroot] [PATCH 1/1] package/python-starlette: bump to version 0.34.0 James Hilliard
2024-02-05 11:15 ` Peter Korsgaard
2024-02-05 13:34 ` Marcus Hoffmann via buildroot
2024-02-05 14:58 ` Peter Korsgaard [this message]
2024-02-05 16:47 ` James Hilliard
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=87il33rm9s.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@bubu1.eu \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@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