From: JamiKettunen <JamiKettunen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: curl: update to 7.84.0.
Date: Sat, 09 Jul 2022 16:07:12 +0200 [thread overview]
Message-ID: <20220709140712.qMBj7_MArlngA40CDhG846OStZ67vieWmn1LCcn7oCY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37823@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 658 bytes --]
New comment by JamiKettunen on void-packages repository
https://github.com/void-linux/void-packages/pull/37823#issuecomment-1179550655
Comment:
Just as a heads-up: on Arch Linux this seems to have started causing `error: curl returned error 12 from transfer` errors seemingly randomly during e.g. package upgrades.
Fixing upstream commit: https://github.com/curl/curl/commit/52e822173aa3cd4f610531d32fbf943f026cdca6
Arch bugtracker: https://bugs.archlinux.org/task/75201 ([they started carrying the patch downstream which reportedly has fixed the issues](https://github.com/archlinux/svntogit-packages/commit/eb7f828fa4cafc73f6c4fb0d6ae78c5753958c2c))
next prev parent reply other threads:[~2022-07-09 14:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 23:58 [PR PATCH] " mhmdanas
2022-07-09 14:07 ` JamiKettunen [this message]
2022-07-09 14:08 ` JamiKettunen
2022-07-14 9:57 ` mhmdanas
2022-07-14 9:57 ` [PR PATCH] [Closed]: " mhmdanas
2022-07-06 10:35 [PR PATCH] " ishaanbhimwal
2022-07-06 14:42 ` classabbyamp
2022-07-13 14:21 [PR PATCH] " MouadCharradi
2022-07-13 15:09 ` biopsin
2022-07-14 9:57 ` mhmdanas
2022-07-14 11:39 ` JamiKettunen
2022-07-14 11:48 ` mhmdanas
2022-07-14 11:49 ` mhmdanas
2022-07-14 11:58 ` JamiKettunen
2022-07-14 12:02 ` JamiKettunen
2022-07-14 12:04 ` mhmdanas
2022-07-14 12:51 ` MouadCharradi
2022-07-14 14:57 ` JamiKettunen
2022-07-17 19:05 ` ericonr
2022-07-17 19:24 ` ericonr
2022-07-17 19:25 ` ericonr
2022-07-17 19:43 ` ericonr
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=20220709140712.qMBj7_MArlngA40CDhG846OStZ67vieWmn1LCcn7oCY@z \
--to=jamikettunen@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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).