... >>> md5 files ;-) files/digest-slocate-2.7-r8 >>> md5 src_uri ;-) slocate-2.7.tar.gz >>> md5 src_uri ;-) slocate-2.7-debian.patch.bz2 * The 'slocate' group has been renamed to 'locate'. I did : n22 / # grep locate /etc/group slocate:x:245: But a after that a manual command works: n22 / # groupmod -n locate slocate n22 / # grep locate /etc/group locate:x:245:
> But a after that a manual command works Uhm? That's what you are supposed to do... slocate-2.7-r8.ebuild <snip> if [[ -n $(egetent group slocate) ]] ; then eerror "The 'slocate' group has been renamed to 'locate'." eerror "You seem to already have a 'slocate' group." eerror "Please rename it:" eerror "groupmod -n locate slocate" die "Change 'slocate' to 'locate'" fi </snip> Also, how is this related to baselayout?
>Uhm? That's what you are supposed to do... Yes, I know, but the log says: "* The 'slocate' group has been renamed to 'locate'." But that was not true, look at the grep output. I had to rename the group manually.
(In reply to comment #2) > >Uhm? That's what you are supposed to do... > Yes, I know, but the log says: > "* The 'slocate' group has been renamed to 'locate'." Would you kindly read the *whole* message (as pasted above)?!
CLOSED.
*** Bug 130853 has been marked as a duplicate of this bug. ***
Does this 'solution' imply that going forard every Gentoo user will be required to run the groupmod command for every update of slocate that comes in the future? Interesting 'solution'... Thanks - the groupmod command does work.
(In reply to comment #6) > Does this 'solution' imply that going forard every Gentoo user will be required > to run the groupmod command for every update of slocate that comes in the > future? Interesting 'solution'... No, it obviously doesn't. It won't be an issue with any following release of slocate, until the group changes again.
