On Tuesday, 10 June 2025 09:05:50 British Summer Time Xu Che wrote:
Hi everyone,
I'm a new Gentoo user. I've installed Gentoo Prefix on a development
server where I don't have root privileges.
After a fresh installation using the bootstrap-prefix.sh script, I
checked the news and saw the item `2024-03-22-new-23-profiles`, which
advises upgrading to the 23.0 profile.
I tried to follow the upgrade instructions carefully. However, I am
stuck at Step 6 ("Select the 23.0 profile...") because the new 23.0
profiles are not visible when I run `eselect profile list`.
This is the full output I currently see:
$ eselect profile list
Available profile symlink targets:
[1] prefix/linux/amd64 (exp)
[2] default/linux/amd64/17.0/no-multilib/prefix/kernel-3.2+ (exp)
[3] default/linux/amd64/17.0/no-multilib/prefix/kernel-2.6.32+ (exp)
[4] default/linux/amd64/17.0/no-multilib/prefix/kernel-2.6.16+ (exp)
[5] default/linux/amd64/17.1/no-multilib/prefix/kernel-3.2+ (exp) *
[6] default/linux/amd64/17.1/no-multilib/prefix/kernel-2.6.32+ (exp)
[7] default/linux/amd64/17.1/no-multilib/prefix/kernel-2.6.16+ (exp)
However, I've noticed that the new 23.0 profile directories *do exist*
on my filesystem. I've also confirmed they are listed in `profiles/profiles.desc`. Here are the relevant lines from the long
file, which show the small difference in the architecture identifier:
# visible 17.1 profile
amd64-linux
default/linux/amd64/17.1/no-multilib/prefix/kernel-3.2+ exp
# invisible 23.0 profile
amd64 default/linux/amd64/23.0/no-multilib/prefix/kernel-3.2+
exp
Despite being listed, `eselect profile list` will not show the 23.0
profiles.
This leaves me a bit confused about how to proceed. What should I do now?
* Should I manually create the symlink to the new profile to continue
the upgrade?
* Or, is the 23.0 profile not yet supported for Prefix?
Thanks for any guidance!
Best regards,
Xu Che
I haven't dabbled in gentoo $PREFIX for years now and the landscape has
changed since. The eselect command only manages symlinks to files and if you look into it (line 43 onward), the script makes some accommodations for EPREFIX.
In the first instance I would just update portage;
emerge -uaNDv portage
and see if this updates eselect too and its available links to profiles.
If this doesn't fix eselect and no one else advises a more specific approach, you can always symlink /etc/portage/make.profile to your chosen profile,
always taking account of your prefix paths. On my non-prefix installation my make.profile symlink looks like this:
~ $ ls -la /etc/portage/make.profile
lrwxrwxrwx 1 root root 74 Mar 24 2024 /etc/portage/make.profile -> ../../var/ db/repos/gentoo/profiles/default/linux/amd64/23.0/desktop/plasma
HTH,
-----BEGIN PGP SIGNATURE-----
iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmhIgs4ACgkQseqq9sKV ZxmlBBAAxfo4kG5chSmdf3LsPzy3s3KXo0crgEu0rfs4m9yNAA3TNjwhRc1DOvMg rpynaAWVGsAXVZ36LHKATFFGDXIwTMQH5T90uBDD20EYZLM91Ba8hXocCRfqOVe+ WDmNFPFDpZkZjSPZp7uEh9Po42b+MzboXKANy6NKWiJNqWeMrjFI/DacByDzZ2Rh t2ikKYYQUnFPk7loVicR3reIOsFpmcAY0oXBVK4lemn7iN2e2QmcV5gKtZgq3O8X 2mx/K0cqT+prM8bhxKlrXC61kqSehpN7nPyp38HsNgoXBDXnyGj3CX0Sj6wcQkkZ R4qokW6mkHIWIaqH1re01HHyMmASDnECONyT05eq/J5u9Y1QjRWDBjzF3GQsg8AV T+CU67CI3UHLH961D9QOnide13ctJ0PbVUxu9eo1iaw0h+IeeMUIIM1gYU5dXOEv rJopARhrMhC3PaQHX06fk+Bw8xfb36girgy9oNkJF/R+2I7UyjTiQLgUKij6xXPe 98EMcUy1HuLUqg0C5HdtgEHUXIZNIaG8M/UhYh9sSkxh4Nmw8CP+4UJW+Tr53juz 1geIg95QSrmc2YO+TWhDbL66+ZHus1zvKMWgvEXlw7HQAIQDsq6z70v9UJuN4nbM Rffp4BXr8TkiyMqDQ+lvR9g/rqqpKJgp2loIlZGFvHOsrKej1+o=
=WXyU
-----END PGP SIGNATURE-----
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)