From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: profiles/features/prefix/standalone/
Date: Sat, 4 Mar 2023 02:23:20 +0000 (UTC) [thread overview]
Message-ID: <1677896561.8d8e2619bd8d6edf4e95ed33b664765b0db9dc8c.sam@gentoo> (raw)
commit: 8d8e2619bd8d6edf4e95ed33b664765b0db9dc8c
Author: Bart Oldeman <bart.oldeman <AT> calculquebec <DOT> ca>
AuthorDate: Fri Mar 3 03:27:50 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Mar 4 02:22:41 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8d8e2619
profiles/features/prefix/standalone: mask getentropy
When bootstrapping on a 3.10 kernel (e.g. CentOS 7.x), libgcrypt notes the following:
```
* Messages for package dev-libs/libgcrypt-1.10.1-r3:
* The getentropy function requires the getrandom syscall.
* This was introduced in Linux 3.17.
* Your system is currently running Linux 3.10.0-1160.45.1.el7.x86_64.
* Disable the 'getentropy' USE flag or upgrade your kernel.
* ERROR: dev-libs/libgcrypt-1.10.1-r3::gentoo failed (pretend phase):
* Kernel is too old for getentropy
```
Since without getrandom it will do a runtime check it's ok to mask.
Signed-off-by: Bart Oldeman <bart.oldeman <AT> calculquebec.ca>
Closes: https://github.com/gentoo/gentoo/pull/29906
Signed-off-by: Sam James <sam <AT> gentoo.org>
profiles/features/prefix/standalone/package.use.mask | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/profiles/features/prefix/standalone/package.use.mask b/profiles/features/prefix/standalone/package.use.mask
index 6c81333b0b2a..cb74107fef3b 100644
--- a/profiles/features/prefix/standalone/package.use.mask
+++ b/profiles/features/prefix/standalone/package.use.mask
@@ -1,6 +1,10 @@
-# Copyright 1999-2019 Gentoo Authors
+# Copyright 1999-2023 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
+# Bart Oldeman <bart.oldeman@calculquebec.ca> (2022-03-02)
+# getentropy requires >=linux=3.17 for __NR_getrandom
+dev-libs/libgcrypt getentropy
+
# Georgy Yakovlev <gyakovlev@gentoo.org> (2021-01-19)
# uchardet not stable/keyworded yet on this profile keyword
# bug #750032
next reply other threads:[~2023-03-04 2:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 2:23 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-11 22:39 [gentoo-commits] repo/gentoo:master commit in: profiles/features/prefix/standalone/ James Le Cuirot
2023-02-11 22:28 James Le Cuirot
2022-06-29 14:29 Sam James
2021-07-15 16:53 Benda XU
2021-06-07 15:23 Guilherme Amadio
2020-05-11 7:17 Benda XU
2020-02-12 12:16 Benda XU
2019-10-09 11:33 Benda XU
2019-10-09 10:54 Benda XU
2019-01-26 11:22 Benda XU
2018-11-15 13:38 Guilherme Amadio
2018-07-05 17:39 Guilherme Amadio
2017-08-22 11:59 Benda XU
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=1677896561.8d8e2619bd8d6edf4e95ed33b664765b0db9dc8c.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