From: baalajimaestro <baalajimaestro@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] docker-buildx: update to 0.10.3.
Date: Tue, 21 Feb 2023 05:25:49 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42369@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 520 bytes --]
There is a new pull request by baalajimaestro against master on the void-packages repository
https://github.com/baalajimaestro/void-packages update/docker-buildx/0.10.3
https://github.com/void-linux/void-packages/pull/42369
docker-buildx: update to 0.10.3.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, glibc, x86_64
A patch file from https://github.com/void-linux/void-packages/pull/42369.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update/docker-buildx/0.10.3-42369.patch --]
[-- Type: text/x-diff, Size: 1176 bytes --]
From e6ddff35c02836ee6ccdc1844314f4ff136bcdbc Mon Sep 17 00:00:00 2001
From: baalajimaestro <me@baalajimaestro.me>
Date: Tue, 21 Feb 2023 09:53:42 +0530
Subject: [PATCH] docker-buildx: update to 0.10.3.
Signed-off-by: baalajimaestro <me@baalajimaestro.me>
---
srcpkgs/docker-buildx/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/docker-buildx/template b/srcpkgs/docker-buildx/template
index 0c4df7c9cec1..41a8e7a91f54 100644
--- a/srcpkgs/docker-buildx/template
+++ b/srcpkgs/docker-buildx/template
@@ -1,6 +1,6 @@
# Template file for 'docker-buildx'
pkgname=docker-buildx
-version=0.9.1
+version=0.10.3
revision=1
build_style=go
go_import_path="github.com/docker/buildx/cmd/buildx"
@@ -11,7 +11,7 @@ maintainer="Gabriel Sanches <gabriel@gsr.dev>"
license="Apache-2.0"
homepage="https://docs.docker.com/buildx/working-with-buildx/"
distfiles="https://github.com/docker/buildx/archive/refs/tags/v${version}.tar.gz"
-checksum=22b0d2acfffaaa4a52d13cd6fa78608e9c817c3d1bdfbaf2e274242325bb293d
+checksum=e21ce4b222cfcc5fe981a1ee51fca1f7c7d59de0f1911ae3f64f6d9a969695a3
post_install() {
vmkdir usr/libexec/docker/cli-plugins
next reply other threads:[~2023-02-21 4:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 4:25 baalajimaestro [this message]
2023-02-23 21:24 ` [PR PATCH] [Merged]: " paper42
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-42369@inbox.vuxu.org \
--to=baalajimaestro@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).