public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Michal Schorm <mschorm@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/cinnamon-control-center] rawhide: Add missing BuildRequires: 'pkgconfig(gudev-1.0) >= 232'
Date: Sat, 25 Jul 2026 23:20:12 GMT [thread overview]
Message-ID: <178502161229.1.2699024365807086448.rpms-cinnamon-control-center-c624ad7f1e95@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/cinnamon-control-center
Branch : rawhide
Commit : c624ad7f1e95c9cce8d9f2fb3a38ffdd18ac1a87
Author : Michal Schorm <mschorm@redhat.com>
Date : 2026-07-25T15:55:32+02:00
Stats : +1/-0 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/cinnamon-control-center/c/c624ad7f1e95c9cce8d9f2fb3a38ffdd18ac1a87?branch=rawhide
Log:
Add missing BuildRequires: 'pkgconfig(gudev-1.0) >= 232'
'meson.build' requires 'dependency('gudev-1.0', version: '>= 232')' but
the spec had no corresponding BuildRequires. The build succeeds only
because gudev is pulled in transitively.
Upstream: https://github.com/linuxmint/cinnamon-control-center/blob/6.7.2-unstable/meson.build#L31
Debian: https://github.com/linuxmint/cinnamon-control-center/blob/6.7.2-unstable/debian/control#L21
Linux Mint's 'debian/control' lists 'libgudev-1.0-dev (>= 232)' with the
same version constraint.
Co-Authored-By: Claude AI <noreply@anthropic.com>
---
diff --git a/cinnamon-control-center.spec b/cinnamon-control-center.spec
index d5ba778..d8f5ffc 100644
--- a/cinnamon-control-center.spec
+++ b/cinnamon-control-center.spec
@@ -39,6 +39,7 @@ BuildRequires: pkgconfig(gio-unix-2.0) >= 2.44.0
BuildRequires: pkgconfig(libnotify) >= 0.7.3
BuildRequires: pkgconfig(x11)
BuildRequires: pkgconfig(polkit-gobject-1) >= 0.103
+BuildRequires: pkgconfig(gudev-1.0) >= 232
BuildRequires: pkgconfig(upower-glib) >= 0.99.8
BuildRequires: pkgconfig(xproto)
BuildRequires: pkgconfig(libnm) >= 1.2.0
reply other threads:[~2026-07-25 23:20 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=178502161229.1.2699024365807086448.rpms-cinnamon-control-center-c624ad7f1e95@fedoraproject.org \
--to=mschorm@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