| 1 |
On Sat, 07 Mar 2009 15:54:22 -0600, Dale wrote: |
| 2 |
|
| 3 |
> > wait 24 hours, resync, try again. |
| 4 |
> > |
| 5 |
> > Or just re-digest the package manually: |
| 6 |
> > |
| 7 |
> > ebuild <path_to_ebuild_file> manifest |
| 8 |
|
| 9 |
Bear in mind this overrides the security that digests provide, although |
| 10 |
it is harmless when it is only a Chnagleog file. |
| 11 |
|
| 12 |
> Does emerge --digest still exist? I recall using something like that a |
| 13 |
> long time ago. I think I used it for googleforearth which never |
| 14 |
> matches. |
| 15 |
|
| 16 |
That's not a good idea as the mismatch could be caused by a hacked |
| 17 |
source or binary file. The problem with Google Earth was that they used |
| 18 |
unversioned tarballs. Whenever you gt a digest error on a distfile, the |
| 19 |
first step is to delete the distfile and let emerge download it again. If |
| 20 |
that doesn't help, resync and then check Bugzilla. Don't redigest a |
| 21 |
distfile unless you can e 100% certain of its validity. |
| 22 |
|
| 23 |
|
| 24 |
-- |
| 25 |
Neil Bothwick |
| 26 |
|
| 27 |
Klingons do NOT sweat! They perspire with honour! |
Archives