From: nilium <nilium@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] sops: update to 3.6.0.
Date: Thu, 16 Jul 2020 01:07:02 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23594@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 307 bytes --]
There is a new pull request by nilium against master on the void-packages repository
https://github.com/nilium/ecks-bops-packages sops
https://github.com/void-linux/void-packages/pull/23594
sops: update to 3.6.0.
A patch file from https://github.com/void-linux/void-packages/pull/23594.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-sops-23594.patch --]
[-- Type: text/x-diff, Size: 950 bytes --]
From 0fc98b506a76fb18350884efa6508d36d9cc5b03 Mon Sep 17 00:00:00 2001
From: Noel Cower <ncower@nil.dev>
Date: Wed, 15 Jul 2020 16:01:49 -0700
Subject: [PATCH] sops: update to 3.6.0.
---
srcpkgs/sops/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/sops/template b/srcpkgs/sops/template
index 3f82978fcee..46da73e523d 100644
--- a/srcpkgs/sops/template
+++ b/srcpkgs/sops/template
@@ -1,7 +1,7 @@
# Template file for 'sops'
pkgname=sops
-version=3.5.0
-revision=2
+version=3.6.0
+revision=1
build_style=go
go_import_path="go.mozilla.org/sops/v3/cmd/sops"
hostmakedepends="git"
@@ -10,4 +10,4 @@ maintainer="Noel Cower <ncower@nil.dev>"
license="MPL-2.0"
homepage="https://github.com/mozilla/sops"
distfiles="${homepage}/archive/v${version}.tar.gz"
-checksum=a9c257dc5ddaab736dce08b8c5b1f00e6ca1e3171909b6d7385689044ebe759b
+checksum=fee1c27f14f9f45b5955627e301aafcc38973c9458b25f99ef241bdd0a3b082c
next reply other threads:[~2020-07-15 23:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 23:07 nilium [this message]
2020-07-20 16:52 ` [PR PATCH] [Merged]: " ahesford
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-23594@inbox.vuxu.org \
--to=nilium@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).