From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Any reason for "Missing digest" errors at the moment
Date: Mon, 13 Nov 2017 11:37:15 +0100 [thread overview]
Message-ID: <4940018.abLzzg2TFq@eve> (raw)
In-Reply-To: <oubfqp$4it$1@blaine.gmane.org>
On Monday, November 13, 2017 7:58:48 AM CET Nikos Chantziaras wrote:
> On 13/11/17 06:43, Andrew Lowe wrote:
> > Hi all,
> >
> > I've just done an "eix-sync" and upon doing "emerge -NuD world", get a
> >
> > few screen fulls of:
> > Missing digest for '/usr/portage/.....
> >
> > where the packages are mostly from kde-frameworks, -5.40.0, and a few
> > from kde-apps, -17.08.3.
> >
> > Has anyone else seen this?
>
> Was getting it too from time to time. I switched from rsync to git and
> it never happened again.
That's one option.
Also make sure the sync succeeded and didn't fail due to insufficient disk-
space. (The git-option requires more diskspace)
--
Joost
prev parent reply other threads:[~2017-11-13 10:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 4:43 [gentoo-user] Any reason for "Missing digest" errors at the moment Andrew Lowe
2017-11-13 6:58 ` [gentoo-user] " Nikos Chantziaras
2017-11-13 10:37 ` J. Roeleveld [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=4940018.abLzzg2TFq@eve \
--to=joost@antarean.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