public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Fedora Release Engineering <releng@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [rpms/uperf] epel10: - Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
Date: Thu, 10 Sep 2026 15:17:59 GMT [thread overview]
Message-ID: <178905347949.1.11954431907381662382.rpms-uperf-953984171f09@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/uperf
Branch : epel10
Commit : 953984171f09f5cf07de7f673a72d6a2c5a00cb5
Author : Fedora Release Engineering <releng@fedoraproject.org>
Date : 2019-02-03T10:53:45+00:00
Stats : +4/-1 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/uperf/c/953984171f09f5cf07de7f673a72d6a2c5a00cb5?branch=epel10
Log:
- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
Signed-off-by: Fedora Release Engineering <releng@fedoraproject.org>
---
diff --git a/uperf.spec b/uperf.spec
index cea5f3c..29cbb91 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.5
-Release: 6%{?dist}
+Release: 7%{?dist}
License: GPLv3
URL: http://www.uperf.org/
Source0: http://downloads.sourceforge.net/uperf/uperf-%{version}.tar.gz
@@ -42,6 +42,9 @@ rm -rf %{buildroot}%{_datadir}/*.xml %{buildroot}%{_datadir}/doc
%{_datadir}/uperf
%changelog
+* Sun Feb 03 2019 Fedora Release Engineering <releng@fedoraproject.org> - 1.0.5-7
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
+
* Sat Jul 14 2018 Fedora Release Engineering <releng@fedoraproject.org> - 1.0.5-6
- Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild
reply other threads:[~2026-09-10 15:17 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=178905347949.1.11954431907381662382.rpms-uperf-953984171f09@fedoraproject.org \
--to=releng@fedoraproject.org \
--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