Github messages for voidlinux
 help / color / mirror / Atom feed
From: pfpulux <pfpulux@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] gocryptfs: update to 2.2.1.
Date: Tue, 16 Aug 2022 06:46:49 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38697@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]

There is a new pull request by pfpulux against master on the void-packages repository

https://github.com/pfpulux/void-packages gocryptfs
https://github.com/void-linux/void-packages/pull/38697

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**

<!--
#### 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/38697.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-gocryptfs-38697.patch --]
[-- Type: text/x-diff, Size: 1063 bytes --]

From 25d3544b56826f42fb5943634f464f1eea215aca Mon Sep 17 00:00:00 2001
From: Pulux <pulux@pf4sh.eu>
Date: Tue, 16 Aug 2022 06:44:42 +0200
Subject: [PATCH] gocryptfs: update to 2.2.1.

---
 srcpkgs/gocryptfs/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/gocryptfs/template b/srcpkgs/gocryptfs/template
index 8dc9d4079321..7ff987a84cd4 100644
--- a/srcpkgs/gocryptfs/template
+++ b/srcpkgs/gocryptfs/template
@@ -1,6 +1,6 @@
 # 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
@@ -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

             reply	other threads:[~2022-08-16  4:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16  4:46 pfpulux [this message]
2022-08-16  4:50 ` [PR PATCH] [Updated] " pfpulux
2022-08-18  5:46 ` [PR PATCH] [Merged]: " classabbyamp
  -- strict thread matches above, loose matches on Subject: below --
2022-03-15  6:47 [PR PATCH] " mustaqimM

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-38697@inbox.vuxu.org \
    --to=pfpulux@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).