public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Filipe Rosset <filiperosset@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [rpms/xev] rawhide: added gcc as BuildRequires
Date: Mon, 13 Jul 2026 20:57:46 GMT [thread overview]
Message-ID: <178397626607.1.8538436327609031788.rpms-xev-c9e920232320@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/xev
Branch : rawhide
Commit : c9e920232320ee53ed5985eaef87a5981b872bc5
Author : Filipe Rosset <filiperosset@fedoraproject.org>
Date : 2026-07-13T17:57:35-03:00
Stats : +1/-0 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/xev/c/c9e920232320ee53ed5985eaef87a5981b872bc5?branch=rawhide
Log:
added gcc as BuildRequires
Signed-off-by: Filipe Rosset <filiperosset@fedoraproject.org>
---
diff --git a/xev.spec b/xev.spec
index 6b2d550..2c59c23 100644
--- a/xev.spec
+++ b/xev.spec
@@ -9,6 +9,7 @@ Source0: https://www.x.org/pub/individual/app/%{name}-%{version}.tar.xz
Source1: https://www.x.org/pub/individual/app/%{name}-%{version}.tar.xz.sig
Source2: gpgkey-3AB285232C46AE43D8E192F4DAB0F78EA6E7E2D2.gpg
+BuildRequires: gcc
BuildRequires: gpgverify
BuildRequires: meson
BuildRequires: pkgconfig(x11)
reply other threads:[~2026-07-13 20:57 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=178397626607.1.8538436327609031788.rpms-xev-c9e920232320@fedoraproject.org \
--to=filiperosset@fedoraproject.org \
--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