* ERROR: acct-group/rtkit-0::gentoo failed (preinst phase): * enewgroup: GID 133 already taken * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_libressl-abi32+64-test_20190624-213954 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-8.3.1 [2] x86_64-pc-linux-gnu-9.1.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) Available Rust versions: [1] rust-1.35.0 * emerge -qpvO acct-group/rtkit [ebuild N ] acct-group/rtkit-0
Created attachment 581666 [details] emerge-info.txt
Created attachment 581668 [details] acct-group:rtkit-0:20190701-115553.log
Created attachment 581670 [details] emerge-history.txt
Created attachment 581672 [details] environment
Created attachment 581674 [details] etc.portage.tbz2
Created attachment 581676 [details] logs.tbz2
According to https://wiki.gentoo.org/wiki/Project:Quality_Assurance/UID_GID_Assignment GID allocation for 'rtkit' is correct so it is likely a conflict with a group created prior to introduction of GLEP 81.
*** This bug has been marked as a duplicate of bug 689102 ***
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=37079e4844246bbae7fea3204c2b3e8e8e24a9a5 commit 37079e4844246bbae7fea3204c2b3e8e8e24a9a5 Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2019-07-08 13:06:35 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2019-07-09 13:29:40 +0000 acct-group.eclass: Do not enforce GID unless requested Correct the enewgroup call not to enforce specified GID unless ACCT_GROUP_ENFORCE_ID is set. Reported-by: Toralf Förster <toralf@gentoo.org> Tested-by: Marek Szuba <marecki@gentoo.org> Closes: https://bugs.gentoo.org/689100 Signed-off-by: Michał Górny <mgorny@gentoo.org> eclass/acct-group.eclass | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
