| 1 |
On 2021.12.11 07:14, Steve Evans wrote: |
| 2 |
> On Fri, 10 Dec 2021 20:09:19 -0500 Jack |
| 3 |
> <ostroffjh@×××××××××××××××××.net> wrote: |
| 4 |
> |
| 5 |
> > Good evening all, calling on the accumulated wisdom here. |
| 6 |
> > |
| 7 |
> > kde-frameworks 5.88 has been marked stable, but my upgrade is |
| 8 |
> blocked |
| 9 |
> > because kwin (5.22.5 is stable, 5.23.4 is still marked testing) is |
| 10 |
> > somehow stuck on kde-frameworks/kglobalaccel-5.85. |
| 11 |
> > |
| 12 |
> > The line from portage is: |
| 13 |
> > (kde-frameworks/kglobalaccel-5.85.0-r1:5/5.85::gentoo, installed) |
| 14 |
> > USE="-debug -doc -nls -test" ABI_X86="(64)" pulled in by |
| 15 |
> > >=kde-frameworks/kglobalaccel-5.82.0:5/5.85= required by |
| 16 |
> > (kde-plasma/kwin-5.22.5:5/5::gentoo, installed) USE="caps handbook |
| 17 |
> > plasma -accessibility -debug -gles2-only -multimedia -screencast |
| 18 |
> > -test" ABI_X86="(64)" |
| 19 |
> > |
| 20 |
> > The actual line in the kwin ebuild is |
| 21 |
> > >=kde-frameworks/kglobalaccel-${KFMIN}:5= |
| 22 |
> > so I'm assuming that trailing "=" is the culprit, although I don't |
| 23 |
> > really follow the syntax. |
| 24 |
> > |
| 25 |
> > Is there any easy way around this, or does it just mean I can't |
| 26 |
> > upgrade any of kde-frameworks from 5.85 to 5.88 until kde-plasma |
| 27 |
> > 5.24.something is marked stable or I unmask it? I'm not in any |
| 28 |
> great |
| 29 |
> > rush, but it means emerge @world always fails, and I've got to |
| 30 |
> > individually pick out those packages I CAN upgrade. |
| 31 |
> > |
| 32 |
> > Jack |
| 33 |
|
| 34 |
> I am having the same problem. It appears as though kde-frameworks 5.88 |
| 35 |
> depends on a matching upgrade to kde-plasma to version 5.23.4. |
| 36 |
> Frameworks has been marked stable, but plasma has not yet :-( |
| 37 |
> |
| 38 |
> See these bugs: |
| 39 |
> |
| 40 |
> - https://bugs.gentoo.org/816042 "KDE Frameworks 5.88 stabilisation" |
| 41 |
> which has a status of IN_PROGRESS |
| 42 |
> |
| 43 |
> - https://bugs.gentoo.org/826898 "KDE Plasma 5.23.4 stabilisation" |
| 44 |
> which has a status of CONFIRMED |
| 45 |
> |
| 46 |
> So I think we are just going to have to wait for kde-plasma to be |
| 47 |
> marked stable. |
| 48 |
I suppose the frameworks stabilization is still "in progress" because |
| 49 |
not all arch's are stable, but amd64 is, which is the only one I need. |
| 50 |
The plasma stabilization did say it was dependent on the frameworks |
| 51 |
updates, but it doesn't say anything about why the older plasma (kwin |
| 52 |
in particular) seems to be preventing the frameworks update. |
| 53 |
|
| 54 |
Anyway, I decided dto go ahead and accept the testing plasma packages. |
| 55 |
I initially put "=kde-plasma/*-5.23* ~amd64" into my packages.accept |
| 56 |
file. eix showed (~) for kwin, but emerge complained about that syntax |
| 57 |
and didn't accept it. I ended up with "kde-plasma/* ~amd64". I don't |
| 58 |
know why the other syntax wasn't ok with portage, but as soon as that |
| 59 |
second bug does get settled, I can remove that line, so I'm not too |
| 60 |
worried about it being over inclusive. |
Archives