After finding out that the council recently promoted 17.1 (the multilib thing) from experimental status I'd like to suggest that it further be made the new default profile in stage3 images.
Everything about the stage is in charge to releng.
My intent with this suggestion is to establish the planned future default as soon as possible, starting with new installs that are by definition not vulnerable to potential migration issues that bug 506276 is handling. Early amendment of the stage3 will also preempt new installs from adding to the support and migration burden in the future, so I see it as a good investment of "do this little thing now to save an increasing amount of time later".
Sorry for rather useless comment: suppose this bug was handled and the stage3 tarballs are based of new 17.1 profile. Perhaps it is already 17.1 as of 8th of June, 2019. How does one check chrooted into the tarball the profile the stage3 tarball was built with? mind you the /usr/portage/profile doesn't exist there, so eselect profile list doesn't work. I couldn't work this out.
(In reply to aidar from comment #3) > Sorry for rather useless comment: > > suppose this bug was handled and the stage3 tarballs are based of new 17.1 > profile. > > Perhaps it is already 17.1 as of 8th of June, 2019. How does one check > chrooted into the tarball the profile the stage3 tarball was built with? > mind you the /usr/portage/profile doesn't exist there, so eselect profile > list doesn't work. > > I couldn't work this out. The stages aren't 17.1 based yet. They won't be until we do some changes and we will announce when that happens. I plan to start working on the 17.1 stages on my own build server this week. When I have some ready, I'll ask on #gentoo-releng and add a note here, asking for those interested to test them.
I've finished the work on my build server and have now completed a 2nd run of 17.1 stage building. Anyone interested, please test the following stages: https://www.jmbsvicetto.name/releases/experimental/amd64/default/20190622/ https://www.jmbsvicetto.name/releases/experimental/amd64/hardened/20190622/ Unless someone in releng objects, I plan to switch the official amd64 stages to the 17.1 profiles in the beginning of July.
(In reply to Jorge Manuel B. S. Vicetto from comment #5) > I've finished the work on my build server and have now completed a 2nd run > of 17.1 stage building. Anyone interested, please test the following stages: > > https://www.jmbsvicetto.name/releases/experimental/amd64/default/20190622/ > https://www.jmbsvicetto.name/releases/experimental/amd64/hardened/20190622/ > > Unless someone in releng objects, I plan to switch the official amd64 stages > to the 17.1 profiles in the beginning of July. All the stages on the main Gentoo download page are still showing 17.0 profiles. Are there any bugs preventing them from being built with 17.1?
For those who didn't notice yet, stage3 are now in 17.1 profile.
(In reply to Stéphane Veyret from comment #7) > For those who didn't notice yet, stage3 are now in 17.1 profile. I've finally been able to update Gentoo's official box to use the new 17.1 profiles for amd64. There are now 17.1 stages[1] on the mirrors. [1] - http://distfiles.gentoo.org/releases/amd64/autobuilds/20190716T103222Z/
