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 by >> (no parents that aren't satisfied by other packages in this slot) > See in particular the last message. > 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). -- ========================,,============================================ SUPPORT ___________//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT `-O----------O---' purslowatchassdotutorontodotca
