New install on an AlphaStation, etc., no interesting additions to make.conf as far as I can tell. The only unusual thing was that the portage tree originally came from Jan 12, 2004, because when I was setting up the system the rsync system was down. However, I've "emerge update" several times since then. Interestingly enough, on the Alpha the fontconfig-2.2.1.ebuild has the line "epatch ${PPREFIX}-2.2-rove_subpixel_test.patch" but that doesn't appear in the same file on my brother's Athlon. Or on any other machine. Also, after every "emerge sync", while "Updating Portage cache", there is an "!!!! eclass 'tcltk' in 'app-misc/grass-5.0.3' does not exist:" That doesn't happen on the Athlon, either. I'm guessing there is something wrong. Reproducible: Always Steps to Reproduce: 1. Set up directory for the chrooting. 2. Unpack stage1-alpha-20030729.tar.bz2 3. Bind-mount /proc, "chroot", "env-update", ". /etc/profile" 4. Unpack portage-20040112.tar.bz2 5. Other things took my time, and by the time I came back the rsync system was back, so "emerge sync" 6. "nano -w /etc/make.conf" to have CFLAGS="-03 -mcpu=ev5 -pipe -mieee" 7. "cd /usr/portage", "scripts/bootstrap.sh", "CONFIG_PROTECT='' emerge system" 8. "emerge sync" 9. "emerge kde" Other things involving fontconfig probably work. Actual Results: Unpacking etc. * Applying fontconfig-2.2-blacklist.patch... [ ok ] * Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is: * * /usr/portage/media-libs/fontconfig/files/patch/fontconfig-2.2-rove_subpixel_test.patch Expected Results: I expect that after "emerge sync" , the ebuilds would appear on my machine like they do on others' machines. For now, the Gentoo system is in a chroot'd environment, in a directory in /home of a Debian Woody system, with vanilla 2.4.24 kernel. Gentoo Base System version 1.4.3.10 Portage 2.0.49-r21 (default-alpha-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.4.24) ================================================================= System uname: 2.4.24 alpha EV5 ACCEPT_KEYWORDS="alpha" AUTOCLEAN="yes" CFLAGS="-O3 -mcpu=ev5 -pipe -mieee" CHOST="alpha-unknown-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O3 -mcpu=ev5 -pipe -mieee" DISTDIR="/usr/portage/distfiles" FEATURES="ccache" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X alpha berkdb crypt cups encode foomaticdb gdbm gif gnome gpm gtk gtk2 imlib jpeg kde libg++ libwww mikmod motif ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime readline sdl slang spell ssl tcpd truetype xml2 xmms xv zlib"
Well, I checked it out, the difference between the portage tree of x86 and alpha both on alpha and amd: 1. SYNC=rsync4.nl.gentoo.org/gentoo-portage (in /etc/make.conf) 2. emerge sync (at the same time) on alpha: 3. nfs export of /usr/portage (with ro,sync,no_root_squash) on amd: 4. mount alpha:/usr/portage /usr/alpha/portage 5. cd /usr for x in `find portage -type f |sort`; do cmp $x alpha/$x done 2>&1 | tee alpha/portage.txt cmp: alpha/portage/app-games/billardgl/ChangeLog: No such file or directory cmp: alpha/portage/app-games/billardgl/Manifest: No such file or directory cmp: alpha/portage/app-games/billardgl/billardgl-1.75-r1.ebuild: No such file or directory cmp: alpha/portage/app-games/billardgl/files/digest-billardgl-1.75-r1: No such file or directory [... cut 103 lines...] cmp: alpha/portage/app-games/trophy/ChangeLog: No such file or directory cmp: alpha/portage/app-games/trophy/Manifest: No such file or directory cmp: alpha/portage/app-games/trophy/files/digest-trophy-1.1.3: No such file or directory cmp: alpha/portage/app-games/trophy/trophy-1.1.3.ebuild: No such file or directory cmp: alpha/portage/current-packages: No such file or directory So my guess was that those ebuilds are not for alpha Let's see and grep KEYWORDS of those ebuilds 6. cat alpha/portage.txt |cut -c12- |cut -d: -f1 |grep ebuild$ |xargs grep ^KEYWORDS portage/app-games/billardgl/billardgl-1.75-r1.ebuild:KEYWORDS="x86 ppc" portage/app-games/bomberclone/bomberclone-0.10.0.ebuild:KEYWORDS="x86" portage/app-games/cannonsmash/cannonsmash-0.6.5.ebuild:KEYWORDS="x86" portage/app-games/corewars/corewars-0.9.12.ebuild:KEYWORDS="x86 ppc" portage/app-games/corewars/corewars-0.9.13.ebuild:KEYWORDS="x86 ~ppc" portage/app-games/flightgear/flightgear-0.9.2.ebuild:KEYWORDS="x86" portage/app-games/foobillard/foobillard-2.8.ebuild:KEYWORDS="x86 ppc" portage/app-games/gl117/gl117-0.9.ebuild:KEYWORDS="x86" portage/app-games/gl117/gl117-1.0.ebuild:KEYWORDS="x86" portage/app-games/gracer/gracer-0.1.5.ebuild:KEYWORDS="x86" portage/app-games/lincity/lincity-1.11a-r1.ebuild:KEYWORDS="x86 ppc" portage/app-games/lincity/lincity-1.12_pre53.ebuild:KEYWORDS="~x86 ~ppc" portage/app-games/pcgen/pcgen-5.2.ebuild:KEYWORDS="x86 ppc sparc alpha" portage/app-games/pcgen/pcgen-5.3.3.ebuild:KEYWORDS="~x86 ~ppc ~sparc ~alpha" portage/app-games/planets/planets-0.1.10.ebuild:KEYWORDS="x86" portage/app-games/race/race-0.5.ebuild:KEYWORDS="x86" portage/app-games/racer-bin/racer-bin-0.5.0-r1.ebuild:KEYWORDS="-* x86" portage/app-games/searchandrescue/searchandrescue-0.8.1.ebuild:KEYWORDS="x86" portage/app-games/senken/senken-0.2.6.ebuild:KEYWORDS="x86" portage/app-games/simutrans/simutrans-0.81.0.ebuild:KEYWORDS="-* x86" portage/app-games/simutrans/simutrans-0.82.3.ebuild:KEYWORDS="-* ~x86" portage/app-games/simutrans/simutrans-0.82.5.ebuild:KEYWORDS="-* ~x86" portage/app-games/slibo/slibo-0.4.4.ebuild:KEYWORDS="x86" portage/app-games/soccar/soccar-0.5.2.ebuild:KEYWORDS="x86" portage/app-games/stoned/stoned-1.0.4.ebuild:KEYWORDS="-* x86" portage/app-games/supertux/supertux-0.0.4.ebuild:KEYWORDS="x86" portage/app-games/torcs/torcs-1.2.1.ebuild:KEYWORDS="x86" portage/app-games/tornado/tornado-1.2.1a.ebuild:KEYWORDS="x86" portage/app-games/trophy/trophy-1.1.3.ebuild:KEYWORDS="x86" Well, most are only for x86, but there ARE also ebuilds for alpha! So, strange that they are in the portage tree on amd, but not on alpha!
There are also files on alpha which don't exist on amd (x86), but the files which exist in both trees don't differ here (see below)! cd /usr/alpha for x in `find portage -type f |sort`; do cmp $x ../$x done cmp: ../portage/app-games/timestamp.x: No such file or directory cmp: ../portage/berlin-base/timestamp.x: No such file or directory cmp: ../portage/bow/timestamp.x: No such file or directory cmp: ../portage/files/timestamp.x: No such file or directory cmp: ../portage/glep/timestamp.x: No such file or directory cmp: ../portage/gnome-apps/timestamp.x: No such file or directory cmp: ../portage/gnome-libs/timestamp.x: No such file or directory cmp: ../portage/gnome-office/timestamp.x: No such file or directory cmp: ../portage/incoming/timestamp.x: No such file or directory cmp: ../portage/jython/timestamp.x: No such file or directory cmp: ../portage/kde-apps/timestamp.x: No such file or directory cmp: ../portage/kde-i18n/timestamp.x: No such file or directory cmp: ../portage/kde-libs/timestamp.x: No such file or directory cmp: ../portage/net-apache/timestamp.x: No such file or directory cmp: ../portage/portage.py: No such file or directory cmp: ../portage/unix2tcp/ChangeLog: No such file or directory cmp: ../portage/unix2tcp/files/digest-unix2tcp-0.7.2: No such file or directory cmp: ../portage/unix2tcp/timestamp.x: No such file or directory cmp: ../portage/unix2tcp/unix2tcp-0.7.2.ebuild: No such file or directory Still the question, why aren't the portage trees equal when synced at the same time?!
this was just a typo already fixed
Even better, for me, was deleting the entire portage tree and "emerge sync"ing it again. The other error also disappeared. Yay for fast campus Internet connections!
