public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] All sorts of digest verification failures
Date: Thu, 12 Nov 2015 16:07:42 +0000 (UTC)	[thread overview]
Message-ID: <n22dge$mnp$1@ger.gmane.org> (raw)

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?

-- 
Grant Edwards               grant.b.edwards        Yow! Why is it that when
                                  at               you DIE, you can't take
                              gmail.com            your HOME ENTERTAINMENT
                                                   CENTER with you??



             reply	other threads:[~2015-11-12 16:08 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12 16:07 Grant Edwards [this message]
2015-11-12 16:19 ` [gentoo-user] All sorts of digest verification failures 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
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='n22dge$mnp$1@ger.gmane.org' \
    --to=grant.b.edwards@gmail.com \
    --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