Re: [gentoo-user] All sorts of digest verification failures
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? > I synced just a few minutes ago and got this: These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R] sys-apps/busybox-1.23.1-r1::gentoo USE="ipv6 static syslog -debug -livecd -make-symlinks -math -mdev -pam* -savedconfig (-selinux) -sep-usr -systemd" 0 KiB [ebuild U ~] media-libs/mesa-11.0.5::gentoo [11.0.4::gentoo] USE="classic dri3 egl gallium gbm llvm nptl udev -bindist -d3d9 -debug -gles1 -gles2 -opencl -openmax -osmesa -pax_kernel -pic (-selinux) -vaapi -vdpau -wayland -xa -xvmc" ABI_X86="32 (64) (-x32)" VIDEO_CARDS="(-freedreno) -i915 -i965 -ilo -intel -nouveau -r100 -r200 -r300 -r600 -radeon -radeonsi -vmware" 7,102 KiB [ebuild U ~] net-analyzer/rrdtool-1.5.5::gentoo [1.5.4::gentoo] USE="graph perl tcl tcpd -dbi -doc -lua -python -rados -rrdcgi -ruby -static-libs" PYTHON_TARGETS="python2_7" 2,137 KiB Total: 3 packages (2 upgrades, 1 reinstall), Size of downloads: 9,238 KiB Would you like to merge these packages? [Yes/No] y >>> Verifying ebuild manifests !!! Digest verification failed: !!! /var/cache/portage/tree/sys-apps/busybox/busybox-.ebuild !!! Reason: Filesize does not match recorded size !!! Got: 8493 !!! Expected: 8580 >>> Emerging (1 of 3) sys-apps/busybox-1.23.1-r1::gentoo >>> Jobs: 0 of 3 complete, 1 runningLoad avg: 1.38, 1.81, 1.98 !!! Digest verification failed: !!! /var/cache/portage/tree/sys-apps/busybox/busybox-.ebuild !!! Reason: Filesize does not match recorded size !!! Got: 8493 !!! Expected: 8580 >>> Emerging (2 of 3) media-libs/mesa-11.0.5::gentoo >>> Failed to emerge sys-apps/busybox-1.23.1-r1 It would seem this is a widespread problem and not just some small fluke. Maybe it will sort out in a few days. Dale :-) :-)
Re: [gentoo-user] All sorts of digest verification failures
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? > This was posted on -dev a bit ago. They know about the issue and sounds like it may have been fixed already according to Wabe. They are working on fixing the lacking changelogs that was broken when they switched to git. Since it was posted on -dev, I'm sure a bug has already been filed on this. Depending on how the server is set up that you sync against, I'd give it a hour or so and sync again. Maybe Wabe is right and it will have filtered down to all sync servers. Dale :-) :-)
[gentoo-user] All sorts of digest verification failures
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.edwardsYow! Why is it that when at you DIE, you can't take gmail.comyour HOME ENTERTAINMENT CENTER with you??
Re: [gentoo-user] All sorts of digest verification failures
Grant Edwardswrote: > 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. -- Regards wabe