use num_prime for factorisation to fix gnu test

util/build-gnu.sh

@@ -221,7 +221,7 @@ grep -rlE '/usr/local/bin/\s?/usr/local/bin' init.cfg tests/* | xargs -r sed -Ei
 # we should not regress our project just to match what GNU is going.
 # So, do some changes on the fly
 
-patch -N -r - -d "$path_GNU" -p 1 -i "`realpath \"$path_UUTILS/util/gnu-patches/tests_env_env-S.pl.patch\"`" || true
+eval cat "$path_UUTILS/util/gnu-patches/*.patch" | patch -N -r - -d "$path_GNU" -p 1 -i - || true
 
 sed -i -e "s|rm: cannot remove 'e/slink'|rm: cannot remove 'e'|g" tests/rm/fail-eacces.sh
 

util/gnu-patches/tests_factor_factor.pl.patch

@@ -0,0 +1,21 @@
+diff --git a/tests/factor/factor.pl b/tests/factor/factor.pl
+index 6e612e418..f19c06ca0 100755
+--- a/tests/factor/factor.pl
++++ b/tests/factor/factor.pl
+@@ -61,12 +61,13 @@ my @Tests =
+       # Map newer glibc diagnostic to expected.
+       # Also map OpenBSD 5.1's "unknown option" to expected "invalid option".
+       {ERR_SUBST => q!s/'1'/1/;s/unknown/invalid/!},
+-      {ERR => "$prog: invalid option -- 1\n"
+-       . "Try '$prog --help' for more information.\n"},
++      {ERR => "error: unexpected argument '-1' found\n\n"
++        . "  tip: to pass '-1' as a value, use '-- -1'\n\n"
++        . "Usage: factor [OPTION]... [NUMBER]...\n"},
+       {EXIT => 1}],
+      ['cont', 'a 4',
+       {OUT => "4: 2 2\n"},
+-      {ERR => "$prog: 'a' is not a valid positive integer\n"},
++      {ERR => "$prog: warning: a: invalid digit found in string\n"},
+       {EXIT => 1}],
+      ['bug-2012-a', '465658903', {OUT => '15259 30517'}],
+      ['bug-2012-b', '2242724851', {OUT => '33487 66973'}],