From: mustaqimM <mustaqimM@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] gocryptfs: update to 2.2.1
Date: Tue, 15 Mar 2022 07:47:54 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36148@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]
There is a new pull request by mustaqimM against master on the void-packages repository
https://github.com/mustaqimM/void-packages update_gocryptfs
https://github.com/void-linux/void-packages/pull/36148
gocryptfs: update to 2.2.1
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
Should I build it with openssl now that it's in Void?
<!--
#### 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 [skip CI](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/36148.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update_gocryptfs-36148.patch --]
[-- Type: text/x-diff, Size: 1442 bytes --]
From ba0157c8d66b1fd2fe45f668b2dbb740c18d1d64 Mon Sep 17 00:00:00 2001
From: mustaqim <git@mustaqim.ml>
Date: Tue, 15 Mar 2022 08:42:15 +0200
Subject: [PATCH] gocryptfs: update to 2.2.1
---
srcpkgs/gocryptfs/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/gocryptfs/template b/srcpkgs/gocryptfs/template
index 8dc9d4079321..00ec6ca223e3 100644
--- a/srcpkgs/gocryptfs/template
+++ b/srcpkgs/gocryptfs/template
@@ -1,12 +1,12 @@
# Template file for 'gocryptfs'
pkgname=gocryptfs
-version=2.2.0
+version=2.2.1
revision=1
wrksrc="${pkgname}_v${version}_src-deps"
build_style=go
go_import_path="github.com/rfjakob/gocryptfs/v2"
-go_build_tags="without_openssl"
go_ldflags="-X main.GitVersion=v${version} -X main.GitVersionFuse="[vendored]" -X main.BuildDate=$(date +%Y-%m-%d)"
+hostmakedepends="pkg-config openssl-devel"
depends="fuse"
short_desc="Encrypted overlay filesystem written in Go"
maintainer="Felipe Nogueira <contato.fnog@gmail.com>"
@@ -14,7 +14,7 @@ license="MIT"
homepage="https://nuetzlich.net/gocryptfs"
changelog="https://github.com/rfjakob/gocryptfs#changelog"
distfiles="https://github.com/rfjakob/${pkgname}/releases/download/v${version}/${pkgname}_v${version}_src-deps.tar.gz"
-checksum=555e8fba2bc5ed87ad52fc9b7a5525ed0fd01b0a34dfd23cb3ecfae6de75edcd
+checksum=8d3f66fe426de6b31dfd56122f26047cc8cda679d2fba7bc26d78448701da5e3
post_install() {
vlicense LICENSE
next reply other threads:[~2022-03-15 6:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 6:47 mustaqimM [this message]
2022-06-29 2:14 ` github-actions
2022-07-13 2:15 ` [PR PATCH] [Closed]: " github-actions
2022-08-16 4:46 [PR PATCH] " pfpulux
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-36148@inbox.vuxu.org \
--to=mustaqimm@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).