From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/ostree/
Date: Sat, 11 May 2024 14:38:17 +0000 (UTC) [thread overview]
Message-ID: <1715438293.3fc0f93ebc815727409fa8a20fe1977b4d097d15.arthurzam@gentoo> (raw)
commit: 3fc0f93ebc815727409fa8a20fe1977b4d097d15
Author: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sat May 11 14:38:13 2024 +0000
Commit: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sat May 11 14:38:13 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3fc0f93e
dev-util/ostree: Stabilize 2024.3 x86, #931753
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>
dev-util/ostree/ostree-2024.3.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-util/ostree/ostree-2024.3.ebuild b/dev-util/ostree/ostree-2024.3.ebuild
index 295c98e3a0b9..afe1ebc5584e 100644
--- a/dev-util/ostree/ostree-2024.3.ebuild
+++ b/dev-util/ostree/ostree-2024.3.ebuild
@@ -15,7 +15,7 @@ S="${WORKDIR}/lib${P}"
LICENSE="LGPL-2+"
SLOT="0"
-KEYWORDS="~amd64 ~arm ~arm64 ~loong ~ppc64 ~riscv ~x86"
+KEYWORDS="~amd64 ~arm ~arm64 ~loong ~ppc64 ~riscv x86"
IUSE="archive +curl doc dracut gnutls +gpg grub +http2 httpd introspection libmount selinux sodium ssl +soup systemd zeroconf"
RESTRICT="test"
REQUIRED_USE="
next reply other threads:[~2024-05-11 14:38 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-11 14:38 Arthur Zamarin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-20 14:32 [gentoo-commits] repo/gentoo:master commit in: dev-util/ostree/ Arthur Zamarin
2024-06-23 1:49 Sam James
2024-05-13 12:39 Arthur Zamarin
2024-05-11 15:16 Arthur Zamarin
2024-02-24 15:26 Arthur Zamarin
2023-12-08 11:08 Sam James
2023-12-08 9:58 Arthur Zamarin
2023-12-08 9:02 Arthur Zamarin
2023-07-09 13:03 Matt Turner
2023-07-07 21:22 Sam James
2023-06-22 17:46 Arthur Zamarin
2023-06-22 17:46 Arthur Zamarin
2023-06-22 17:46 Arthur Zamarin
2023-06-03 17:21 Arthur Zamarin
2023-05-10 18:30 Arthur Zamarin
2023-05-10 18:30 Arthur Zamarin
2023-05-10 0:29 Sam James
2023-05-01 5:29 Arthur Zamarin
2023-04-30 23:50 Sam James
2023-04-30 23:50 Sam James
2023-03-16 23:49 Zac Medico
2023-03-16 23:49 Zac Medico
2023-01-16 23:18 Zac Medico
2022-11-24 2:33 Zac Medico
2022-11-03 8:08 Agostino Sarubbo
2022-11-03 6:40 Sam James
2022-11-03 6:15 Sam James
2022-10-31 2:43 WANG Xuerui
2022-10-07 23:55 Zac Medico
2022-10-07 23:38 Zac Medico
2022-07-24 19:07 Zac Medico
2022-06-08 3:16 Zac Medico
2022-06-08 3:13 Zac Medico
2022-04-13 3:08 Zac Medico
2022-04-13 2:50 Zac Medico
2022-04-02 12:04 Arthur Zamarin
2022-04-01 15:17 Jakov Smolić
2022-04-01 15:17 Jakov Smolić
2022-03-05 0:22 Zac Medico
2022-02-16 22:11 David Seifert
2022-02-12 16:52 Zac Medico
2022-02-12 16:52 Zac Medico
2022-01-09 19:04 Zac Medico
2021-10-28 5:57 Zac Medico
2021-10-18 4:23 Zac Medico
2021-10-18 4:23 Zac Medico
2021-10-18 4:23 Zac Medico
2021-10-02 15:43 Sam James
2021-09-22 6:54 Agostino Sarubbo
2021-09-21 6:37 Agostino Sarubbo
2021-09-19 21:52 Zac Medico
2021-09-16 19:11 Sam James
2021-09-16 12:32 Marek Szuba
2021-08-18 14:59 Sam James
2021-08-04 21:01 Sam James
2021-07-30 0:31 Georgy Yakovlev
2021-05-02 17:56 Mikle Kolyada
2021-01-21 7:40 Agostino Sarubbo
2021-01-07 17:34 Sam James
2021-01-07 10:07 Sam James
2020-11-27 21:09 Zac Medico
2020-10-30 17:38 Zac Medico
2020-10-29 18:24 Georgy Yakovlev
2020-10-28 16:23 Sam James
2020-10-20 8:18 Sam James
2020-10-18 3:51 Zac Medico
2020-10-05 16:40 Zac Medico
2020-10-04 19:19 Zac Medico
2020-10-04 18:47 Zac Medico
2020-06-26 5:39 Zac Medico
2020-01-21 20:02 Zac Medico
2020-01-21 7:48 Zac Medico
2020-01-21 7:48 Zac Medico
2020-01-21 7:48 Zac Medico
2020-01-21 7:48 Zac Medico
2019-01-07 23:14 Zac Medico
2019-01-07 19:15 Lars Wendler
2018-11-28 3:57 Zac Medico
2018-06-05 1:48 Zac Medico
2018-06-03 20:45 Zac Medico
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=1715438293.3fc0f93ebc815727409fa8a20fe1977b4d097d15.arthurzam@gentoo \
--to=arthurzam@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