dev-lang/perl causes slot conflicts when updating

[Shadow_Fury]

when trying to update "system, install cucumber, and finally just update perl, all causes a nasty slot conflict that i am unsure on how to resolve

here's the verbose list from trying to update perl

[freke]

Are you mixing stable and unstable? (I see dev-lang/perl-5.40.0 which is not marked stable, but also see app-text/po4a-0.69 which is the latest stable)

That can be hard-ish to maintain.

[Shadow_Fury]

[Hu]

Are you trying to update perl or trying to update world, and perl happens to be part of world? You should show the full command you used, so that we can check that. The output looks like you are trying to change only perl, and thus causing a subslot conflict because you are not rebuilding things which depend on perl:0/5.38.

[Shadow_Fury]

i've tried:

[Hu]

What happens if you update @world? Updating @system is unusual, and often not what you want.

[Shadow_Fury]

exact same thing. just tried it and perl is still conflicting

[Hu]

Are those virtuals not reachable from world? Does emerge --ask --depclean offer to remove them?

[flexibeast]

Is this one of those situations where one needs to use app-admin/perl-cleaner:

[Shadow_Fury]

[Hu]

This seems weird. I could believe these kinds of problems on an old system that has not been maintained, but you said this is a new and not yet finished system. I still think the issue is that you have packages that have a subslot-dependency on old perl and are not reachable from a deep world upgrade, so emerge -avuUD @world does not plan to upgrade them, and since it does not upgrade them, you get a conflict. Forcing emerge to include those in the update by naming them explicitly will probably work: emerge -avuUD1 --autounmask-keep-masks=y @world app-text/po4a (and 29 more with the same problem). They all need to be done in one command, so that Portage has permission to rebuild all of them.

[Shadow_Fury]

[freke]

Show emerge --info ?

Are you also setting up/running SELinux (one of your outputs mentioned SELinux)

[Shadow_Fury]

here's emerge --info:

[Hu]

You are welcome to wipe and restart, but there is no reason to believe you will not make the same as-yet-unidentified mistakes again. Generally, we discourage people from wiping and restarting.

You did not previously mention that this system is LLVM-based, nor did your first post mention SELinux. When you choose unusual system options, you should mention them, so that prospective helpers know this system is unusual.

I see numerous non-default CFLAGS enabled. Where did you get these?

For your libffi problem, I suggest you follow the instructions that Portage printed when it failed.

[Shadow_Fury]

[Hu]

We do try to keep on subject, though an argument could be made that since you need to update the system before you can fix your perl problem, that libffi could go here. I suggest opening a new thread about your libffi problem, and posting here a link to that thread. Once that thread is resolved, we can return to perl.

[Shadow_Fury]

new thread about libffi issue: https://forums.gentoo.org/viewtopic-p-8837101.html#8837101