From: Jack <ostroffjh@users.sourceforge.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] KDE upgrade dependency problem
Date: Sat, 11 Dec 2021 19:41:24 -0500 [thread overview]
Message-ID: <WGT47S3M.I7ESMRLQ.L6TBXOJC@JDOI773P.2L4C2H3D.HNNY5UVQ> (raw)
In-Reply-To: <20211211121423.329eef5f@cylon.local>
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.
next prev parent reply other threads:[~2021-12-12 0:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 1:09 [gentoo-user] KDE upgrade dependency problem Jack
2021-12-11 8:55 ` Arve Barsnes
2021-12-11 10:08 ` Dale
2021-12-11 12:14 ` Steve Evans
2021-12-12 0:41 ` Jack [this message]
2021-12-12 9:14 ` Steve Evans
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=WGT47S3M.I7ESMRLQ.L6TBXOJC@JDOI773P.2L4C2H3D.HNNY5UVQ \
--to=ostroffjh@users.sourceforge.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox