kde August 2019

kde@lists.fedoraproject.org

16 participants
14 discussions

KDE on EPEL 8
by Troy Dawson 06 Aug '19

06 Aug '19

Hi, EPEL 8 is getting close to being available. I think now is the time to start talking about KDE on EPEL8 in earnest. Who is going to do the EPEL8 KDE packages? I am volunteering to do them, but from what I've heard, there are several other people who want to do it as well. I don't want to duplicate effort, or take the spotlight from others. Maybe if there is enough people we do it as a group and/or SIG. On the flip side, I also want them initially done quickly. If someone is volunteering, yet they've never built a package for Fedora or EPEL before, I'd rather I do it then pass off the maintenance to them. Just to save time. Anyway, thoughts? Troy

5 24

kmail not starting after the last update on F30
by José Abílio Oliveira Matos 06 Aug '19

06 Aug '19

After the last update, this morning, kmail no longer starts. $ kmail kmail: symbol lookup error: /lib64/libQt5WebEngineCore.so.5: undefined symbol: _ZN3re23RE23Arg9parse_intEPKciPv What is strange is that today's update seems innocuous (famous last words, I know :-) ): Packages Altered: Upgrade LibRaw-0.19.4-1.fc30.x86_64 @updates-testing Upgraded LibRaw-0.19.2-3.fc30.x86_64 @@System Upgrade dbusmenu-qt-0.9.3-0.21.20160218.fc30.x86_64 @updates-testing Upgraded dbusmenu-qt-0.9.3-0.20.20160218.fc30.x86_64 @@System Upgrade dbusmenu-qt5-0.9.3-0.21.20160218.fc30.x86_64 @updates-testing Upgraded dbusmenu-qt5-0.9.3-0.20.20160218.fc30.x86_64 @@System Upgrade libmodulemd1-1.8.15-3.fc30.1.x86_64 @updates-testing Upgraded libmodulemd1-1.8.15-3.fc30.x86_64 @@System Upgrade oldstandard-sfd-fonts-2.0.2-26.fc30.noarch @updates-testing Upgraded oldstandard-sfd-fonts-2.0.2-24.fc30.noarch @@System Upgrade python3-libmodulemd1-1.8.15-3.fc30.1.x86_64 @updates-testing Upgraded python3-libmodulemd1-1.8.15-3.fc30.x86_64 @@System Upgrade re2-20190801-1.fc30.x86_64 @updates-testing Upgraded re2-20160401-8.fc30.x86_64 @@System Upgrade spirv-tools-libs-2019.4-0.1.20190715.gitaa9e8f5.fc30.x86_64 @updates-testing Upgraded spirv-tools-libs-2019.1-1.fc30.x86_64 @@System Upgrade vulkan-loader-1.1.114.0-1.fc30.x86_64 @updates-testing Upgraded vulkan-loader-1.1.97.0-0.fc30.x86_64 @@System So from here only dbusmenu-qt and dbusmenu-qt5 seem related to qt/kde. Best regards, -- José Abílio

3 2

Amarok systray context menu not working
by Syam Krishnan 05 Aug '19

05 Aug '19

Hi I have noticed recently that right-clicking on Amarok's systray icon no longer brings up a proper menu. All I get is a menu with just a a single item labelled "Amarok" and even that is not clickable. Any idea why this is happening? Thanks and regards, Syam

4 4

EPEL8 KDE - Which Build Area
by Troy Dawson 01 Aug '19

01 Aug '19

Hi, EPEL8 is almost a reality. I am finally able to request branches, and have done so. Something new in EPEL (starting with EPEL8) is the "playground".[1] You can think of it as Fedora's rawhide, but different. Unlike Fedora Rawhide, the -playground branch will not automatically be branched or merged into EPEL8. I think playground is very descriptive, and the article I linked to describes things better than I can. I am going to start my first builds in playground, so I'm sure things are working. But the question is ... what about the whole build. My initial thought it to just build the whole thing in normal EPEL8 and not worry about playground for now. But then I thought, what about having KDE as a module. EPEL modules will not happen until the RHEL 8.1 timeframe (4 to 5 months from now). If we have KDE as a module, it will do two positive things for us. 1 - we don't have to be so dependent on CRB for some -devel packages. (ie: we could build out own gpgme to get the -devel package we need) 2 - We can replace certain RHEL8 packages (qt5) that are limiting our KDE versions. If we want to go to module only, for KDE. It might be better to have our initial build of EPEL8 KDE be in playground only. That way, we will not have to pull any packages out of the regular EPEL8 repository when we move everything to modules. Anyone wanting to use KDE that is running RHEL 8.0, would have to enable the playground repository. I don't know if that is a good or bad thing. Anyway, I wanted others opinions. Troy [1] https://www.scrye.com/wordpress/nirik/2019/07/30/epel8-playground/

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

kde August 2019