Bug 688912 – KDE Applications 19.04.3 stabilisation

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Andreas Sturmlechner 2019-06-29 07:47:18 UTC]

Yes, it's only released on 2019-07-11, but we still got to plan with it already.

[Comment 1 Aaron Bauman (RETIRED) 2019-07-27 02:16:55 UTC]

(In reply to Andreas Sturmlechner from comment #0)
> Yes, it's only released on 2019-07-11, but we still got to plan with it
> already.

Please CC arm64 when ready.  Running checks now against it (stable bot won't catch it when the time comes)

[Comment 2 Frank Krömmelbein 2019-07-27 22:09:56 UTC]

Only one real problem has occurred and this has been caused by the profile change to 17.1 and is not a KDE issue. kde-apps/ktp-call-ui-19.04.3 failed for me, error already known: 
"kde-apps/ktp-call-ui - ninja: error: '/usr/lib/libtelepathy-farstream.so', needed by 'src/ktp-call-ui', missing and no known rule to make it"
https://bugs.gentoo.org/683796
After "emerge -1 telepathy-qt telepathy-farstream", i could build kde-apps/ktp-call-ui-19.04.3.

I ignored some useflags -alsa, +libav, -pdf, +systemd, -xml and -xmp

[Comment 3 Andreas Sturmlechner 2019-07-27 22:12:43 UTC]

Thank you very much for testing, as always!

[Comment 4 Andreas Sturmlechner 2019-07-27 22:17:26 UTC]

No reason to any further delay then, arches please stabilise!

[Comment 5 Frank Krömmelbein 2019-07-27 22:36:36 UTC]

(In reply to Andreas Sturmlechner from comment #4)
> No reason to any further delay then, arches please stabilise!

KDE Frameworks 5.60 should be stabilized first.
https://bugs.gentoo.org/690096

[Comment 6 Andreas Sturmlechner 2019-07-27 22:37:51 UTC]

Do you have any particular reason for that?

[Comment 7 Frank Krömmelbein 2019-07-27 22:45:24 UTC]

(In reply to Andreas Sturmlechner from comment #6)
> Do you have any particular reason for that?

I could not start the kde-apps update until after I had updated frameworks. 
Unfortunately I did not save the portage output.

Maybe that's the cause, from kde5-functions.eclass:

        kde-apps)
                if [[ ${PV} = 18.12.3 ]]; then
                        : ${FRAMEWORKS_MINIMAL:=5.57.0}
                        : ${PLASMA_MINIMAL:=5.14.5}
                        : ${QT_MINIMAL:=5.11.1}
                fi
                [[ ${PV} = 19.04.3 ]] && : ${FRAMEWORKS_MINIMAL:=5.60.0}
                ;;

[Comment 8 Andreas Sturmlechner 2019-07-27 22:48:19 UTC]

(In reply to Frank Krömmelbein from comment #7)
> Maybe that's the cause, from kde5-functions.eclass:
Of course. Thanks for reminding me of my original plan ;)

[Comment 9 Stabilization helper bot 2019-07-28 00:12:47 UTC]

An automated check of this bug failed - repoman reported dependency errors (95 lines truncated): 

> dependency.bad kde-apps/kross-interpreters/kross-interpreters-19.04.3.ebuild: DEPEND: amd64(default/linux/amd64/17.0) ['dev-lang/ruby:2.5']
> dependency.bad kde-apps/kross-interpreters/kross-interpreters-19.04.3.ebuild: RDEPEND: amd64(default/linux/amd64/17.0) ['dev-lang/ruby:2.5']
> dependency.bad kde-apps/kross-interpreters/kross-interpreters-19.04.3.ebuild: DEPEND: amd64(default/linux/amd64/17.0/desktop) ['dev-lang/ruby:2.5']

[Comment 10 Mikle Kolyada (RETIRED) 2019-07-28 00:39:01 UTC]

(In reply to Stabilization helper bot from comment #9)
> An automated check of this bug failed - repoman reported dependency errors
> (95 lines truncated): 
> 
> > dependency.bad kde-apps/kross-interpreters/kross-interpreters-19.04.3.ebuild: DEPEND: amd64(default/linux/amd64/17.0) ['dev-lang/ruby:2.5']
> > dependency.bad kde-apps/kross-interpreters/kross-interpreters-19.04.3.ebuild: RDEPEND: amd64(default/linux/amd64/17.0) ['dev-lang/ruby:2.5']
> > dependency.bad kde-apps/kross-interpreters/kross-interpreters-19.04.3.ebuild: DEPEND: amd64(default/linux/amd64/17.0/desktop) ['dev-lang/ruby:2.5']

^^ unccing amd64/x86, it is the single problem, will stabilize myself for both once fixed

[Comment 11 Stabilization helper bot 2019-07-28 00:58:41 UTC]

An automated check of this bug succeeded - the previous repoman errors are now resolved.

[Comment 12 Mikle Kolyada (RETIRED) 2019-07-28 01:12:21 UTC]

(In reply to Stabilization helper bot from comment #11)
> An automated check of this bug succeeded - the previous repoman errors are
> now resolved.

^^ it is not

[Comment 13 Larry the Git Cow 2019-07-28 02:08:18 UTC]

The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7791a127ecc420788cdab49f0666f105dfe22f0b

commit 7791a127ecc420788cdab49f0666f105dfe22f0b
Author:     Andreas Sturmlechner <[e-mail]>
AuthorDate: 2019-07-28 01:59:30 +0000
Commit:     Andreas Sturmlechner <[e-mail]>
CommitDate: 2019-07-28 01:59:30 +0000

    kde-apps/kross-interpreters: Revbump to make room for ruby24-compat r0
    
    Bug: https://bugs.gentoo.org/688912
    Package-Manager: Portage-2.3.69, Repoman-2.3.16
    Signed-off-by: Andreas Sturmlechner <[e-mail]>

 .../kross-interpreters-19.04.3-r1.ebuild           | 37 ++++++++++++++++++++++
 .../kross-interpreters-19.04.3.ebuild              |  2 +-
 2 files changed, 38 insertions(+), 1 deletion(-)

[Comment 14 Mikle Kolyada (RETIRED) 2019-07-28 02:31:29 UTC]

amd64 stable

[Comment 15 Mikle Kolyada (RETIRED) 2019-07-28 02:43:46 UTC]

x86 stable

[Comment 16 Aaron Bauman (RETIRED) 2019-07-29 18:44:05 UTC]

arm64 stable