From: Kai Peter <kp@lists.openqmail.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Portage verification fails on games-action
Date: Fri, 08 Jun 2018 07:42:02 +0200 [thread overview]
Message-ID: <342a828835b49e6370d109e00f8a9440@lists.openqmail.org> (raw)
In-Reply-To: <20180607220527.07082123@phoucgh.digimed.co.uk>
On 2018-06-07 23:05, Neil Bothwick wrote:
> On Wed, 06 Jun 2018 16:38:52 +0100, Mick wrote:
>
>> Your pointer for RSYNC* proved useful. At some point in the past I
>> must have decided rsync was taking an awful long time sync'ing the
>> games directories. Since I don't emerge or play games I had added this
>> entry in my make.conf:
>>
>> $ grep RSYNC_ /etc/make.conf
>> PORTAGE_RSYNC_RETRIES="3"
>> PORTAGE_RSYNC_EXTRA_OPTS="--exclude-from=/etc/portage/rsync_excludes"
>>
>> $ cat /etc/portage/rsync_excludes
>> games-*/*
>
> I wondered if it might be something like that.
>
>> Once I commented this option out the verification succeeded. So ...
>> this verification problem seems to be caused by my intentional
>> exclusion of games from sync'ing.
>>
>> Does this mean I won't be able to exclude games hereafter if I want to
>> verify portage's contents, or is there a different approach required?
>
> As long as it only fails on verification of games-* I don't see a
> problem, unless you are relying on a zero return code from emerge
> --sync.
>
> Does gasmes-* still take a long time to sync? I wouldn't have thought
> there would be a lot of changes in there compared with other sections,
> such as kde-*.
I got the same issue and it doesn't depend on games*. Verification fails
at the first excluded category in the order listed in the metamanifest.
regards
Kai
--
Sent with eQmail-1.11 beta
prev parent reply other threads:[~2018-06-08 5:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 8:23 [gentoo-user] Portage verification fails on games-action Mick
2018-06-06 8:58 ` hitachi303
2018-06-06 9:33 ` Mick
2018-06-06 12:18 ` Neil Bothwick
2018-06-06 15:38 ` Mick
2018-06-07 21:05 ` Neil Bothwick
2018-06-07 22:42 ` Mick
2018-06-07 23:05 ` Neil Bothwick
2018-06-08 5:42 ` Kai Peter [this message]
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=342a828835b49e6370d109e00f8a9440@lists.openqmail.org \
--to=kp@lists.openqmail.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