Mick <[EMAIL PROTECTED]> wrote: >On 21/04/06, Neil Bothwick <[EMAIL PROTECTED]> wrote: >> On Fri, 21 Apr 2006 11:24:11 -0700, Richard Fish wrote: >> >> > > su -c "ebuild /path/to/slocate-2.7-r8.ebuild digest;emerge --verbose >> > > --ask slocate" >> >> or even "emerge --verbose --ask --digest slocate" >> >> > But do an emerge --sync first. The most likely cause of this is that >> > your last sync was done while the server was being updated, and you >> > got the updated manifest but not the ebuild. These kinds of problems >> > are almost always fixed by a new sync. Using the digest command is >> > overkill. >> >> Not to mention potentially dangerous. If the digest mismatch is a fault >> in portage, a sync will usually fix it. But if it is due to a compromised >> archive, redigesting removes that safety check. > >I don't think this is related, but this is what I got in the last >update to sys-apps/slocate-2.7-r8: >=================================== > The 'slocate' group has been renamed to 'locate'. > You seem to already have a 'slocate' group. > Please rename it: > groupmod -n locate slocate >=================================== >Renaming it allows the ebuild to complete as suggested.
I got that same error when I did the upgrade. Once I renamed it also, the ebuild completed fine. Jeff -- gentoo-user@gentoo.org mailing list
