From: fnogcps <fnogcps@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] gocryptfs: update to 2.3.
Date: Tue, 07 Feb 2023 11:56:40 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42127@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 380 bytes --]
There is a new pull request by fnogcps against master on the void-packages repository
https://github.com/fnogcps/void-packages gocryptfs
https://github.com/void-linux/void-packages/pull/42127
gocryptfs: update to 2.3.
#### Testing the changes
- I tested the changes in this PR: **YES**
A patch file from https://github.com/void-linux/void-packages/pull/42127.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-gocryptfs-42127.patch --]
[-- Type: text/x-diff, Size: 1259 bytes --]
From f701e438db280e08e00e07759db59af29aaad195 Mon Sep 17 00:00:00 2001
From: Felipe Nogueira <contato.fnog@gmail.com>
Date: Tue, 7 Feb 2023 07:54:21 -0300
Subject: [PATCH] gocryptfs: update to 2.3.
---
srcpkgs/gocryptfs/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/gocryptfs/template b/srcpkgs/gocryptfs/template
index a821cf927546..56f584e85228 100644
--- a/srcpkgs/gocryptfs/template
+++ b/srcpkgs/gocryptfs/template
@@ -1,6 +1,6 @@
# Template file for 'gocryptfs'
pkgname=gocryptfs
-version=2.2.1
+version=2.3
revision=1
build_style=go
go_import_path="github.com/rfjakob/gocryptfs/v2"
@@ -12,8 +12,8 @@ maintainer="Felipe Nogueira <contato.fnog@gmail.com>"
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=8d3f66fe426de6b31dfd56122f26047cc8cda679d2fba7bc26d78448701da5e3
+distfiles="https://github.com/rfjakob/gocryptfs/releases/download/v${version}/gocryptfs_v${version}_src-deps.tar.gz"
+checksum=945e3287311547f9227f4a5b5d051fd6df8b8b41ce2a65f424de9829cc785129
post_install() {
vlicense LICENSE
next reply other threads:[~2023-02-07 10:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 10:56 fnogcps [this message]
2023-02-14 21:08 ` [PR PATCH] [Merged]: " paper42
-- strict thread matches above, loose matches on Subject: below --
2023-01-13 17:31 [PR PATCH] " fnogcps
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-42127@inbox.vuxu.org \
--to=fnogcps@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).