public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/uperf] epel10: 1.0.4
Date: Thu, 10 Sep 2026 15:17:52 GMT	[thread overview]
Message-ID: <178905347234.1.10789933530291808539.rpms-uperf-bc4abcf59c35@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/uperf
Branch : epel10
Commit : bc4abcf59c3511cf8b3b743534f4e15edfe90cba
Author : Terje R�sten <terje.rosten@ntnu.no>
Date   : 2012-12-03T14:00:13+01:00
Stats  : +24/-6 in 4 file(s)
URL    : https://src.fedoraproject.org/rpms/uperf/c/bc4abcf59c3511cf8b3b743534f4e15edfe90cba?branch=epel10

Log:
1.0.4

---
diff --git a/.gitignore b/.gitignore
index b83c41c..2968649 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1,2 @@
 uperf-1.0.3-beta.tar.gz
+/uperf-1.0.4.tar.bz2

diff --git a/sources b/sources
index ea2f620..07128e2 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-428035a33729a877f1ecd4ced8911a6f  uperf-1.0.3-beta.tar.gz
+ccbc52686451c14c5532d7ccd67b699c  uperf-1.0.4.tar.bz2

diff --git a/uperf-1.0.4-dso.patch b/uperf-1.0.4-dso.patch
new file mode 100644
index 0000000..b13182c
--- /dev/null
+++ b/uperf-1.0.4-dso.patch
@@ -0,0 +1,13 @@
+diff --git a/configure b/configure
+index e94aded..aa79dfd 100755
+--- a/configure
++++ b/configure
+@@ -3542,7 +3542,7 @@ _ACEOF
+ 		sctp_default="yes"
+ 		ssl_default="no"
+ 		cpc_default="no"
+-		UPERF_LIBS="$UPERF_LIBS -lrt -lm"
++		UPERF_LIBS="$UPERF_LIBS -lpthread -lrt -lm"
+ 		CFLAGS="-D_GNU_SOURCE $CFLAGS"
+ 		SCTP_LIBS="-lsctp"
+ 		SCTP_LIBNAME="sctp"

diff --git a/uperf.spec b/uperf.spec
index c8d00d0..e46045e 100644
--- a/uperf.spec
+++ b/uperf.spec
@@ -1,11 +1,12 @@
 Summary:        Network performance tool with modelling and replay support
 Name:           uperf
-Version:        1.0.3
-Release:        0.6.beta%{?dist}
+Version:        1.0.4
+Release:        1%{?dist}
 License:        GPLv3
 Group:          Applications/Internet
 URL:            http://www.uperf.org/
-Source0:        http://downloads.sourceforge.net/uperf/uperf-%{version}-beta.tar.gz
+Source0:        http://downloads.sourceforge.net/uperf/uperf-%{version}.tar.bz2
+Patch0:         uperf-1.0.4-dso.patch
 BuildRequires:  lksctp-tools-devel openssl-devel
 BuildRoot:      %{_tmppath}/%{name}-%{version}-%{release}-root
 %description
@@ -13,7 +14,8 @@ Network performance tool that supports modelling and replay of various
 networking patterns.
 
 %prep
-%setup -q -n %{name}-%{version}-beta
+%setup -q -n %{name}-%{version}
+%patch0 -p1
 find src -type f -print0 | xargs --null chmod 0644
 find workloads -type f -print0 | xargs --null chmod 0644
 chmod 0644 AUTHORS ChangeLog COPYING README
@@ -46,6 +48,9 @@ chmod 0644 AUTHORS ChangeLog COPYING README
 %{_datadir}/%{name}
 
 %changelog
+* Mon Dec 03 2012 Terje Rosten <terje.rosten@ntnu.no> - 1.0.4-1
+- 1.0.4
+
 * Sun Jul 22 2012 Fedora Release Engineering <rel-eng@lists.fedoraproject.org> - 1.0.3-0.6.beta
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_18_Mass_Rebuild
 
@@ -63,4 +68,3 @@ chmod 0644 AUTHORS ChangeLog COPYING README
 
 * Mon Feb  1 2010 Terje Rosten <terje.rosten@ntnu.no> - 1.0.3-0.1.beta
 - initial build
-

                 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=178905347234.1.10789933530291808539.rpms-uperf-bc4abcf59c35@fedoraproject.org \
    --to=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