From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 13EBF1384B4 for ; Thu, 12 Nov 2015 16:55:06 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AE02021C257; Thu, 12 Nov 2015 16:54:58 +0000 (UTC) Received: from smarthost03d.mail.zen.net.uk (smarthost03d.mail.zen.net.uk [212.23.1.23]) by pigeon.gentoo.org (Postfix) with ESMTP id 7D23321C23E for ; Thu, 12 Nov 2015 16:54:57 +0000 (UTC) Received: from [82.69.80.10] (helo=wstn.localnet) by smarthost03d.mail.zen.net.uk with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1Zwv9E-0000a5-Ow for gentoo-user@lists.gentoo.org; Thu, 12 Nov 2015 16:54:56 +0000 From: Peter Humphrey To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: All sorts of digest verification failures Date: Thu, 12 Nov 2015 16:54:56 +0000 Message-ID: <1591639.SLE7aWMN0n@wstn> User-Agent: KMail/4.14.8 (Linux/4.1.12-gentoo; KDE/4.14.8; x86_64; ; ) In-Reply-To: <5644C238.6040008@gmail.com> References: <5644C238.6040008@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Originating-smarthost03d-IP: [82.69.80.10] X-Archives-Salt: 7a3a3e10-3041-46db-9f08-a5a3d7cce6d2 X-Archives-Hash: 8d34b92b97aa05d7661f0a082892df22 On Thursday 12 Nov 2015 18:45:44 Alan McKinnon wrote: > On 12/11/2015 18:42, Grant Edwards wrote: > > On 2015-11-12, wrote: > >> Grant Edwards 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: > >>> > >>> !!! Digest verification failed: > >>> !!! /usr/portage/dev-libs/libxml2/ChangeLog > >>> !!! Reason: Filesize does not match recorded size > >>> !!! Got: 5221 > >>> !!! Expected: 5038 > >>> > >>> !!! Digest verification failed: > >>> !!! /usr/portage/app-text/iso-codes/ChangeLog > >>> !!! Reason: Filesize does not match recorded size > >>> !!! Got: 4195 > >>> !!! Expected: 4014 > >>> > >>> [ ... and so on for another dozen or so packages ... ] > >>> > >>> I removed the emerge timestamp, sync'ed again, and got the same > >>> result. Based on past experiences, I'm guessing that if I wait a day > >>> or two and sync again the problems will go away. > >>> > >>> But I am curious what causes these temporary breakages. Does anybody > >>> know how this happens? > >> > >> Try it again. I just synced and received new Manifest and Changelog > >> files for every(?) package of the portage tree. But no report of bad > >> digest. > > > > Just for fun, I removed the files from the portage tree that were > > reported as bad, and did another sync. Apparently, the rsync host > > that got chosen that time had just been updated, because it downloaded > > 313 files (I didn't pay much attention to which files exactly), and > > now emerge is happy again. > > > > I assume that the portage trees on the rsync servers from my first two > > attempts were in some intermediate state with new manifist files and > > old ChangeLog files or vice versa. > > > > In the past I've wondered how portage tree updates and rsync servers > > are managed so that people don't run into problems like this more > > often. > > 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. Yes, and I got 74,000 files transferred this morning. And yesterday a couple of manifests were wrong, but they were corrected soon enough. > 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. -- Rgds Peter