public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/hping3] rawhide: Moderize the spec file
Date: Fri, 10 Jul 2026 19:57:14 GMT	[thread overview]
Message-ID: <178371343498.1.17268178946487189948.rpms-hping3-9fa717bd88e6@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/hping3
Branch : rawhide
Commit : 9fa717bd88e697df426e3a17cb1f3c652415be03
Author : Petr Písař <ppisar@redhat.com>
Date   : 2026-07-09T16:59:51+02:00
Stats  : +7/-4 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/hping3/c/9fa717bd88e697df426e3a17cb1f3c652415be03?branch=rawhide

Log:
Moderize the spec file

---
diff --git a/hping3.spec b/hping3.spec
index 2aec06a..0ea23c3 100644
--- a/hping3.spec
+++ b/hping3.spec
@@ -16,7 +16,8 @@ Patch4: hping3-man.patch
 Patch5: hping3-20051105-typo.patch
 Patch6: hping3-common.patch
 Patch7: hping3-Port-to-TCL-9.patch
-BuildRequires:  gcc
+BuildRequires: coreutils
+BuildRequires: gcc
 BuildRequires: libpcap-devel, tcl-devel
 BuildRequires: make
 Obsoletes: hping2
@@ -43,7 +44,7 @@ Since version 3, hping implements scripting capabilties
 
 %build
 %configure --force-libpcap
-make %{?_smp_mflags}
+%{make_build}
 
 %install
 rm -rf $RPM_BUILD_ROOT
@@ -60,8 +61,10 @@ ln -sf hping3 $RPM_BUILD_ROOT%{_sbindir}/hping2
 %doc COPYING *BUGS CHANGES README TODO docs/AS-BACKDOOR docs/HPING2-HOWTO.txt
 %doc docs/HPING2-IS-OPEN docs/MORE-FUN-WITH-IPID docs/SPOOFED_SCAN.txt
 %doc docs/HPING3.txt
-%attr(755,root,root) %{_sbindir}/*
-%{_mandir}/man8/*
+%{_sbindir}/hping
+%{_sbindir}/hping2
+%attr(755,root,root) %{_sbindir}/hping3
+%{_mandir}/man8/hping3.*
 
 %changelog
 * Thu Jul 09 2026 Petr Pisar <ppisar@redhat.com> - 0.0.20051105-50

                 reply	other threads:[~2026-07-10 19:57 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=178371343498.1.17268178946487189948.rpms-hping3-9fa717bd88e6@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