Re: [gentoo-user] faded images with Gwenview : solved

2021-09-18 Thread Philip Webb
210917 Philip Webb wrote:
> It's only when I crop a PNG image in Gwenview
> & save it in place (ie with the same name), that the colors are faded
> & that's only when viewed with Gwenview, not eg with Feh.
> The bad case does look like a Gwenview bug,
> & in fact, as I had forgotten (grimace), I did submit a bug previously :
> KDE Bug 420357 back in April 2020, to which no-one has yet responded.
> I've added a comment & we'll see if there's any response this time.

Tibor Nagy of KDE Bugzilla has replied very promptly :

  My guess this happens due to botched gamma handling.
  Washed out images are a prime symptom of that kind of bugs.
  Seems like when a PNG gAMA chunk is present,
  Gwenview applies the gamma transform in the opposite direction it should,
  thus the washed out images.  Seems to be Qt bug, already fixed in 5.15.x :
  https://github.com/qt/qtbase/commit/de2c3ccd49cb89e0c6912da3b03705a36ef03946

As you can see from the link above, some coder forgot to invert a value,
using 'gamma' when it sb '1/gamma'.

The patch is dated 'June 11', so it make take awhile yet to reach Gentoo.

Meanwhile, I have  2  workarounds which are in fact improvements for me.
I have amended the Imagemagick 'import' command I use for screenshots
to produce them as JPGs, which cb safely cropped already via Gwenview.
Alternatively, Firefox will make screenshots via R-click on its window
& the area to be grabbed cb marked on the screen, so already cropped.

>From the beginning, I thought it was a programming bug,
as it appeared suddenly after a KDE update in spring 2020.

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




Re: [gentoo-user] The old wine/harfbuzz/freetype circle ...

2021-09-18 Thread David Haller
Hello,

On Sat, 18 Sep 2021, antlists wrote:
>I've got stuck on this merry-go-round ...
>
>I'm trying to emerge wine, and it's come up with this. It insisted on adding
>abi_x86_32 or whatever it is to loads of things, but it's now blowing up with
>this circular dependency. If I try and install one with "use = -theother" it
>won't go ...

This should work:

# USE="-harfbuzz" emerge media-libs/freetype
# emerge media-libs/harfbuzz
# emerge media-libs/freetype

HTH,
-dnh

-- 
Sheridan: "If you're gonna wait for the universe to start making
sense you'll have a *long* wait ahead of you."
 -- Babylon 5 - 4x12 - Conflicts of Interest



Re: [gentoo-user] pm-suspend replacement?

2021-09-18 Thread Anna “CyberTailor”
On 2021-09-18 18:39, Alan Mackenzie wrote:
> I feel there must be something like this in portage, I just don't know
> how to find it.

https://wiki.gentoo.org/wiki/Suspend_and_hibernate

sys-power/suspend
sys-power/hibernate-script



Re: [gentoo-user] pm-suspend replacement?

2021-09-18 Thread Marco Rebhan
On Saturday, 18 September 2021 20.39.45 CEST Alan Mackenzie wrote:
> I used to have a utility pm-suspend which would suspend the current
> state of the machine to RAM (or, maybe to the swap partition) and shut
> the machine down to a resting state.  A keypress or mouse movement
> would restore full functionality in a few seconds.

> Is there anything to take its place?

I'm pretty sure pm-suspend is deprecated. loginctl suspend should do the 
same thing.

signature.asc
Description: This is a digitally signed message part.


[gentoo-user] revisit bouncing messages from this list

2021-09-18 Thread Jack
I continue to get the occasional message from gentoo-user+owner that  
messages to me have bounced, but since I am receiving that message,  
things are OK again.  Unfortunately, if I request a re-send of the  
bounced message (it is usually just one) it never arrives, and  
sometimes results in another message about a bounce.  My assumption at  
this point is that the bounce is most likely due to DMARC and related  
rules on the sender's email server and something in the list rewriting  
(or not) some of the headers before forwarding it on to me.  Of course  
with no way of knowing who sent the message, I can't begin to confirm  
that premise, or just see the message, which is what I'd like to do.


I reread most of two threads about this from 2018 and 2019, and there  
was a post that seemed to imply there was a way to translate the  
message number (196927 was the latest from this list for me) to a URL  
to see the message in the list archives at gentoo.org.  Does such a  
translation actually exist, and can someone point me to it?


