From: dmarto <dmarto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] openrazer-meta: update to 3.3.0.
Date: Tue, 17 May 2022 02:49:29 +0200 [thread overview]
Message-ID: <20220517004929.gjDjMAfRqijqocRL1uXgjmzQab0-td9o69hPWSnDoF0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36623@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 490 bytes --]
There is an updated pull request by dmarto against master on the void-packages repository
https://github.com/dmarto/void-packages openrazer
https://github.com/void-linux/void-packages/pull/36623
openrazer-meta: update to 3.3.0.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### 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/36623.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-openrazer-36623.patch --]
[-- Type: text/x-diff, Size: 1161 bytes --]
From c6421dda5d346f58231e6789045c44959d80f685 Mon Sep 17 00:00:00 2001
From: Martin Dimov <martin@dmarto.com>
Date: Mon, 11 Apr 2022 03:15:20 +0300
Subject: [PATCH] openrazer-meta: update to 3.3.0.
---
srcpkgs/openrazer-meta/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/openrazer-meta/template b/srcpkgs/openrazer-meta/template
index 3cd401cb9878..81c08b768467 100644
--- a/srcpkgs/openrazer-meta/template
+++ b/srcpkgs/openrazer-meta/template
@@ -1,7 +1,7 @@
# Template file for 'openrazer-meta'
pkgname=openrazer-meta
-version=3.0.1
-revision=3
+version=3.3.0
+revision=1
wrksrc="openrazer-${version}"
build_style=gnu-makefile
make_install_target="setup_dkms udev_install daemon_install xdg_install
@@ -13,7 +13,7 @@ maintainer="Luca Weiss <luca@z3ntu.xyz>"
license="GPL-2.0-or-later"
homepage="https://openrazer.github.io"
distfiles="https://github.com/openrazer/openrazer/releases/download/v${version}/openrazer-${version}.tar.xz"
-checksum=b27a7ab459e5290f9fe4d56f49922f97ed83fc92ba2bc0154aff8c4cdd1de73f
+checksum=cb7bc5c4761f601c1f0da36022153382384058f61fb72b23ee02c575ec41546a
do_build() {
:
next prev parent reply other threads:[~2022-05-17 0:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 0:17 [PR PATCH] " dmarto
2022-05-17 0:49 ` dmarto [this message]
2022-06-29 20:42 ` [PR PATCH] [Merged]: " Duncaen
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=20220517004929.gjDjMAfRqijqocRL1uXgjmzQab0-td9o69hPWSnDoF0@z \
--to=dmarto@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).