From: Alan Mackenzie <acm@muc.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: All sorts of digest verification failures
Date: Sun, 15 Nov 2015 11:01:53 +0000 [thread overview]
Message-ID: <20151115110153.GD1766@acm.fritz.box> (raw)
In-Reply-To: <2BE25BAB-1326-4F34-856D-DB87C08291BB@iki.fi>
Hello, Matti
On Sun, Nov 15, 2015 at 12:22:39PM +0200, Matti Nykyri wrote:
> > On Nov 15, 2015, at 11:59, Alan Mackenzie <acm@muc.de> wrote:
> >> On Thu, Nov 12, 2015 at 06:45:44PM +0200, Alan McKinnon wrote:
> >>> On 12/11/2015 18:42, Grant Edwards wrote:
> >>>> On 2015-11-12, <wabenbau@gmail.com> <wabenbau@gmail.com> wrote:
> >>>> Grant Edwards <grant.b.edwards@gmail.com> wrote:
> >>>>> After an emerge --sync that appeared to work with no problems, my
> >>>>> "emerge -auvND world" command is reporting that the Changelong files
> >>>>> are broken for about 2/3 of the packages it wants to update:
> > [ .... ]
> >> The dev are doing some $MAGIC to reinstate ChangeLogs and the first run
> >> is expected to take a while (i.e. several hours). I suppose you can
> >> expect some breakage till it finishes.
> >> It's being discussed and tracked on gentoo-dev, you can drop a mail
> >> there with specifics to let the devs know what's happening.
> > Three days later. I'm still getting this error message, but with a nasty
> > twist in the tail. emerge -puND @world reports (amongst others) the
> > following update:
> > [ebuild R ] sys-apps/busybox-1.23.1-r1 USE="-pam*"
> > , and the error message I get on actually trying to start the update is
> > !!! Digest verification failed:
> > !!! /usr/portage/sys-apps/busybox/busybox-9999.ebuild
> > !!! Reason: Filesize does not match recorded size
> > !!! Got: 8493
> > !!! Expected: 8580
> > . Why is the build system looking at the digest for version 9999 when it
> > should be rebuilding version 1.23.1-r1?
> Well it's not. It just checks all the manifests and complains about
> errors. It doesn't affect the building of 1.23.1-r1.
Ah, OK. But it causes emerge to bail out, so never gets round to
building 1.23.1-r1.
> If I were you I'ld download the latest portage snapshot. That should
> take care of any remaining issues. Is your portage upto date?
I'd just synched my portage tree immediately before attempting the build.
I'll try again tomorrow, in the hope everything will have been sorted out
by then.
> --
> -M
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2015-11-15 11:00 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 16:07 [gentoo-user] All sorts of digest verification failures Grant Edwards
2015-11-12 16:19 ` wabenbau
2015-11-12 16:42 ` [gentoo-user] " Grant Edwards
2015-11-12 16:45 ` Alan McKinnon
2015-11-12 16:54 ` Peter Humphrey
2015-11-15 9:59 ` Alan Mackenzie
2015-11-15 10:22 ` Matti Nykyri
2015-11-15 10:43 ` Peter Humphrey
2015-11-15 10:56 ` Matti Nykyri
2015-11-15 11:44 ` Peter Humphrey
2015-11-15 11:01 ` Alan Mackenzie [this message]
2015-11-15 11:15 ` Matti Nykyri
2015-11-15 19:33 ` Alan Mackenzie
2015-11-15 21:43 ` Matti Nykyri
2015-11-15 10:41 ` Neil Bothwick
2015-11-15 11:42 ` Neil Bothwick
2015-11-15 14:56 ` Martin Vaeth
2015-11-15 17:17 ` Neil Bothwick
2015-11-15 19:05 ` Martin Vaeth
2015-11-15 20:19 ` Dale
2015-11-15 20:29 ` covici
2015-11-15 21:02 ` Simon Thelen
2015-11-16 6:45 ` Martin Vaeth
2015-11-16 7:33 ` covici
2015-11-16 17:21 ` Martin Vaeth
2015-11-16 21:49 ` Marc Joliet
2015-11-16 22:32 ` Rich Freeman
2015-11-17 7:09 ` Marc Joliet
2015-11-15 20:43 ` Grant Edwards
2015-11-16 8:51 ` Dale
2015-11-16 1:39 ` walt
2015-11-16 9:33 ` Neil Bothwick
2015-11-16 9:48 ` Dale
2015-11-16 13:53 ` Neil Bothwick
2015-11-15 19:29 ` Alan Mackenzie
2015-11-12 16:59 ` Dale
2015-11-12 16:33 ` [gentoo-user] " Dale
2015-11-16 0:06 ` Dale
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=20151115110153.GD1766@acm.fritz.box \
--to=acm@muc.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