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 1FXDR8-0000az-5F for garchives@archives.gentoo.org; Sat, 22 Apr 2006 08:25:50 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.6/8.13.6) with SMTP id k3M8Og4o007852; Sat, 22 Apr 2006 08:24:42 GMT Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.235]) by robin.gentoo.org (8.13.6/8.13.6) with ESMTP id k3M8KdXN013408 for ; Sat, 22 Apr 2006 08:20:40 GMT Received: by wproxy.gmail.com with SMTP id i5so778543wra for ; Sat, 22 Apr 2006 01:20:38 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=YTwh1Nm49FdNgAbWmIpQiBnFbPTA6trWv2tKzRUrwUjvtI81fu2JkZ1QByCpqiZ3ah0vIC8zCkidprKvtG2Xglq168cTBwUUlFh3uglfxiWPsCsa7E/jS84lNswvnANCzmSjDzZpyrTPWtSEno3F2Wm0ih7yHmxJIsZUptUc4eY= Received: by 10.65.192.12 with SMTP id u12mr1620929qbp; Sat, 22 Apr 2006 01:20:38 -0700 (PDT) Received: from localhost ( [88.1.227.53]) by mx.gmail.com with ESMTP id q17sm421385qbq.2006.04.22.01.20.36; Sat, 22 Apr 2006 01:20:37 -0700 (PDT) Date: Sat, 22 Apr 2006 10:20:38 +0200 From: =?utf8?B?Sm9ow6FtLUx1w61zIE1pZ3XDqW5z?= Vila To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] What do I do about slocate 3.1/2.7 ? Message-ID: <20060422082038.GA16465@galiza_ceive> Mail-Followup-To: gentoo-user@lists.gentoo.org References: <1145603382.15597.26.camel@omc-2.omesc.com> <20060421154430.GA20265@galiza_ceive> <7573e9640604211124n14107a1u78f9c93aaed158a6@mail.gmail.com> <20060421222724.654a4ed0@krikkit.digimed.co.uk> 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: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="J/dobhs11T7y2rNN" Content-Disposition: inline In-Reply-To: <20060421222724.654a4ed0@krikkit.digimed.co.uk> User-Agent: Mutt/1.5.11 X-Archives-Salt: 9a8e6edd-680e-4ff6-9d80-4aafcb8179a5 X-Archives-Hash: 536163f088f93d76c03d786eb4327cf1 --J/dobhs11T7y2rNN Content-Type: text/plain; charset=utf8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 22:27 Fri 21 Apr , Neil Bothwick wrote: > On Fri, 21 Apr 2006 11:24:11 -0700, Richard Fish wrote: >=20 > > > su -c "ebuild /path/to/slocate-2.7-r8.ebuild digest;emerge --verbose > > > --ask slocate" >=20 > or even "emerge --verbose --ask --digest slocate" Didn't know about '--digest' switch... As I'm playing with some CVS/SVN overlays it's really useful for me. > > 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. >=20 > 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. >=20 Yes, It was definitely a bad bad answer by me. The "Files listed in the manifest do not exist" claims for a resync and not for a redigest. I rarely has sync issues . Whenever I had digest issues they were related t= o SVN/CVS overlays, so redigesting is safe there, AFAIK. My apologies to thread starter. Cheers. --=20 A ouvir (mpd): Dirty Three - Jim's Dog - GPG KeyID:0x9D2FD6C8 --J/dobhs11T7y2rNN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFESedWNlr/7p0v1sgRApzPAJ954Wmo7Sj8ESqvs8RWQI08UrAmJwCgknXs A2iuptNkLV1wb9AVCip/kh4= =pZri -----END PGP SIGNATURE----- --J/dobhs11T7y2rNN-- -- gentoo-user@gentoo.org mailing list