With new profiles, we need to generate images with those new profiles.
Is this bug still relevant? I checked `eselect list profiles` in a recent stage3 docker image, and I saw the merged-usr profiles in there
I did a spot check on https://hub.docker.com/layers/gentoo/stage3/latest/images/sha256-21fbf5bdf26f6ba4ff3bd3a8d8e9214c8bcb29abfb450fde4bb7b7ac4a66f38d?context=explore and found the amd64 version using default/linux/amd64/17.1/systemd/merged-usr but the 386 version using default/linux/x86/17.0.
The default (17.1) binhost in the docker images is now offline, only 23.0 remains: https://distfiles.gentoo.org/releases/amd64/binpackages/ Please update the profiles of the docker images, the lack of 23.0/merged-usr is slowing things down for me [1] and I suspect it also affects the building of gentoo-kernel-bin[2]. [1] https://github.com/projg2/installkernel-gentoo/actions [2] https://github.com/projg2/binpkg-docker/
The Docker images just pull in whatever the latest stage3 is for the given type, so they should naturally get newer profiles as the underlying stage3's get updated defaults. Seems like the newer 23.0 images are indeed merged-usr by default. Am I missing any somehow?