From: TeddyDD <TeddyDD@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] docker-buildx: update to 0.14.0.
Date: Tue, 23 Apr 2024 11:09:24 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49995@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1257 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/49995
docker-buildx: update to 0.14.0.
<!-- 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/49995.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update-docker-buildx-49995.patch --]
[-- Type: text/x-diff, Size: 1111 bytes --]
From be60e7f75322963e37916a9acf1ed88d3f30066d Mon Sep 17 00:00:00 2001
From: Daniel Lewan <daniel@teddydd.me>
Date: Tue, 23 Apr 2024 11:08:59 +0200
Subject: [PATCH] docker-buildx: update to 0.14.0.
---
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 46b2a906ec31b0..18bf2d7cba2ebd 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.13.1
+version=0.14.0
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=6e77b77d9b7fae6f00955968569ec32673ae6e2bed31587ea016f9a5169b0f61
+checksum=9ed27d47b728288500ba2535366792d9b006354e02178688360919663f92b63e
post_install() {
vmkdir usr/libexec/docker/cli-plugins
next reply other threads:[~2024-04-23 9:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 9:09 TeddyDD [this message]
2024-04-23 17:57 ` [PR PATCH] [Merged]: " cinerea0
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-49995@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).