Gentoo Archives: gentoo-user

From: Neil Bothwick <neil@××××××××××.uk>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Re: All sorts of digest verification failures
Date: Sun, 15 Nov 2015 17:17:51
Message-Id: 20151115171735.4fd31dc3@digimed.co.uk
In Reply to: [gentoo-user] Re: All sorts of digest verification failures by Martin Vaeth
1 On Sun, 15 Nov 2015 14:56:42 +0000 (UTC), Martin Vaeth wrote:
2
3 > > !!! /usr/portage/sys-apps/busybox/busybox-9999.ebuild
4 > > !!! Got: 8493
5 > > !!! Expected: 8580
6 >
7 > Do you use the default (rsync) for syncing, or have you changed
8 > the method?
9 >
10 > I have the above claimed filesize (8493), but the Manifest
11 > I obtained from rsync is correct.
12 >
13 > The timestamp of the Manifest file in that folder is
14 > Nov 13, 08:17:31 (UTC)
15 > (do not forget to export TZ=UTC when you check the date).
16 > Exactly the same date has the ChangeLog file in that folder
17 > (which is not surprsing).
18 >
19 > If in your case ChangeLog and Manifest *both* have an older date,
20 > you got the data perhaps from an outdated mirror.
21 >
22
23 I deleted the busybox directory from the tree then ran emerge --sync. The
24 error is still there
25
26 -rw-r--r-- 1 root root 8388 Aug 9 21:34 busybox-1.21.0.ebuild
27 -rw-r--r-- 1 root root 8573 Aug 9 21:34 busybox-1.23.1.ebuild
28 -rw-r--r-- 1 root root 8611 Aug 9 21:34 busybox-1.23.1-r1.ebuild
29 -rw-r--r-- 1 root root 8724 Aug 9 21:34 busybox-1.23.2.ebuild
30 -rw-r--r-- 1 root root 8577 Nov 13 06:01 busybox-1.24.1.ebuild
31 -rw-r--r-- 1 root root 8493 Nov 13 06:01 busybox-9999.ebuild
32 -rw-r--r-- 1 root root 4402 Nov 13 07:17 ChangeLog
33 -rw-r--r-- 1 root root 60228 Nov 9 05:01 ChangeLog-2015
34 drwxr-xr-x 1 root root 1528 Nov 15 17:15 files
35 -rw-r--r-- 1 root root 19287 Nov 13 07:17 Manifest
36 -rw-r--r-- 1 root root 788 Aug 24 22:01 metadata.xml
37
38 --
39 Neil Bothwick
40
41 Our bikinis are exciting. They are simply the tops.

Replies

Subject Author
[gentoo-user] Re: All sorts of digest verification failures Martin Vaeth <martin@×××××.de>