public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Benjamin A. Beasley <code@musicinmybrain.net>
To: git-commits@fedoraproject.org
Subject: [rpms/abseil-cpp] rawhide: Add an .rpmlintrc file
Date: Wed, 09 Sep 2026 17:13:31 GMT	[thread overview]
Message-ID: <178897401131.1.18098077578032065941.rpms-abseil-cpp-686d1f487702@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/abseil-cpp
            Branch : rawhide
            Commit : 686d1f4877026c91e7346a82b39f9b7f4740def9
            Author : Benjamin A. Beasley <code@musicinmybrain.net>
            Date   : 2026-09-09T13:07:15+01:00
            Stats  : +8/-0 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/abseil-cpp/c/686d1f4877026c91e7346a82b39f9b7f4740def9?branch=rawhide

            Log:
            Add an .rpmlintrc file

[skip changelog]

---
diff --git a/abseil-cpp.rpmlintrc b/abseil-cpp.rpmlintrc
new file mode 100644
index 0000000..39cb486
--- /dev/null
+++ b/abseil-cpp.rpmlintrc
@@ -0,0 +1,8 @@
+# There really is no documentation specific to the -devel or -testing
+# subpackages or to the mingw subpackages.
+addFilter(r"^abseil-cpp-(devel|testing)\.[.\S]+: W: no-documentation$")
+addFilter(r"^mingw(32|64)-abseil-cpp\.[.\S]+: W: no-documentation$")
+# Really, rpmlint just doesn’t understand MinGW very well.
+addFilter(r"^mingw(32|64)-abseil-cpp-debuginfo\.noarch: W: only-non-binary-in-usr-lib$")
+addFilter(r"^mingw(32|64)-abseil-cpp.noarch: W: devel-file-in-non-devel-package /")
+addFilter(r"^mingw(32|64)-abseil-cpp.noarch: E: arch-independent-package-contains-binary-or-object /")

                 reply	other threads:[~2026-09-09 17:13 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=178897401131.1.18098077578032065941.rpms-abseil-cpp-686d1f487702@fedoraproject.org \
    --to=code@musicinmybrain.net \
    --cc=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