Github messages for voidlinux
 help / color / mirror / Atom feed
From: filiprojek <filiprojek@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] docker-compose: update to 2.26.0
Date: Tue, 02 Apr 2024 18:50:54 +0200	[thread overview]
Message-ID: <20240402165054.C6D88223CB@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49192@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 503 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/49192

docker-compose: update to 2.26.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)


A patch file from https://github.com/void-linux/void-packages/pull/49192.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-docker-compose-49192.patch --]
[-- Type: text/x-diff, Size: 1113 bytes --]

From 0e4dab7f0d23aeda1580bf627071d29bb18ff9d6 Mon Sep 17 00:00:00 2001
From: Filip Rojek <filip@filiprojek.cz>
Date: Fri, 8 Mar 2024 14:28:32 +0100
Subject: [PATCH] docker-compose: update to 2.26.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 998bc9d07a0064..ea7c0b99974b45 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.24.6
+version=2.26.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=14fffeba19b82c8e5a9cdf6d873522a11ee4e25bbb86bbdf468795274429db70
+checksum=081ad40241f8e144cad088a65e6fd0ec588e3d36931e5baabb3dc5ab068ceb60
 
 post_install() {
 	vmkdir usr/libexec/docker/cli-plugins

  parent reply	other threads:[~2024-04-02 16:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08 14:22 [PR PATCH] docker-compose: update to 2.24.7 filiprojek
2024-03-20 13:52 ` [PR PATCH] [Updated] " filiprojek
2024-03-26 23:17 ` [PR PATCH] [Updated] docker-compose: update to 2.25.0 filiprojek
2024-04-02 16:50 ` filiprojek [this message]
2024-04-02 16:58 ` docker-compose: update to 2.26.1 filiprojek
2024-04-06 20:25 ` [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=20240402165054.C6D88223CB@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).