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.
On 18/09/2021 12.10, Philip Webb wrote:
There is an update available for KDE Frameworks.You have another package that wants a kde-frameworks/kcoreaddons < 5.85.0,
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.
so you should look for that package. If you have equery installed,
then run 'equery d kde-frameworks/kcoreaddons' :
you will get a list of potential packages.
Is this the complete message about the conflicts ?
If there is nothing more,
please try again with the --verbose-conflicts emerge parameter.
210918 J.O. Aho wrote:
On 18/09/2021 12.10, Philip Webb wrote:That makes no sense : the pkg cited is Kglobalaccel-5.85.0-r1 ,
There is an update available for KDE Frameworks.You have another package that wants a kde-frameworks/kcoreaddons < 5.85.0, >> so you should look for that package. If you have equery installed,
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.
then run 'equery d kde-frameworks/kcoreaddons' :
you will get a list of potential packages.
which isn't going to want an earlier version of another KDE pkg.
The emphasised value is '=', not '<'.
Someone else offered :
Is this the complete message about the conflicts ?No : there's a long list of the same msgs, but for other KDE pkgs.
If there is nothing more,I already did that.
please try again with the --verbose-conflicts emerge parameter.
Thanks certainly for trying, but has anyone anything more helpful ?
Here is the whole command + output in gruesome detail :
root:522 ~> !498
PYTHON_SINGLE_TARGET="python3_9" emerge -pv --backtrack=30 attica frameworkintegration kactivities kactivities-stats kcmutils kconfig kcoreaddons kcrash kdesu kdnssd kglobalaccel kholidays khtml
kidletime kimageformats knotifyconfig kpeople kross krunner
ktexteditor kwayland kwindowsystem qqc2-desktop-style
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.
On 18/09/2021 12.10, Philip Webb wrote:
There is an update available for KDE Frameworks.Have you actually shown the complete output for the conflict for kcoreaddons? I only see one version listed for the slot.
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 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?
210918 Jack wrote:
On 18/09/2021 12.10, Philip Webb wrote:
There is an update available for KDE Frameworks.Have you actually shown the complete output for the conflict for
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.
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.
=kde-frameworks/kcoreaddons-5.85*:5 required by(kde-frameworks/kdeclarative-5.85.0:5/5.85::gentoo, ebuild scheduled for
=kde-frameworks/kcoreaddons-5.82*:5 required by(kde-frameworks/kcrash-5.82.0:5/5.82::gentoo, installed) USE="-debug
=kde-frameworks/kcrash-5.85*:5 required by(kde-frameworks/kservice-5.85.0:5/5.85::gentoo, ebuild scheduled for
=kde-frameworks/kcrash-5.82*:5 required by(kde-frameworks/kglobalaccel-5.82.0-r1:5/5.82::gentoo, installed)
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
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.
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.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 38:04:28 |
Calls: | 6,648 |
Files: | 12,193 |
Messages: | 5,329,242 |