public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jack <ostroffjh@users.sourceforge.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] KDE upgrade dependency problem
Date: Fri, 10 Dec 2021 20:09:19 -0500	[thread overview]
Message-ID: <ZB55DVO3.PDS3DLNV.6Q4QYTUA@JB6VJU4K.3HZ5GOEZ.2WY67KVC> (raw)

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


             reply	other threads:[~2021-12-11  1:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-11  1:09 Jack [this message]
2021-12-11  8:55 ` [gentoo-user] KDE upgrade dependency problem Arve Barsnes
2021-12-11 10:08 ` Dale
2021-12-11 12:14 ` Steve Evans
2021-12-12  0:41   ` Jack
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=ZB55DVO3.PDS3DLNV.6Q4QYTUA@JB6VJU4K.3HZ5GOEZ.2WY67KVC \
    --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