From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] docker-credential-pass: update to 0.6.3
Date: Mon, 21 Oct 2019 14:02:23 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15665@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 339 bytes --]
There is a new pull request by sihoang against master on the void-packages repository
https://github.com/sihoang/void-packages docker-credential-pass
https://github.com/void-linux/void-packages/pull/15665
docker-credential-pass: update to 0.6.3
A patch file from https://github.com/void-linux/void-packages/pull/15665.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-docker-credential-pass-15665.patch --]
[-- Type: text/x-diff, Size: 1237 bytes --]
From e06da6f49c83f119d34af54a0da6e71062bdacb1 Mon Sep 17 00:00:00 2001
From: Hoang Nguyen <hoang@wetrust.io>
Date: Mon, 21 Oct 2019 04:58:39 -0700
Subject: [PATCH] docker-credential-pass: update to 0.6.3
---
srcpkgs/docker-credential-pass/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/docker-credential-pass/template b/srcpkgs/docker-credential-pass/template
index 0b3592f5fb5..bf72bb14b36 100644
--- a/srcpkgs/docker-credential-pass/template
+++ b/srcpkgs/docker-credential-pass/template
@@ -1,7 +1,7 @@
# Template file for 'docker-credential-pass'
pkgname=docker-credential-pass
-version=0.6.1
-revision=2
+version=0.6.3
+revision=1
wrksrc="docker-credential-helpers-${version}"
archs="x86_64* ppc64le*"
build_style=go
@@ -13,7 +13,7 @@ maintainer="Hoang Nguyen <hoang@wetrust.io>"
license="MIT"
homepage="https://github.com/docker/docker-credential-helpers"
distfiles="https://${go_import_path}/archive/v${version}.tar.gz"
-checksum=9b36ae15d5bceaaf3496b80413acafa6325c633af3ae211ce10724dfa7046883
+checksum=441684cf1d2434aa1024aa2f8455e11502c44858e93ea171b19caa656dd2b2e2
# the build step installed the binary named cmd because
# the authors structured their code that way.
next reply other threads:[~2019-10-21 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 12:02 voidlinux-github [this message]
2019-10-21 17:11 ` [PR PATCH] [Updated] " voidlinux-github
2019-10-21 17:11 ` voidlinux-github
2019-10-21 17:13 ` voidlinux-github
2019-10-21 17:13 ` voidlinux-github
2019-10-24 12:25 ` [PR PATCH] [Merged]: " voidlinux-github
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-15665@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--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).