From: ishaanbhimwal <ishaanbhimwal@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] kvantum: update to 1.0.3
Date: Thu, 07 Jul 2022 21:29:16 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37915@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
There is a new pull request by ishaanbhimwal against master on the void-packages repository
https://github.com/ishaanbhimwal/void-packages kvantum
https://github.com/void-linux/void-packages/pull/37915
kvantum: update to 1.0.3
<!-- 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/37915.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-kvantum-37915.patch --]
[-- Type: text/x-diff, Size: 1066 bytes --]
From 1695530bcefa5460512c9923d14812ed4370bc23 Mon Sep 17 00:00:00 2001
From: Ishaan Bhimwal <ishaanbhimwal@protonmail.com>
Date: Fri, 8 Jul 2022 00:57:04 +0530
Subject: [PATCH] kvantum: update to 1.0.3
---
srcpkgs/kvantum/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/kvantum/template b/srcpkgs/kvantum/template
index 68be85c44e6b..f64fbb9c97bd 100644
--- a/srcpkgs/kvantum/template
+++ b/srcpkgs/kvantum/template
@@ -1,6 +1,6 @@
# Template file for 'kvantum'
pkgname=kvantum
-version=1.0.0
+version=1.0.3
revision=1
wrksrc="Kvantum-${version}"
build_wrksrc=Kvantum
@@ -14,7 +14,7 @@ license="GPL-3.0-or-later"
homepage="https://github.com/tsujan/Kvantum"
changelog="https://raw.githubusercontent.com/tsujan/Kvantum/master/Kvantum/ChangeLog"
distfiles="https://github.com/tsujan/Kvantum/archive/V${version}.tar.gz"
-checksum=0b80d934e1d38588582a2f5c10e362aa8ee37f00446e5c028bda4e5eca6a2b4c
+checksum=87222a5e7b452cfde367638dab89740cf559075579e10f11178db731957f7fb3
post_install() {
vdoc doc/Theme-Config.pdf
next reply other threads:[~2022-07-07 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 19:29 ishaanbhimwal [this message]
2022-08-07 18:38 ` classabbyamp
2022-11-06 2:13 ` github-actions
2022-11-21 2:11 ` [PR PATCH] [Closed]: " github-actions
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-37915@inbox.vuxu.org \
--to=ishaanbhimwal@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).