Help with ~amd64 Plasma 6 update

[draco005]

Hello,

I have been waiting for Plasma 6 to finally hit ~amd64 and now that it has when I go to update @world I seem to have some blocking packages that I'm not sure how to resolve. Was hoping for some help with this.

emerge -avuDN --backtrack=999 @world : https://paste.gentoo.zip/EDHaWs3c
(I don't normally use --backtrack when updating my system but I was hoping it would help in this case)

emerge --info : https://paste.gentoo.zip/On6AzrAY

It's also not clear to me if the Firefox rust slot dependency is related or not.

Thanks for your help.

[asturm]

You can only have USE=mobi on one of the two slots of kfilemetadata, not both.

[draco005]

Thanks for the reply. I removed mobi from my make.conf and that cleared the kdegraphics-mobipocket block. kde-frameworks/kirigami is still blocked though. I'm not sure how to read the block message to figure out how to proceed.

[asturm]

You can't have USE=examples on both slots of kirigami at the same time.

Why are people enabling this flag globally? It happens again and again.

[pietinger]

draco005,

first of all: Welcome to Gentoo Forums !


@asturm:

[draco005]

@pietinger: Thanks.

@asturm:

Please see https://wiki.gentoo.org/wiki/USE_flag#.22Local.22_vs_.22global.22_USE_flags. "For the end user, whether a USE flag is "global" or "local" has little importance."

When I emerge packages that have source code examples, I want those included, regardless of what package it is, and so I add it to my global USE= variable in make.conf. Same for any feature that I consider a "global" feature for my system, like .mobi support, or mp3 support.

I think a more productive question might be why does a package with multiple slots filled break on both slots having an "examples" USE flag, especially when examples refers generally additional file inclusions and not compiled functionality?

A following question is how to we better inform the user in portage. With the kirigama problem, there was this line in the world update output: [blocks B ] kde-frameworks/kirigami:5[examples] ("kde-frameworks/kirigami:5[examples]" is soft blocking kde-frameworks/kirigami-6.3.0)

I'm assuming the [examples] here is supposed to refer to the USE flag that's blocking kde-frameworks/kirigami-6.3.0.

But for the kfilemetadata blocking there's no equivalent line in the output.

[asturm]

Flags being global does not mean global conflict resolution is provided as a service. Neither is it recommended to enable debug, test or doc flags globally, even though they are global flags. examples is of such minor importance that no extra effort for side by side installability was made, since there was enough to do in other places already.

[draco005]

So I managed to successfully complete the emerge @world by changing my global USE flags, but portage informed me of packages that needed to be rebuilt in @preserved-rebuild, however there are more blockers.

I also rebooting into Plasma 6 and there are some odd things going on (like the resolution is wrong and theres a QML error in System Settings when I go to the monitor settings) that I hope fixing these blocks will solve.

emerge @preserved-rebuild : https://paste.gentoo.zip/VZbBy5vR

I looked through the block messages and its really not clear what is causing the blocks.

Any help is really appreciated.

[Josef.95]

After the @world update, please run

[asturm]