To make it short, portage-2.1_pre4 dies with errors about wrong checksums on any non MD5 checksum. It says that what it got for RMD160, SHA256... etc is not what is in the Manifest. I investigated a bit (just a bit) and found out that the checksums generated on amd64 and x86 are very different. Here is an illustration: chutz@ols-dell ~ $ echo foo > foo chutz@ols-dell ~ $ uname -a Linux ols-dell 2.6.15.1-d1 #1 SMP Thu Jan 19 12:53:04 JST 2006 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz GenuineIntel GNU/Linux chutz@ols-dell ~ $ python Python 2.4.2 (#1, Dec 1 2005, 14:38:33) [GCC 3.3.6 (Gentoo 3.3.6, ssp-3.3.6-1.0, pie-8.7.8)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import portage_checksum >>> portage_checksum.perform_all("./foo") {'RMD160': 'ec0af898b7b1ab23ccf8c5036cb97e9ab23442ab', 'SHA1': 'f1d2d2f924e986ac86fdf7b36c94bcdf32beec15', 'SHA256': 'b5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c', 'MD5': 'd3b07384d113edec49eaa6238ad5ff00'} >>> chutz@lion ~ $ echo foo > foo chutz@lion ~ $ uname -a Linux lion 2.6.15.1-y1 #1 Wed Jan 18 06:31:27 JST 2006 x86_64 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux chutz@lion ~ $ python Python 2.4.2 (#1, Dec 2 2005, 10:00:28) [GCC 3.4.4 (Gentoo 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import portage_checksum >>> portage_checksum.perform_all("./foo") {'RMD160': 'b57b6d894a881656fe532aaca1a2ecb76eeef013', 'SHA1': 'f1d2d2f924e986ac86fdf7b36c94bcdf32beec15', 'SHA256': '79588fb40d62d96fa00ea340bb14a5c7231344c6e11874f0242650bda10da7aa', 'MD5': 'd3b07384d113edec49eaa6238ad5ff00'} >>> I'd submit "emerge --info", but why clutter the bug unneccessarily. This is probably a python problem (or some other library problem), but it is portage that suffers heavily from it.
version of pycrypto installed?
Had the same problem but I emerged pycrypto-2.0.1 and did a emerge sync then it worked. :) rzn@paradox: pts/4: 116 files totalt 1,6Gb -> uname -a Linux paradox 2.6.15-gentoo #4 PREEMPT Tue Jan 17 16:57:26 CET 2006 x86_64 AMD Athlon(tm) 64 Processor 3200+ AuthenticAMD GNU/Linux rzn@paradox: pts/4: 116 files totalt 1,6Gb -> emerge info Portage 2.1_pre4 (default-linux/amd64/2005.1, gcc-3.4.4, glibc-2.3.5-r2, 2.6.15- gentoo x86_64) ================================================================= System uname: 2.6.15-gentoo x86_64 AMD Athlon(tm) 64 Processor 3200+ Gentoo Base System version 1.6.14 dev-lang/python: 2.3.5-r2, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 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 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=k8 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share /config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib64/mozilla/default s/pref /usr/share/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/texmf/web2c /etc/ env.d" CXXFLAGS="-march=k8 -O2 -pipe" DISTDIR="/usr/portage/distfiles" EMERGE_DEFAULT_OPTS="--alphabetical" FEATURES="autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://ds.thn.htu.se/linux/gentoo http://mirror.pudas.net/gentoo http://ftp.du.se/pub/os/gentoo http://mirror.uni-c.dk/gentoo/ http://pandemoniu m.tiscali.de/pub/gentoo/" LANG="sv_SE.utf8" LC_ALL="sv_SE.utf8" LINGUAS="sv en" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="amd64 X aac acl acpi alsa amd bash-completion berkdb bitmap-fonts bmp bzip2 cairo cddb cdparanoia cdr crypt cups curl dbus directfb dts dvb dvd dvdr dvdrea d emboss encode exif fat fbcon ffmpeg firefox flac foomaticdb fortran gdbm gif g imp gimpprint glitz gnome gphoto2 gpm gstreamer gtk gtk2 gtkhtml guile hal hfs i dn imagemagick imlib input_devices_evdev input_devices_keyboard input_devices_mo use ipv6 jack java jfs joystick jpeg jpg junit lcms lzw lzw-tiff mad matroska mi kmod mkv mmap mng modplug mono motif mozilla mp3 mpeg mplayer musicbrainz ncurse s nls nptl nptlonly nsplugin ntfs nvidia offensive ogg oggvorbis openal opengl o penssl pam pcre pdflib perl png python quicktime readline reiser4 reiserfs ruby sblive scanner sdk sdl slang sndfile snmp sox speex spell sqlite ssl svg tcltk t cpd tetex theora threads tiff truetype truetype-fonts type1-fonts unicode usb us erlocales vim-pager vorbis wma xfs xine xml xml2 xmms xpm xv xvid zlib elibc_gli bc kernel_linux linguas_sv linguas_en userland_GNU video_cards_nvidia" Unset: ASFLAGS, CTARGET, LDFLAGS /Andreas
What version of pycrypto did you two have merged prior?
I had pycrypto-2.0-r1 before
Broken here on a amd64 laptop as well with the pre4. I noticed that by using ebuild <path_to_an_ebuild> digest (which now generates non-md5 digests) and emerge that ebuild. It would fail on rmd160 on the ebuild everytime. The reason an emerge sync fixed the problem is that the deployed portage use md5 only.
(In reply to comment #3) > What version of pycrypto did you two have merged prior? Just to confirm that 2.0-r1 has problems but 2.0.1 does not. chutz@lion ~ $ emerge -p pycrypto | grep ebuild; echo foo > foo; python -c "import portage_checksum; print portage_checksum.perform_all('./foo')" [ebuild U ] dev-python/pycrypto-2.0.1 [2.0-r1] USE="-bindist%" 0 kB {'RMD160': 'b57b6d894a881656fe532aaca1a2ecb76eeef013', 'SHA1': 'f1d2d2f924e986ac86fdf7b36c94bcdf32beec15', 'SHA256': '79588fb40d62d96fa00ea340bb14a5c7231344c6e11874f0242650bda10da7aa', 'MD5': 'd3b07384d113edec49eaa6238ad5ff00'} chutz@lion ~ $ emerge -p pycrypto | grep ebuild; echo foo > foo; python -c "import portage_checksum; print portage_checksum.perform_all('./foo')" [ebuild R ] dev-python/pycrypto-2.0.1 USE="-bindist" 0 kB {'RMD160': 'ec0af898b7b1ab23ccf8c5036cb97e9ab23442ab', 'SHA1': 'f1d2d2f924e986ac86fdf7b36c94bcdf32beec15', 'SHA256': 'b5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c', 'MD5': 'd3b07384d113edec49eaa6238ad5ff00'}
Just emerged the new pycrypto (to 2.0.1). This didn't fix the problem. I'm still ending up with 0 byte digests (particularly xorg-x11) W
correction. After an emerge sync it worked.
portage-2.1_pre-r1 now depends directly on >=dev-python/pycrypto-2.0.1. The arches just CC'd (+m68k) have had their keywords removed due to lack of an available version.
guess I was just to late then with adding it. pycrypto is now ~ppc-macos, please put back ~ppc-macos keyword.
Guess I should have cvs up'd in that dir first as well.. ppc-macos and sh re-added.
I've also restored 2.1_pre3-r1 for the other archs and in case any other digest-related problems surface.
Jason, I don't see why alpha and ia64 are cc'd on this bug. If there's no reason, could you remove them from the cc list?
Alpha and ia64 aren't on the list; at least they're not on the list that I can see.. I see mips, ppc64 and s390.
readded ~ppc64
mips stable.
Everyone already has at least ~arch: http://packages.gentoo.org/packages/?category=dev-python;name=pycrypto