Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
View Bug Activity | Format For Printing | XML | Clone This Bug
Fallout from bug 131293 will be tracked here.
Created an attachment (id=85598) [edit] List of (possibly) broken stuff First column is manifest signedness. Second column is HORKED if the sha256 hash is wrong, UNCHECKED if a sha256 hash was present but the file was not on the mirror this ran on so it could not be checked. Third column is category/package. Fourth column is the file (can be a portdir file or distfile).
If your bug got duped to this one and you are not a developer: Wait until your package is fixed (sync in a couple of hours). We will try to do occasional status updates on this bug. If you are a developer and hit a broken digest: Feel free to fix it if only the SHA256 hash mismatches.
*** Bug 131447 has been marked as a duplicate of this bug. ***
*** Bug 131448 has been marked as a duplicate of this bug. ***
*** Bug 131449 has been marked as a duplicate of this bug. ***
*** Bug 131450 has been marked as a duplicate of this bug. ***
*** Bug 131451 has been marked as a duplicate of this bug. ***
*** Bug 131452 has been marked as a duplicate of this bug. ***
*** Bug 131453 has been marked as a duplicate of this bug. ***
*** Bug 131461 has been marked as a duplicate of this bug. ***
*** Bug 131488 has been marked as a duplicate of this bug. ***
*** Bug 131510 has been marked as a duplicate of this bug. ***
*** Bug 131509 has been marked as a duplicate of this bug. ***
!!! /usr/portage/sys-fs/lvm2/lvm2-2.01.09-r1.ebuild !!! Reason: Failed on SHA256 verification !!! Got: 15124bffdb2b37fcb362ddfdffc87d29e8e19dcadae974327efe1bb3c06c2b7f !!! Expected: d6a06788c8449797752f741559885de9a260c92c124ac428e3794383543bbe53
This problem is still ongoing. Sorry. But waiting 2 hours and re`syncing did not work. There are just too many invalid SHA256 hashes that an rsync would fix, unless we completely wiped out portdir and repopulated it with the latest portage tarball. In fact I not only waited 2 hours, I waited more than 4 .. and still several of my world file apps need updates, but have bad SHA256 hashes in the Manifest So .. My question is .. IS there a fix for this or not?
I am sorry, but my initial "couple of hours" estimate was vastly too optimistic. We are making progress (in alphabetical order most of kde-* and everything above that is fixed, as well as part of net-*), and will leave this bug open until we think everything is fixed.
Most of the tree is fixed now. If you still hit a failing sha256 check and your portage tree is up to date (current cvs, aka rsync in about an hour) please report it here.
Created an attachment (id=85643) [edit] fresh list Fri Apr 28 06:10 UTC 2006 Here is a fresh list.
!!! Digest verification Failed: !!! /usr/portage/media-sound/alsa-headers/alsa-headers-1.0.10.ebuild !!! Reason: Failed on SHA256 verification !!! Got: cabe2f34e06c2df3fffbe11af60e438f4c874498a9cfd886ba846a8cd377c991 !!! Expected: 33e93e86259d993c46fe7841661728f41e5fae6757728533ce905ba2dda8e087 -------------------------------------------------------------------------------- !!! Digest verification Failed: !!! /usr/portage/sys-apps/portage/files/digest-portage-2.0.53 !!! Reason: Failed on SHA256 verification !!! Got: bbd40b87ac5725ca9761b4dfd3656ca180d13957b4c82823c7d22490ae08489b !!! Expected: ff2838b2919a71fbd64f7b9fb45297c6e8b0c924b68ac943e31176e35f0f0e90
*** Bug 131570 has been marked as a duplicate of this bug. ***
!!! Digest verification failed: !!! /usr/portage/distfiles/gstreamer-0.10.5.tar.bz2 !!! Reason: Failed on SHA256 verification !!! Got: 1c055d04fc31ac5730a766743ece1402f93f967c8f815cd5c97112dfab8f4aa1 !!! Expected: ec85e33b37a0fad9dc9adbdcc27bffda53110c808c47a334fa788b848d36c392 Portage 2.1_pre9-r5 (default-linux/x86/2006.0, gcc-3.4.6, glibc-2.3.6-r3, 2.6.17-rc1-mm3 i686) ================================================================= System uname: 2.6.17-rc1-mm3 i686 AMD Athlon(TM) XP 1800+ Gentoo Base System version 1.12.0_pre18 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.4 [enabled] dev-lang/python: 2.3.5, 2.4.2-r1 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r2 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r5 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=athlon-xp -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=athlon-xp -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache collision-protect distcc distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.chem.wisc.edu/gentoo/ ftp://gentoo.chem.wisc.edu/gentoo/" MAKEOPTS="-j4" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="x86 3dnow X alsa am apache2 apm avi berkdb bitmap-fonts bzip2 cdr chroot cli crypt dri dv dvd dvdr eds emboss encode foomaticdb fortran gdbm gif gnome gpm gstreamer gtk gtk2 hal imlib isdnlog jpeg kde kdeenablefinal libg++ libwww mad mikmod mmx motif mp3 mpeg ncurses nls nptl ogg oggvorbis opengl oss pam pcre pdflib perl png pppd pwdb python qt quicktime readline reflection sdl session spell spl sse ssl tiff truetype truetype-fonts type1-fonts udev vorbis xml xmms xorg xv zlib elibc_glibc input_devices_keyboard input_devices_mouse kernel_linux userland_GNU video_cards_nvidia" Unset: ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS Using dev-python/pycrypto-2.0.1-r5
Comment #19: looks like you're not running the latest pycrypto. Please upgrade to the latest pycrypto, and be aware portage needs to be restarted after it is merged (so if your world upgrade pulls in pycrypto and fails on a digest afterwards simply restart the emerge). Comment #21: thanks, fixed in cvs.
*** Bug 131594 has been marked as a duplicate of this bug. ***
Some more mismatches (after running "emerge --resync"): x11-libs/openmotif-2.2.3-r9: !!! Digest verification failed: !!! /usr/portage/x11-libs/openmotif/openmotif-2.2.3-r7.ebuild !!! Reason: Failed on SHA256 verification !!! Got: 822ebd816f1e66ae7548ced167d16599ee9906ec32e452be29542171d22ffb92 !!! Expected: c2e26a1a6ac3af730ad8445287fe4cda97226d57dd96822bc60ab0a746c02b23 x11-misc/rss-glx-0.8.0-r3: !!! Digest verification failed: !!! /usr/portage/x11-misc/rss-glx/rss-glx-0.8.0-r2.ebuild !!! Reason: Failed on SHA256 verification !!! Got: 10c043b4434a0fce4ad2e3f32fe9862ccd076659a1e6c37bef67ef638dd6154a !!! Expected: 4a3f7d8fd95ddbdae60aca7ebf769c8579250f0c8e71e3f9a59a434c2cc1b5b7
comment #24: both fixed, thanks.
>>> Emerging (2 of 3) sys-apps/portage-2.1_pre9-r5 to / >>> checking ebuild checksums >>> checking auxfile checksums !!! Digest verification failed: !!! /usr/portage/sys-apps/portage/files/2.1_pre7/1130_r3087_bug_129098.patch !!! Reason: Failed on SHA256 verification !!! Got: e7822a02fa4e2eaa0fa87e081d442866b66408520bac4e29e4927ad7439636e9 !!! Expected: 5cf3d33b7d4768914e4bd5f7ffb37ab33e984184f138ef9b82c3a46fac1969b0
Created an attachment (id=85737) [edit] list for Sat Apr 29 05:49 UTC 2006 New list
(In reply to comment #26) > >>> Emerging (2 of 3) sys-apps/portage-2.1_pre9-r5 to / > >>> checking ebuild checksums > >>> checking auxfile checksums > !!! Digest verification failed: > !!! /usr/portage/sys-apps/portage/files/2.1_pre7/1130_r3087_bug_129098.patch > !!! Reason: Failed on SHA256 verification > !!! Got: e7822a02fa4e2eaa0fa87e081d442866b66408520bac4e29e4927ad7439636e9 > !!! Expected: 5cf3d33b7d4768914e4bd5f7ffb37ab33e984184f138ef9b82c3a46fac1969b0 > Try again. You probably had the old version of pycrypto still loaded in memory (if it was #1 in the merge list).
Sat Apr 29 17:20:20 2006 >>> dev-python/pycrypto-2.0.1-r5 looks like your right :) thx.
!!! Digest verification failed: !!! /usr/portage/sys-libs/timezone-data/timezone-data-2006a.ebuild !!! Reason: Failed on SHA256 verification !!! Got: d1aaab6eb3130d2ad515bea79dd6d2bde811a4855820569b604e1f48e0085ecf !!! Expected: 4b95d4cd18a220672516cdf0fe9db15101fc9f4e6aab19adae843f67f952affe
Comment #30: That was fixed about 40 hours ago, please sync.
Created an attachment (id=85808) [edit] list for Sun Apr 30 03:49 UTC 2006
!!! /usr/portage/media-libs/tiff/files/tiff-3.7.1-tiffdump.patch !!! Reason: Failed on SHA256 verification !!! Got: 3697a051dd64fbfb2c05971bd04089c35ff202461287ed7c9663d12c0397aecb !!! Expected: a4ad4ca4599713f71474225f0eb6191a913d01db1ff06569715d27f7afb96319
*** Bug 131888 has been marked as a duplicate of this bug. ***
(In reply to comment #33) > !!! /usr/portage/media-libs/tiff/files/tiff-3.7.1-tiffdump.patch > !!! Reason: Failed on SHA256 verification > !!! Got: 3697a051dd64fbfb2c05971bd04089c35ff202461287ed7c9663d12c0397aecb > !!! Expected: a4ad4ca4599713f71474225f0eb6191a913d01db1ff06569715d27f7afb96319 The "Expected" value is the value I actually get for the file, according to the cvs history your "Got" value is the one you get from a broken pycrypto. Are you on the latest (2.0.1-r5) pycrypto? Did emerge get restarted after you upgraded to that version?
Sorry, you are right. I still had the -r4 version of pycrypto.
Created an attachment (id=85953) [edit] list for Mon May 01 19:53 UTC 2006
*** Bug 131983 has been marked as a duplicate of this bug. ***
I found greater problems than digests mismatch due to bad sha256sum. There is also filesize mismatching in current CVS for 'sys-apps/dbus-0.23.4-r1' and dbus Manifest file. Downloaded CVS file: 3658 bytes, Manifest says 3639 bytes. I'm writing here because I think this problem may be related with digests mismatches.
Comment #39: I am unable to reproduce. The file dbus-0.23.4-r1.ebuild is 3639 bytes in my cvs checkout, hasn't been touched for the last 3 weeks according to cvs log, and passes digest checks. How did you get this file? Does a sync make the problem go away?
When emerging python 2.4.3 on alpha I get this... !!! Digest verification Failed: !!! /usr/portage/dev-lang/python/files/digest-python-2.4.3 !!! Reason: Failed on SHA256 verification !!! Got: cb1f85d43ffcb62f214711b3ab7231ad711ac382ab729dc9013e4e482eaaf238 !!! Expected: 3f77c805317ac37a5bbe788bc0ad4b723c3584c0d676d6ee4e2040291cb4177d
(In reply to comment #41) > When emerging python 2.4.3 on alpha I get this... > > !!! Digest verification Failed: > !!! /usr/portage/dev-lang/python/files/digest-python-2.4.3 > !!! Reason: Failed on SHA256 verification > !!! Got: cb1f85d43ffcb62f214711b3ab7231ad711ac382ab729dc9013e4e482eaaf238 > !!! Expected: 3f77c805317ac37a5bbe788bc0ad4b723c3584c0d676d6ee4e2040291cb4177d Actually, because of the dependencies, the pycrypto module wouldn't have been updated before python 2.4.3 got emerged using a traditional 'emerge -uD world'. So I had to emerge pycrypto manually before issuing the -uD world again. Now it's fine.
>>> Emerging (1 of 15) media-libs/mesa-6.5-r3 to / >>> checksums files ;-) mesa-6.5-r3.ebuild >>> checksums files ;-) mesa-6.4.2-r2.ebuild >>> checksums files ;-) files/64bit-fix-indirect-vertex-array.patch !!! Digest verification Failed: !!! /usr/portage/media-libs/mesa/files/6.5-re-order-context-destruction.patch!!! Reason: Failed on SHA256 verification !!! Got: 64fc2ec01fb786a5f2d861449e6243bf41e6c4e40031c9713b5ad34e3a6fcde9 !!! Expected: dda980be89d14df3659c0d409c56e4ccd6a03afdca2e8edc502845943423a600 Portage tree was synced a minute earlier.
*** Bug 132128 has been marked as a duplicate of this bug. ***
Comment #43: The "expected" value seems to be accurate. Perhaps you need to upgrade pycrypto?
(In reply to comment #45) > Comment #43: The "expected" value seems to be accurate. Perhaps you need to > upgrade pycrypto? > I did check the version before, but missread r4 for r5. Sorry about that. Upgraded, resynced and it worked.
!!! Digest verification Failed: !!! /usr/portage/media-libs/tiff/files/tiff-3.7.1-tiffdump.patch !!! Reason: Failed on SHA256 verification !!! Got: a4ad4ca4599713f71474225f0eb6191a913d01db1ff06569715d27f7afb96319 !!! Expected: 3697a051dd64fbfb2c05971bd04089c35ff202461287ed7c9663d12c0397aecb this one is sticky.
Comment #47: thanks for reporting, fixed in cvs.
*** Bug 132218 has been marked as a duplicate of this bug. ***
*** Bug 132272 has been marked as a duplicate of this bug. ***
Created an attachment (id=86190) [edit] list for Fri May 5 08:20 UTC 2006
!!! Digest verification Failed: !!! /usr/portage/www-client/mozilla-firefox/mozilla-firefox-1.5.0.2.ebuild !!! Reason: Failed on SHA256 verification !!! Got: 62f0d54c92f911f8be2544f10b385789da0aa9837122333a9d05bd3c630714e1 !!! Expected: 65eb7a7e41effc9347256b9afd395bdc092df94f9fef54a8a00b4ebd98cfd1d1 !!! Digest verification Failed: !!! /usr/portage/sys-apps/sandbox/files/digest-sandbox-1.2.12 !!! Reason: Failed on SHA256 verification !!! Got: 7a1fcb1f51ed88f84ded15c6267769ab59f5a4f06e026a34101cf6aef9152c3c !!! Expected: 458a2a6625d973b66b077631d56a16d875742fa5bc4fa1d950cb3033b820981b
>>> Emerging (1 of 33) dev-libs/openssl-0.9.7j to / >>> checking ebuild checksums >>> checking auxfile checksums !!! Digest verification failed: !!! /usr/portage/dev-libs/openssl/files/openssl-0.9.8-ppc64.patch !!! Reason: Failed on SHA256 verification !!! Got: b38d4178098df3c2f487a542035d5de747f8c2d2a921f2d85eea324518dc2064 !!! Expected: 9e521f5b76a46a56414cf49cde452f4bd96c9f42f5ac30257c0404808b125886
!!! Digest verification Failed: !!! /usr/portage/sys-devel/gcc/files/digest-gcc-3.2.2 !!! Reason: Failed on SHA256 verification !!! Got: c15c963fc6834d8ae7cbc231c3678eafbf85597749353cc5c0a697b87abaa688 !!! Expected: 2c69fc1e2cb4b30c70b8ce8bde9fc84010569f1b2a7eb7700877d19dc030c727
*** Bug 132691 has been marked as a duplicate of this bug. ***
glibc-2.4-r1 SHA256 files/nsswitch.conf
!!! Digest verification Failed: !!! /var/portage/distfiles/OOO_2_0_2-core.tar.bz2 !!! Reason: Failed on SHA256 verification !!! Got: e938a4edb6d11ef4a634a18ad55c6d9e9a371a5ab9771d17e71832fbb12cc230 !!! Expected: e9afb8806b323880a99c5fd323a5702a86a58ce9f2ba024ad09846d847e7bd53
!!! Digest verification Failed: !!! /var/portage/sys-libs/glibc/files/nsswitch.conf !!! Reason: Failed on SHA256 verification !!! Got: 21c07e3c3a6ed59c6bfca84b6e4a4931a82c745fd4d1ce136c69a6c03418b11c !!! Expected: 6c38b8642d5da884327ad678d0351d57be3621562253bd9711394bad87e45e2d (glibc-2.3.6-r3)
*** Bug 132906 has been marked as a duplicate of this bug. ***
!!! Digest verification Failed: !!! /usr/portage/sys-boot/grub/grub-0.96-r2.ebuild !!! Reason: Failed on SHA256 verification !!! Got: 76368c0b90e303141a46032edadbb251f735e1f98a5113bf7635e47457c52670 !!! Expected: 3be87c06ae7f39ea3ac8c00befab972f5c1b56da31d9db7d1aede49a8ae1f246
(In reply to comment #60) > !!! Digest verification Failed: > !!! /usr/portage/sys-boot/grub/grub-0.96-r2.ebuild > !!! Reason: Failed on SHA256 verification > !!! Got: 76368c0b90e303141a46032edadbb251f735e1f98a5113bf7635e47457c52670 > !!! Expected: 3be87c06ae7f39ea3ac8c00befab972f5c1b56da31d9db7d1aede49a8ae1f246 > I had old pycrypto. Retrying. Sorry for not reading the bug... :(
*** Bug 133063 has been marked as a duplicate of this bug. ***
(In reply to comment #58) > !!! Digest verification Failed: > !!! /var/portage/sys-libs/glibc/files/nsswitch.conf > !!! Reason: Failed on SHA256 verification > !!! Got: 21c07e3c3a6ed59c6bfca84b6e4a4931a82c745fd4d1ce136c69a6c03418b11c > !!! Expected: 6c38b8642d5da884327ad678d0351d57be3621562253bd9711394bad87e45e2d > > (glibc-2.3.6-r3) > I had this bug when did emerge -Dv --update system But after removing --deep key (emerge -v --update system) bug resolved Think after updating pycrypto problems resolves
# emerge xorg-x11 Calculating dependencies... done! >>> Emerging (1 of 104) x11-proto/kbproto-1.0.2 to / >>> checking ebuild checksums ;-) >>> checking auxfile checksums ;-) >>> checking miscfile checksums ;-) >>> checking kbproto-1.0.2.tar.bz2 !!! Digest verification failed: !!! /usr/portage/distfiles/kbproto-1.0.2.tar.bz2 !!! Reason: Failed on RMD160 verification !!! Got: 3e3ab52a8354ba0f9de2d392e75f84764f38d628 !!! Expected: dfc8692c0f9d6bee748a8ad469b4eba7381d72c4 Portage: 2.1_pre10-r5 pycrypto: 2.0.1-r5
Disregard previous comment... I tried removing kbproto from distfiles folder three times... and trying to get things to work I removed it yet again and it worked.... :-/ yeaaaa....
as I said in Bug 133063 : ebuild /usr/portage/media-sound/alsa-headers/alsa-headers-1.0.10.ebuild manifest is a command to fix any broken ebuild or checksum files. This allowed me to fix 3 more broken problems in 5s each.
(in reply to Comment #66) > as I said in Bug 133063 : > > ebuild /usr/portage/media-sound/alsa-headers/alsa-headers-1.0.10.ebuild manifest > > is a command to fix any broken ebuild or checksum files. This allowed me to fix > 3 more broken problems in 5s each. Well you could do that *after* reporting the bad checksum here!
It's also a good way to make sure compromised software _does_ get onto your system, if you do it without thinking.
*** Bug 133125 has been marked as a duplicate of this bug. ***
root@moon_gen:~# emerge -v1 rpm2targz Calculating dependencies... done! >>> Emerging (1 of 1) app-arch/rpm2targz-9.0-r5 to / mv: cannot stat `/mnt/big/portage/rpm2targz-9.0-r5/temp/environment': No such file or directory >>> checksums files ;-) rpm2targz-9.0-r3.ebuild >>> checksums files ;-) rpm2targz-9.0-r2.ebuild >>> checksums files ;-) rpm2targz-9.0-r4.ebuild !!! Digest verification Failed: !!! /usr/portage/app-arch/rpm2targz/rpm2targz-9.0-r5.ebuild !!! Reason: Failed on SHA256 verification !!! Got: d5a231e191c4133589e8a636ff80c932672d6344d248fbe87c5ed122936ceeec !!! Expected: 9eecf430164b9a38ec2012e3bae8cd749472f92a440d8f112f0a24c66a439f8e >>> Please ensure you have sync'd properly. Please try 'emerge sync' and >>> optionally examine the file(s) for corruption. A sync will fix most cases. ******************************************************* root@moon_gen:~# ebuild /usr/portage/app-arch/rpm2targz/rpm2targz-9.0-r5.ebuild manifest >>> Generating the manifest file... does fix.
>>> checksums files ;-) gtk+-2.8.16.ebuild >>> checksums files ;-) gtk+-2.8.8.ebuild !!! Digest verification Failed: !!! /usr/portage/x11-libs/gtk+/gtk+-2.8.17.ebuild !!! Reason: Failed on SHA256 verification !!! Got: 4be27fbd7309eed7d6bb9154456b81d56ed0389a215ef35a5a7c8731dd9344e1 !!! Expected: d4896fb5ede1ffaf9a19c672e1e89cce4d483765ff36c5e210998272cb97d9c1 same fix.
root@moon_gen:/home/dhp# emerge -v1 vlc Calculating dependencies... done! >>> Emerging (1 of 1) media-video/vlc-0.8.5 to / mv: cannot stat `/mnt/big/portage/vlc-0.8.5/temp/environment': No such file or directory >>> checksums files ;-) vlc-0.8.4a-r1.ebuild !!! Digest verification Failed: !!! /usr/portage/media-video/vlc/vlc-0.8.4a.ebuild !!! Reason: Failed on SHA256 verification !!! Got: 5c426be79983614951683896c6e38e3febb3efb7c230699302ede70c2b6000e7 !!! Expected: d2339f58717e338330870a65c1cbb18e6d3b0e34e23cdaf0a14b9e21cfb1e310 >>> Please ensure you have sync'd properly. Please try 'emerge sync' and >>> optionally examine the file(s) for corruption. A sync will fix most cases. fix is same as usual.
!!! Digest verification Failed: !!! /usr/portage/media-libs/tiff/files/tiff-3.7.1-tiffdump.patch !!! Reason: Failed on SHA256 verification !!! Got: 3697a051dd64fbfb2c05971bd04089c35ff202461287ed7c9663d12c0397aecb !!! Expected: a4ad4ca4599713f71474225f0eb6191a913d01db1ff06569715d27f7afb96319
(In reply to comment #53) > !!! /usr/portage/dev-libs/openssl/files/openssl-0.9.8-ppc64.patch > !!! Got: b38d4178098df3c2f487a542035d5de747f8c2d2a921f2d85eea324518dc2064 > !!! Expected: 9e521f5b76a46a56414cf49cde452f4bd96c9f42f5ac30257c0404808b125886 !!! /usr/portage/dev-libs/openssl/files/digest-openssl-0.9.6m !!! Got: 5a5fedfc3009915054be70ad6f7f15089099b3aeaa789e0826ca995ac07e4316 !!! Expected: 9358151d15b51644133f46a752034b8c913d62c76c7eb884851e7aa54b5e4053
(In reply to Comment #68) > It's also a good way to make sure compromised software _does_ get onto your > system, if you do it without thinking. Yes, you should only update the manifest if you're sure it's a bogus SHA256 checksum and the other checksums are okay. It's useful to get out of a hole and continue emerging without having to wait for it to be fixed in portage CVS. But to reiterate, the bad checksums should be reported here as well!
(In reply to comment #71) > !!! Got: 4be27fbd7309eed7d6bb9154456b81d56ed0389a215ef35a5a7c8731dd9344e1 > !!! Expected: d4896fb5ede1ffaf9a19c672e1e89cce4d483765ff36c5e210998272cb97d9c1 That "expected" value is the correct one. Are you sure you are on the latest pycrypto?
pycrypto-2.0.1-r5[0]: testing and stabilization bug filed. bug 133299
!!! Digest verification failed: !!! /usr/portage/media-video/vlc/vlc-0.8.4a.ebuild !!! Reason: Failed on SHA256 verification !!! Got: d2339f58717e338330870a65c1cbb18e6d3b0e34e23cdaf0a14b9e21cfb1e310 !!! Expected: 5c426be79983614951683896c6e38e3febb3efb7c230699302ede70c2b6000e7
(In reply to comment #76) > (In reply to comment #71) > > !!! Got: 4be27fbd7309eed7d6bb9154456b81d56ed0389a215ef35a5a7c8731dd9344e1 > > !!! Expected: d4896fb5ede1ffaf9a19c672e1e89cce4d483765ff36c5e210998272cb97d9c1 > > > That "expected" value is the correct one. Are you sure you are on the latest > pycrypto? > I have latest r5 since 2006 may 13rd, 19:20; FYI I am in France/Paris, and comment #71 is said to be posted 2006-05-12 22:10 so by that time I had not the latest version, but any further ones will. I had over 170 updates to do last week; emerge world did not put portage nor pycrypto as urgent ones, so that it took days before upgrades. Genlop still says me I have over 30h of compile to do ... but I keep posting SHA problems before I fix them locally. After I compleeted upgrades, I ll esync, then check again all SHA that I said here to be bad, see whats around.
(In reply to comment #78) > !!! Digest verification failed: > !!! /usr/portage/media-video/vlc/vlc-0.8.4a.ebuild > !!! Reason: Failed on SHA256 verification > !!! Got: d2339f58717e338330870a65c1cbb18e6d3b0e34e23cdaf0a14b9e21cfb1e310 > !!! Expected: 5c426be79983614951683896c6e38e3febb3efb7c230699302ede70c2b6000e7 > That makes no sense. Your "Got" value is correct, but it is also the one in the Manifest at the moment and in all the previous revisions I've checked. Perhaps you redigested this one with a broken pycrypto and it's now failing with an unbroken pycrypto? Before you report any more of these can you please do the following: - Make sure your portage tree is current and has no local changes ("emerge sync" will do this). - Make sure you are on a sufficiently recent pycrypto. - Make sure portage was restarted after that pycrypto was upgraded. Thanks.
*** Bug 133385 has been marked as a duplicate of this bug. ***
Would it be possible to be sure that on any "emerge -u" on a system which has a known-"broken" pycrypto that pycrypto will be emerged first, and then perhaps the emerge will be restarted in the same way it does if a new portage has been emerged?
(In reply to comment #82) > Would it be possible to be sure that on any "emerge -u" on a system which has a > known-"broken" pycrypto that pycrypto will be emerged first, and then perhaps > the emerge will be restarted in the same way it does if a new portage has been > emerged? If I knew a sensible way to do that I would probably have done it by now :) Most workarounds (like making portage ignore sha256 digests for files with a size that's susceptible to this pycrypto bug) involve changing portage, so they don't really help any more than simply upgrading portage now does already (since that will pull in the right pycrypto and trigger a reload of portage). I do not know a non-insane way to make sure the portage upgrade is pulled first (other than throwing in some portage dependencies in various important places but that is evil and ugly). Suggestions on non-insane ways to accomplish this are appreciated.
!!! Digest verification failed: !!! /usr/local/portage/games-strategy/glest/glest-2.0.0.ebuild !!! Reason: Failed on SHA256 verification !!! Got: 0c3895383d33b3f3fd4d434b622e6a284ad64b6e9ac9d26205d1a36df0abcf46 !!! Expected: 2b9182a51dd6232db6ea0ba3dbd36e2a6091e88a2a435958199f61f0e2973dc7
Sorry please forget about glest. I see that this was an ebuild I bumped...
Very much x packages are broken lets start with xextproto.
xcmiscproto
Please make sure these still fail after removing the copy from /usr/portage/distfiles and refetching it. The tarballs changed between an xorg 7 release candidate and the final release without a rename. If you still have old tarballs in /usr/portage/distfiles they will cause digest failures with the current Manifest/digest files.
(In reply to comment #88) > Please make sure these still fail after removing the copy from > /usr/portage/distfiles and refetching it. The tarballs changed between an xorg > 7 release candidate and the final release without a rename. If you still have > old tarballs in /usr/portage/distfiles they will cause digest failures with the > current Manifest/digest files. You are right. This why isn't portage anticipating on this? Is it a bug?
(In reply to comment #89) > (In reply to comment #88) > You are right. This why isn't portage anticipating on this? Is it a bug? Portage does not usually try to remove and refetch a distfile if the digest does not match. This could be considered a missing feature. For now it's good practice to remove and refetch a distfile if the digest check fails. This is particularly easy to hit on xorg 7 because upstream changed the tarballs without renaming them (which really should not happen). If you have tarballs from that time around (as far as I know that means you fetched them while xorg 7 was in package.mask) you will need to remove them.
!!! Digest verification failed: !!! /usr/portage/x11-drivers/ati-drivers/files/fglrx-2.6.12-pci_name.patch !!! Reason: Failed on SHA256 verification !!! Got: 8dc2a7d9cdf449fd040ed9bb6b7f891f3885cf33a35a39e858b8072eb505f67a !!! Expected: 80300e0810a35f42e6d1323c6aef1cd1a4d6c40ebf8d508269c5d06f3cc79817 Shouldn't all devs ('lu_zero' in this case) be using the correct pycrypto by now?
*** Bug 134511 has been marked as a duplicate of this bug. ***
Should MD5 hash verification failures be filed here, or is this a separate bug? The following packages have ebuilds that fail verification: kde-base/kstars-3.5.2 kde-base/kdeartwork-kscreensaver-3.5.2 kde-base/libkdeedu-3.5.2 kde-base/kontact-3.5.2 Resyncing has not resolved the problem; there may be other similarly affected packages that I don't have installed (I found them using "emerge -ef world".)
I'm marking this "fixed" because by now the tree itself is fixed and devs have upgraded so it shouldn't be broken by this again. The problem will only resurface if a dev who's running ~arch portage commits something while not having upgraded since this bug was discovered. comment #93: Not this bug. You should file one if it has not been fixed yet, but from cvs logs this was fixed about 2 hours ago, so an "emerge sync" should fix it now.
(In reply to comment #94) > I'm marking this "fixed" because by now the tree itself is fixed and devs have > upgraded so it shouldn't be broken by this again. The problem will only > resurface if a dev who's running ~arch portage commits something while not > having upgraded since this bug was discovered. So is the best way to catch those developers to file package-specific bugs? I'll do that in the case of ati-drivers (see comment #91) unless someone else has beat me to it!
It took me a week of --sync-ing my portage tree to figure out why I cannot upgrade anymore because of bad checksums. After I tried to find where does the sha256sum from I found newer coreutils provide sha256sum. After a copying that binary from a working machine to the problematic one I found the sha256sum is the one reported to be expected by emerge, and that the one calculated by emerge is wrong. So I finally got to this bugreport. I have about 12 othe rmachines in exactly same stage. Now I finally see I have to do 'emerge -uO pycrypto' otherwise I will never get ahead. The below output shows my setup and that sha256sum from a newer machine computes correctly on the bad host. As I said, upgrading pycrypto to -r5 fixed my problem. Please improve portage dependencies/logic to upgrade pycrypto before it attempts any othe rpackage. For example, in my case it always tries gettext or bash first. :( phylo1 etc # emerge -uO autoconf Calculating dependencies... done! >>> Emerging (1 of 1) sys-devel/autoconf-2.61 to / >>> Downloading http://distfiles.gentoo.org/distfiles/autoconf-2.61.tar.gz --23:03:28-- http://distfiles.gentoo.org/distfiles/autoconf-2.61.tar.gz => `/usr/portage/distfiles/autoconf-2.61.tar.gz' Resolving distfiles.gentoo.org... 64.50.236.52, 64.50.238.52, 156.56.247.195, ... Connecting to distfiles.gentoo.org|64.50.236.52|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 1,396,855 (1.3M) [application/x-gzip] 100%[==========================================================================================================================================================================================>] 1,396,855 463.87K/s 23:03:32 (462.63 KB/s) - `/usr/portage/distfiles/autoconf-2.61.tar.gz' saved [1396855/1396855] >>> checksums files ;-) autoconf-2.59-r7.ebuild >>> checksums files ;-) autoconf-2.13.ebuild >>> checksums files ;-) autoconf-2.60.ebuild >>> checksums files ;-) autoconf-2.61.ebuild >>> checksums files ;-) files/autoconf-2.13-gentoo.patch >>> checksums files ;-) files/digest-autoconf-2.13 >>> checksums files ;-) files/autoconf-2.13-destdir.patch >>> checksums files ;-) files/digest-autoconf-2.59-r7 >>> checksums files ;-) files/autoconf-2.59-more-quotes.patch >>> checksums files ;-) files/autoconf-2.60-tests.patch >>> checksums files ;-) files/digest-autoconf-2.60 >>> checksums files ;-) files/digest-autoconf-2.61 !!! Digest verification Failed: !!! /usr/portage/distfiles/autoconf-2.61.tar.gz !!! Reason: Failed on SHA256 verification !!! Got: 6557534b0d785fddb18c02de222c67bb4de556651005b5e56ead392d42deb79d !!! Expected: 9d14f2ed0d1b6f8180498a66517f511c7c49c870d6873219a3ff4b8b3082a68b phylo1 etc # sha256sum /usr/portage/distfiles/autoconf-2.61.tar.gz 9d14f2ed0d1b6f8180498a66517f511c7c49c870d6873219a3ff4b8b3082a68b /usr/portage/distfiles/autoconf-2.61.tar.gz phylo1 etc # emerge -s pycrypto Searching... [ Results for search key : pycrypto ] [ Applications found : 1 ] * dev-python/pycrypto Latest version available: 2.0.1-r5 Latest version installed: 2.0.1-r4 Size of files: 452 kB Homepage: http://www.amk.ca/python/code/crypto.html Description: Python Cryptography Toolkit License: freedist phylo1 etc # # emerge --info Portage 2.1_pre5-r4 (default-linux/x86/2006.1, gcc-3.4.5, glibc-2.3.6-r3, 2.6.15-rc5 i686) ================================================================= System uname: 2.6.15-rc5 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz Gentoo Base System version 1.12.0_pre16 app-admin/eselect-compiler: [Not Present] dev-java/java-config: [Not Present] dev-lang/python: 2.3.5, 2.4.2-r1 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.59 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1-r2 sys-devel/gcc-config: 1.3.13-r1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r3 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O3 -march=pentium4 -mmmx -msse -msse2 -msse3 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/spool/PBS /var/qmail/alias /var/qmail/control /var/spool/PBS" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mcpu=i686 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 FFmpeg X Xaw3d aalib acpi alsa apache2 avi berkdb bidi bitmap-fonts caca cdr cli cracklib crypt cscope curl dba divx divx4 divx4linux divx5 divx5linux dlloader dri dvd dvdr dvdread emacs emacs-w3 encode f77 faad faad2 fam fame ffmpeg flash fortran fvwm fvwm2 gb gd gdbm ggi gif gpm gtk gtk2 gtkhtml i8x0 icc iconv imagemagick imlib imlib2 innodb ipv6 isdnlog ithreads java javascript jpeg kerberos lcms leim libg++ libwww live lzo mad mcal mesa mikmod mmx mmx2 motif mozilla mpeg mule mysql ncurses network nls nptl nptlonly opengl pam pcre pda pdflib perl plotutils plugin png ppds pppd pthread pthreads python qt qtx quicktime readline reflection rtc samba scp sdl server session slp spell spl sse sse2 sse3 ssl tcltk tcpd tetex theora thread threads tiff truetype truetype-fonts type1-fonts udev unicode usb v4l v4l2 win32 winvidix wmf xml xml2 xorg xosd xv xvid xvmc zeo zlib elibc_glibc input_devices_keyboard input_devices_mouse input_devices_evdev kernel_linux userland_GNU video_cards_radeon" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS, PORTAGE_RSYNC_EXTRA_OPTS, PORTAGE_RSYNC_OPTS
