From: "Walter Dnes" <waltdnes@waltdnes.org>
To: Gentoo Users List <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Emerge --sync fails on excluded stuff
Date: Mon, 22 Oct 2018 10:26:35 -0400 [thread overview]
Message-ID: <20181022142635.GA16830@waltdnes.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]
I have a 10 year old Core2 as an emergency backup machine. Let's just
say it's not as fast as modern machines. To speed up "emerge --sync". I
put a bunch of unneeded stuff in an "rsync_excludes" file (attached).
Now "emerge --sync" has started failing, because it obviously can't
verify the missing directories/files. Here's the error message...
* Manifest timestamp: 2018-10-22 13:08:41 UTC
* Valid OpenPGP signature found:
* - primary key: DCD05B71EAB94199527F44ACDB6B8C1F96D8BF6D
* - subkey: E1D6ABB63BFCFB4BA02FDF1CEC590EEAC9189250
* - timestamp: 2018-10-22 13:08:41 UTC
* Verifying /usr/portage/.tmp-unverified-download-quarantine ...!!! Manifest verification failed:
Manifest mismatch for app-dicts/Manifest.gz
__exists__: expected: True, have: False
app_dicts is the first entry in my "rsync_excludes", and I assume that
all the other entries would be problematic too. How do I turn off this
bleeping "helpful" verification feature?
--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
[-- Attachment #2: rsync_excludes.gz --]
[-- Type: application/octet-stream, Size: 476 bytes --]
next reply other threads:[~2018-10-22 14:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 14:26 Walter Dnes [this message]
2018-10-22 16:11 ` [gentoo-user] Emerge --sync fails on excluded stuff Kai Peter
2018-10-22 17:36 ` [gentoo-user] [SOLVED] " Walter Dnes
2018-10-22 22:21 ` Neil Bothwick
2018-10-23 3:05 ` Walter Dnes
2018-10-23 3:30 ` Dale
2018-10-23 7:21 ` Neil Bothwick
2018-10-23 15:13 ` Mick
2018-10-23 21:10 ` Neil Bothwick
2018-10-23 21:14 ` Walter Dnes
2018-10-23 21:30 ` Neil Bothwick
2018-10-23 22:32 ` Mick
2018-10-24 1:49 ` Walter Dnes
2018-10-24 7:28 ` Neil Bothwick
2018-10-24 8:26 ` Peter Humphrey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181022142635.GA16830@waltdnes.org \
--to=waltdnes@waltdnes.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox