On 19/09/2021 14:06, Philip Webb wrote:
210919 antlists wrote:
On 19/09/2021 08:03, Philip Webb wrote:
Portage ought to be able to recognise when a set of pkgs
are creating destructive circular dependencies among themselves
& resolve the conflict by updating all of them together.
Until you
On 9/19/21 12:03 AM, Philip Webb wrote:
> 210918 cal wrote:
>>> (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
210919 antlists wrote:
> On 19/09/2021 08:03, Philip Webb wrote:
>> Portage ought to be able to recognise when a set of pkgs
>> are creating destructive circular dependencies among themselves
>> & resolve the conflict by updating all of them together.
> Until you hit my version of the problem,
>
On 19/09/2021 08:03, Philip Webb wrote:
Portage ought to be able to recognise when a set of pkgs
are creating destructive circular dependencies among themselves
& resolve the conflict by updating all of them together.
Until you hit my version of the problem, where if a is not there, b
crashes
210918 cal wrote:
>> (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
On Saturday, 18 September 2021 17.19.45 CEST Philip Webb wrote:
> 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
cal wrote:
>
> 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
>
>
Just a shot in the dark, could some KDE packages have crept
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
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
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
On 9/18/21 09:08, Philip Webb wrote:
210918 J.O. Aho 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
210918 J.O. Aho 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
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
13 matches
Mail list logo
