public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-containers/docker-compose/
Date: Thu, 20 Apr 2023 05:01:58 +0000 (UTC)	[thread overview]
Message-ID: <1681966871.d1b161e0c7665ebc4b934625c1f7ccb96585d1e8.sam@gentoo> (raw)

commit:     d1b161e0c7665ebc4b934625c1f7ccb96585d1e8
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Apr 20 05:00:43 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Apr 20 05:01:11 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d1b161e0

app-containers/docker-compose: Stabilize 1.29.2-r3 amd64, #904614

Signed-off-by: Sam James <sam <AT> gentoo.org>

 app-containers/docker-compose/docker-compose-1.29.2-r3.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-containers/docker-compose/docker-compose-1.29.2-r3.ebuild b/app-containers/docker-compose/docker-compose-1.29.2-r3.ebuild
index 90aa5aa0b0db..4f274a47deae 100644
--- a/app-containers/docker-compose/docker-compose-1.29.2-r3.ebuild
+++ b/app-containers/docker-compose/docker-compose-1.29.2-r3.ebuild
@@ -14,7 +14,7 @@ SRC_URI="https://github.com/docker/compose/archive/${MY_PV}.tar.gz -> ${P}.gh.ta
 
 LICENSE="Apache-2.0"
 SLOT="0"
-KEYWORDS="~amd64 arm64"
+KEYWORDS="amd64 arm64"
 
 RDEPEND="
 	>=dev-python/distro-1.5.0[${PYTHON_USEDEP}]


             reply	other threads:[~2023-04-20  5:02 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-20  5:01 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-03 17:46 [gentoo-commits] repo/gentoo:master commit in: app-containers/docker-compose/ Sebastian Pipping
2024-09-28 10:27 Arthur Zamarin
2024-07-02 17:52 William Hubbs
2024-06-14 12:26 Michał Górny
2024-04-12 15:49 William Hubbs
2024-03-22 20:23 Arthur Zamarin
2024-03-22 18:26 Sam James
2024-01-11 18:35 William Hubbs
2024-01-11 18:26 William Hubbs
2023-12-12 23:25 Sebastian Pipping
2023-11-05 19:35 Sebastian Pipping
2023-11-05 19:35 Sebastian Pipping
2023-10-26 19:55 William Hubbs
2023-08-13  4:58 Sam James
2023-08-13  3:21 William Hubbs
2023-08-11 16:06 William Hubbs
2023-08-11 16:06 William Hubbs
2023-08-11 15:20 William Hubbs
2023-07-08 14:05 Sebastian Pipping
2023-04-19 18:09 Arthur Zamarin
2023-04-16 16:43 Sebastian Pipping
2023-04-13  1:49 Sam James
2023-04-13  1:49 Sam James
2023-04-12 21:06 William Hubbs
2023-04-07  4:56 William Hubbs
2023-04-07  4:13 William Hubbs
2023-03-11 21:43 William Hubbs
2023-03-11  0:34 William Hubbs
2023-03-10 21:35 William Hubbs
2023-03-10  2:34 Sebastian Pipping
2022-11-15  4:10 William Hubbs
2022-11-15  4:10 William Hubbs
2022-09-30  3:41 William Hubbs
2022-09-29 15:35 William Hubbs
2022-06-13 20:27 William Hubbs
2022-06-03 17:13 William Hubbs
2022-05-02 15:23 William Hubbs
2022-04-10 19:01 William Hubbs
2022-03-26 17:07 Arthur Zamarin
2022-03-26  1:37 Sam James
2022-03-17 21:39 William Hubbs
2022-03-17 21:39 William Hubbs
2022-03-16 13:25 Sebastian Pipping
2022-03-15 19:24 William Hubbs
2022-03-15 19:24 William Hubbs
2022-03-15 17:24 William Hubbs

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=1681966871.d1b161e0c7665ebc4b934625c1f7ccb96585d1e8.sam@gentoo \
    --to=sam@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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