Github messages for voidlinux
 help / color / mirror / Atom feed
From: nilium <nilium@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] sops: update to 3.7.0.
Date: Sun, 28 Mar 2021 04:20:54 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29796@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1584 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/29796

sops: update to 3.7.0.
<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] 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/29796.patch is attached

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

From 892b0d7a6bbd3e6aff4d392ab7807a53555f245a Mon Sep 17 00:00:00 2001
From: Noel Cower <ncower@nil.dev>
Date: Sat, 27 Mar 2021 19:19:34 -0700
Subject: [PATCH] sops: update to 3.7.0.

---
 srcpkgs/sops/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/sops/template b/srcpkgs/sops/template
index ca43b4a502dd..f1215b6c3eb7 100644
--- a/srcpkgs/sops/template
+++ b/srcpkgs/sops/template
@@ -1,7 +1,7 @@
 # Template file for 'sops'
 pkgname=sops
-version=3.6.1
-revision=2
+version=3.7.0
+revision=1
 build_style=go
 go_import_path="go.mozilla.org/sops/v3"
 go_package="${go_import_path}/cmd/sops"
@@ -11,4 +11,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=bb6611eb70580ff74a258aa8b9713fdcb9a28de5a20ee716fe6b516608a60237
+checksum=909496eaed98f6ff4fadc216ad904ef2d2a82ff229e6af6cc0cb1625e2df5d83

             reply	other threads:[~2021-03-28  2:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-28  2:20 nilium [this message]
2021-03-28  4:37 ` [PR PATCH] [Merged]: " ericonr

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-29796@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).