From: filiprojek <filiprojek@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] docker-compose: update to 2.30.0
Date: Tue, 29 Oct 2024 22:52:51 +0100 [thread overview]
Message-ID: <20241029215251.3DAD930AC8@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-52843@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 605 bytes --]
There is an updated pull request by filiprojek against master on the void-packages repository
https://github.com/filiprojek/void-packages docker-compose
https://github.com/void-linux/void-packages/pull/52843
docker-compose: update to 2.30.0
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- x86_64-musl
A patch file from https://github.com/void-linux/void-packages/pull/52843.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-docker-compose-52843.patch --]
[-- Type: text/x-diff, Size: 1164 bytes --]
From d6716380444fcef1d49051574835a119b775858f Mon Sep 17 00:00:00 2001
From: Filip Rojek <filip@filiprojek.cz>
Date: Tue, 29 Oct 2024 22:42:30 +0100
Subject: [PATCH] docker-compose: update to 2.30.0
---
srcpkgs/docker-compose/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/docker-compose/template b/srcpkgs/docker-compose/template
index fd436141076146..8aa2a75732d20b 100644
--- a/srcpkgs/docker-compose/template
+++ b/srcpkgs/docker-compose/template
@@ -1,7 +1,7 @@
# Template file for 'docker-compose'
pkgname=docker-compose
-version=2.29.1
-revision=2
+version=2.30.0
+revision=1
build_style=go
go_import_path="github.com/docker/compose/v2"
go_package="${go_import_path}/cmd"
@@ -13,7 +13,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=9749d621b1b8bc1f5881741e0cbad20b5133a0aeedb9339af06b0187be8141b1
+checksum=f2bfce36128a14862192162dfd03bb1f4a493c0cb09ebe9b13105b2e12e4a088
post_install() {
vmkdir usr/libexec/docker/cli-plugins
next prev parent reply other threads:[~2024-10-29 21:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 21:50 [PR PATCH] " filiprojek
2024-10-29 21:52 ` filiprojek [this message]
2025-01-28 1:57 ` [WIP] " github-actions
2025-02-11 1:58 ` [PR PATCH] [Closed]: " github-actions
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=20241029215251.3DAD930AC8@inbox.vuxu.org \
--to=filiprojek@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).