| 1 |
On 9/19/21 12:03 AM, Philip Webb wrote: |
| 2 |
> 210918 cal wrote: |
| 3 |
>>> (kde-frameworks/kglobalaccel-5.82.0-r1:5/5.82::gentoo, installed) USE="-debug -doc -nls -test" ABI_X86="(64)" pulled in by |
| 4 |
>>> (no parents that aren't satisfied by other packages in this slot) |
| 5 |
>> See in particular the last message. |
| 6 |
>> I'm not sure what causes that message in particular, |
| 7 |
>> but it seems like kglobalaccel is causing the problem |
| 8 |
>> by pulling in a bunch of 5.82.0 deps causing a slot conflict. |
| 9 |
> |
| 10 |
> That is the key, but it doesn't work the way you suggest. |
| 11 |
> |
| 12 |
> I cut the Gordian knot Alexander-fashion : |
| 13 |
> I simply unmerged the 7 objecting pkgs via 'emerge -C ... ', |
| 14 |
> ie attica kactivities kconfig kcoreaddons kcrash kglobalaccel kwindowsystem. |
| 15 |
> after that, I was able to update the whole list of pkgs without a problem. |
| 16 |
> |
| 17 |
> This has to be a bug in Portage, |
| 18 |
> at least in the sense of an unintended + obstructive feature. |
| 19 |
> Portage ought to be able to recognise when a set of pkgs |
| 20 |
> are creating destructive circular dependencies among themselves |
| 21 |
> & resolve the conflict by updating all of them together. |
| 22 |
> This sort of traffic-jam happens regularly & has done so for many years : |
| 23 |
> one case is Qt, which forces the user to unmerge the whole set, |
| 24 |
> then merge the updates as a set too. |
| 25 |
> |
| 26 |
> Perhaps one of our hard-working unpaid devs is listening ... (smile). |
| 27 |
> |
| 28 |
|
| 29 |
For what it's worth, I have had these same KDE packages listed above |
| 30 |
installed for 3 years, and have never experienced the slot conflict you |
| 31 |
encountered (in particular, the recent upgrade from 5.82 to 5.85 worked |
| 32 |
fine on my systems). So whether or not the end result could be |
| 33 |
considered a bug in portage, it seems likely that, like others have |
| 34 |
suggested on the thread, there is possibly a strange configuration |
| 35 |
somewhere on your system triggering the problem to occur (I have usually |
| 36 |
found this to be the case when my emerge updates blow up with strange |
| 37 |
conflicts). |
| 38 |
|
| 39 |
I'm not a portage dev, but I suspect if you wanted someone to look into |
| 40 |
it, you'd need to file a bug report and clarify the details about your |
| 41 |
system profile, world set, USE flags, package keywords, whether the |
| 42 |
problem occurs if you emerge @world instead of directly merging certain |
| 43 |
packages, etc. |
| 44 |
|
| 45 |
cal |
Archives