From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1FXJK7-00078b-57 for garchives@archives.gentoo.org; Sat, 22 Apr 2006 14:42:59 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.6/8.13.6) with SMTP id k3MEfsPj001365; Sat, 22 Apr 2006 14:41:54 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.6/8.13.6) with ESMTP id k3MEbmmD028669 for ; Sat, 22 Apr 2006 14:37:48 GMT Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by smtp.gentoo.org with esmtp (Exim 4.54) id 1FXJF6-00017d-1s for gentoo-user@lists.gentoo.org; Sat, 22 Apr 2006 14:37:48 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FXJF4-0002Od-47 for gentoo-user@gentoo.org; Sat, 22 Apr 2006 16:37:46 +0200 Received: from cip-68-208.bbs.surfcity.net ([66.116.68.208]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 22 Apr 2006 16:37:46 +0200 Received: from jeff by cip-68-208.bbs.surfcity.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 22 Apr 2006 16:37:46 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Jeff Grossman Subject: [gentoo-user] Re: What do I do about slocate 3.1/2.7 ? Date: Sat, 22 Apr 2006 07:37:40 -0700 Organization: Stikman.com Message-ID: References: <1145603382.15597.26.camel@omc-2.omesc.com> <20060421154430.GA20265@galiza_ceive> <7573e9640604211124n14107a1u78f9c93aaed158a6@mail.gmail.com> <20060421222724.654a4ed0@krikkit.digimed.co.uk> <358eca8f0604220128r5a583317ia862f1b8fc69f74b@mail.gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: cip-68-208.bbs.surfcity.net X-Newsreader: Forte Agent 3.3/32.846 Sender: news X-Archives-Salt: addf1c62-ce12-4ca8-9cfd-72a71538d5d5 X-Archives-Hash: cca2978afa1c9bd287bcd65fc9fc948b Mick wrote: >On 21/04/06, Neil Bothwick 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