| 1 |
210918 cal wrote: |
| 2 |
>> (kde-frameworks/kglobalaccel-5.82.0-r1:5/5.82::gentoo, installed) USE="-debug -doc -nls -test" ABI_X86="(64)" pulled in by |
| 3 |
>> (no parents that aren't satisfied by other packages in this slot) |
| 4 |
> See in particular the last message. |
| 5 |
> I'm not sure what causes that message in particular, |
| 6 |
> but it seems like kglobalaccel is causing the problem |
| 7 |
> by pulling in a bunch of 5.82.0 deps causing a slot conflict. |
| 8 |
|
| 9 |
That is the key, but it doesn't work the way you suggest. |
| 10 |
|
| 11 |
I cut the Gordian knot Alexander-fashion : |
| 12 |
I simply unmerged the 7 objecting pkgs via 'emerge -C ... ', |
| 13 |
ie attica kactivities kconfig kcoreaddons kcrash kglobalaccel kwindowsystem. |
| 14 |
after that, I was able to update the whole list of pkgs without a problem. |
| 15 |
|
| 16 |
This has to be a bug in Portage, |
| 17 |
at least in the sense of an unintended + obstructive feature. |
| 18 |
Portage ought to be able to recognise when a set of pkgs |
| 19 |
are creating destructive circular dependencies among themselves |
| 20 |
& resolve the conflict by updating all of them together. |
| 21 |
This sort of traffic-jam happens regularly & has done so for many years : |
| 22 |
one case is Qt, which forces the user to unmerge the whole set, |
| 23 |
then merge the updates as a set too. |
| 24 |
|
| 25 |
Perhaps one of our hard-working unpaid devs is listening ... (smile). |
| 26 |
|
| 27 |
-- |
| 28 |
========================,,============================================ |
| 29 |
SUPPORT ___________//___, Philip Webb |
| 30 |
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto |
| 31 |
TRANSIT `-O----------O---' purslowatchassdotutorontodotca |
Archives