During emerge --sync: >>> Updating Portage cache: 100% * An update to portage is available. It is _highly_ recommended * that you update portage now, before any other packages are updated. * Please run 'emerge portage' and then update ALL of your * configuration files. Then: # emerge portage Calculating dependencies... done! >>> Emerging (1 of 1) sys-apps/portage-2.1_pre7-r5 to / >>> checksums files ;-) portage-2.1_pre7-r5.ebuild >>> checksums files ;-) portage-2.1_pre3-r1.ebuild >>> checksums files ;-) portage-2.0.54.ebuild !!! Digest verification Failed: !!! /usr/portage/sys-apps/portage/portage-2.0.54-r1.ebuild !!! Reason: Filesize does not match recorded size !!! Got: 4005 !!! Expected: 4011 >>> 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. (emerge syncing again does not help) Are the checksums wrong or is it me? Not sure why it is checking 2.0.54-r1? emerge --info Portage 2.1_pre7 (default-linux/amd64/2005.1, gcc-3.4.6, glibc-2.4-r1, 2.6.16-gentoo x86_64) ================================================================= System uname: 2.6.16-gentoo x86_64 AMD Athlon(tm) 64 Processor 4000+ Gentoo Base System version 1.12.0_pre16 dev-lang/python: 2.3.5, 2.4.2-r1 sys-apps/sandbox: 1.2.13 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-r1 sys-devel/binutils: 2.16.1-r2 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r3 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2 -march=athlon64 -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.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-O2 -march=athlon64 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LC_ALL="en_US.UTF-8" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X alsa arts avi berkdb bitmap-fonts bluetooth browserplugin cdparanoia cdr crypt cups dri dvd dvdr eds emboss encode exif flac foomaticdb fortran gd gif gpm gstreamer gtk2 hal ieee1394 imlib ipv6 isdnlog jabber java jikes jpeg kde ldap lzw lzw-tiff mp3 mpeg mule ncurses nls nptl nptlonly nsplugin ogg opengl pam pdflib perl png pppd python qt quicktime readline sdl spell ssl symlink tcpd tiff truetype truetype-fonts type1-fonts udb unicode usb verbose xine xml xml2 xpm xv zlib elibc_glibc kernel_linux userland_GNU" Unset: ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
I noticed this before it was reported and fixed it. You can use `env FEATURES="-strict" emerge portage` to work around it until the rsync mirrors catch up. A correct copy of the Manifest and ebuilds is available at http://dev.gentoo.org/~zmedico/overlay/sys-apps/portage/
The faulty commit was with 2.1_pre6-r6 (dead manifest1 code) so I guess we can negelect it...
