public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Gabriel Somlo <gsomlo@gmail.com>
To: git-commits@fedoraproject.org
Subject: [rpms/iperf] f44: update to 2.2.2
Date: Sat, 21 Nov 2026 01:43:53 GMT [thread overview]
Message-ID: <179522543334.1.4056042662899404369.rpms-iperf-58396d1933dc@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/iperf
Branch : f44
Commit : 58396d1933dc0beefbf3af6ee42c6022b03eb59d
Author : Gabriel Somlo <gsomlo@gmail.com>
Date : 2026-11-20T20:43:47-05:00
Stats : +12/-4 in 3 file(s)
URL : https://src.fedoraproject.org/rpms/iperf/c/58396d1933dc0beefbf3af6ee42c6022b03eb59d?branch=f44
Log:
update to 2.2.2
---
diff --git a/.gitignore b/.gitignore
index 8b71da4..bc5411b 100644
--- a/.gitignore
+++ b/.gitignore
@@ -17,3 +17,4 @@ iperf-2.0.5.tar.gz
/iperf-2.1.9.tar.gz
/iperf-2.2.0.tar.gz
/iperf-2.2.1.tar.gz
+/iperf-2.2.2.tar.gz
diff --git a/iperf.spec b/iperf.spec
index 3ab61cc..f601f88 100644
--- a/iperf.spec
+++ b/iperf.spec
@@ -1,8 +1,8 @@
#%%global alphatag rc
Name: iperf
-Version: 2.2.1
-Release: 4%{?alphatag:.%{alphatag}}%{?dist}
+Version: 2.2.2
+Release: 5%{?alphatag:.%{alphatag}}%{?dist}
Summary: Measurement tool for TCP/UDP bandwidth performance
License: BSD-3-Clause
URL: http://sourceforge.net/projects/iperf2
@@ -20,7 +20,8 @@ jitter, datagram loss.
%build
%configure
-%{__make} %{?_smp_mflags}
+%make_build CFLAGS="%{optflags}" CXXFLAGS="%{optflags}" \
+ LDFLAGS="%{?__global_ldflags}" %{?_smp_mflags}
%install
%{__rm} -rf %{buildroot}
@@ -32,6 +33,12 @@ jitter, datagram loss.
%{_mandir}/man*/*
%changelog
+* Fri Nov 20 2026 Gabriel Somlo <gsomlo@gmail.com> - 2.2.2-1
+- update to 2.2.2 (#2572680)
+
+* Thu Jul 16 2026 Fedora Release Engineering <releng@fedoraproject.org> - 2.2.1-5
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_45_Mass_Rebuild
+
* Fri Jan 16 2026 Fedora Release Engineering <releng@fedoraproject.org> - 2.2.1-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_44_Mass_Rebuild
diff --git a/sources b/sources
index 6fcf6cf..2bb9031 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (iperf-2.2.1.tar.gz) = 07a08afe647e87939e05c9cd55601ca1227c91f44ef32fdf305a0e15e524d1de29d38e9a3f66253d7308585224e54db395d7dec654d31eea746f45c6947ebc2a
+SHA512 (iperf-2.2.2.tar.gz) = 15c02e7ff59150d31a17e50bc711e8d4f4161cc755db594e28dce5bb597bbf39e0db4fb3b14d5ed13dbd7aeaf443504f9391392bb2ed3d5f8fa3d297f9c880f8
next reply other threads:[~2026-11-21 1:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-21 1:43 Gabriel Somlo [this message]
2026-11-21 2:10 [rpms/iperf] f44: update to 2.2.2 Gabriel Somlo
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=179522543334.1.4056042662899404369.rpms-iperf-58396d1933dc@fedoraproject.org \
--to=gsomlo@gmail.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