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

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