From: atweiden <atweiden@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] cryfs: rebuild for spdlog-1.10.0.
Date: Mon, 30 May 2022 12:45:34 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37353@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 476 bytes --]
There is a new pull request by atweiden against master on the void-packages repository
https://github.com/atweiden/void-packages cryfs
https://github.com/void-linux/void-packages/pull/37353
cryfs: rebuild for spdlog-1.10.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
A patch file from https://github.com/void-linux/void-packages/pull/37353.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-cryfs-37353.patch --]
[-- Type: text/x-diff, Size: 621 bytes --]
From de290c78c2680ff94624e53de552c670a257d187 Mon Sep 17 00:00:00 2001
From: atweiden <atweiden@ioiojo.com>
Date: Mon, 30 May 2022 20:42:26 +1000
Subject: [PATCH] cryfs: rebuild for spdlog-1.10.0.
---
srcpkgs/cryfs/template | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/cryfs/template b/srcpkgs/cryfs/template
index ef585572fbec..495c2b318a3b 100644
--- a/srcpkgs/cryfs/template
+++ b/srcpkgs/cryfs/template
@@ -1,7 +1,7 @@
# Template file for 'cryfs'
pkgname=cryfs
version=0.10.2
-revision=4
+revision=5
create_wrksrc=yes
build_style=cmake
configure_args="-DCRYFS_UPDATE_CHECKS=off
next reply other threads:[~2022-05-30 10:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 10:45 atweiden [this message]
2022-05-31 16:53 ` [PR PATCH] [Merged]: " sgn
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-37353@inbox.vuxu.org \
--to=atweiden@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).