From: TeddyDD <TeddyDD@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] docker-buildx: update to 0.15.1.
Date: Fri, 21 Jun 2024 09:27:46 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50908@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]
There is a new pull request by TeddyDD against master on the void-packages repository
https://github.com/TeddyDD/void-packages-1 update-docker-buildx
https://github.com/void-linux/void-packages/pull/50908
docker-buildx: update to 0.15.1.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- 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/50908.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update-docker-buildx-50908.patch --]
[-- Type: text/x-diff, Size: 1111 bytes --]
From 5832c5bb9ac297f697ef2e5bb9f0127613d8d757 Mon Sep 17 00:00:00 2001
From: Daniel Lewan <daniel@teddydd.me>
Date: Fri, 21 Jun 2024 09:26:48 +0200
Subject: [PATCH] docker-buildx: update to 0.15.1.
---
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 9f7f3c883a525c..702fb0ff3ccb74 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.14.1
+version=0.15.1
revision=1
build_style=go
go_import_path="github.com/docker/buildx"
@@ -12,7 +12,7 @@ maintainer="Daniel Lewan <daniel@teddydd.me>"
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=01e39cc6d674e20547a62f52d80bc3cbd6c1cff6764d7869e182bdcdd49ac297
+checksum=af8a6733b166c7b7676348e7553b1abaa9e62b416827f1be790a8fe7ec21c8a9
post_install() {
vmkdir usr/libexec/docker/cli-plugins
next reply other threads:[~2024-06-21 7:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 7:27 TeddyDD [this message]
2024-06-22 0:12 ` [PR PATCH] [Closed]: " classabbyamp
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-50908@inbox.vuxu.org \
--to=teddydd@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).