Today I unpacked the latest (I think) x32 stage3 tarball: stage3-x32-20140325.tar.bz2 with sha512sum: 38c37f60c280773deaa393a066b429c34ec2823d2300ad7e73fcab63ba7eb96662c26c258841dc14aab9ea7109562d771ec88942f98d650ee9729b78cdbe2068 stage3-x32-20140325.tar.bz2 and noticed an eclectic bunch of configuration files in /root. It seems like someone's personal configuration files ended up in the stage tarball. I'm sure those are not supposed to be there... might want to check it out: % tar tf stage3-x32-20140325.tar.bz2 ./root ./root/ ./root/.gdbinit ./root/.inputrc ./root/.nanorc ./root/.keep ./root/.gitconfig ./root/.bash_history ./root/.nano/ % head root/.gitconfig [user] name = Mike Frysinger email = vapier@gentoo.org [color] ui = auto diff = auto status = auto [color "diff"] old = red bold new = green bold
you're welcome ! ;) when triaging some things, i did run my chroot scripts, and those tend to hand copy files into the /root/ dir automatically for me. i would have expected the autostage builder to have run by now and uploaded a new stage3 for x32. the stage1->2->3 process creates /root from scratch so any random junk in the stage3 would have been reset. the upload i did there was a stop gap ...
We (infra) still need to enable X32 support in the build host to get the stages to build again. In the meantime, if you want, you can grab the stages I build using the official specs. The latest are available at http://www.jmbsvicetto.name/releases/auto/amd64/default/20140505/
ok, i'll refresh the stages locally again and upload them to the mirrors to replace the existing ones
i've built & uploaded a 20140508 snapshot that should be a bit cleaner ;)
