| 1 |
On Sat, Sep 18, 2010 at 1:13 AM, Albert Hopkins <marduk@×××××××××××.org> wrote: |
| 2 |
> On Fri, 2010-09-17 at 18:23 -0700, Mark Knecht wrote: |
| 3 |
> [...] |
| 4 |
>> >>> Verifying ebuild manifests |
| 5 |
>> |
| 6 |
>> !!! Digest verification failed: |
| 7 |
>> !!! /usr/portage/kde-base/ark/files/ark-4.4.5-cli7zip.patch |
| 8 |
>> !!! Reason: Failed on RMD160 verification |
| 9 |
>> !!! Got: 285b725e7542b78815f0f909a65b4b6ec20cee89 |
| 10 |
>> !!! Expected: 57369a955bff3038ad0c105eea0179bbb795a030 |
| 11 |
>> firefly ~ # |
| 12 |
>> |
| 13 |
>> Google isn't turning anything up. Normally these things get cleared |
| 14 |
>> up within about a day but this time around I'm starting to wonder if I |
| 15 |
>> have some other problem here and this is only a symptom? |
| 16 |
>> |
| 17 |
>> I'm sure there's some way I can get past it WRT emerge but I'd |
| 18 |
>> rather get it handled at the source if possible. I though about |
| 19 |
>> deleting things in the path shown above but I haven't ever removed |
| 20 |
>> anything except distfiles and didn't want to start now. |
| 21 |
> |
| 22 |
> Why not? It's in your portage tree. Any deleted/altered files get |
| 23 |
> replaced on the next --sync anyway. |
| 24 |
> |
| 25 |
> Having said that. My copy of the file indeed matches the manifest. So |
| 26 |
> either you need to re --sync, delete the file and re --sync, or try |
| 27 |
> syncing from a different mirror. |
| 28 |
|
| 29 |
Thanks Albert. It worked and the problem is gone. |
| 30 |
|
| 31 |
In a related way I've never stopped to look at /usr in the process of |
| 32 |
doing an install. I have an old Mac Mini that I've been trying to get |
| 33 |
Gentoo running on recently so in the middle of my install this morning |
| 34 |
I stopped after untarring the stage-3 tarball and before untarring the |
| 35 |
portage snapshot and found that /usr/portage doesn't exist at that |
| 36 |
point. |
| 37 |
|
| 38 |
Does this suggest that I'm actually free at any time to rm -r |
| 39 |
/usr/portage and just untar the current snapshot? Other than distfiles |
| 40 |
and the overhead of downloading all that stuff again is there anything |
| 41 |
in /usr/portage that once erased would damage the machine? |
| 42 |
|
| 43 |
I can always get most of distfile from other machines around here so |
| 44 |
it's really a question as to whether portage and emerge build anything |
| 45 |
in /usr/portage that cannot be recreated without much trouble. |
| 46 |
|
| 47 |
Thanks again, |
| 48 |
Mark |
Archives