http://distfiles.gentoo.org/releases/amd64/autobuilds/current-stage3-amd64-systemd/stage3-amd64-systemd-20180818.tar.bz2 1.2K size :-)
Also affects stage3-i686-systemd-20180818
This might be related to the stabilisation of catalyst 3.0.2 on amd64 on the 15th of August. The catalyst "sharedir" has moved from /usr/lib64/catalyst in 2.0.18, to /usr/share/catalyst in 3.0.2. In the event that catalyst 3.0.2 is given an empty or non-existing sharedir, catalyst does none of the work to prepare the stage, except in this case unpacking the contents of the specfile's portage_confdir, and does not report this as an error; catalyst outputs a tarball with that content. The workaround is to modify your catalyst configuration, after updating to catalyst 3.0.2, to set sharedir to the new location, or symlink the old location to the new. This would need to be carried out on the build server for release media in order for it to be reflected on the mirrors. It may also be useful for catalyst to raise an error if the sharedir is empty, but I'm not sure if this behaviour might otherwise be desired...
*** Bug 664686 has been marked as a duplicate of this bug. ***
(In reply to Daniel Cordero from comment #2) > This might be related to the stabilisation of catalyst 3.0.2 on amd64 on the > 15th of August. > It is and I'm on it.
(In reply to Anthony Basile from comment #4) > (In reply to Daniel Cordero from comment #2) > > This might be related to the stabilisation of catalyst 3.0.2 on amd64 on the > > 15th of August. > > > > It is and I'm on it. Can people please check the mirrors tomorrow and see if 20180827 has landed and works. If it does, please close this bug. Sorry for the inconvenience, but the system that does this upgraded to catalyst-3 and broke. On back on catalyst-2 for now until I get catalyst-3 working right.
I can confirm that new stage3-systemd is working well.