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 58E511384B4 for ; Thu, 12 Nov 2015 16:47:01 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8B86221C24E; Thu, 12 Nov 2015 16:46:48 +0000 (UTC) Received: from mail-wm0-f47.google.com (mail-wm0-f47.google.com [74.125.82.47]) (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 46E0421C237 for ; Thu, 12 Nov 2015 16:46:47 +0000 (UTC) Received: by wmec201 with SMTP id c201so42503867wme.0 for ; Thu, 12 Nov 2015 08:46:46 -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=ylxOCi8rAwTLdputprR9yt+g104Z3x+CNgfyqV8r+e8=; b=rmo2sHAp4ILRfzV9knnAjW5rpFVkTdoJZkrbZQNnBmui2x9hMHG9mdVm8G/gEn2VBy XO534pDss0qHHg2DL8FXgeTKSR6VoFQa9jsiDf6sF/wFsSnCztVMdZFqSyJfcffEPyIx nq/5LPoMGZFwEPRXkHi3dLwTmDDmbgYxXO5F0agsI1QdpVtqbDvKcxIKg0oJzEoyGzjs 0ebH6Kk1Asf7RIavE2CQDvMgZnv3LIRvHEc4xfXTls+eQsVJisp7WLgeT6XfS2vBbl3k k1PskNIY5TTtr5o0TUfIT5yT0fOL09whx7/NZ8ovSLzSUpfxzg3AnnaNPdU9dKdATVQL BmmA== X-Received: by 10.194.90.169 with SMTP id bx9mr13915622wjb.1.1447346805939; Thu, 12 Nov 2015 08:46:45 -0800 (PST) Received: from [172.29.2.13] ([209.212.109.4]) by smtp.googlemail.com with ESMTPSA id c1sm15322805wjf.19.2015.11.12.08.46.44 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Nov 2015 08:46:45 -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: Alan McKinnon Message-ID: <5644C238.6040008@gmail.com> Date: Thu, 12 Nov 2015 18:45:44 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 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=utf-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 97729b9a-d254-4501-aca4-9a237188cd3b X-Archives-Hash: 183bea0bb511efcbf025f5ff28212f79 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. 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. -- Alan McKinnon alan.mckinnon@gmail.com