public inbox for dtrace@lists.linux.dev
 help / color / mirror / Atom feed
From: Eugene Loh <eugene.loh@oracle.com>
To: Kris Van Hees <kris.van.hees@oracle.com>,
	dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [DTrace-devel] [PATCH] spec: add testsuite dependency for perl-Net-Ping
Date: Wed, 19 Nov 2025 18:03:30 -0500	[thread overview]
Message-ID: <075f124a-f2ae-b4f1-6040-eadea0125399@oracle.com> (raw)
In-Reply-To: <BY5PR10MB3987DF7E2FC1582D1AAE045BC2D7A@BY5PR10MB3987.namprd10.prod.outlook.com>

Reviewed-by: Eugene Loh <eugene.loh@oracle.com>

On 11/19/25 16:14, Kris Van Hees via DTrace-devel wrote:
> Commit 1e689f55 ("Make a start at reviving the ip tests.") added the
> perlping.pl script, but did not ensure that a dependency was added
> for perl-Net-Ping that the script depends on.
>
> Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>
> ---
>   dtrace.spec | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/dtrace.spec b/dtrace.spec
> index 0905763f..4b20dc40 100644
> --- a/dtrace.spec
> +++ b/dtrace.spec
> @@ -112,7 +112,7 @@ Summary:      DTrace testsuite.
>   Requires:     make glibc-devel(%{__isa_name}-64) libgcc(%{__isa_name}-64)
>   Requires:     dtrace-headers >= 2.0.0 module-init-tools
>   Requires:     %{name}-devel = %{version}-%{release} perl gcc java
> -Requires:     java-devel perl-IO-Socket-IP xfsprogs
> +Requires:     java-devel perl-IO-Socket-IP perl-Net-Ping xfsprogs
>   Requires:     exportfs vim-minimal %{name}%{?_isa} = %{version}-%{release}
>   Requires:     coreutils wireshark %{glibc32}
>   Requires:     perf time bc nfs-utils

      reply	other threads:[~2025-11-19 23:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19 21:14 [PATCH] spec: add testsuite dependency for perl-Net-Ping Kris Van Hees
2025-11-19 23:03 ` Eugene Loh [this message]

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=075f124a-f2ae-b4f1-6040-eadea0125399@oracle.com \
    --to=eugene.loh@oracle.com \
    --cc=dtrace-devel@oss.oracle.com \
    --cc=dtrace@lists.linux.dev \
    --cc=kris.van.hees@oracle.com \
    /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