From: darknebula05 <darknebula05@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-evdev: update to 1.6.0.
Date: Fri, 12 Aug 2022 21:52:06 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38641@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]
There is a new pull request by darknebula05 against master on the void-packages repository
https://github.com/darknebula05/void-packages master
https://github.com/void-linux/void-packages/pull/38641
python3-evdev: update to 1.6.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 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/38641.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-38641.patch --]
[-- Type: text/x-diff, Size: 3424 bytes --]
From 370af6a8a01c39cfebcad2938bdbfb0687125820 Mon Sep 17 00:00:00 2001
From: darknebula05 <camms205@aol.com>
Date: Thu, 11 Aug 2022 11:08:10 -0400
Subject: [PATCH] python3-evdev: update to 1.6.0.
---
srcpkgs/python3-evdev/patches/time64.patch | 45 ----------------------
srcpkgs/python3-evdev/template | 8 ++--
2 files changed, 5 insertions(+), 48 deletions(-)
delete mode 100644 srcpkgs/python3-evdev/patches/time64.patch
diff --git a/srcpkgs/python3-evdev/patches/time64.patch b/srcpkgs/python3-evdev/patches/time64.patch
deleted file mode 100644
index bfcb6598f0c5..000000000000
--- a/srcpkgs/python3-evdev/patches/time64.patch
+++ /dev/null
@@ -1,45 +0,0 @@
---- a/evdev/input.c 2019-04-07 17:40:25.000000000 +0200
-+++ b/evdev/input.c 2020-12-14 14:48:49.568344738 +0100
-@@ -60,8 +60,8 @@
- return NULL;
- }
-
-- PyObject* sec = PyLong_FromLong(event.time.tv_sec);
-- PyObject* usec = PyLong_FromLong(event.time.tv_usec);
-+ PyObject* sec = PyLong_FromLong(event.input_event_sec);
-+ PyObject* usec = PyLong_FromLong(event.input_event_usec);
- PyObject* val = PyLong_FromLong(event.value);
- PyObject* py_input_event = NULL;
-
-@@ -102,8 +102,8 @@
-
- // Construct a list of event tuples, which we'll make sense of in Python
- for (unsigned i = 0 ; i < nread/event_size ; i++) {
-- sec = PyLong_FromLong(event[i].time.tv_sec);
-- usec = PyLong_FromLong(event[i].time.tv_usec);
-+ sec = PyLong_FromLong(event[i].input_event_sec);
-+ usec = PyLong_FromLong(event[i].input_event_usec);
- val = PyLong_FromLong(event[i].value);
-
- py_input_event = Py_BuildValue("OOhhO", sec, usec, event[i].type, event[i].code, val);
---- a/evdev/uinput.c 2019-04-07 17:40:25.000000000 +0200
-+++ b/evdev/uinput.c 2020-12-14 14:51:58.809761744 +0100
-@@ -226,6 +226,7 @@
- static PyObject *
- uinput_write(PyObject *self, PyObject *args)
- {
-+ struct timeval tv;
- int fd, type, code, value;
-
- int ret = PyArg_ParseTuple(args, "iiii", &fd, &type, &code, &value);
-@@ -233,7 +234,9 @@
-
- struct input_event event;
- memset(&event, 0, sizeof(event));
-- gettimeofday(&event.time, 0);
-+ gettimeofday(&tv, 0);
-+ event.input_event_sec = tv.tv_sec;
-+ event.input_event_usec = tv.tv_usec;
- event.type = type;
- event.code = code;
- event.value = value;
diff --git a/srcpkgs/python3-evdev/template b/srcpkgs/python3-evdev/template
index 962216d71325..8ae95b3d25a2 100644
--- a/srcpkgs/python3-evdev/template
+++ b/srcpkgs/python3-evdev/template
@@ -1,17 +1,19 @@
# Template file for 'python3-evdev'
pkgname=python3-evdev
-version=1.2.0
-revision=5
+version=1.6.0
+revision=1
wrksrc="python-evdev-$version"
build_style=python3-module
hostmakedepends="python3-setuptools"
makedepends="python3-devel"
+checkdepends="python3-pytest"
short_desc="Python3 bindings for the Linux input subsystem"
maintainer="Orphaned <orphan@voidlinux.org>"
license="BSD-3-Clause"
homepage="https://github.com/gvalkov/python-evdev"
+changelog="https://raw.githubusercontent.com/gvalkov/python-evdev/main/docs/changelog.rst"
distfiles="https://github.com/gvalkov/python-evdev/archive/v${version}.tar.gz"
-checksum=f788584510620251c6a6c68802935b71c4b474df99b87ee223e18b84dd1719a6
+checksum=85877121b46e0eacf390c1ee4a07e6f5fcb3c603c1649efcccdd554f2fe0c3ab
post_install() {
vlicense LICENSE
next reply other threads:[~2022-08-12 19:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 19:52 darknebula05 [this message]
2022-08-12 19:58 ` classabbyamp
2022-08-12 21:12 ` classabbyamp
2022-11-11 2:13 ` github-actions
2022-11-26 2:01 ` [PR PATCH] [Closed]: " github-actions
-- strict thread matches above, loose matches on Subject: below --
2022-08-11 15:16 [PR PATCH] " darknebula05
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-38641@inbox.vuxu.org \
--to=darknebula05@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).