Github messages for voidlinux
 help / color / mirror / Atom feed
From: kruceter <kruceter@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] acpid: ignore arrow key events
Date: Tue, 31 Jan 2023 18:30:40 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41995@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]

There is a new pull request by kruceter against master on the void-packages repository

https://github.com/kruceter/void-packages acpid
https://github.com/void-linux/void-packages/pull/41995

acpid: ignore arrow key events
<!-- 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 [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
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/41995.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-acpid-41995.patch --]
[-- Type: text/x-diff, Size: 1891 bytes --]

From b83859c3d3a0b9bd0a73e531cabdda433650357b Mon Sep 17 00:00:00 2001
From: Krul Ceter <kruceter@proton.me>
Date: Tue, 31 Jan 2023 20:24:51 +0300
Subject: [PATCH] acpid: ignore arrow key events

Upstream added new keys to the list of input events in
b336c96e32c959ed3df15eaf5669f47ea589d977 (see
https://sourceforge.net/p/acpid2/code).

Due to that change syslog gets flooded with arrow key events which
are not used by /etc/acpi/handler.sh.
---
 srcpkgs/acpid/files/buttons | 2 ++
 srcpkgs/acpid/template      | 6 ++++--
 2 files changed, 6 insertions(+), 2 deletions(-)
 create mode 100644 srcpkgs/acpid/files/buttons

diff --git a/srcpkgs/acpid/files/buttons b/srcpkgs/acpid/files/buttons
new file mode 100644
index 000000000000..c269364696e1
--- /dev/null
+++ b/srcpkgs/acpid/files/buttons
@@ -0,0 +1,2 @@
+event=button/(up|down|left|right|kpenter)
+action=<drop>
diff --git a/srcpkgs/acpid/template b/srcpkgs/acpid/template
index 6e066b9409ba..a4b96daf8681 100644
--- a/srcpkgs/acpid/template
+++ b/srcpkgs/acpid/template
@@ -1,7 +1,7 @@
 # Template file for 'acpid'
 pkgname=acpid
 version=2.0.34
-revision=1
+revision=2
 build_style=gnu-configure
 short_desc="ACPI Daemon (acpid) With Netlink Support"
 maintainer="Enno Boland <gottox@voidlinux.org>"
@@ -10,10 +10,12 @@ homepage="https://sourceforge.net/projects/acpid2/"
 changelog="https://sourceforge.net/p/acpid2/code/ci/master/tree/Changelog?format=raw"
 distfiles="${SOURCEFORGE_SITE}/acpid2/acpid-${version}.tar.xz"
 checksum=2d095c8cfcbc847caec746d62cdc8d0bff1ec1bc72ef7c674c721e04da6ab333
-conf_files="/etc/acpi/events/anything /etc/acpi/handler.sh"
+conf_files="/etc/acpi/events/anything /etc/acpi/events/buttons
+ /etc/acpi/handler.sh"
 
 post_install() {
 	vinstall ${FILESDIR}/handler.sh 755 etc/acpi
 	vinstall ${FILESDIR}/anything 644 etc/acpi/events
+	vinstall ${FILESDIR}/buttons 644 etc/acpi/events
 	vsv acpid
 }

             reply	other threads:[~2023-01-31 17:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31 17:30 kruceter [this message]
2023-02-08 23:53 ` [PR PATCH] [Closed]: " kruceter

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-41995@inbox.vuxu.org \
    --to=kruceter@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).