From: Bnyro <Bnyro@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] xf86-input-libinput: update to 1.3.0.
Date: Mon, 17 Jul 2023 09:16:38 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45075@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 588 bytes --]
There is a new pull request by Bnyro against master on the void-packages repository
https://github.com/Bnyro/void-packages xf86-input-libinput
https://github.com/void-linux/void-packages/pull/45075
xf86-input-libinput: update to 1.3.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
A patch file from https://github.com/void-linux/void-packages/pull/45075.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-xf86-input-libinput-45075.patch --]
[-- Type: text/x-diff, Size: 1131 bytes --]
From 265e64013b574a635e5999f15740a4978307c9a1 Mon Sep 17 00:00:00 2001
From: Bnyro <bnyro@tutanota.com>
Date: Mon, 17 Jul 2023 08:59:24 +0200
Subject: [PATCH] xf86-input-libinput: update to 1.3.0.
---
srcpkgs/xf86-input-libinput/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/xf86-input-libinput/template b/srcpkgs/xf86-input-libinput/template
index 3f507a5ebd97..697f2b16f52c 100644
--- a/srcpkgs/xf86-input-libinput/template
+++ b/srcpkgs/xf86-input-libinput/template
@@ -1,6 +1,6 @@
# Template file for 'xf86-input-libinput'
pkgname=xf86-input-libinput
-version=1.2.1
+version=1.3.0
revision=1
build_style=gnu-configure
hostmakedepends="pkg-config"
@@ -13,7 +13,7 @@ homepage="https://xorg.freedesktop.org/"
# no official changelog
#changelog="https://gitlab.freedesktop.org/xorg/driver/xf86-input-libinput/-/commits/master/"
distfiles="${XORG_SITE}/driver/${pkgname}-${version}.tar.xz"
-checksum=8151db5b9ddb317c0ce92dcb62da9a8db5079e5b8a95b60abc854da21e7e971b
+checksum=1446ba20a22bc968b5a4a0b4dbc3b8e037c50d9c59ac75fa3f7fc506c58c1abb
lib32disabled=yes
post_install() {
next reply other threads:[~2023-07-17 7:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 7:16 Bnyro [this message]
2023-07-22 23:31 ` [PR PATCH] [Merged]: " Piraty
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-45075@inbox.vuxu.org \
--to=bnyro@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).