[gentoo-user] KDE update puzzle

[gentoo-user] KDE update puzzle

[Philip Webb]

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.

-- 
========================,,============================================
SUPPORT     ___________//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT    `-O----------O---'   purslowatchassdotutorontodotca

[gentoo-user] Re: KDE update puzzle

[Nuno Silva]

On 2021-09-18, 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.

Is this the complete message about the conflicts? If there is nothing
more, please try again with the --verbose-conflicts emerge parameter.

-- 
Nuno Silva

Re: [gentoo-user] KDE update puzzle

[cal]

On 9/18/21 2:59 AM, 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.
> 
I replied elsewhere in the thread about my hunch where your problem is,
but just to clarify something here: when there is a slot conflict,
emerge will print the dependents causing the conflict.  You've only
pasted the first message here, which is saying that
kde-frameworks/kglobalaccel-5.85.0-r1 depends on
=kde-frameworks/kcoreaddons-5.85*:5.

Below this line, there is probably another one telling you about a
different package that depends on a mutually exclusive version of
kcoreaddons.  So the "=" here is only telling you what one of the
packages in conflict depends on.

[gentoo-user] Re: KDE update puzzle

[Nuno Silva]

On 2021-09-18, Philip Webb wrote:

> 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.

Portage might be able to handle this automatically if you upgrade @world
directly, but if you only ask to upgrade specific packages (the case
here?), you may be leaving out some package which needs to be upgraded
at the same time.

If that is the problem, solving it is probably a matter of identifying
packages which are not being upgraded and that depend on currently
installed versions of packages that will be upgraded. The output you
have included in the message I'm replying to is, unfortunately, not
enough - unless I'm misreading, I think it only says that:

- kcrash needs to be upgraded to allow the kcoreaddons upgrade, and

- kglobalaccel needs to be upgraded to allow kconfig, kwindowsystem,
  kdbusaddon and kcrash upgrades

But these two are already part of your emerge command, so there is
possibly something else that is not in this list. Could you please share
the output with --verbose-conflicts?

-- 
Nuno Silva