From: dataCobra <dataCobra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] docker-compose: update to 2.12.2.
Date: Tue, 22 Nov 2022 13:35:31 +0100 [thread overview]
Message-ID: <20221122123531.zJQvh5VGDDXa4jg6dvOqo9CUGHBjSaJSg_EtP_9d5GQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40598@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 664 bytes --]
There is an updated pull request by dataCobra against master on the void-packages repository
https://github.com/dataCobra/void-packages docker-compose
https://github.com/void-linux/void-packages/pull/40598
docker-compose: update to 2.12.2.
#### 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)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl (crossbuild)
Update to 2.12.2 is also necessary to fix a CVE.
A patch file from https://github.com/void-linux/void-packages/pull/40598.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-docker-compose-40598.patch --]
[-- Type: text/x-diff, Size: 1121 bytes --]
From ba789067528b33c135b1e81c9bf9065f366a95c3 Mon Sep 17 00:00:00 2001
From: dataCobra <datacobra@thinkbot.de>
Date: Fri, 18 Nov 2022 15:11:56 +0100
Subject: [PATCH] docker-compose: update to 2.12.2.
---
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 0976f7c2d575..2f5b855dc23d 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.10.2
+version=2.12.2
revision=1
build_style=go
go_import_path="github.com/docker/compose/v2/cmd"
@@ -11,7 +11,7 @@ maintainer="Michal Vasilek <michal@vasilek.cz>"
license="Apache-2.0"
homepage="https://docs.docker.com/compose/"
distfiles="https://github.com/docker/compose/archive/refs/tags/v${version}.tar.gz"
-checksum=74c86d544fcfb80bb2d3b58187bd017adb0e62863d22114a66c14fc94fdbc421
+checksum=311131c5d930fdb1f5e86de19ea2ad1705d23e5745b780c0b10b2eb3f964fc69
post_install() {
mkdir -p ${DESTDIR}/usr/libexec/docker/cli-plugins
next prev parent reply other threads:[~2022-11-22 12:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 14:14 [PR PATCH] " dataCobra
2022-11-22 12:35 ` dataCobra [this message]
2022-11-22 21:34 ` [PR PATCH] [Merged]: " paper42
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=20221122123531.zJQvh5VGDDXa4jg6dvOqo9CUGHBjSaJSg_EtP_9d5GQ@z \
--to=datacobra@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).