public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Terje Rosten <terje.rosten@ntnu.no>
To: git-commits@fedoraproject.org
Subject: [rpms/uperf] epel10.2: Fix build deps after openssl changes
Date: Thu, 10 Sep 2026 15:19:35 GMT [thread overview]
Message-ID: <178905357522.1.4331709834766696937.rpms-uperf-620e46bb971f@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/uperf
Branch : epel10.2
Commit : 620e46bb971fe9831fc8a35d5f4448c3cf5e0cee
Author : Terje Rosten <terje.rosten@ntnu.no>
Date : 2024-07-07T14:49:14+02:00
Stats : +7/-1 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/uperf/c/620e46bb971fe9831fc8a35d5f4448c3cf5e0cee?branch=epel10.2
Log:
Fix build deps after openssl changes
---
diff --git a/uperf.spec b/uperf.spec
index b51b0e7..63c5be6 100644
--- a/uperf.spec
+++ b/uperf.spec
@@ -1,7 +1,7 @@
Summary: Network performance tool with modelling and replay support
Name: uperf
Version: 1.0.8
-Release: 2%{?dist}
+Release: 3%{?dist}
License: GPLv3
URL: http://www.uperf.org/
Source0: https://github.com/uperf/uperf/archive/v%{version}.tar.gz
@@ -11,6 +11,9 @@ BuildRequires: gcc
BuildRequires: lksctp-tools-devel
BuildRequires: make
BuildRequires: openssl-devel
+%if 0%{?fedora} > 40
+BuildRequires: openssl-devel-engine
+%endif
%description
Network performance tool that supports modelling and replay of various
networking patterns.
@@ -45,6 +48,9 @@ rm -rf %{buildroot}%{_datadir}/*.xml %{buildroot}%{_datadir}/doc
%{_datadir}/uperf
%changelog
+* Sun Jul 07 2024 Terje Rosten <terje.rosten@ntnu.no> - 1.0.8-3
+- Fix build deps after openssl changes
+
* Sat Jan 27 2024 Fedora Release Engineering <releng@fedoraproject.org> - 1.0.8-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild
reply other threads:[~2026-09-10 15:19 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=178905357522.1.4331709834766696937.rpms-uperf-620e46bb971f@fedoraproject.org \
--to=terje.rosten@ntnu.no \
--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