Blame SOURCES/0009-Change-n-flag-to-nn-in-TESTonce.patch

1f5cfb
From 04e23aa3f91ff137237daf68f02e7b3c0c1a9168 Mon Sep 17 00:00:00 2001
1f5cfb
From: rpm-build <rpm-build>
1f5cfb
Date: Tue, 11 Apr 2017 09:19:48 +0200
1f5cfb
Subject: [PATCH 09/13] Change -n flag to -nn in TESTonce
1f5cfb
1f5cfb
We need to change this because we have a different meaning of -n
1f5cfb
flag than upstream does. We use -nn in those cases.
1f5cfb
---
1f5cfb
 tests/TESTonce | 2 +-
1f5cfb
 1 file changed, 1 insertion(+), 1 deletion(-)
1f5cfb
1f5cfb
diff --git a/tests/TESTonce b/tests/TESTonce
1f5cfb
index 7026624..e348701 100755
1f5cfb
--- a/tests/TESTonce
1f5cfb
+++ b/tests/TESTonce
1f5cfb
@@ -21,7 +21,7 @@ if ($^O eq 'MSWin32') {
1f5cfb
 else {
1f5cfb
     # we used to do this as a nice pipeline, but the problem is that $r fails to
1f5cfb
     # to be set properly if the tcpdump core dumps.
1f5cfb
-    $r = system "../tcpdump 2>/dev/null -n -t -r $input $options >NEW/$output";
1f5cfb
+    $r = system "../tcpdump 2>/dev/null -nn -t -r $input $options >NEW/$output";
1f5cfb
     if($r != 0) {
1f5cfb
         # this means tcpdump failed.
1f5cfb
         open(OUTPUT, ">>"."NEW/$output") || die "fail to open $output\n";
1f5cfb
-- 
1f5cfb
2.13.5
1f5cfb