Created attachment 583656 [details] Output of "ls -R /home/release" After a fresh Gentoo installation with the profile default/linux/amd64/17.1/no-multilib (stable), I find an unexpected directory /home/release. It contains several MB worth of portage related log files (see attachment).
For the move to 17.1 profiles, the release team had to hand-update & hand-repack a 17.1-ready seed stage, to feed the autobuild system with. Something went wrong in the first round of builds, and what got pushed to mirrors is that custom-built seed stage. You may notice some indications that it was actually built around June 22, even though the release dir date is July 14/15. Once another full round of autobuilds goes through successfully, we'll be back to where we should be, without this /home/release build artifact. We can keep this bug open until that happens, to track the progress.
jmbsvicetto@nightheron ~ $ sudo tar tvf /release/buildroot/amd64-dev/builds/default/stage1-amd64-20190714T214502Z.tar.xz | grep home/ drwxr-xr-x root/root 0 2019-07-14 21:53 ./home/ -rw-r--r-- root/root 0 2019-07-14 21:53 ./home/.keep jmbsvicetto@nightheron ~ $ sudo tar tvf /release/buildroot/amd64-dev/buildsjmbsvicetto@nightheron ~ $ sudo tar tvf /release/buildroot/amd64-dev/builds/default/stage1-amd64-20190714T214502Z.tar.xz | grep etc/portage/make.profile lrwxrwxrwx root/root 0 2019-07-14 23:13 ./etc/portage/make.profile -> ../../../../usr/portage/profiles/default/linux/amd64/17.0 jmbsvicetto@nightheron ~ $ sudo tar tvf /release/buildroot/amd64-dev/builds/default/stage1-amd64-20190715T232030Z.tar.xz | grep home/ drwxr-xr-x root/root 0 2019-07-15 23:34 ./home/ -rw-r--r-- root/root 0 2019-07-15 23:34 ./home/.keep jmbsvicetto@nightheron ~ $ sudo tar tvf /release/buildroot/amd64-dev/builds/default/stage1-amd64-20190715T232030Z.tar.xz | grep etc/portage/make.profile lrwxrwxrwx root/root 0 2019-07-16 00:51 ./etc/portage/make.profile -> ../../../../var/db/repos/gentoo/profiles/default/linux/amd64/17.1 I'm storing the builds logs in my build server, so it is possible that you did get one of my stages that was pushed to serve as a seed to build the new 17.1 stages. However, looking at the above, I don't see /home/release inside the above stages. Can you please provide the full name of the stage you used for the install? In the meantime, in case you were waiting for feedback, feel free to drop everything under /home/release.
(In reply to Jorge Manuel B. S. Vicetto from comment #2) > Can you please provide the full name of the stage you used > for the install? I started the installation on 2019-07-16, but did not keep the stage archive on disk. Based on the date, the archive might still be available via http://distfiles.gentoo.org/releases/amd64/autobuilds/20190715T005025Z/stage3-amd64-nomultilib-20190715T005025Z.tar.xz , but I cannot be sure. > In the meantime, in case you were waiting for feedback, feel free > to drop everything under /home/release. Thanks for the confirmation.
I was looking at the wrong stages. jmbsvicetto@nightheron /release/buildroot/amd64-dev/builds/default $ sudo tar tvf stage3-amd64-20190715T005025Z.tar.xz | grep etc/portage/make.profile lrwxrwxrwx root/root 0 2019-06-22 03:23 ./etc/portage/make.profile -> ../../var/db/repos/gentoo/profiles/default/linux/amd64/17.1 jmbsvicetto@nightheron /release/buildroot/amd64-dev/builds/default $ sudo tar tvf stage3-amd64-20190715T005025Z.tar.xz | grep home/ drwxr-xr-x root/root 0 2019-06-22 01:39 ./home/ drwxr-xr-x root/root 0 2019-06-22 01:39 ./home/release/ drwxr-xr-x root/root 0 2019-06-22 01:39 ./home/release/tmp/ drwxrws--- portage/portage 0 2019-06-22 03:23 ./home/release/tmp/logs/ -rw-rw---- portage/portage 278 2019-06-22 01:39 ./home/release/tmp/logs/sys-devel:binutils-2.31.1-r6:20190622-013940.log -rw-rw---- portage/portage 278 2019-06-22 02:14 ./home/release/tmp/logs/virtual:perl-File-Spec-3.740.0:20190622-021448.log <snip> -rw-rw---- portage/portage 286 2019-06-22 02:28 ./home/release/tmp/logs/virtual:perl-Perl-OSType-1.10.0-r2:20190622-022828.log -rw-r--r-- root/root 0 2019-06-22 00:53 ./home/.keep So my stages do have build logs. jmbsvicetto@nightheron /release/buildroot/amd64-dev/builds/default $ sudo tar tvf stage3-amd64-20190716T103222Z.tar.xz | grep etc/portage/make.profile lrwxrwxrwx root/root 0 2019-07-16 16:33 ./etc/portage/make.profile -> ../../var/db/repos/gentoo/profiles/default/linux/amd64/17.1 jmbsvicetto@nightheron /release/buildroot/amd64-dev/builds/default $ sudo tar tvf stage3-amd64-20190716T103222Z.tar.xz | grep home/ drwxr-xr-x root/root 0 2019-07-16 10:49 ./home/ -rw-r--r-- root/root 0 2019-07-16 10:49 ./home/.keep jmbsvicetto@nightheron /release/buildroot/amd64-dev/builds/default $ But the new 17.1 stages build on the release box are "clutter" free. I'm going to drop my stages as they were just needed to serve as seeds.
I've left stage3-amd64-nomultilib-20190715T005025Z.tar.xz on the build box / mirrors as we still need to get a new stage built on the build server - the build for this stage failed on the last run.
I believe this is fixed, please reopen if you still see the problem somewhere.
