Summary: | emerge --sync fails with "gpg: Fatal: getentropy is not supported: Function not implemented" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Vincent Le Ligeour <gentoo> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Vincent Le Ligeour
2022-11-18 07:46:07 UTC
If running an old kernel, please try USE=-getentropy on dev-libs/libgcrypt. ``` commit 8bacde9ab38c268737a14ffa2c5c239c406d23d8 Author: Mike Gilbert <floppym@gentoo.org> Date: Fri Nov 4 11:55:40 2022 -0400 dev-libs/libgcrypt: add kernel version check for getentropy Signed-off-by: Mike Gilbert <floppym@gentoo.org> commit 8c19036cac71bf2b45459cc7d66b5985e2956c69 Author: Mike Gilbert <floppym@gentoo.org> Date: Fri Nov 4 11:34:10 2022 -0400 dev-libs/libgcrypt: add 'getentropy' USE flag This allows for explicit control of the --enable-random configure option. Signed-off-by: Mike Gilbert <floppym@gentoo.org> ``` (I am wondering if we should change it to USE=old-kernel like Qt has, because at least then it's something somewhat obvious to set if you're on something ancient.) Hello, Indeed the timestamp of my Manifest is exactly during the time the tree was broken (not possible to sync the tree anymore after libgcrypt update): TIMESTAMP 2022-11-01T23:09:46Z By downloading the latest version of the ebuild from git (https://gitweb.gentoo.org/repo/gentoo.git/plain/dev-libs/libgcrypt/libgcrypt-1.10.1-r2.ebuild?id=8bacde9ab38c268737a14ffa2c5c239c406d23d8) and rebuilding the ebuild's digest, compilation is fine: - error by default (telling that getentropy is not supported for old kernels), - compiles correctly with USE=-getentropy, - emerge --sync then works correctly. |