On 9/18/21 8:19 AM, Philip Webb wrote: > 210918 Jack wrote: >> On 18/09/2021 12.10, Philip Webb wrote: >>> There is an update available for KDE Frameworks. >>> When I try to perform it, I get a conflict statement which begins >>> >>> !!! Multiple package instances within a single package slot have been >>> pulled >>> !!! into the dependency graph, resulting in a slot conflict: >>> kde-frameworks/kcoreaddons:5 >>> >>> (kde-frameworks/kcoreaddons-5.85.0:5/5.85::gentoo, ebuild scheduled for >>> merge) USE="-debug -doc (-fam) -nls -test" ABI_X86="(64)" pulled in by >>> =kde-frameworks/kcoreaddons-5.85*:5 required by >>> (kde-frameworks/kglobalaccel-5.85.0-r1:5/5.85::gentoo, ebuild scheduled for >>> merge) USE="-debug -doc -nls -test" ABI_X86="(64)" >>> ^ ^^^^^^^ >>> >>> The ^ signs emphasise =kde-frameworks/kcoreaddons-5.85*:5 >>> >>> I can't make sense of this : surely, '5.85*' includes '5.85.0', >>> so the requirement sb fulfilled. I don't remember seeing this before. >> Have you actually shown the complete output for the conflict for >> kcoreaddons? I only see one version listed for the slot. >> Is there another one showing perhaps the current installed version >> and it being required by something else (also installed) >> which cannot work with the newer version? > > Here is the whole command + output in gruesome detail : > > (elided) > > --- end of gruesome details --- > > It mb that I have to remove the whole of the present versions > in order to (re-)install the new ones ; it usually happens with Qt. > I've never understood why Portage can't handle that itself. >
Tracing through the slot conflicts: There is a conflict between kde-frameworks/kcoreaddons-5.85.0 and -5.82.0, this is what the first messages in your gruesome detail are saying: > =kde-frameworks/kcoreaddons-5.85*:5 required by (kde-frameworks/kdeclarative-5.85.0:5/5.85::gentoo, ebuild scheduled for merge) USE="-debug -doc" ABI_X86="(64)" > =kde-frameworks/kcoreaddons-5.82*:5 required by (kde-frameworks/kcrash-5.82.0:5/5.82::gentoo, installed) USE="-debug -doc -nls -test" ABI_X86="(64)" So why is kcrash-5.82.0 being pulled in? This package is the result of another slot conflict: > =kde-frameworks/kcrash-5.85*:5 required by (kde-frameworks/kservice-5.85.0:5/5.85::gentoo, ebuild scheduled for merge) USE="-debug -doc -man -test" ABI_X86="(64)" > =kde-frameworks/kcrash-5.82*:5 required by (kde-frameworks/kglobalaccel-5.82.0-r1:5/5.82::gentoo, installed) USE="-debug -doc -nls -test" ABI_X86="(64)" So why is kglobalaccel-5.82.0 being pulled in? > kde-frameworks/kglobalaccel:5 > > (kde-frameworks/kglobalaccel-5.85.0-r1:5/5.85::gentoo, ebuild scheduled for > merge) USE="-debug -doc -nls -test" ABI_X86="(64)" pulled in by > kde-frameworks/kglobalaccel (Argument) > =kde-frameworks/kglobalaccel-5.85*:5 required by > (kde-frameworks/kxmlgui-5.85.0:5/5.85::gentoo, ebuild scheduled for merge) > USE="-debug -designer -doc -test" ABI_X86="(64)" > ^ ^^^^^^^ > > > > > (and 3 more with the same problems) > > (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. cal
