From: xolophreny <xolophreny@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] vkBasalt: update to 0.3.2.10
Date: Thu, 06 Jul 2023 00:40:53 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44871@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
There is a new pull request by xolophreny against master on the void-packages repository
https://github.com/xolophreny/void-packages vkBasalt
https://github.com/void-linux/void-packages/pull/44871
vkBasalt: update to 0.3.2.10
<!-- 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/44871.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-vkBasalt-44871.patch --]
[-- Type: text/x-diff, Size: 1122 bytes --]
From 420af0aa6840aaf693f954e2c89c89d1be9ada8d Mon Sep 17 00:00:00 2001
From: xolophreny <xolophreny@proton.me>
Date: Thu, 6 Jul 2023 03:35:55 +0500
Subject: [PATCH] vkBasalt: update to 0.3.2.10
---
srcpkgs/vkBasalt/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/vkBasalt/template b/srcpkgs/vkBasalt/template
index 0436662e65b1..065da2698ba4 100644
--- a/srcpkgs/vkBasalt/template
+++ b/srcpkgs/vkBasalt/template
@@ -1,13 +1,13 @@
# Template file for 'vkBasalt'
pkgname=vkBasalt
-version=0.3.2.9
+version=0.3.2.10
revision=1
build_style=meson
hostmakedepends="glslang pkg-config"
makedepends="libX11-devel SPIRV-Headers Vulkan-Headers"
short_desc="Vulkan post-processing layer"
-maintainer="xolophreny <xolophreny@proton.me>"
+maintainer="Nika Jay <xolophreny@proton.me>"
license="Zlib"
homepage="https://github.com/DadSchoorse/vkBasalt"
distfiles="https://github.com/DadSchoorse/vkBasalt/archive/v${version}.tar.gz"
-checksum=f13ff6e8f05218800f0fb516f927983170d5ad4dc661ad671bc1fbc436d53b46
+checksum=22f0d44518361b12cf51f30fc9931423977af32a396e746ebf6d726c05788de6
next reply other threads:[~2023-07-05 22:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 22:40 xolophreny [this message]
2023-07-08 18:16 ` [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-44871@inbox.vuxu.org \
--to=xolophreny@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).