Thanks.

Jack



[gentoo-user] Re: KDE update puzzle

2021-09-18 Thread nunojsilva
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




[gentoo-user] console scrollback (kernel 5.14)

2021-09-18 Thread Jorge Almeida
Hello, gentooers in general and Alan in particular

I've been using Alan Mackenzie's patch until kernel 5.13, with
success. It failed with 5.14.4 --yes, I know, but it doesn't hurt to
try :)

Jorge Almeida

Just in case it is useful:

(Stripping trailing CRs from patch; use --binary to disable.)
patching file ./include/linux/vt_kern.h
Hunk #1 succeeded at 115 (offset -12 lines).
(Stripping trailing CRs from patch; use --binary to disable.)
patching file ./include/linux/console_struct.h
Hunk #1 succeeded at 110 (offset 1 line).
(Stripping trailing CRs from patch; use --binary to disable.)
patching file ./drivers/video/fbdev/core/fbcon.c
Hunk #1 succeeded at 3053 with fuzz 2 (offset -31 lines).
(Stripping trailing CRs from patch; use --binary to disable.)
patching file ./drivers/video/console/Kconfig
(Stripping trailing CRs from patch; use --binary to disable.)
patching file ./drivers/tty/vt/vt.c
Hunk #11 succeeded at 1358 with fuzz 2.
Hunk #12 succeeded at 1454 (offset -1 lines).
Hunk #13 succeeded at 1519 (offset -1 lines).
Hunk #16 FAILED at 3264.
Hunk #18 succeeded at 3709 (offset -7 lines).
Hunk #19 succeeded at 3736 (offset -7 lines).
Hunk #20 succeeded at 3797 (offset -7 lines).
Hunk #21 succeeded at 4497 (offset -8 lines).
Hunk #22 succeeded at 4798 (offset -8 lines).
1 out of 22 hunks FAILED -- saving rejects to file ./drivers/tty/vt/vt.c.rej
## cat ./drivers/tty/vt/vt.c.rej
--- ./drivers/tty/vt/vt.c.orig  2020-12-13 22:41:30.0 +
+++ ./drivers/tty/vt/vt.c   2021-04-05 16:20:32.624563241 +
@@ -3264,6 +3640,14 @@

param.vc = vc;

+   /* NEW STOUGH, 2021-04-03 */
+#ifdef CONFIG_FRAMEBUFFER_CONSOLE_SOFT_SCROLLBACK
+   /* Undo any soft scrolling -  and  do
+  not pass through this function.  */
+   concon_set_origin (vc);
+#endif
+   /* END OF NEW STOUGH */
+
while (!tty->stopped && count) {
int orig = *buf;
buf++;



Re: [gentoo-user] KDE update puzzle

2021-09-18 Thread Marco Rebhan
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 kcrash kdesu kdnssd kglobalaccel kholidays khtml
> kidletime kimageformats knotifyconfig kpeople kross krunner
> ktexteditor kwayland kwindowsystem qqc2-desktop-style

Is this the command you ran to get this output? I assume the same 
happens with emerge -auDU @world, but did you try emerge -ac first? 
Maybe something is still installed but deselected which I believe causes 
it to not get rebuilt and potentially block other packages. All of these 
packages that claim to pull in the older versions seem to themselves be 
scheduled for update, that's why I'm thinking somewhere there is one 
package that isn't that's causing all this mess.

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

That's what I would suggest if what I wrote above doesn't work. I 
haven't ever encountered this issue myself yet though despite 
extensively using KDE packages, so I'm not sure what's going wrong here.

-Marco

signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] pm-suspend replacement?

2021-09-18 Thread tastytea
On 2021-09-18 18:39+ Alan Mackenzie  wrote:

> Hello, Gentoo.
> 
> I used to have a utility pm-suspend which would suspend the current
> state of the machine to RAM (or, maybe to the swap partition) and shut
> the machine down to a resting state.  A keypress or mouse movement
> would restore full functionality in a few seconds.
> 
> I think I lost this program in the emerge --depclean I did a couple of
> months ago (the one that wanted to make my machine unbootable).
> 
> Is there anything to take its place?  In particular I want actively to
> put the machine into resting state (as opposed to it happening after a
> period of inactivity), and I would prefer to do this without having to
> start a GUI session.
> 
> I feel there must be something like this in portage, I just don't know
> how to find it.
> 
> Thanks for the help!
> 

`loginctl suspend`[1] if you use sys-auth/elogind. `echo mem >
/sys/power/state`[2] if not.

[1] 
[2] 

-- 
Get my PGP key with `gpg --locate-keys tasty...@tastytea.de` or at
.


pgp8XLdUQN6XG.pgp
Description: Digitale Signatur von OpenPGP


[gentoo-user] pm-suspend replacement?

2021-09-18 Thread Alan Mackenzie
Hello, Gentoo.

I used to have a utility pm-suspend which would suspend the current
state of the machine to RAM (or, maybe to the swap partition) and shut
the machine down to a resting state.  A keypress or mouse movement would
restore full functionality in a few seconds.

I think I lost this program in the emerge --depclean I did a couple of
months ago (the one that wanted to make my machine unbootable).

Is there anything to take its place?  In particular I want actively to
put the machine into resting state (as opposed to it happening after a
period of inactivity), and I would prefer to do this without having to
start a GUI session.

I feel there must be something like this in portage, I just don't know
how to find it.

Thanks for the help!

-- 
Alan Mackenzie (Nuremberg, Germany).



[gentoo-user] The old wine/harfbuzz/freetype circle ...

2021-09-18 Thread antlists

I've got stuck on this merry-go-round ...

I'm trying to emerge wine, and it's come up with this. It insisted on 
adding abi_x86_32 or whatever it is to loads of things, but it's now 
blowing up with this circular dependency. If I try and install one with 
"use = -theother" it won't go ...


If I try --nodeps, the config blows up ...

Looking on the web, everybody seems to be recommending those approaches 
but they're not working. It does say circular dependencies are hard to 
fix. The only thing I haven't got at the moment is ~amd. Is that likely 
to help?


Any advice please ...

Cheers,
Wol



Re: [gentoo-user] KDE update puzzle

2021-09-18 Thread Dale
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 their way in
the world file maybe, perhaps even a specific version, older version at
that? 

Dale

:-)  :-) 



Re: [gentoo-user] KDE update puzzle

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



Re: [gentoo-user] KDE update puzzle

2021-09-18 Thread cal
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



Re: [gentoo-user] KDE update puzzle

