public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/gcc] rhel-f41-base: Make rpminspect in CI less loud
Date: Mon, 29 Jun 2026 12:30:49 GMT	[thread overview]
Message-ID: <178273624904.1.3161400083364614386.rpms-gcc-d35dbeca6690@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/gcc
            Branch : rhel-f41-base
            Commit : d35dbeca6690f70744ed3822ffdd684c63f11c02
            Author : Václav Kadlčík <vkadlcik@redhat.com>
            Date   : 2025-08-13T07:54:14+02:00
            Stats  : +37/-0 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/gcc/c/d35dbeca6690f70744ed3822ffdd684c63f11c02?branch=rhel-f41-base

            Log:
            Make rpminspect in CI less loud

Configure exceptions for  rpminspect
(fedora-ci.koji-build.rpminspect.static-analysis in Fedora CI) so the
reports don't overwhelm us with failures (be it false ones or genuine
ones that we are OK with).

---
diff --git a/rpminspect.yaml b/rpminspect.yaml
new file mode 100644
index 0000000..f31bc02
--- /dev/null
+++ b/rpminspect.yaml
@@ -0,0 +1,37 @@
+inspections:
+    # GCC subpackages are inter-dependent but without requesting an explicit
+    # version - which rpmdeps dislikes and creates huge reports. We can't fix
+    # it easily and it's not a practical problem anyway. Unfortunately we
+    # can't tell rpmdeps to ignore just that particular warning. Switching off
+    # the rpmdeps checks looks like a lesser evil.
+    rpmdeps: off
+
+badfuncs:
+    # GCC doesn't use the so called bad functions "much". If they appear then
+    # - it is instrumenting them in sanitizers
+    # - in languages that don't move further downstream.
+    # We are OK with that.
+    ignore:
+      - /usr/lib*/libasan.so.*.*.*
+      - /usr/lib*/libtsan.so.*.*.*
+      - /usr/lib*/libgnat-*.so
+      - /usr/lib*/libgphobos.so.*.*.*
+      - /usr/lib*/libm2iso.so.*.*.*
+      - /usr/lib*/libm2pim.so.*.*.*
+
+pathmigration:
+    # Incomplete UsrMove, known but not planned at the moment
+    ignore:
+      - /lib*/libgcc_s-*.so.*
+      - /lib*/libgcc_s.so.*
+
+debuginfo:
+    # Skip the Go binaries, they ship unstripped
+    ignore:
+      - /usr/bin/go.gcc
+      - /usr/bin/gofmt.gcc
+      - /usr/lib*/libgo.so.*.*.*
+      - /usr/libexec/gcc/*-redhat-linux/*/buildid
+      - /usr/libexec/gcc/*-redhat-linux/*/cgo
+      - /usr/libexec/gcc/*-redhat-linux/*/test2json
+      - /usr/libexec/gcc/*-redhat-linux/*/vet

                 reply	other threads:[~2026-06-29 12:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178273624904.1.3161400083364614386.rpms-gcc-d35dbeca6690@fedoraproject.org \
    --to=git-commits@fedoraproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox