| 1 |
On Fri, 21 Apr 2006 11:24:11 -0700, Richard Fish wrote: |
| 2 |
|
| 3 |
> > su -c "ebuild /path/to/slocate-2.7-r8.ebuild digest;emerge --verbose |
| 4 |
> > --ask slocate" |
| 5 |
|
| 6 |
or even "emerge --verbose --ask --digest slocate" |
| 7 |
|
| 8 |
> But do an emerge --sync first. The most likely cause of this is that |
| 9 |
> your last sync was done while the server was being updated, and you |
| 10 |
> got the updated manifest but not the ebuild. These kinds of problems |
| 11 |
> are almost always fixed by a new sync. Using the digest command is |
| 12 |
> overkill. |
| 13 |
|
| 14 |
Not to mention potentially dangerous. If the digest mismatch is a fault |
| 15 |
in portage, a sync will usually fix it. But if it is due to a compromised |
| 16 |
archive, redigesting removes that safety check. |
| 17 |
|
| 18 |
|
| 19 |
-- |
| 20 |
Neil Bothwick |
| 21 |
|
| 22 |
If your VCR still flashes 12:00 - then Linux is not for you. |
Archives