From: Vaelatern <Vaelatern@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] vault: update to 1.12.3.
Date: Fri, 10 Feb 2023 06:57:13 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42177@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 508 bytes --]
There is a new pull request by Vaelatern against master on the void-packages repository
https://github.com/Vaelatern/void-packages vault-config-change
https://github.com/void-linux/void-packages/pull/42177
vault: update to 1.12.3.
@the-maldridge I also changed the config file to be backwards compatible but to allow me to change the config for my own usage (I like `/etc/vault.d` and this change lets that happen)
A patch file from https://github.com/void-linux/void-packages/pull/42177.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-vault-config-change-42177.patch --]
[-- Type: text/x-diff, Size: 1502 bytes --]
From 223d4a76688543cb3a71935aed7936ebdf615d65 Mon Sep 17 00:00:00 2001
From: Toyam Cox <Vaelatern@voidlinux.org>
Date: Fri, 10 Feb 2023 00:57:18 -0500
Subject: [PATCH] vault: update to 1.12.3.
---
srcpkgs/vault/files/vault/run | 5 ++++-
srcpkgs/vault/template | 4 ++--
2 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/vault/files/vault/run b/srcpkgs/vault/files/vault/run
index 6b08c00f5c2e..43742a8ee0a0 100644
--- a/srcpkgs/vault/files/vault/run
+++ b/srcpkgs/vault/files/vault/run
@@ -1,4 +1,7 @@
#!/bin/sh
exec 2>&1
-exec chpst -u _vault vault server -config=/etc/vault/
+[ -r ./conf ] && . ./conf
+: ${OPTS:=server -config=/etc/vault/}
+
+exec chpst -u _vault vault ${OPTS}
diff --git a/srcpkgs/vault/template b/srcpkgs/vault/template
index b8cc146ca579..194ddcc2270f 100644
--- a/srcpkgs/vault/template
+++ b/srcpkgs/vault/template
@@ -1,6 +1,6 @@
# Template file for 'vault'
pkgname=vault
-version=1.12.1
+version=1.12.3
revision=1
build_style=go
go_import_path="github.com/hashicorp/vault"
@@ -13,7 +13,7 @@ maintainer="Michael Aldridge <maldridge@voidlinux.org>"
license="MPL-2.0"
homepage="https://www.vaultproject.io/"
distfiles="https://github.com/hashicorp/vault/archive/v${version}.tar.gz"
-checksum=32dc19ca35496ecaeaf906f8670d3acf569f0c7a43531cbdc9ab69f69f7c4a68
+checksum=be65f2fcc2e5ed0e01978c72a5ee8142470e7115088c96d8c0d1a66e0b5ec17a
system_accounts="_vault"
make_dirs="/var/lib/vault 0700 _vault _vault
/etc/vault 0750 root _vault"
next reply other threads:[~2023-02-10 5:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 5:57 Vaelatern [this message]
2023-02-10 6:25 ` [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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42177@inbox.vuxu.org \
--to=vaelatern@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).