From: m3tav3rse <m3tav3rse@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] qmk: update to 1.1.2.
Date: Fri, 18 Aug 2023 17:16:25 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45657@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]
There is a new pull request by m3tav3rse against master on the void-packages repository
https://github.com/m3tav3rse/void-packages qmk
https://github.com/void-linux/void-packages/pull/45657
qmk: update to 1.1.2.
<!-- 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/45657.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-qmk-45657.patch --]
[-- Type: text/x-diff, Size: 1435 bytes --]
From a0e3fedff472bec514dc1812e1ddb4c3ddb08f30 Mon Sep 17 00:00:00 2001
From: m3tav3rse <mtvrs@tuta.io>
Date: Fri, 18 Aug 2023 16:57:14 +0200
Subject: [PATCH] qmk: update to 1.1.2.
---
srcpkgs/qmk/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/qmk/template b/srcpkgs/qmk/template
index 5c1bc5ecda2ea..45859116530b3 100644
--- a/srcpkgs/qmk/template
+++ b/srcpkgs/qmk/template
@@ -1,7 +1,7 @@
# Template file for 'qmk'
pkgname=qmk
-version=1.0.0
-revision=2
+version=1.1.2
+revision=1
build_style=python3-pep517
hostmakedepends="python3-wheel"
# This includes the requirements from requirements.txt in the qmk_firmware
@@ -10,12 +10,12 @@ depends="avr-gcc avrdude cross-arm-none-eabi dfu-programmer dfu-util
python3-Pygments python3-appdirs python3-argcomplete python3-colorama
python3-dotty-dict python3-hid python3-hjson python3-jsonschema python3-milc
python3-nose2 python3-usb python3-yapf"
-short_desc="CLI tool for working with QMK firmware of mechanical keyboards"
+short_desc="Program to help users work with QMK Firmware"
maintainer="Orphaned <orphan@voidlinux.org>"
license="MIT"
homepage="https://github.com/qmk/qmk_cli"
distfiles="${PYPI_SITE}/q/qmk/qmk-${version}.tar.gz"
-checksum=da62eec73c4548cc37b0b9be3937202dc3a301dc2f2663610ecca751a610f9ca
+checksum=f871f88f1a0ca31ba31a009d716417e46bc538a4f8df8ede6a801c9076c22998
post_install() {
vlicense LICENSE
next reply other threads:[~2023-08-18 15:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 15:16 m3tav3rse [this message]
2023-08-20 14:39 ` [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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45657@inbox.vuxu.org \
--to=m3tav3rse@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).