2021-09-18 Thread Philip Webb
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 :

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

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N ] x11-base/xwayland-21.1.2-r2::gentoo  USE="-ipv6 -rpc 
(-selinux) -unwind -xcsecurity" VIDEO_CARDS="-nvidia" 1,230 KiB
[ebuild U  ] kde-frameworks/extra-cmake-modules-5.85.0:5/5.85::gentoo 
[5.82.0:5/5.82::gentoo] USE="-doc -test" 311 KiB
[ebuild U  ] kde-frameworks/kcoreaddons-5.85.0:5/5.85::gentoo 
[5.82.0:5/5.82::gentoo] USE="-debug -doc (-fam) -nls -test" 418 KiB
[ebuild U  ] kde-frameworks/kconfig-5.85.0:5/5.85::gentoo 
[5.82.0:5/5.82::gentoo] USE="dbus -debug -doc -nls -test" 265 KiB
[ebuild U  ] kde-frameworks/ki18n-5.85.0:5/5.85::gentoo 
[5.82.0:5/5.82::gentoo] USE="-debug -doc -test" 
PYTHON_SINGLE_TARGET="(-python3_10) -python3_8 python3_9" 577 KiB
[ebuild U  ] kde-frameworks/kwidgetsaddons-5.85.0:5/5.85::gentoo 
[5.82.0:5/5.82::gentoo] USE="-debug -designer -doc -nls -test" 2,253 KiB
[ebuild U  ] kde-frameworks/kwindowsystem-5.85.0:5/5.85::gentoo 
[5.82.0:5/5.82::gentoo] USE="X -debug -doc -nls -test" 175 KiB
[ebuild U  ] kde-frameworks/karchive-5.85.0:5/5.85::gentoo 
[5.82.0:5/5.82::gentoo] USE="-debug -doc -test -zstd" 963 KiB
[ebuild U  ] kde-frameworks/kdbusaddons-5.85.0:5/5.85::gentoo 
[5.82.0:5/5.82::gentoo] USE="X -debug -doc -nls -test" 43 KiB
[ebuild U  ] kde-frameworks/kitemviews-5.85.0:5/5.85::gentoo 
[5.82.0:5/5.82::gentoo] USE="-debug -designer -doc -nls -test" 74 KiB
[ebuild U  ] kde-frameworks/kguiaddons-5.85.0:5/5.85::gentoo 
[5.82.0:5/5.82::gentoo] USE="-debug -doc -test -wayland" 60 KiB
[ebuild U  ] kde-frameworks/kcodecs-5.85.0:5/5.85::gentoo 
[5.82.0:5/5.82::gentoo] USE="-debug -doc -nls -test" 227 KiB
[ebuild U  ] kde-frameworks/kwayland-5.85.0-r1:5/5.85::gentoo 
[5.82.0:5/5.82::gentoo] USE="-debug -doc -test" 324 KiB
[ebuild U  ] kde-frameworks/sonnet-5.85.0:5/5.85::gentoo 
[5.82.0:5/5.82::gentoo] USE="-aspell -debug -designer -doc -hunspell -nls 
-test" 291 KiB
[ebuild U  ] kde-frameworks/solid-5.85.0:5/5.85::gentoo 
[5.82.0:5/5.82::gentoo] USE="-debug -doc -ios -nls -test" 246 KiB
[ebuild  r  U  ] kde-frameworks/kidletime-5.85.0:5/5.85::gentoo 
[5.82.0:5/5.82::gentoo] USE="X -debug -doc -xscreensaver" 26 KiB
[ebuild U  ] kde-frameworks/attica-5.85.0:5/5.85::gentoo 
[5.82.0:5/5.82::gentoo] USE="-debug -doc -test" 66 KiB
[ebuild  N ] kde-plasma/layer-shell-qt-5.22.5:5::gentoo  USE="-debug" 18 KiB
[ebuild U  ] kde-frameworks/syntax-highlighting-5.85.0-r1:5/5.85::gentoo 
[5.82.0:5/5.82::gentoo] USE="-debug -doc -nls -test" 2,281 KiB
[ebuild U  ] kde-frameworks/threadweaver-5.85.0:5/5.85::gentoo 
[5.82.0:5/5.82::gentoo] USE="-debug -doc -test" 1,378 KiB
[ebuild U  ] kde-frameworks/kdnssd-5.85.0:5/5.85::gentoo 
[5.82.0:5/5.82::gentoo] USE="-debug -doc -nls -test -zeroconf" 58 KiB
[ebuild U  ] kde-frameworks/kholidays-5.85.0:5/5.85::gentoo 
[5.82.0:5/5.82::gentoo] USE="-debug -nls -test" 226 KiB
[ebuild U  ] kde-frameworks/kcrash-5.85.0:5/5.85::gentoo 
[5.82.0:5/5.82::gentoo] USE="-debug -doc -nls -test" 28 KiB
[ebuild U  ] kde-frameworks/kcompletion-5.85.0:5/5.85::gentoo 
[5.82.0:5/5.82::gentoo] USE="-debug -designer -doc -nls -test" 120 KiB
[ebuild U  ] kde-frameworks/kpackage-5.85.0:5/5.85::gentoo 
[5.82.0:5/5.82::gentoo] USE="-debug -doc 

Re: [gentoo-user] KDE update puzzle

2021-09-18 Thread Jack

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

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,
then run 'equery d kde-frameworks/kcoreaddons' :
you will get a list of potential packages.

That makes no sense : the pkg cited is Kglobalaccel-5.85.0-r1 ,
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,
please try again with the --verbose-conflicts emerge parameter.

I already did that.

Thanks certainly for trying, but has anyone anything more helpful ?


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?


Jack




Re: [gentoo-user] KDE update puzzle

2021-09-18 Thread Philip Webb
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 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.
> 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,
> then run 'equery d kde-frameworks/kcoreaddons' :
> you will get a list of potential packages.

That makes no sense : the pkg cited is Kglobalaccel-5.85.0-r1 ,
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,
> please try again with the --verbose-conflicts emerge parameter.

I already did that.

Thanks certainly for trying, but has anyone anything more helpful ?

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




[gentoo-user] Re: KDE update puzzle

2021-09-18 Thread nunojsilva
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




[gentoo-user] KDE update puzzle

2021-09-18 Thread 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