From 3ebd62205f6f06e9aef831bc23a505d27a7e8e3c Mon Sep 17 00:00:00 2001 From: Florian Festi Date: Fri, 22 Jan 2021 16:09:58 +0100 Subject: [PATCH] Prevent patch asking questions during build Builds should always run unattended and never require user interactions. We also don't want unser input to affect the result. Without any options patch will ask for files to patch or whether it should reverse pachtes if they could be applied then. As -t aka --batch does reverse patches and skips patches with wrong version for the Prereq: line it is not suited for rpmbuild. We rather want the build to fail than silently drop (possibly security relevant) patches. We would prefer patch to error out when ever the patch looks not quite matching but -f aka --force is the option available closest to that. See man patch for details Resolves: #978 --- macros.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/macros.in b/macros.in index c7664d800f..ebeeca30be 100644 --- a/macros.in +++ b/macros.in @@ -389,7 +389,7 @@ package or when debugging this package.\ # Default patch flags #%_default_patch_flags -s -%_default_patch_flags --no-backup-if-mismatch +%_default_patch_flags --no-backup-if-mismatch -f #============================================================================== # ---- Build configuration macros.