From: Bnyro <Bnyro@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] docker-compose: update to 2.19.0.
Date: Fri, 23 Jun 2023 14:56:57 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44587@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 577 bytes --]
There is a new pull request by Bnyro against master on the void-packages repository
https://github.com/Bnyro/void-packages docker-compose
https://github.com/void-linux/void-packages/pull/44587
docker-compose: update to 2.19.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
A patch file from https://github.com/void-linux/void-packages/pull/44587.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-docker-compose-44587.patch --]
[-- Type: text/x-diff, Size: 1121 bytes --]
From 9a543719a87836ebdc48e56774bb08d328dab367 Mon Sep 17 00:00:00 2001
From: Bnyro <bnyro@tutanota.com>
Date: Fri, 23 Jun 2023 14:54:42 +0200
Subject: [PATCH] docker-compose: update to 2.19.0.
---
srcpkgs/docker-compose/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/docker-compose/template b/srcpkgs/docker-compose/template
index 7271843da8cf..772cbb1e0f18 100644
--- a/srcpkgs/docker-compose/template
+++ b/srcpkgs/docker-compose/template
@@ -1,6 +1,6 @@
# Template file for 'docker-compose'
pkgname=docker-compose
-version=2.18.1
+version=2.19.0
revision=1
build_style=go
go_import_path="github.com/docker/compose/v2/cmd"
@@ -12,7 +12,7 @@ license="Apache-2.0"
homepage="https://docs.docker.com/compose/"
changelog="https://github.com/docker/compose/releases"
distfiles="https://github.com/docker/compose/archive/refs/tags/v${version}.tar.gz"
-checksum=192c47c177d9bfd8492ed0c49214af0c740586da6db0b7e9c9a07da37c9dc722
+checksum=0be3fd713ef84985f63d76de4c58451401aed1dfbeb235127dd77a57d1890996
post_install() {
mkdir -p ${DESTDIR}/usr/libexec/docker/cli-plugins
next reply other threads:[~2023-06-23 12:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 12:56 Bnyro [this message]
2023-06-26 9:06 ` [PR PATCH] [Merged]: " 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-44587@inbox.vuxu.org \
--to=bnyro@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).