Github messages for voidlinux
 help / color / mirror / Atom feed
From: Hnaguski <Hnaguski@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] sc-controller: update to 0.4.8.7.
Date: Tue, 21 Jun 2022 23:09:56 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37635@inbox.vuxu.org> (raw)

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

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

https://github.com/Hnaguski/void-packages sc-controller
https://github.com/void-linux/void-packages/pull/37635

sc-controller: update to 0.4.8.7.
<!-- 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/37635.patch is attached

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

From b7053cdb442f5f83bb09aa9aa88f22c9d3201923 Mon Sep 17 00:00:00 2001
From: Henry Naguski <henry@nilsu.org>
Date: Tue, 21 Jun 2022 17:02:57 -0400
Subject: [PATCH] sc-controller: update to 0.4.8.7.

---
 srcpkgs/sc-controller/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/sc-controller/template b/srcpkgs/sc-controller/template
index f1d641021f82..f3e6c04b239c 100644
--- a/srcpkgs/sc-controller/template
+++ b/srcpkgs/sc-controller/template
@@ -1,6 +1,6 @@
 # Template file for 'sc-controller'
 pkgname=sc-controller
-version=0.4.8.6
+version=0.4.8.7
 revision=1
 build_style=python3-module
 hostmakedepends="python3-setuptools"
@@ -11,4 +11,4 @@ maintainer="Henry Naguski <henry@nilsu.org>"
 license="GPL-2.0-only"
 homepage="https://github.com/Ryochan7/sc-controller"
 distfiles="https://github.com/Ryochan7/sc-controller/archive/refs/tags/v$version.tar.gz"
-checksum=e6b8c736877acbee0a90acb3470650327c6c76ab9a4c13a3359356e6858943f5
+checksum=af96bc2f2a90207007bc5ed00c626a1927085bb2aab7efb373e7e4339d4d11ae

             reply	other threads:[~2022-06-21 21:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21 21:09 Hnaguski [this message]
2022-06-21 21:47 ` [PR PATCH] [Updated] " Hnaguski
2022-06-28 22:27 ` [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-37635@inbox.vuxu.org \
    --to=hnaguski@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).