Github messages for voidlinux
 help / color / mirror / Atom feed
From: Goorzhel <Goorzhel@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] vault: update to 1.6.1
Date: Wed, 13 Jan 2021 04:30:46 +0100	[thread overview]
Message-ID: <20210113033046.wkQuylupPFjymaTTq-M-MslnU9hXHXiEwebsEZTyxj8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27851@inbox.vuxu.org>

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

There is an updated pull request by Goorzhel against master on the void-packages repository

https://github.com/Goorzhel/void-packages vault
https://github.com/void-linux/void-packages/pull/27851

vault: update to 1.6.1
@the-maldridge 

* Here are [the minor-version changes](https://github.com/hashicorp/vault/blob/master/CHANGELOG.md#160).
* For consistency's sake I matched `_git_commit` to `v1.6.1`'s hash. 

Sanity check:
```
$ ./xbps-src pkg vault
<...>
$ xi vault
<...>
$ vault version
Vault v1.6.1 (6d2db3f033e02e70202bef9ec896360062b88b03) (cgo)
$ vault server -dev &> /dev/null &
[1] 9125
$ export VAULT_ADDR='http://127.0.0.1:8200'
$ vault secrets enable -path=kv kv
Success! Enabled the kv secrets engine at: kv/
$ vault kv put kv/foo foo=bar
Success! Data written to: kv/foo
$ vault kv get kv/foo
=== Data ===
Key    Value
---    -----
foo    bar
```
Lemme know if there're any more tests you'd like me to run.

A patch file from https://github.com/void-linux/void-packages/pull/27851.patch is attached

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

From 3515abd74b9803e6a67d97ec435f25b022e39ad8 Mon Sep 17 00:00:00 2001
From: Antonio Gurgel <antonio@goorzhel.com>
Date: Mon, 11 Jan 2021 23:14:16 -0800
Subject: [PATCH] vault: update to 1.6.1

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

diff --git a/srcpkgs/vault/template b/srcpkgs/vault/template
index 5b34538ad0c..9f8fe87fd3a 100644
--- a/srcpkgs/vault/template
+++ b/srcpkgs/vault/template
@@ -1,11 +1,11 @@
 # Template file for 'vault'
 pkgname=vault
-version=1.5.4
+version=1.6.1
 revision=1
 build_style=go
 go_import_path="github.com/hashicorp/${pkgname}"
 go_build_tags="release"
-_git_commit=e16495da552c996068e05574cddf69875199f949
+_git_commit=6d2db3f033e02e70202bef9ec896360062b88b03
 go_ldflags="-X ${go_import_path}/sdk/version.GitCommit=${_git_commit}"
 hostmakedepends="git"
 short_desc="Manage Secrets and Protect Sensitive Data"
@@ -13,7 +13,7 @@ maintainer="Michael Aldridge <maldridge@voidlinux.org>"
 license="MPL-2.0"
 homepage="https://www.vaultproject.io/"
 distfiles="https://github.com/hashicorp/${pkgname}/archive/v${version}.tar.gz"
-checksum=99e3145a9b6f5ee6429b997f3e1f35f648d07c617ff6aef7041f91fcf34e1582
+checksum=fb5d96e682a48bfd421b13cdfffd710da0238dbded1988aab822dd5aae75b4c4
 system_accounts="_vault"
 make_dirs="/var/lib/vault 0700 _vault _vault
  /etc/vault 0700 root root"

  parent reply	other threads:[~2021-01-13  3:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12  7:47 [PR PATCH] " Goorzhel
2021-01-12  7:48 ` the-maldridge
2021-01-12  8:02 ` Goorzhel
2021-01-12  8:19 ` Goorzhel
2021-01-12  8:23 ` Goorzhel
2021-01-13  2:45 ` Goorzhel
2021-01-13  2:50 ` ericonr
2021-01-13  3:30 ` Goorzhel [this message]
2021-01-13  3:45 ` the-maldridge
2021-01-13  7:14 ` ericonr
2021-01-13  7:20 ` Goorzhel
2021-01-13  7:21 ` [PR PATCH] [Updated] " Goorzhel
2021-01-13  7:21 ` Goorzhel
2021-01-13  7:28 ` Goorzhel
2021-01-13 11:31 ` q66
2021-01-13 11:41 ` the-maldridge
2021-01-13 17:03 ` [PR PATCH] [Updated] " Goorzhel
2021-01-14  7:33 ` Goorzhel
2021-01-14  7:50 ` [PR PATCH] [Merged]: " the-maldridge

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=20210113033046.wkQuylupPFjymaTTq-M-MslnU9hXHXiEwebsEZTyxj8@z \
    --to=goorzhel@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).