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 A505D1384B4 for ; Thu, 12 Nov 2015 16:59:47 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6BBC021C23A; Thu, 12 Nov 2015 16:59:39 +0000 (UTC) Received: from mail-yk0-f182.google.com (mail-yk0-f182.google.com [209.85.160.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 46BA821C05B for ; Thu, 12 Nov 2015 16:59:38 +0000 (UTC) Received: by ykdv3 with SMTP id v3so101865966ykd.0 for ; Thu, 12 Nov 2015 08:59:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-type:content-transfer-encoding; bh=MzkGZ8TQNSBiE93GDn2liHtqKYEX11CNDkWMzy7oQLQ=; b=jNM4gb4YAWNdTMEohEcpJy0L/RempJFMUv3SdOlITTRgvDL98w2sS0WQ+tdxIfbPlt hmbs9owWwG5IFQvDQJ3kFuclq1rDfAt5C9kRkqEoCOzSiuW8j0w7QrRCpfV1Rrdbziso XPFEHc5+7+H2LbGLYyf3+tYSjMeqCL857DNgXmZbI88TlRzkGzZGG7VqnIhu1dPuBDqr zA7RGfmnFxbIPe/CXrPioGNa6zk7WcDTFUA1AxMuAfsdVbW0lJfXDscv0pfdhDsXdMUC t+OJkNXCt8YPdaXJC15fQNJGoWzwW2/nTkMhlYyaHRlRdKlgV9kyiHGhtAzdixbyYZIa 2cmw== X-Received: by 10.129.115.139 with SMTP id o133mr15461240ywc.172.1447347577602; Thu, 12 Nov 2015 08:59:37 -0800 (PST) Received: from [192.168.2.5] (adsl-65-0-116-226.jan.bellsouth.net. [65.0.116.226]) by smtp.gmail.com with ESMTPSA id e64sm16146815ywb.25.2015.11.12.08.59.35 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Nov 2015 08:59:36 -0800 (PST) Subject: Re: [gentoo-user] Re: All sorts of digest verification failures To: gentoo-user@lists.gentoo.org References: <20151112171903.68e1b944@hal9000.localdomain> From: Dale X-Enigmail-Draft-Status: N1110 Message-ID: <5644C575.1000302@gmail.com> Date: Thu, 12 Nov 2015 10:59:33 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 Firefox/41.0 SeaMonkey/2.38 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 In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 7bf549ab-7cb3-4fa3-98f3-5e0a7c93304f X-Archives-Hash: c114df1ca8fa2a98223ab691da058809 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=20 >> 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. > There's a page on g.o somewhere that explains this. I read it a long time ago, not sure how much has changed. I think it updates like every 30 minutes or something but I seem to recall that some servers can adjust that to hours or even just once a day if they need to. It's been a while but I bet it is still over there somewhere. Got curious so I went and found it. https://wiki.gentoo.org/wiki/Project:Infrastructure/Rsync=20 There are two links there. Top one should give you a general idea.=20 Dale :-) :-)=20