From: n952162 <n952162@web.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge --sync keeps failing
Date: Mon, 2 Aug 2021 17:43:25 +0200 [thread overview]
Message-ID: <fd7411ed-bf5f-f72e-c5dd-539d3656bfde@web.de> (raw)
In-Reply-To: <2475063.Lt9SDvczpP@lenovo.localdomain>
On 8/2/21 2:01 PM, Michael wrote:
> On Monday, 2 August 2021 12:10:12 BST n952162 wrote:
>> On 8/1/21 8:32 PM, Michael Orlitzky wrote:
>>> On Sun, 2021-08-01 at 17:32 +0200, n952162 wrote:
>>>> * Verifying /var/db/repos/gentoo/.tmp-unverified-download-quarantine
>>>>
>>>> ...!!! Manifest verification failed:
>>>> Manifest mismatch for metadata/news/Manifest
>>>>
>>>> I've raised this question before and the only useful answer I got was to
>>>> keep trying
>>> On the off chance that something is screwy on the remote end, you can
>>> always use "emerge-webrsync" and delay the problem until next time.
>>>
>>> Otherwise, I would say check "dmesg" for disk errors, but if it's
>>> happening on two machines that's a lot less likely.
>> I have this problem every month. Why does it fail? Is it just a
>> timeout because my network is slow? Can that be tweaked?
> I get this problem over here, but on rare occasions. Leaving it for half a
> day usually fixes it. Have you tried a different rsync mirror? You can use
> 'mirrorselect -i -r' for this task.
Ah, good idea.
next prev parent reply other threads:[~2021-08-02 15:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 15:32 [gentoo-user] emerge --sync keeps failing n952162
2021-08-01 18:32 ` Michael Orlitzky
2021-08-02 7:20 ` n952162
2021-08-02 8:08 ` n952162
2021-08-02 11:02 ` Michael Orlitzky
2021-08-02 11:10 ` n952162
2021-08-02 12:01 ` Michael
2021-08-02 13:23 ` Dale
2021-08-02 15:43 ` n952162 [this message]
2021-08-02 21:17 ` Neil Bothwick
2021-08-02 22:42 ` Michael
2021-08-03 1:28 ` John Covici
2021-08-03 8:55 ` Michael
2021-08-03 10:49 ` Neil Bothwick
2021-08-03 10:51 ` Michael
2021-09-06 13:55 ` n952162
2021-08-04 13:19 ` Michael Orlitzky
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=fd7411ed-bf5f-f72e-c5dd-539d3656bfde@web.de \
--to=n952162@web.de \
--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