From: travankor <travankor@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libinput: update to 1.20.0.
Date: Thu, 24 Feb 2022 14:38:07 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35825@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]
There is a new pull request by travankor against master on the void-packages repository
https://github.com/travankor/void-packages libinput
https://github.com/void-linux/void-packages/pull/35825
libinput: update to 1.20.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/35825.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libinput-35825.patch --]
[-- Type: text/x-diff, Size: 1190 bytes --]
From 3e95e355d4c1936cb0f175cf7b762a5947f55e75 Mon Sep 17 00:00:00 2001
From: travankor <travankor@tuta.io>
Date: Thu, 24 Feb 2022 06:37:26 -0700
Subject: [PATCH] libinput: update to 1.20.0.
---
srcpkgs/libinput/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/libinput/template b/srcpkgs/libinput/template
index 118f703d9275..38fe908dbb36 100644
--- a/srcpkgs/libinput/template
+++ b/srcpkgs/libinput/template
@@ -1,6 +1,6 @@
# Template file for 'libinput'
pkgname=libinput
-version=1.19.3
+version=1.20.0
revision=1
build_style=meson
configure_args="-Dtests=false"
@@ -12,8 +12,8 @@ short_desc="Provides handling input devices in Wayland compositors and X"
maintainer="Michal Vasilek <michal@vasilek.cz>"
license="MIT"
homepage="https://www.freedesktop.org/wiki/Software/libinput"
-distfiles="${FREEDESKTOP_SITE}/${pkgname}/${pkgname}-${version}.tar.xz"
-checksum=3cae78ccde19d7d0f387e58bc734d4d17ab5f6426f54a9e8b728c90b17baa068
+distfiles="https://gitlab.freedesktop.org/libinput/libinput/-/archive/${version}/libinput-${version}.tar.gz"
+checksum=04d27bce1eb8387e99740e43224b0de7ea65161826d120199bf96230132e5186
CFLAGS="-UNDEBUG"
next reply other threads:[~2022-02-24 13:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 13:38 travankor [this message]
2022-02-27 10:33 ` [PR PATCH] [Merged]: " paper42
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-35825@inbox.vuxu.org \
--to=travankor@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).