(kde-frameworks/kglobalaccel-5.82.0-r1:5/5.82::gentoo, installed) USE="-debug -doc -nls -test" ABI_X86="(64)" pulled in bySee in particular the last message.
(no parents that aren't satisfied by other packages in this slot)
I'm not sure what causes that message in particular,
but it seems like kglobalaccel is causing the problem
by pulling in a bunch of 5.82.0 deps causing a slot conflict.
Portage ought to be able to recognise when a set of pkgs
are creating destructive circular dependencies among themselves
& resolve the conflict by updating all of them together.
On 19/09/2021 08:03, Philip Webb wrote:
Portage ought to be able to recognise when a set of pkgsUntil you hit my version of the problem,
are creating destructive circular dependencies among themselves
& resolve the conflict by updating all of them together.
where if a is not there, b crashes when you try to build it ...
And of course, installing a crashes because b is not there ...
210918 cal wrote:
(kde-frameworks/kglobalaccel-5.82.0-r1:5/5.82::gentoo, installed) USE="-debug -doc -nls -test" ABI_X86="(64)" pulled in bySee in particular the last message.
(no parents that aren't satisfied by other packages in this slot)
I'm not sure what causes that message in particular,
but it seems like kglobalaccel is causing the problem
by pulling in a bunch of 5.82.0 deps causing a slot conflict.
That is the key, but it doesn't work the way you suggest.
I cut the Gordian knot Alexander-fashion :
I simply unmerged the 7 objecting pkgs via 'emerge -C ... ',
ie attica kactivities kconfig kcoreaddons kcrash kglobalaccel kwindowsystem. after that, I was able to update the whole list of pkgs without a problem.
This has to be a bug in Portage,
at least in the sense of an unintended + obstructive feature.
Portage ought to be able to recognise when a set of pkgs
are creating destructive circular dependencies among themselves
& resolve the conflict by updating all of them together.
This sort of traffic-jam happens regularly & has done so for many years :
one case is Qt, which forces the user to unmerge the whole set,
then merge the updates as a set too.
Perhaps one of our hard-working unpaid devs is listening ... (smile).
210919 antlists wrote:
On 19/09/2021 08:03, Philip Webb wrote:
Portage ought to be able to recognise when a set of pkgsUntil you hit my version of the problem,
are creating destructive circular dependencies among themselves
& resolve the conflict by updating all of them together.
where if a is not there, b crashes when you try to build it ...
And of course, installing a crashes because b is not there ...
So you emerge both together :
I've never run into a version of your case where that wasn't the solution. And I don't expect anything like that to happen
with a related group of pkgs like Qt or KDE.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 293 |
Nodes: | 16 (2 / 14) |
Uptime: | 228:27:24 |
Calls: | 6,624 |
Calls today: | 6 |
Files: | 12,171 |
Messages: | 5,318,992 |