public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Vit Mojzis <vmojzis@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/setools] f44: Drop unused BuildRequires
Date: Fri, 31 Jul 2026 16:47:38 GMT	[thread overview]
Message-ID: <178551645874.1.7054196239922576081.rpms-setools-f2b940a99d90@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/setools
            Branch : f44
            Commit : f2b940a99d905151710222115f410d8cb793f1d7
            Author : Vit Mojzis <vmojzis@redhat.com>
            Date   : 2026-07-31T18:46:22+02:00
            Stats  : +1/-3 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/setools/c/f2b940a99d905151710222115f410d8cb793f1d7?branch=f44

            Log:
            Drop unused BuildRequires

Bison, flex and swig appear to be left over from an older build system
(switched to Cython in setools-4.2.0).

libsepol has only been linked dynamically since
e6ea477: Convert to direct sepol structure access

Reported by Marián Konček <mkoncek@redhat.com>
https://mkoncek.fedorapeople.org/unbreq.html

Fixes: SELINUX-6551

---
diff --git a/setools.spec b/setools.spec
index bee9a0d..054e49d 100644
--- a/setools.spec
+++ b/setools.spec
@@ -18,10 +18,8 @@ Patch:          https://github.com/SELinuxProject/setools/pull/156.patch
 Patch:          https://github.com/SELinuxProject/setools/pull/157.patch
 
 Obsoletes:      setools < 4.0.0, setools-devel < 4.0.0
-BuildRequires:  flex,  bison
 BuildRequires:  glibc-devel, gcc, git-core
-BuildRequires:  libsepol-devel >= %{sepol_ver}, libsepol-static >= %{sepol_ver}
-BuildRequires:  swig
+BuildRequires:  libsepol-devel >= %{sepol_ver}
 BuildRequires:  python3-Cython
 BuildRequires:  python3-devel
 BuildRequires:  libselinux-devel

                 reply	other threads:[~2026-07-31 16:47 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=178551645874.1.7054196239922576081.rpms-setools-f2b940a99d90@fedoraproject.org \
    --to=vmojzis@redhat.com \
    --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