| 1 |
On Fri, 2010-09-17 at 18:23 -0700, Mark Knecht wrote: |
| 2 |
[...] |
| 3 |
> >>> Verifying ebuild manifests |
| 4 |
> |
| 5 |
> !!! Digest verification failed: |
| 6 |
> !!! /usr/portage/kde-base/ark/files/ark-4.4.5-cli7zip.patch |
| 7 |
> !!! Reason: Failed on RMD160 verification |
| 8 |
> !!! Got: 285b725e7542b78815f0f909a65b4b6ec20cee89 |
| 9 |
> !!! Expected: 57369a955bff3038ad0c105eea0179bbb795a030 |
| 10 |
> firefly ~ # |
| 11 |
> |
| 12 |
> Google isn't turning anything up. Normally these things get cleared |
| 13 |
> up within about a day but this time around I'm starting to wonder if I |
| 14 |
> have some other problem here and this is only a symptom? |
| 15 |
> |
| 16 |
> I'm sure there's some way I can get past it WRT emerge but I'd |
| 17 |
> rather get it handled at the source if possible. I though about |
| 18 |
> deleting things in the path shown above but I haven't ever removed |
| 19 |
> anything except distfiles and didn't want to start now. |
| 20 |
|
| 21 |
Why not? It's in your portage tree. Any deleted/altered files get |
| 22 |
replaced on the next --sync anyway. |
| 23 |
|
| 24 |
Having said that. My copy of the file indeed matches the manifest. So |
| 25 |
either you need to re --sync, delete the file and re --sync, or try |
| 26 |
syncing from a different mirror. |
Archives