From: "WANG Xuerui" <xen0n@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: profiles/arch/base/
Date: Wed, 19 Oct 2022 11:00:23 +0000 (UTC) [thread overview]
Message-ID: <1666177055.0afbad121e56dcf973f0fe9757f4b065ecfbcecb.xen0n@gentoo> (raw)
commit: 0afbad121e56dcf973f0fe9757f4b065ecfbcecb
Author: WANG Xuerui <xen0n <AT> gentoo <DOT> org>
AuthorDate: Wed Oct 19 10:57:35 2022 +0000
Commit: WANG Xuerui <xen0n <AT> gentoo <DOT> org>
CommitDate: Wed Oct 19 10:57:35 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0afbad12
profiles/arch/base: sync USE=experimental-loong mask updates
The previous commit didn't update the base masks.
Fixes: d54b4d3d87d3b10a452b2996f18c31a70d0a9cea
Signed-off-by: WANG Xuerui <xen0n <AT> gentoo.org>
profiles/arch/base/package.use.mask | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/profiles/arch/base/package.use.mask b/profiles/arch/base/package.use.mask
index 26044840a092..fad744752618 100644
--- a/profiles/arch/base/package.use.mask
+++ b/profiles/arch/base/package.use.mask
@@ -31,9 +31,8 @@ media-libs/libva-intel-driver hybrid
# In the meantime, force-enable on loong only.
# This is not inside use.mask, because crossdev toolchain packages would
# want to have the flag enabled without hassle.
-dev-libs/libffi experimental-loong
-sys-kernel/linux-headers experimental-loong
-sys-libs/glibc experimental-loong
+<dev-libs/libffi-3.4.3 experimental-loong
+<sys-libs/glibc-2.36 experimental-loong
sys-libs/libseccomp experimental-loong
# James Le Cuirot <chewi@gentoo.org> (2022-02-24)
next reply other threads:[~2022-10-19 11:00 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 11:00 WANG Xuerui [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-05 16:29 [gentoo-commits] repo/gentoo:master commit in: profiles/arch/base/ Matt Turner
2025-04-22 0:41 Sam James
2025-04-10 8:37 Alexys Jacob
2025-01-24 10:51 Viorel Munteanu
2024-10-23 19:27 Viorel Munteanu
2024-09-18 18:12 Sam James
2024-09-13 12:57 Andreas Sturmlechner
2024-04-13 18:19 Mike Gilbert
2023-10-28 21:46 Sam James
2023-10-27 3:20 Sam James
2023-10-27 2:59 Sam James
2023-10-27 2:34 Sam James
2022-12-04 22:21 Georgy Yakovlev
2022-08-15 1:19 John Helmert III
2022-04-24 1:58 WANG Xuerui
2021-11-07 5:27 Georgy Yakovlev
2021-08-27 10:50 Lars Wendler
2021-08-05 22:08 Ionen Wolkens
2021-07-12 7:00 Sam James
2021-07-10 10:06 Ionen Wolkens
2021-06-21 22:26 Sam James
2021-06-12 5:18 Sam James
2021-01-02 22:33 David Seifert
2020-12-18 14:17 Fabian Groffen
2020-09-20 16:16 Sam James
2020-09-20 16:16 Sam James
2020-09-11 16:17 Andreas K. Hüttel
2020-08-24 23:02 Georgy Yakovlev
2020-06-06 0:34 Andreas Sturmlechner
2020-05-02 11:29 Ulrich Müller
2020-04-26 15:57 Georgy Yakovlev
2019-08-28 8:33 Georgy Yakovlev
2019-07-16 17:02 Matt Turner
2019-06-23 3:19 Georgy Yakovlev
2019-05-03 21:49 Andreas K. Hüttel
2018-05-28 16:02 Nick Sarnie
2018-05-27 10:43 Mikle Kolyada
2018-05-02 1:33 Nick Sarnie
2018-05-01 2:57 Nick Sarnie
2018-04-30 3:13 Nick Sarnie
2018-04-30 1:57 Nick Sarnie
2017-12-30 11:49 Michał Górny
2017-12-30 10:16 Michał Górny
2017-11-24 5:05 Matt Turner
2017-09-21 17:03 Michał Górny
2017-08-31 21:13 Alon Bar-Lev
2017-08-31 20:02 Alon Bar-Lev
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=1666177055.0afbad121e56dcf973f0fe9757f4b065ecfbcecb.xen0n@gentoo \
--to=xen0n@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