From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] What do I do about slocate 3.1/2.7 ?
Date: Fri, 21 Apr 2006 22:27:24 +0100 [thread overview]
Message-ID: <20060421222724.654a4ed0@krikkit.digimed.co.uk> (raw)
In-Reply-To: <7573e9640604211124n14107a1u78f9c93aaed158a6@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
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.
--
Neil Bothwick
If your VCR still flashes 12:00 - then Linux is not for you.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-04-21 21:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 7:09 [gentoo-user] What do I do about slocate 3.1/2.7 ? Jules Colding
2006-04-21 7:40 ` Thomas Kear
2006-04-21 15:44 ` Johám-Luís Miguéns Vila
2006-04-21 18:24 ` Richard Fish
2006-04-21 19:00 ` Johám-Luís Miguéns Vila
2006-04-21 21:27 ` Neil Bothwick [this message]
2006-04-22 8:20 ` Johám-Luís Miguéns Vila
2006-04-22 8:28 ` Mick
2006-04-22 14:37 ` [gentoo-user] " Jeff Grossman
2006-04-24 8:10 ` [gentoo-user] " Jules Colding
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060421222724.654a4ed0@krikkit.digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox