Good evening all, calling on the accumulated wisdom here.

kde-frameworks 5.88 has been marked stable, but my upgrade is blocked
because kwin (5.22.5 is stable, 5.23.4 is still marked testing) is
somehow stuck on kde-frameworks/kglobalaccel-5.85.

The line from portage is:
(kde-frameworks/kglobalaccel-5.85.0-r1:5/5.85::gentoo, installed) USE="-debug -doc -nls -test" ABI_X86="(64)" pulled in by
>=kde-frameworks/kglobalaccel-5.82.0:5/5.85= required by (kde-plasma/kwin-5.22.5:5/5::gentoo, installed) USE="caps handbook
plasma -accessibility -debug -gles2-only -multimedia -screencast -test" ABI_X86="(64)"

The actual line in the kwin ebuild is
>=kde-frameworks/kglobalaccel-${KFMIN}:5=
so I'm assuming that trailing "=" is the culprit, although I don't
really follow the syntax.

Is there any easy way around this, or does it just mean I can't upgrade
any of kde-frameworks from 5.85 to 5.88 until kde-plasma 5.24.something
is marked stable or I unmask it? I'm not in any great rush, but it
means emerge @world always fails, and I've got to individually pick out
those packages I CAN upgrade.

Jack

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sat, 11 Dec 2021 at 02:09, Jack <ostroffjh@users.sourceforge.net> wrote:

The line from portage is:
(kde-frameworks/kglobalaccel-5.85.0-r1:5/5.85::gentoo, installed) USE="-debug -doc -nls -test" ABI_X86="(64)" pulled in by
>=kde-frameworks/kglobalaccel-5.82.0:5/5.85= required by (kde-plasma/kwin-5.22.5:5/5::gentoo, installed) USE="caps handbook
plasma -accessibility -debug -gles2-only -multimedia -screencast -test" ABI_X86="(64)"

Feels like there should be more output that would explain this,
nothing in this output claims that this dependency would not be
satisfied by the upgrade. Please post more if you can.

Cheers,
Arve

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Jack wrote:

Good evening all, calling on the accumulated wisdom here.

kde-frameworks 5.88 has been marked stable, but my upgrade is blocked
because kwin (5.22.5 is stable, 5.23.4 is still marked testing) is
somehow stuck on kde-frameworks/kglobalaccel-5.85.

The line from portage is:
  (kde-frameworks/kglobalaccel-5.85.0-r1:5/5.85::gentoo, installed) USE="-debug -doc -nls -test" ABI_X86="(64)" pulled in by
    >=kde-frameworks/kglobalaccel-5.82.0:5/5.85= required by (kde-plasma/kwin-5.22.5:5/5::gentoo, installed) USE="caps handbook
plasma -accessibility -debug -gles2-only -multimedia -screencast
-test" ABI_X86="(64)"

The actual line in the kwin ebuild is
        >=kde-frameworks/kglobalaccel-${KFMIN}:5=
so I'm assuming that trailing "=" is the culprit, although I don't
really follow the syntax.

Is there any easy way around this, or does it just mean I can't
upgrade any of kde-frameworks from 5.85 to 5.88 until kde-plasma 5.24.something is marked stable or I unmask it?  I'm not in any great
rush, but it means emerge @world always fails, and I've got to
individually pick out those packages I CAN upgrade.

Jack

I think I run into a problem with this a while back.  I run unstable
with KDE.  I think it was a USE flag that needed changing to fix it but
I can't recall what I had to change.  I don't have notes.  May want to
look at the output just in case you are hitting the same thing and it
isn't obvious.

The best thing, post the entire output including the command itself. 
If, like me, you have defaults set in make.conf, you may need to post
them too.  On occasion, I copy it from emerge.log since it records all options, from command line as well as make.conf settings. 

Dale

:-)  :-) 

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, 10 Dec 2021 20:09:19 -0500
Jack <ostroffjh@users.sourceforge.net> wrote:

Good evening all, calling on the accumulated wisdom here.

kde-frameworks 5.88 has been marked stable, but my upgrade is blocked
because kwin (5.22.5 is stable, 5.23.4 is still marked testing) is
somehow stuck on kde-frameworks/kglobalaccel-5.85.

The line from portage is:
(kde-frameworks/kglobalaccel-5.85.0-r1:5/5.85::gentoo, installed) USE="-debug -doc -nls -test" ABI_X86="(64)" pulled in by
>=kde-frameworks/kglobalaccel-5.82.0:5/5.85= required by (kde-plasma/kwin-5.22.5:5/5::gentoo, installed) USE="caps handbook
plasma -accessibility -debug -gles2-only -multimedia -screencast
-test" ABI_X86="(64)"

The actual line in the kwin ebuild is
>=kde-frameworks/kglobalaccel-${KFMIN}:5=
so I'm assuming that trailing "=" is the culprit, although I don't
really follow the syntax.

Is there any easy way around this, or does it just mean I can't
upgrade any of kde-frameworks from 5.85 to 5.88 until kde-plasma 5.24.something is marked stable or I unmask it? I'm not in any great
rush, but it means emerge @world always fails, and I've got to
individually pick out those packages I CAN upgrade.

Jack

I am having the same problem. It appears as though kde-frameworks 5.88
depends on a matching upgrade to kde-plasma to version 5.23.4.
Frameworks has been marked stable, but plasma has not yet :-(

See these bugs:

- https://bugs.gentoo.org/816042 "KDE Frameworks 5.88 stabilisation"
which has a status of IN_PROGRESS

- https://bugs.gentoo.org/826898 "KDE Plasma 5.23.4 stabilisation"
which has a status of CONFIRMED

So I think we are just going to have to wait for kde-plasma to be
marked stable.

Steve
--
____________________________________________________________________
Steve Evans E-mail: mailto:stevee@gorbag.com
Registered Linux user #217906: http://counter.li.org
Public Encryption Key: http://www.gorbag.com/public-key.html ____________________________________________________________________

5.10.76-gentoo-r1 Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz GNU/Linux

12:08:12 up 34 days, 22:07, 5 users, load average: 0.70, 1.16, 0.78

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2021.12.11 07:14, Steve Evans wrote:

On Fri, 10 Dec 2021 20:09:19 -0500 Jack
<ostroffjh@users.sourceforge.net> wrote:

Good evening all, calling on the accumulated wisdom here.

kde-frameworks 5.88 has been marked stable, but my upgrade is

blocked

because kwin (5.22.5 is stable, 5.23.4 is still marked testing) is
somehow stuck on kde-frameworks/kglobalaccel-5.85.

The line from portage is:
(kde-frameworks/kglobalaccel-5.85.0-r1:5/5.85::gentoo, installed) USE="-debug -doc -nls -test" ABI_X86="(64)" pulled in by
>=kde-frameworks/kglobalaccel-5.82.0:5/5.85= required by (kde-plasma/kwin-5.22.5:5/5::gentoo, installed) USE="caps handbook
plasma -accessibility -debug -gles2-only -multimedia -screencast
-test" ABI_X86="(64)"

The actual line in the kwin ebuild is
>=kde-frameworks/kglobalaccel-${KFMIN}:5=
so I'm assuming that trailing "=" is the culprit, although I don't
really follow the syntax.

Is there any easy way around this, or does it just mean I can't
upgrade any of kde-frameworks from 5.85 to 5.88 until kde-plasma 5.24.something is marked stable or I unmask it? I'm not in any

great

rush, but it means emerge @world always fails, and I've got to
individually pick out those packages I CAN upgrade.

Jack

I am having the same problem. It appears as though kde-frameworks 5.88 depends on a matching upgrade to kde-plasma to version 5.23.4.
Frameworks has been marked stable, but plasma has not yet :-(

See these bugs:

- https://bugs.gentoo.org/816042 "KDE Frameworks 5.88 stabilisation"
which has a status of IN_PROGRESS

- https://bugs.gentoo.org/826898 "KDE Plasma 5.23.4 stabilisation"
which has a status of CONFIRMED

So I think we are just going to have to wait for kde-plasma to be
marked stable.

I suppose the frameworks stabilization is still "in progress" because
not all arch's are stable, but amd64 is, which is the only one I need.
The plasma stabilization did say it was dependent on the frameworks
updates, but it doesn't say anything about why the older plasma (kwin
in particular) seems to be preventing the frameworks update.

Anyway, I decided dto go ahead and accept the testing plasma packages.
I initially put "=kde-plasma/*-5.23* ~amd64" into my packages.accept
file. eix showed (~) for kwin, but emerge complained about that syntax
and didn't accept it. I ended up with "kde-plasma/* ~amd64". I don't
know why the other syntax wasn't ok with portage, but as soon as that
second bug does get settled, I can remove that line, so I'm not too
worried about it being over inclusive.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sat, 11 Dec 2021 12:14:23 +0000
Steve Evans <gentoo-user@gorbag.com> wrote:

On Fri, 10 Dec 2021 20:09:19 -0500
Jack <ostroffjh@users.sourceforge.net> wrote:

Good evening all, calling on the accumulated wisdom here.

kde-frameworks 5.88 has been marked stable, but my upgrade is
blocked because kwin (5.22.5 is stable, 5.23.4 is still marked
testing) is somehow stuck on kde-frameworks/kglobalaccel-5.85.

The line from portage is:
(kde-frameworks/kglobalaccel-5.85.0-r1:5/5.85::gentoo,
installed) USE="-debug -doc -nls -test" ABI_X86="(64)" pulled in by
>=kde-frameworks/kglobalaccel-5.82.0:5/5.85= required by (kde-plasma/kwin-5.22.5:5/5::gentoo, installed) USE="caps handbook
plasma -accessibility -debug -gles2-only -multimedia -screencast
-test" ABI_X86="(64)"

The actual line in the kwin ebuild is
>=kde-frameworks/kglobalaccel-${KFMIN}:5=
so I'm assuming that trailing "=" is the culprit, although I don't
really follow the syntax.

Is there any easy way around this, or does it just mean I can't
upgrade any of kde-frameworks from 5.85 to 5.88 until kde-plasma 5.24.something is marked stable or I unmask it? I'm not in any
great rush, but it means emerge @world always fails, and I've got to individually pick out those packages I CAN upgrade.

Jack

I am having the same problem. It appears as though kde-frameworks 5.88 depends on a matching upgrade to kde-plasma to version 5.23.4.
Frameworks has been marked stable, but plasma has not yet :-(

See these bugs:

- https://bugs.gentoo.org/816042 "KDE Frameworks 5.88 stabilisation"
which has a status of IN_PROGRESS

- https://bugs.gentoo.org/826898 "KDE Plasma 5.23.4 stabilisation"
which has a status of CONFIRMED

So I think we are just going to have to wait for kde-plasma to be
marked stable.

Steve

A bug has been opened for this problem https://bugs.gentoo.org/828963.
It suggested emerging with --backtrack=200. That solved the problem for
me.

Steve
--
____________________________________________________________________
Steve Evans E-mail: mailto:stevee@gorbag.com
Registered Linux user #217906: http://counter.li.org
Public Encryption Key: http://www.gorbag.com/public-key.html ____________________________________________________________________

5.10.76-gentoo-r1 Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz GNU/Linux

09:13:59 up 35 days, 19:12, 5 users, load average: 3.05, 2.13, 1.37

Science and religion are in full accord but science and faith are in
complete discord.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)