From: filiprojek <filiprojek@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] docker-compose: update to 2.24.1
Date: Fri, 19 Jan 2024 00:07:15 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48274@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 498 bytes --]
There is a new 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/48274
docker-compose: update to 2.24.1
#### 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)
A patch file from https://github.com/void-linux/void-packages/pull/48274.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-docker-compose-48274.patch --]
[-- Type: text/x-diff, Size: 1112 bytes --]
From a58f3e2e0551c3f0990a11033f3c2bb2cbbee8da Mon Sep 17 00:00:00 2001
From: Filip Rojek <filip@filiprojek.cz>
Date: Fri, 19 Jan 2024 00:05:44 +0100
Subject: [PATCH] docker-compose: update to 2.24.1
---
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 e297fbc77ce23..47ad2a174b539 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.21.0
+version=2.24.1
revision=1
build_style=go
go_import_path="github.com/docker/compose/v2"
@@ -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=0014b23382a50c90f91849e491500568366052882e22011822ca2d8a3b2976f2
+checksum=6bc723e36c1bd6c83f83fc1ee65097df29c6780f5e136e61e53ef96316be593f
post_install() {
vmkdir usr/libexec/docker/cli-plugins
next reply other threads:[~2024-01-18 23:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 23:07 filiprojek [this message]
2024-01-26 1:33 ` [PR PATCH] [Updated] " filiprojek
2024-01-26 1:34 ` docker-compose: update to 2.24.3 filiprojek
2024-01-29 15:04 ` [PR PATCH] [Updated] " filiprojek
2024-01-30 18:56 ` [PR PATCH] [Updated] docker-compose: update to 2.24.3, adopt filiprojek
2024-01-30 18:59 ` docker-compose: update to 2.24.4, adopt filiprojek
2024-02-03 11:59 ` [PR PATCH] [Updated] " filiprojek
2024-02-03 12:03 ` filiprojek
2024-02-03 12:10 ` docker-compose: update to 2.24.5, adopt filiprojek
2024-02-17 18:51 ` [PR PATCH] [Updated] " filiprojek
2024-02-19 16:20 ` [PR PATCH] [Merged]: docker-compose: update to 2.24.6, adopt leahneukirchen
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-48274@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).