From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-containers/containerd/
Date: Fri, 21 Jul 2023 23:52:15 +0000 (UTC) [thread overview]
Message-ID: <1689983515.fc6e20d0588a11dc3b1ee91ebcfa77b9cbe1565e.sam@gentoo> (raw)
commit: fc6e20d0588a11dc3b1ee91ebcfa77b9cbe1565e
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Jul 21 23:51:55 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Jul 21 23:51:55 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fc6e20d0
app-containers/containerd: Stabilize 1.7.1-r1 arm64, #910651
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-containers/containerd/containerd-1.7.1-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-containers/containerd/containerd-1.7.1-r1.ebuild b/app-containers/containerd/containerd-1.7.1-r1.ebuild
index 6722ebddbf79..3ab8ac111f46 100644
--- a/app-containers/containerd/containerd-1.7.1-r1.ebuild
+++ b/app-containers/containerd/containerd-1.7.1-r1.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://github.com/containerd/containerd/archive/v${PV}.tar.gz -> ${P}.
LICENSE="Apache-2.0"
SLOT="0"
-KEYWORDS="amd64 ~arm ~arm64 ~ppc64 ~riscv ~x86"
+KEYWORDS="amd64 ~arm arm64 ~ppc64 ~riscv ~x86"
IUSE="apparmor btrfs device-mapper +cri hardened +seccomp selinux test"
DEPEND="
next reply other threads:[~2023-07-21 23:52 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 23:52 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-29 16:06 [gentoo-commits] repo/gentoo:master commit in: app-containers/containerd/ William Hubbs
2024-09-24 22:07 James Le Cuirot
2024-09-24 22:07 James Le Cuirot
2024-08-27 19:09 William Hubbs
2024-07-16 20:29 James Le Cuirot
2024-06-18 22:40 William Hubbs
2024-06-13 17:57 Sam James
2024-06-13 2:15 Sam James
2024-06-13 1:56 Sam James
2024-04-26 5:08 William Hubbs
2024-03-17 14:56 William Hubbs
2024-02-01 16:24 William Hubbs
2023-11-09 22:54 William Hubbs
2023-09-25 19:20 William Hubbs
2023-07-25 15:59 William Hubbs
2023-07-25 15:20 William Hubbs
2023-07-24 21:26 William Hubbs
2023-07-24 20:54 Sam James
2023-07-21 21:52 Sam James
2023-07-21 5:17 William Hubbs
2023-07-20 19:33 William Hubbs
2023-04-23 21:34 William Hubbs
2023-04-14 15:23 William Hubbs
2023-04-13 0:55 Sam James
2023-04-13 0:55 Sam James
2023-04-13 0:55 Sam James
2023-04-07 17:48 William Hubbs
2023-01-05 5:39 William Hubbs
2023-01-05 5:05 Sam James
2023-01-03 19:34 William Hubbs
2023-01-03 19:16 Arthur Zamarin
2023-01-02 22:22 William Hubbs
2022-08-20 22:09 William Hubbs
2022-08-19 19:33 Arthur Zamarin
2022-08-15 7:42 Agostino Sarubbo
2022-08-15 7:40 Agostino Sarubbo
2022-08-14 22:46 William Hubbs
2022-05-17 14:52 William Hubbs
2022-04-14 22:40 William Hubbs
2022-04-09 19:46 Arthur Zamarin
2022-04-06 6:32 Agostino Sarubbo
2022-04-05 2:37 Sam James
2022-04-04 19:39 William Hubbs
2022-04-04 15:28 William Hubbs
2022-03-28 5:35 William Hubbs
2022-03-28 5:35 William Hubbs
2022-03-28 5:35 William Hubbs
2022-03-25 19:24 Sam James
2022-02-14 9:48 Jakov Smolić
2022-01-07 18:06 Georgy Yakovlev
2022-01-07 17:55 Georgy Yakovlev
2022-01-06 8:17 Georgy Yakovlev
2022-01-06 8:17 Georgy Yakovlev
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=1689983515.fc6e20d0588a11dc3b1ee91ebcfa77b9cbe1565e.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