public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Filipe Rosset <rosset.filipe@gmail.com>
To: git-commits@fedoraproject.org
Subject: [rpms/xmodmap] rawhide: update to 1.0.12 fixes rhbz#2502637
Date: Thu, 23 Jul 2026 01:01:46 GMT [thread overview]
Message-ID: <178476850609.1.12806956855372718252.rpms-xmodmap-a73a5ef91f9f@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/xmodmap
Branch : rawhide
Commit : a73a5ef91f9fc5f71d25ad6fdce3337b9d6eeb82
Author : Filipe Rosset <rosset.filipe@gmail.com>
Date : 2026-07-21T02:09:26-03:00
Stats : +20/-8 in 3 file(s)
URL : https://src.fedoraproject.org/rpms/xmodmap/c/a73a5ef91f9fc5f71d25ad6fdce3337b9d6eeb82?branch=rawhide
Log:
update to 1.0.12 fixes rhbz#2502637
Signed-off-by: Filipe Rosset <rosset.filipe@gmail.com>
---
diff --git a/.gitignore b/.gitignore
index 553374e..1a84018 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1,3 @@
/xmodmap-*.tar.xz
+/xmodmap-1.0.12.tar.xz.sig
+/gpgkey-3AB285232C46AE43D8E192F4DAB0F78EA6E7E2D2.gpg
diff --git a/sources b/sources
index 4089fdd..83529ff 100644
--- a/sources
+++ b/sources
@@ -1 +1,3 @@
-SHA512 (xmodmap-1.0.11.tar.xz) = a78f916f048d2017f079733becc99232c087c360ece61ec6c4fa4b5b130b96a1b10c4ce1b64a15bdcab7ea05de3c7f16035503d5be6f8ce1a7612ce71d558510
+SHA512 (xmodmap-1.0.12.tar.xz) = 2319f1b7eee54d650930c9e16c06e8db5a0c19eaef1902d6196d666bcab8bc288baaea65d3b561e117fc98b918cbcd9c2660c91c556f3fa08e0f57a8f0d38f82
+SHA512 (xmodmap-1.0.12.tar.xz.sig) = 6854ff05eff0e6677224883af580537b587b287703de26481e935e309fe9e159c0a12255244ee920c5fa89eec54751a9093b9d8ee69f2e787ddd73122e8942d7
+SHA512 (gpgkey-3AB285232C46AE43D8E192F4DAB0F78EA6E7E2D2.gpg) = a2b4aef6f48a6d6bab50f72a23295c7be63a3e6880237f52b1983e7cfa8b2798b7e30883e4e3f09dd7b905f0eb2952ba8993f7ea9b0172266337822c9be951c0
diff --git a/xmodmap.spec b/xmodmap.spec
index a62ce8b..c4ff3f4 100644
--- a/xmodmap.spec
+++ b/xmodmap.spec
@@ -1,25 +1,29 @@
Name: xmodmap
-Version: 1.0.11
+Version: 1.0.12
Release: %autorelease
Summary: Edit and display the X11 core keyboard map
License: MIT AND MIT-open-group
URL: https://www.x.org
-Source0: https://www.x.org/pub/individual/app/%{name}-%{version}.tar.xz
-
-BuildRequires: automake libtool
-BuildRequires: gcc make
+Source0: https://xorg.freedesktop.org/archive/individual/app/%{name}-%{version}.tar.xz
+Source1: https://xorg.freedesktop.org/archive/individual/app/%{name}-%{version}.tar.xz.sig
+Source2: gpgkey-3AB285232C46AE43D8E192F4DAB0F78EA6E7E2D2.gpg
+
+BuildRequires: automake
+BuildRequires: gcc
+BuildRequires: gnupg2
+BuildRequires: libtool
+BuildRequires: make
BuildRequires: pkgconfig(x11)
BuildRequires: pkgconfig(xorg-macros) >= 1.8
-Obsoletes: xorg-x11-server-utils < 7.7-40
-
%description
The xmodmap program is used to edit and display the keyboard modifier
map and keymap table that are used by client applications to convert
event keycodes into keysyms.
%prep
+%{gpgverify} --keyring=%{SOURCE2} --signature=%{SOURCE1} --data=%{SOURCE0}
%autosetup
%build
@@ -30,6 +34,9 @@ autoreconf -v --install
%install
%make_install
+%check
+%make_build check
+
%files
%license COPYING
%{_bindir}/%{name}
@@ -37,3 +44,4 @@ autoreconf -v --install
%changelog
%autochangelog
+
reply other threads:[~2026-07-23 1:01 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=178476850609.1.12806956855372718252.rpms-xmodmap-a73a5ef91f9f@fedoraproject.org \
--to=rosset.filipe@gmail.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