From: motorto <motorto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] xkbcomp: update to 1.4.6;adopt.
Date: Sun, 15 Jan 2023 16:39:49 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41666@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]
There is a new pull request by motorto against master on the void-packages repository
https://github.com/motorto/void-packages xkbcomp-1.4.6
https://github.com/void-linux/void-packages/pull/41666
xkbcomp: update to 1.4.6;adopt.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
```
SUMMARY
pkg host target cross result
xkbcomp x86_64 x86_64 n OK
xkbcomp x86_64-musl x86_64-musl n OK
xkbcomp i686 i686 n OK
xkbcomp x86_64-musl aarch64-musl y OK
xkbcomp x86_64-musl aarch64 y OK
xkbcomp x86_64-musl armv7l-musl y OK
xkbcomp x86_64-musl armv7l y OK
xkbcomp x86_64-musl armv6l-musl y OK
xkbcomp x86_64-musl armv6l y OK
```
A patch file from https://github.com/void-linux/void-packages/pull/41666.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-xkbcomp-1.4.6-41666.patch --]
[-- Type: text/x-diff, Size: 1202 bytes --]
From dbd9aae7d2476c65abbb701efa4e941f26a0dc79 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20Cerqueira?= <acerqueira021@gmail.com>
Date: Sun, 15 Jan 2023 15:33:23 +0000
Subject: [PATCH] xkbcomp: update to 1.4.6;adopt.
---
srcpkgs/xkbcomp/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/xkbcomp/template b/srcpkgs/xkbcomp/template
index 29d1760dff72..629a306822c4 100644
--- a/srcpkgs/xkbcomp/template
+++ b/srcpkgs/xkbcomp/template
@@ -1,16 +1,16 @@
# Template file for 'xkbcomp'
pkgname=xkbcomp
-version=1.4.5
+version=1.4.6
revision=1
build_style=gnu-configure
hostmakedepends="pkg-config bison"
makedepends="libX11-devel libxkbfile-devel"
short_desc="XKBD keymap compiler"
-maintainer="Orphaned <orphan@voidlinux.org>"
+maintainer="André Cerqueira <acerqueira021@gmail.com>"
license="MIT"
homepage="https://www.x.org/"
-distfiles="${XORG_SITE}/app/${pkgname}-${version}.tar.bz2"
-checksum=6851086c4244b6fd0cc562880d8ff193fb2bbf1e141c73632e10731b31d4b05e
+distfiles="${XORG_SITE}/app/${pkgname}-${version}.tar.xz"
+checksum=fa50d611ef41e034487af7bd8d8c718df53dd18002f591cca16b0384afc58e98
post_install() {
vlicense COPYING LICENSE
next reply other threads:[~2023-01-15 15:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 15:39 motorto [this message]
2023-01-16 8:10 ` [PR REVIEW] " classabbyamp
2023-01-16 8:10 ` classabbyamp
2023-01-16 15:12 ` [PR PATCH] [Updated] " motorto
2023-01-17 11:37 ` motorto
2023-01-17 16:43 ` [PR PATCH] [Merged]: " classabbyamp
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41666@inbox.vuxu.org \
--to=motorto@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).