From: Matt Jolly <Matt.Jolly@footclan.ninja>
To: distributions@lists.linux.dev
Subject: cURL 7.88.0 HTTP/2 breakage
Date: Thu, 16 Feb 2023 17:22:27 +1100 [thread overview]
Message-ID: <e3306ab8-3656-3128-40f8-f76e6871a3a3@footclan.ninja> (raw)
Hi all,
We've had to mask cURL 7.88.0 in Gentoo (and I note Arch and Alpine have taken similar action)
due to a commit that causes broken HTTP/2 transfers impacting things like `cargo fetch`.
https://github.com/curl/curl/issues/10525
https://github.com/alpinelinux/aports/commit/ed89ad7059e2ccf3d5bd9cd7bbde506ccc0bf6d8
https://github.com/gentoo/gentoo/commit/1a9121ddab7ce24b861ff6f1d6c00539d30afa30
Nothing much to say about it otherwise, PRs awaiting upstream; it may be best to revert the offending commit
or wait for a new patch release if you're looking at updating cURL packages.
Cheers,
Matt
reply other threads:[~2023-02-16 6:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e3306ab8-3656-3128-40f8-f76e6871a3a3@footclan.ninja \
--to=matt.jolly@footclan.ninja \
--cc=distributions@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).