public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jan Macku <jamacku@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/curl] rawhide: new upstream release - 8.21.0~rc1
Date: Fri, 05 Jun 2026 10:41:20 GMT	[thread overview]
Message-ID: <178065608006.1.9640916792308953031.rpms-curl-c5cf6ac05c10@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/curl
Branch : rawhide
Commit : c5cf6ac05c1020eca477058129547d1df50a7de3
Author : Jan Macku <jamacku@redhat.com>
Date   : 2026-06-05T10:46:00+02:00
Stats  : +8/-48 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/curl/c/c5cf6ac05c1020eca477058129547d1df50a7de3?branch=rawhide

Log:
new upstream release - 8.21.0~rc1

---
diff --git a/0001-curl-8.20.0-event-fix-wakeup-consumption.patch b/0001-curl-8.20.0-event-fix-wakeup-consumption.patch
deleted file mode 100644
index b09d4a0..0000000
--- a/0001-curl-8.20.0-event-fix-wakeup-consumption.patch
+++ /dev/null
@@ -1,37 +0,0 @@
-From 89abc89a30819a402a427d86f5b6e61aaceedd6e Mon Sep 17 00:00:00 2001
-From: Stefan Eissing <stefan@eissing.org>
-Date: Mon, 11 May 2026 14:56:04 +0200
-Subject: [PATCH] event: fix wakeup consumption
-
-The events on a multi wakeup socketpair were only consumed via
-curl_multi_poll()/curl_multi_wait() but not in event based processing on
-a curl_multi_socket() call. That led to busy loops as reported in
-
-Fixes #21547
-Reported-by: Earnestly on github
-Closes #21549
-
-(cherry picked from commit 2a2104f3cff44bb28bb570a093be52bbeeed8f23)
----
- lib/multi.c | 5 +++++
- 1 file changed, 5 insertions(+)
-
-diff --git a/lib/multi.c b/lib/multi.c
-index 7520253d70..a0012d8faf 100644
---- a/lib/multi.c
-+++ b/lib/multi.c
-@@ -2479,6 +2479,11 @@ static CURLMcode multi_runsingle(struct Curl_multi *multi,
-   Curl_uint32_bset_remove(&multi->dirty, data->mid);
- 
-   if(data == multi->admin) {
-+#ifdef ENABLE_WAKEUP
-+    /* Consume any pending wakeup signals before processing.
-+     * This is necessary for event based processing. See #21547 */
-+    (void)Curl_wakeup_consume(multi->wakeup_pair, TRUE);
-+#endif
- #ifdef USE_RESOLV_THREADED
-     Curl_async_thrdd_multi_process(multi);
- #endif
--- 
-2.54.0
-

diff --git a/curl.spec b/curl.spec
index 39b71e4..6ea9bd2 100644
--- a/curl.spec
+++ b/curl.spec
@@ -12,8 +12,8 @@
 
 Summary: A utility for getting files from remote servers (FTP, HTTP, and others)
 Name: curl
-Version: 8.20.0
-Release: 2%{?dist}
+Version: 8.21.0~rc1
+Release: 1%{?dist}
 License: curl
 Source0: https://curl.se/download/%{name}-%{version_no_tilde}.tar.xz
 Source1: https://curl.se/download/%{name}-%{version_no_tilde}.tar.xz.asc
@@ -22,9 +22,6 @@ Source1: https://curl.se/download/%{name}-%{version_no_tilde}.tar.xz.asc
 # which points to the GPG key as of April 7th 2016 of https://daniel.haxx.se/mykey.asc
 Source2: mykey.asc
 
-# Fix potential 100% CPU usage in curl_multi_socket()
-Patch001: 0001-curl-8.20.0-event-fix-wakeup-consumption.patch
-
 # patch making libcurl multilib ready
 Patch101: 0101-curl-7.32.0-multilib.patch
 
@@ -48,7 +45,6 @@ BuildRequires: automake
 BuildRequires: brotli-devel
 BuildRequires: coreutils
 BuildRequires: gcc
-BuildRequires: groff
 BuildRequires: krb5-devel
 BuildRequires: libidn2-devel
 BuildRequires: libnghttp2-devel
@@ -80,9 +76,6 @@ BuildRequires: zlib-devel
 # For gpg verification of source tarball
 BuildRequires: gnupg2
 
-# needed to compress content of tool_hugehelp.c after changing curl.1 man page
-BuildRequires: perl(IO::Compress::Gzip)
-
 # needed for generation of shell completions
 BuildRequires: perl(Getopt::Long)
 BuildRequires: perl(Pod::Usage)
@@ -264,6 +257,7 @@ printf "619\n620\n621\n622\n623\n624\n625\n626\n627\n628\n" >>tests/data/DISABLE
 printf "629\n630\n631\n633\n634\n635\n636\n637\n638\n639\n" >>tests/data/DISABLED
 printf "640\n641\n642\n656\n664\n665\n" >>tests/data/DISABLED
 printf "1446\n1459\n1583\n2004\n2007\n" >>tests/data/DISABLED
+printf "3021\n3022\n" >>tests/data/DISABLED
 %endif
 
 # test3026: avoid pthread_create() failure due to resource exhaustion on i386
@@ -471,6 +465,9 @@ rm -f ${RPM_BUILD_ROOT}%{_mandir}/man1/wcurl.1*
 %{_libdir}/libcurl.so.4.[0-9].[0-9].minimal
 
 %changelog
+* Fri Jun 05 2026 Jan Macku <jamacku@redhat.com> - 8.21.0~rc1-1
+- new upstream release candidate
+
 * Mon May 18 2026 Jan Macku <jamacku@redhat.com> - 8.20.0-2
 - Fix potential 100% CPU usage in curl_multi_socket()
 

diff --git a/sources b/sources
index bf8e005..a9ec4d0 100644
--- a/sources
+++ b/sources
@@ -1,2 +1,2 @@
-SHA512 (curl-8.20.0.tar.xz.asc) = 188b7f664ed0cd4b1b0a8eb743a9b05e54fca38dbfe56c38a1591942c64c1c79dc29466745d8ec824513809708b13d9c7ced52b15eb71522da32e8a633a66488
-SHA512 (curl-8.20.0.tar.xz) = edfa5882aaeefcf2226fe03b19246151c0377c3656f9c8cc385bdaf34565e1354e762005b58780917a6d98039ae34085e4a4bcb44255c77e3b0e1d94090c010b
+SHA512 (curl-8.21.0-rc1.tar.xz.asc) = 93f1f6a35b19e16856bdb8c2e039147d847429f8fb8fbe17bd8b56464181107455afbb89a01507a8a52cb266fbbf02b6c54b98fbe732803a474fcf778298670b
+SHA512 (curl-8.21.0-rc1.tar.xz) = d74fb419c4a047b422ff5380ae607d4150e6b824941a654211f2aca7d52a4e644a1614ca3ea6f2a9ec20fe6ef6baa9a5cd149c2eec62a014d29c43e7a5798af4

                 reply	other threads:[~2026-06-05 10:41 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=178065608006.1.9640916792308953031.rpms-curl-c5cf6ac05c10@fedoraproject.org \
    --to=jamacku@redhat.com \
    --cc=git-commits@fedoraproject.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