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 1FX3Kq-0002nT-Qt for garchives@archives.gentoo.org; Fri, 21 Apr 2006 21:38:41 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.6/8.13.6) with SMTP id k3LLZGPK014511; Fri, 21 Apr 2006 21:35:16 GMT Received: from rutherford.zen.co.uk (rutherford.zen.co.uk [212.23.3.142]) by robin.gentoo.org (8.13.6/8.13.6) with ESMTP id k3LLRUeo000435 for ; Fri, 21 Apr 2006 21:27:31 GMT Received: from [82.69.83.178] (helo=desiato.digimed.co.uk) by rutherford.zen.co.uk with esmtp (Exim 4.34) id 1FX3A2-0006kR-Jx for gentoo-user@lists.gentoo.org; Fri, 21 Apr 2006 21:27:30 +0000 Received: from krikkit.digimed.co.uk (krikkit.digimed.co.uk [192.168.1.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by desiato.digimed.co.uk (Postfix) with ESMTP id CE06914001AF for ; Fri, 21 Apr 2006 22:27:25 +0100 (BST) Date: Fri, 21 Apr 2006 22:27:24 +0100 From: Neil Bothwick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] What do I do about slocate 3.1/2.7 ? Message-ID: <20060421222724.654a4ed0@krikkit.digimed.co.uk> In-Reply-To: <7573e9640604211124n14107a1u78f9c93aaed158a6@mail.gmail.com> References: <1145603382.15597.26.camel@omc-2.omesc.com> <20060421154430.GA20265@galiza_ceive> <7573e9640604211124n14107a1u78f9c93aaed158a6@mail.gmail.com> Organization: Digital Media Production X-Mailer: Sylpheed-Claws 2.1.1 (GTK+ 2.8.13; powerpc-unknown-linux-gnu) X-GPG-Fingerprint: 7260 0F33 97EC 2F1E 7667 FE37 BA6E 1A97 4375 1903 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; boundary=Sig_ug+UHFHt6x1St0ua5OHZQQg; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-Originating-Rutherford-IP: [82.69.83.178] X-Archives-Salt: 7f53f9e2-333a-4d38-9df2-9fbde93e1bd8 X-Archives-Hash: 577107493e4e928bef2c277839135f4c --Sig_ug+UHFHt6x1St0ua5OHZQQg Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable 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. --=20 Neil Bothwick If your VCR still flashes 12:00 - then Linux is not for you. --Sig_ug+UHFHt6x1St0ua5OHZQQg Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFESU48um4al0N1GQMRAjiIAJwLV2ETaKdHDRBm0N28IZ2POvuWeQCgxq0V FsXmqHXB8Zszh74WVy9rKZE= =b4me -----END PGP SIGNATURE----- --Sig_ug+UHFHt6x1St0ua5OHZQQg-- -- gentoo-user@gentoo.org mailing list