From 14e354e0a1a4187f2e315ba44daf1968bc666c43 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?V=C3=A1clav=20Kadl=C4=8D=C3=ADk?= <vkadlcik@redhat.com>
Date: Tue, 10 Sep 2024 11:59:25 +0200
Subject: [PATCH] Avoid some rpminspect failures in gating

- badfuncs - skip false positives
- specname and runpath: adapt to how is the GTS collection designed
---
 rpminspect.yaml | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)
 create mode 100644 rpminspect.yaml

diff --git a/rpminspect.yaml b/rpminspect.yaml
new file mode 100644
index 0000000..c250da0
--- /dev/null
+++ b/rpminspect.yaml
@@ -0,0 +1,22 @@
+badfuncs:
+    # GCC doesn't use the "forbidden" functions as such. Just some of its
+    # sanitizers can instrument those functions which leads to false
+    # positives in the badfuncs test.
+    ignore:
+      - /usr/lib*/libasan.so.*.*.*
+      - /usr/lib*/libtsan.so.*.*.*
+
+specname:
+    # In GCC toolsets builds, the spec file name and the package are not
+    # exactly the same, the package is prefixed with gcc-toolset-NN-.
+    # Let's ignore the prefix.
+    match: suffix
+    primary: filename
+
+runpath:
+    # Although gcc-toolset sanitizers link gcc-toolset libraries from
+    # /opt/..., they themselves are placed in /usr. The runpath test
+    # doesn't like this difference. Explicitly allow it.
+    allowed_paths:
+      - /opt/rh/gcc-toolset-14/root/usr/lib64
+      - /opt/rh/gcc-toolset-14/root/usr/lib