| 1 |
On 2018-10-22 16:26, Walter Dnes wrote: |
| 2 |
> I have a 10 year old Core2 as an emergency backup machine. Let's just |
| 3 |
> say it's not as fast as modern machines. To speed up "emerge --sync". |
| 4 |
> I |
| 5 |
> put a bunch of unneeded stuff in an "rsync_excludes" file (attached). |
| 6 |
> Now "emerge --sync" has started failing, because it obviously can't |
| 7 |
> verify the missing directories/files. Here's the error message... |
| 8 |
> |
| 9 |
> * Manifest timestamp: 2018-10-22 13:08:41 UTC |
| 10 |
> * Valid OpenPGP signature found: |
| 11 |
> * - primary key: DCD05B71EAB94199527F44ACDB6B8C1F96D8BF6D |
| 12 |
> * - subkey: E1D6ABB63BFCFB4BA02FDF1CEC590EEAC9189250 |
| 13 |
> * - timestamp: 2018-10-22 13:08:41 UTC |
| 14 |
> * Verifying /usr/portage/.tmp-unverified-download-quarantine ...!!! |
| 15 |
> Manifest verification failed: |
| 16 |
> Manifest mismatch for app-dicts/Manifest.gz |
| 17 |
> __exists__: expected: True, have: False |
| 18 |
> |
| 19 |
> |
| 20 |
> app_dicts is the first entry in my "rsync_excludes", and I assume |
| 21 |
> that |
| 22 |
> all the other entries would be problematic too. How do I turn off this |
| 23 |
> bleeping "helpful" verification feature? |
| 24 |
|
| 25 |
It fails at the first exclude entry always - I wrote this already. The |
| 26 |
whole manifest verification is buggy like hell - not well deliberated. |
| 27 |
Even if you sync from a local mirror it loads the key from the default |
| 28 |
key server. My suggestion is to disable it if you don't stay with the |
| 29 |
default. |
| 30 |
|
| 31 |
-- |
| 32 |
Sent with eQmail-1.11 beta - a fork of djb's famous qmail |
Archives