KDE CI: Frameworks » purpose » kf5-qt5 WindowsMSVCQt5.15 - Build # 235 - Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/purpose/job/kf5-qt5%20WindowsMSVCQt5.15/235/ Project: kf5-qt5 WindowsMSVCQt5.15 Date of build: Sat, 27 Aug 2022 01:48:10 + Build duration: 25 min and counting JUnit Tests Name: projectroot Failed: 1 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 2 test(s)Failed: projectroot.autotests.menutest
KDE CI: Frameworks » knewstuff » kf5-qt5 SUSEQt5.15 - Build # 537 - Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/knewstuff/job/kf5-qt5%20SUSEQt5.15/537/ Project: kf5-qt5 SUSEQt5.15 Date of build: Sat, 27 Aug 2022 01:47:55 + Build duration: 5 min 8 sec and counting BUILD ARTIFACTS acc/KF5NewStuff-5.98.0.xml JUnit Tests Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s)Name: projectroot.autotests Failed: 1 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 3 test(s)Failed: projectroot.autotests.core.knewstuff_installationtest Cobertura Report Project Coverage Summary Name PackagesFilesClassesLinesConditionalsCobertura Coverage Report41% (7/17)26% (22/84)26% (22/84)20% (1680/8353)11% (1414/13215)Coverage Breakdown by Package Name FilesClassesLinesConditionalsautotests100% (1/1)100% (1/1)100% (58/58)53% (33/62)autotests.core67% (2/3)67% (2/3)41% (73/180)25% (37/146)autotests.kmoretools50% (1/2)50% (1/2)73% (225/307)47% (109/234)src20% (2/10)20% (2/10)4% (22/559)0% (0/171)src.attica0% (0/2)0% (0/2)0% (0/418)0% (0/1349)src.core48% (12/25)48% (12/25)26% (736/2873)12% (872/7310)src.core.jobs0% (0/7)0% (0/7)0% (0/301)0% (0/647)src.kmoretools60% (3/5)60% (3/5)48% (433/902)33% (156/472)src.opds0% (0/1)0% (0/1)0% (0/336)0% (0/1120)src.qtquick0% (0/12)0% (0/12)0% (0/924)0% (0/468)src.staticxml100% (1/1)100% (1/1)67% (133/199)33% (207/636)src.tools.knewstuff-dialog0% (0/2)0% (0/2)0% (0/84)0% (0/35)src.ui0% (0/8)0% (0/8)0% (0/781)0% (0/317)src.upload0% (0/1)0% (0/1)0% (0/124)0% (0/154)src.widgets0% (0/2)0% (0/2)0% (0/67)0% (0/18)tests0% (0/1)0% (0/1)0% (0/98)0% (0/48)tests.kmoretools0% (0/1)0% (0/1)0% (0/142)0% (0/28)
Re: Aura Browser in KDE Review
El divendres, 26 d’agost de 2022, a les 12:27:22 (CEST), Aditya Mehra va escriure: > Hi, > > Aura Browser is in KDE Review and would like to release it along with Plasma > Bigscreen > > Aura browser is a web browser specifically designed to work with remote > controls and key navigation for Plasma Bigscreen, it supports a virtual > mouse cursor and multiple tabs it also includes a third party AdBlock from > brave browser based on easy list. > > You can find the repository here: > https://invent.kde.org/plasma-bigscreen/aura-browser > > Request to please review Aura Browser. wcgrep text: | grep \" will show you lots of places that need i18n (or qstr that you use in 2 places) You have a Messages.sh but if you're going to keep using qstr you need to update it to use the Qt extraction command not the ki18n one. All those third-party are a bit sub-optimal, can we depend on packaged versions of them or they don't exist as such? Can you make cmake complain if the virtualkeyboard is not found? i think we have RUNTIME warning categories for that? It's relatively easy to get it crashing on closing the app, open a webpage (i tried wikipedia), close the app gdb trace https://pst.klgrth.io/paste/jobc7 Cheers, Albert > > Regards, > Aditya
KDE CI: Frameworks » kcmutils » kf5-qt5 WindowsMSVCQt5.15 - Build # 239 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/kcmutils/job/kf5-qt5%20WindowsMSVCQt5.15/239/ Project: kf5-qt5 WindowsMSVCQt5.15 Date of build: Fri, 26 Aug 2022 22:34:49 + Build duration: 2 min 35 sec and counting JUnit Tests Name: projectroot Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s)Name: projectroot.autotests Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)
Re: Plasma Remote Controllers in KDE Review
El divendres, 26 d’agost de 2022, a les 12:21:40 (CEST), Aditya Mehra va escriure: > Hi, > > Plasma remote controllers is in KDE Review and would like to release it > along with Plasma Bigscreen > > Plasma remote controllers allows translating various input device events > into keyboard and pointer events send from remote control type devices like > CEC and Gamepads to provide key navigation support in applications. It also > allows re mapping of keys to specific events. > > You can find the repository here: > https://invent.kde.org/plasma-bigscreen/plasma-remotecontrollers > > Request to please review Plasma remote controllers. There's a few "can be marked override" that i think that you should. You need to call KLocalizedString::setApplicationDomain in the main of the app. Cheers, Albert > > Regards, > Aditya
Re: Plank Player in KDE Review
El divendres, 26 d’agost de 2022, a les 12:29:31 (CEST), Aditya Mehra va escriure: > Hi, > > Plank Player is in KDE Review and would like to release it along with Plasma > Bigscreen > > Plank Player is a local media player specifically designed to work with > remote controls and key navigation for bigscreen. > > You can find the repository here: > https://invent.kde.org/plasma-bigscreen/plank-player > > Request to please review Plank Player. This seems wrong MimeType=application/vnd.debian.binary-package;application/x-rpm; This needs i18n / or qstr ./app/qml/Menu.qml:91:text: "Press 'esc' or the [←] Back button to close" and then you need the appropriate a Messages.sh I'm not sure having the folders sorted case sensitive makes sense, i think we stopped doing that a while ago? Cheers, Albert > > Regards, > Aditya
Incubation of pico-wizard
Hello KDE developers, I develop pico-wizard, an OEM install wizard used in Plasma Mobile and Plasma Bigscreen. We would like to incubate it to work more closely with KDE, and perhaps eventually use it for OEM installs on Plasma Desktop too. Currently it is hosted on Github at https://github.com/pico-wizard/pico-wizard but moving it to KDE Gitlab is not a problem. Current contributors are me(Anupam Basak), Probal Basak, Aditya Mehra, Erik D, and Bart Ribbers. We are willing to comply with the KDE manifesto. Would anyone like to sponsor? Thanks and regards, Anupam Basak
KDE CI: Frameworks » kio » kf5-qt5 SUSEQt5.15 - Build # 1816 - Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20SUSEQt5.15/1816/ Project: kf5-qt5 SUSEQt5.15 Date of build: Fri, 26 Aug 2022 16:57:38 + Build duration: 19 min and counting BUILD ARTIFACTS acc/KF5KIO-5.98.0.xml JUnit Tests Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 1 test(s), Passed: 61 test(s), Skipped: 0 test(s), Total: 62 test(s)Failed: projectroot.autotests.kiogui_openurljobtestName: projectroot.autotests Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)Name: projectroot.src.ioslaves.trash Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.src.kpasswdserver Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s) Cobertura Report Project Coverage Summary Name PackagesFilesClassesLinesConditionalsCobertura Coverage Report61% (25/41)70% (301/433)70% (301/433)58% (39929/69198)42% (22140/52906)Coverage Breakdown by Package Name FilesClassesLinesConditionalsautotests95% (62/65)95% (62/65)92% (11575/12643)46% (7338/15990)autotests.http100% (5/5)100% (5/5)99% (527/528)58% (167/290)autotests.kcookiejar100% (1/1)100% (1/1)94% (173/185)63% (70/112)src100% (1/1)100% (1/1)94% (50/53)77% (23/30)src.core89% (111/125)89% (111/125)61% (9749/15945)53% (4851/9188)src.core.kssl100% (1/1)100% (1/1)38% (33/86)50% (2/4)src.filewidgets79% (31/39)79% (31/39)57% (5428/9480)43% (2274/5273)src.gui100% (12/12)100% (12/12)72% (947/1320)57% (488/856)src.gui.systemd50% (2/4)50% (2/4)4% (7/170)1% (1/88)src.ioslaves.file71% (5/7)71% (5/7)50% (695/1403)39% (481/1225)src.ioslaves.file.kauth0% (0/2)0% (0/2)0% (0/187)0% (0/83)src.ioslaves.http88% (7/8)88% (7/8)43% (1872/4353)37% (1360/3713)src.ioslaves.http.kcookiejar40% (2/5)40% (2/5)49% (664/1364)56% (588/1053)src.ioslaves.telnet0% (0/1)0% (0/1)0% (0/43)0% (0/32)src.ioslaves.trash63% (5/8)63% (5/8)58% (862/1494)48% (459/960)src.ioslaves.trash.tests67% (2/3)67% (2/3)90%
KDE CI: Frameworks » kio » kf5-qt5 SUSEQt5.15 - Build # 1815 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20SUSEQt5.15/1815/ Project: kf5-qt5 SUSEQt5.15 Date of build: Fri, 26 Aug 2022 16:35:23 + Build duration: 22 min and counting BUILD ARTIFACTS acc/KF5KIO-5.98.0.xml JUnit Tests Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 0 test(s), Passed: 62 test(s), Skipped: 0 test(s), Total: 62 test(s)Name: projectroot.autotests Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)Name: projectroot.src.ioslaves.trash Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.src.kpasswdserver Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s) Cobertura Report Project Coverage Summary Name PackagesFilesClassesLinesConditionalsCobertura Coverage Report61% (25/41)70% (301/433)70% (301/433)58% (39949/69200)42% (22151/52906)Coverage Breakdown by Package Name FilesClassesLinesConditionalsautotests95% (62/65)95% (62/65)92% (11575/12643)46% (7334/15990)autotests.http100% (5/5)100% (5/5)99% (527/528)58% (167/290)autotests.kcookiejar100% (1/1)100% (1/1)94% (173/185)63% (70/112)src100% (1/1)100% (1/1)94% (50/53)77% (23/30)src.core89% (111/125)89% (111/125)61% (9746/15946)53% (4851/9188)src.core.kssl100% (1/1)100% (1/1)38% (33/86)50% (2/4)src.filewidgets79% (31/39)79% (31/39)57% (5428/9481)43% (2270/5273)src.gui100% (12/12)100% (12/12)72% (947/1320)57% (488/856)src.gui.systemd50% (2/4)50% (2/4)4% (7/170)1% (1/88)src.ioslaves.file71% (5/7)71% (5/7)50% (695/1403)39% (482/1225)src.ioslaves.file.kauth0% (0/2)0% (0/2)0% (0/187)0% (0/83)src.ioslaves.http88% (7/8)88% (7/8)44% (1895/4353)37% (1379/3713)src.ioslaves.http.kcookiejar40% (2/5)40% (2/5)49% (664/1364)56% (588/1053)src.ioslaves.telnet0% (0/1)0% (0/1)0% (0/43)0% (0/32)src.ioslaves.trash63% (5/8)63% (5/8)58% (862/1494)48% (459/960)src.ioslaves.trash.tests67% (2/3)67% (2/3)90%
KDE CI: Frameworks » kio » kf5-qt5 FreeBSDQt5.15 - Build # 1831 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/1831/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Fri, 26 Aug 2022 16:50:41 + Build duration: 6 min 6 sec and counting JUnit Tests Name: projectroot Failed: 0 test(s), Passed: 61 test(s), Skipped: 0 test(s), Total: 61 test(s)Name: projectroot.autotests Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)Name: projectroot.src.ioslaves.trash Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.src.kpasswdserver Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)
Re: Plasma Remote Controllers in KDE Review
Hi, Thanks for the review, I have fixed most of the issues mentioned in this list. Please review again. Regards, Aditya From: Harald Sitter Sent: Friday, August 26, 2022 10:43 PM To: Aditya Mehra Cc: kde-core-devel Subject: Re: Plasma Remote Controllers in KDE Review - src dir is missing i18n setup (messages.sh and define in cmakelists) - not reuse covered - metainfo.xml missing (appstream) - doesn't have gitlab ci builds apparently? - doesn't have bugzilla product - clazy is not happy On Fri, Aug 26, 2022 at 12:21 PM Aditya Mehra wrote: > > Hi, > > Plasma remote controllers is in KDE Review and would like to release it along > with Plasma Bigscreen > > Plasma remote controllers allows translating various input device events into > keyboard and pointer events send from remote control type devices like CEC > and Gamepads to provide key navigation support in applications. It also > allows re mapping of keys to specific events. > > You can find the repository here: > https://invent.kde.org/plasma-bigscreen/plasma-remotecontrollers > > Request to please review Plasma remote controllers. > > Regards, > Aditya
KDE CI: Frameworks » kio » kf5-qt5 FreeBSDQt5.15 - Build # 1830 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/1830/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Fri, 26 Aug 2022 16:35:23 + Build duration: 15 min and counting JUnit Tests Name: projectroot Failed: 2 test(s), Passed: 59 test(s), Skipped: 0 test(s), Total: 61 test(s)Failed: projectroot.autotests.applicationlauncherjob_forkingtestFailed: projectroot.autotests.applicationlauncherjob_servicetestName: projectroot.autotests Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)Name: projectroot.src.ioslaves.trash Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.src.kpasswdserver Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)
Re: https://invent.kde.org/graphics/kuickshow and imlib1
Marius P writes: > 1. Can someone build kuickshow? If so, how? > 2. Can we please archive https://invent.kde.org/graphics/kuickshow ? Yes, it builds for me here - again with Gentoo. That distro packages imlib1 separately from imlib2 so they can be coinstalled and appears to have no plans to remove it, although as you say imlib1 has not been updated since 2004. But it still works, even for new image formats(e.g. WebP), and Kuickshow is great as a fast and uncluttered image viewer. Yes, Gwenview has lots more features for browsing and viewing image collections, but sometimes all that is needed is a quick look. So I'd prefer to see Kuickshow still available even if it has to be moved to unmaintained. > In fact kuickshow is a wrapper around imlib1/imlibwidget.cpp. Having looked again at the source it doesn't actually seem to use imlib for much at all - image loading and transformation yes, but it doesn't use the library for displaying the image, only raw X11. (Which means that Kuickshow as it is now will never work on Wayland). So it could be made future proof by either porting to imlib2, which wouldn't involve very much work (only 4 source files actually call imlib), or even eliminating both X11 and imlib and using the corresponding Qt facilities instead (more work, but removes a dependency). Hopefully Kuickshow will live on! -- Jonathan Marten http://www.keelhaul.me.uk Twickenham, UK j...@keelhaul.me.uk
Re: Plasma Remote Controllers in KDE Review
- src dir is missing i18n setup (messages.sh and define in cmakelists) - not reuse covered - metainfo.xml missing (appstream) - doesn't have gitlab ci builds apparently? - doesn't have bugzilla product - clazy is not happy On Fri, Aug 26, 2022 at 12:21 PM Aditya Mehra wrote: > > Hi, > > Plasma remote controllers is in KDE Review and would like to release it along > with Plasma Bigscreen > > Plasma remote controllers allows translating various input device events into > keyboard and pointer events send from remote control type devices like CEC > and Gamepads to provide key navigation support in applications. It also > allows re mapping of keys to specific events. > > You can find the repository here: > https://invent.kde.org/plasma-bigscreen/plasma-remotecontrollers > > Request to please review Plasma remote controllers. > > Regards, > Aditya
Re: Aura Browser in KDE Review
This is missing an Appstream file and the licencing isn't clear, it should get SPDX licences. Jonathan On Fri, 26 Aug 2022 at 11:27, Aditya Mehra wrote: > Hi, > > Aura Browser is in KDE Review and would like to release it along with > Plasma Bigscreen > > Aura browser is a web browser specifically designed to work with remote > controls and key navigation for Plasma Bigscreen, it supports a virtual > mouse cursor and multiple tabs it also includes a third party AdBlock from > brave browser based on easy list. > > You can find the repository here: > https://invent.kde.org/plasma-bigscreen/aura-browser > > Request to please review Aura Browser. > > Regards, > Aditya >
KDE CI: Frameworks » kcmutils » kf5-qt5 WindowsMSVCQt5.15 - Build # 238 - Failure!
BUILD FAILURE Build URL https://build.kde.org/job/Frameworks/job/kcmutils/job/kf5-qt5%20WindowsMSVCQt5.15/238/ Project: kf5-qt5 WindowsMSVCQt5.15 Date of build: Fri, 26 Aug 2022 11:37:51 + Build duration: 7 min 9 sec and counting CONSOLE OUTPUT [...truncated 437 lines...][2022-08-26T11:44:52.533Z] Unknown property type for key "X-KDE-Keywords[sl]" -> falling back to string[2022-08-26T11:44:52.533Z] Unknown property type for key "X-KDE-Keywords[sr]" -> falling back to string[2022-08-26T11:44:52.533Z] Unknown property type for key "X-KDE-Keywords[sr@ijekavian]" -> falling back to string[2022-08-26T11:44:52.533Z] Unknown property type for key "X-KDE-Keywords[sr@ijekavianlatin]" -> falling back to string[2022-08-26T11:44:52.533Z] Unknown property type for key "X-KDE-Keywords[sr@latin]" -> falling back to string[2022-08-26T11:44:52.533Z] Unknown property type for key "X-KDE-Keywords[sv]" -> falling back to string[2022-08-26T11:44:52.533Z] Unknown property type for key "X-KDE-Keywords[tr]" -> falling back to string[2022-08-26T11:44:52.533Z] Unknown property type for key "X-KDE-Keywords[ug]" -> falling back to string[2022-08-26T11:44:52.533Z] Unknown property type for key "X-KDE-Keywords[uk]" -> falling back to string[2022-08-26T11:44:52.534Z] Unknown property type for key "X-KDE-Keywords[vi]" -> falling back to string[2022-08-26T11:44:52.534Z] Unknown property type for key "X-KDE-Keywords[wa]" -> falling back to string[2022-08-26T11:44:52.534Z] Unknown property type for key "X-KDE-Keywords[x-test]" -> falling back to string[2022-08-26T11:44:52.534Z] Unknown property type for key "X-KDE-Keywords[zh_CN]" -> falling back to string[2022-08-26T11:44:52.534Z] Unknown property type for key "X-KDE-Keywords[zh_TW]" -> falling back to string[2022-08-26T11:44:52.534Z] Unknown property type for key "Categories" -> falling back to string[2022-08-26T11:44:52.534Z] Generated "C:/CI/Job Build/build/autotests/desktopfilekcm/kcmtest.json"[2022-08-26T11:44:52.534Z] [3/66] Automatic MOC for target kcmdesktopfilegenerator[2022-08-26T11:44:52.534Z] [4/66] Building CXX object tools\CMakeFiles\kcmdesktopfilegenerator.dir\kcmdesktopfilegenerator_autogen\mocs_compilation.cpp.obj[2022-08-26T11:44:52.795Z] [5/66] Automatic MOC for target KF5KCMUtilsCore[2022-08-26T11:44:52.795Z] [6/66] Automatic MOC for target jsonplugin[2022-08-26T11:44:52.795Z] [7/66] Automatic MOC for target kcmtest[2022-08-26T11:44:53.056Z] [8/66] Generating src/KF5KCMUtils.qch, src/KF5KCMUtils.tags[2022-08-26T11:44:53.645Z] [9/66] Building CXX object autotests\jsonplugin\CMakeFiles\jsonplugin.dir\jsonplugin_autogen\mocs_compilation.cpp.obj[2022-08-26T11:44:53.910Z] [10/66] Building CXX object tools\CMakeFiles\kcmdesktopfilegenerator.dir\kcmmetadatagenerator.cpp.obj[2022-08-26T11:44:53.910Z] [11/66] Building CXX object src\core\CMakeFiles\KF5KCMUtilsCore.dir\kcmutilscore_debug.cpp.obj[2022-08-26T11:44:53.910Z] [12/66] Building CXX object src\core\CMakeFiles\KF5KCMUtilsCore.dir\KF5KCMUtilsCore_autogen\mocs_compilation.cpp.obj[2022-08-26T11:44:53.910Z] [13/66] Building CXX object autotests\jsonplugin\CMakeFiles\jsonplugin.dir\jsonplugin.cpp.obj[2022-08-26T11:44:53.910Z] [14/66] Building CXX object autotests\desktopfilekcm\CMakeFiles\kcmtest.dir\kcmtest_autogen\mocs_compilation.cpp.obj[2022-08-26T11:44:53.910Z] [15/66] Building CXX object autotests\desktopfilekcm\CMakeFiles\kcmtest.dir\kcmtest.cpp.obj[2022-08-26T11:44:54.172Z] [16/66] Building CXX object src\core\CMakeFiles\KF5KCMUtilsCore.dir\kpluginmodel.cpp.obj[2022-08-26T11:44:54.172Z] [17/66] Linking CXX executable bin\kcmdesktopfilegenerator.exe[2022-08-26T11:44:54.172Z] [18/66] cmd.exe /C "cd /D "C:\CI\Job Build\build\autotests\fakekcm" && "C:\CI\Job Build\build\bin\kcmdesktopfilegenerator.exe" "C:/CI/Job Build/autotests/fakekcm/fakekcm.json" "C:/CI/Job Build/build/autotests/fakekcm/fakekcm.desktop""[2022-08-26T11:44:54.812Z] [19/66] Automatic MOC for target fakekcm[2022-08-26T11:44:54.812Z] [20/66] Linking CXX shared module bin\testplugins\jsonplugin.dll[2022-08-26T11:44:54.812Z] LINK : warning LNK4044: unrecognized option '/Wl,-Bsymbolic-functions'; ignored[2022-08-26T11:44:54.812Z]Creating library lib\jsonplugin.lib and object lib\jsonplugin.exp[2022-08-26T11:44:54.812Z] LINK : warning LNK4044: unrecognized option '/Wl,-Bsymbolic-functions'; ignored[2022-08-26T11:44:54.812Z] LINK : warning LNK4044: unrecognized option '/Wl,-Bsymbolic-functions'; ignored[2022-08-26T11:44:54.812Z]Creating library lib\jsonplugin.lib and object lib\jsonplugin.exp[2022-08-26T11:44:55.074Z] [21/66] Building CXX object autotests\fakekcm\CMakeFiles\fakekcm.dir\fakekcm_autogen\mocs_compilation.cpp.obj[2022-08-26T11:44:55.074Z] [22/66] Linking CXX shared module bin\kcmtest.dll[2022-08-26T11:44:55.074Z] LINK : warning LNK4044: unrecognized option '/Wl,-Bsymbolic-functions'; ignored[2022-08-26T11:44:55.074Z]Creating library lib\kcmtest.lib and object
KDE CI: Frameworks » kio » kf5-qt5 SUSEQt5.15 - Build # 1814 - Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20SUSEQt5.15/1814/ Project: kf5-qt5 SUSEQt5.15 Date of build: Fri, 26 Aug 2022 10:50:25 + Build duration: 13 min and counting BUILD ARTIFACTS acc/KF5KIO-5.98.0.xml JUnit Tests Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 1 test(s), Passed: 61 test(s), Skipped: 0 test(s), Total: 62 test(s)Failed: projectroot.autotests.kiocore_threadtestName: projectroot.autotests Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)Name: projectroot.src.ioslaves.trash Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.src.kpasswdserver Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s) Cobertura Report Project Coverage Summary Name PackagesFilesClassesLinesConditionalsCobertura Coverage Report61% (25/41)69% (300/433)69% (300/433)58% (39910/69195)42% (22139/52900)Coverage Breakdown by Package Name FilesClassesLinesConditionalsautotests94% (61/65)94% (61/65)91% (11540/12640)46% (7322/15984)autotests.http100% (5/5)100% (5/5)99% (527/528)58% (167/290)autotests.kcookiejar100% (1/1)100% (1/1)94% (173/185)63% (70/112)src100% (1/1)100% (1/1)94% (50/53)77% (23/30)src.core89% (111/125)89% (111/125)61% (9746/15946)53% (4851/9188)src.core.kssl100% (1/1)100% (1/1)38% (33/86)50% (2/4)src.filewidgets79% (31/39)79% (31/39)57% (5428/9480)43% (2274/5273)src.gui100% (12/12)100% (12/12)72% (947/1320)57% (488/856)src.gui.systemd50% (2/4)50% (2/4)4% (7/170)1% (1/88)src.ioslaves.file71% (5/7)71% (5/7)50% (694/1402)39% (481/1225)src.ioslaves.file.kauth0% (0/2)0% (0/2)0% (0/187)0% (0/83)src.ioslaves.http88% (7/8)88% (7/8)43% (1892/4353)37% (1375/3713)src.ioslaves.http.kcookiejar40% (2/5)40% (2/5)49% (664/1364)56% (588/1053)src.ioslaves.telnet0% (0/1)0% (0/1)0% (0/43)0% (0/32)src.ioslaves.trash63% (5/8)63% (5/8)58% (862/1494)48% (459/960)src.ioslaves.trash.tests67% (2/3)67% (2/3)90%
KDE CI: Frameworks » kio » kf5-qt5 FreeBSDQt5.15 - Build # 1829 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/1829/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Fri, 26 Aug 2022 10:47:36 + Build duration: 15 min and counting JUnit Tests Name: projectroot Failed: 2 test(s), Passed: 59 test(s), Skipped: 0 test(s), Total: 61 test(s)Failed: projectroot.autotests.applicationlauncherjob_forkingtestFailed: projectroot.autotests.kiogui_openurljobtestName: projectroot.autotests Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)Name: projectroot.src.ioslaves.trash Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.src.kpasswdserver Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)
KDE CI: Frameworks » kio » kf5-qt5 FreeBSDQt5.15 - Build # 1828 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/1828/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Fri, 26 Aug 2022 10:30:44 + Build duration: 16 min and counting JUnit Tests Name: projectroot Failed: 2 test(s), Passed: 59 test(s), Skipped: 0 test(s), Total: 61 test(s)Failed: projectroot.autotests.applicationlauncherjob_scopetestFailed: projectroot.autotests.kiogui_openurljobtestName: projectroot.autotests Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)Name: projectroot.src.ioslaves.trash Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.src.kpasswdserver Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)
Plank Player in KDE Review
Hi, Plank Player is in KDE Review and would like to release it along with Plasma Bigscreen Plank Player is a local media player specifically designed to work with remote controls and key navigation for bigscreen. You can find the repository here: https://invent.kde.org/plasma-bigscreen/plank-player Request to please review Plank Player. Regards, Aditya
Aura Browser in KDE Review
Hi, Aura Browser is in KDE Review and would like to release it along with Plasma Bigscreen Aura browser is a web browser specifically designed to work with remote controls and key navigation for Plasma Bigscreen, it supports a virtual mouse cursor and multiple tabs it also includes a third party AdBlock from brave browser based on easy list. You can find the repository here: https://invent.kde.org/plasma-bigscreen/aura-browser Request to please review Aura Browser. Regards, Aditya
Plasma Remote Controllers in KDE Review
Hi, Plasma remote controllers is in KDE Review and would like to release it along with Plasma Bigscreen Plasma remote controllers allows translating various input device events into keyboard and pointer events send from remote control type devices like CEC and Gamepads to provide key navigation support in applications. It also allows re mapping of keys to specific events. You can find the repository here: https://invent.kde.org/plasma-bigscreen/plasma-remotecontrollers Request to please review Plasma remote controllers. Regards, Aditya
KDE CI: Frameworks » kio » kf5-qt5 FreeBSDQt5.15 - Build # 1827 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/1827/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Fri, 26 Aug 2022 09:51:42 + Build duration: 10 min and counting JUnit Tests Name: projectroot Failed: 2 test(s), Passed: 59 test(s), Skipped: 0 test(s), Total: 61 test(s)Failed: projectroot.autotests.applicationlauncherjob_forkingtestFailed: projectroot.autotests.kiocore_jobtestName: projectroot.autotests Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)Name: projectroot.src.ioslaves.trash Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.src.kpasswdserver Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)
KDE CI: Frameworks » kio » kf5-qt5 FreeBSDQt5.15 - Build # 1826 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/1826/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Fri, 26 Aug 2022 09:45:13 + Build duration: 6 min 26 sec and counting JUnit Tests Name: projectroot Failed: 1 test(s), Passed: 60 test(s), Skipped: 0 test(s), Total: 61 test(s)Failed: projectroot.autotests.kiocore_jobtestName: projectroot.autotests Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)Name: projectroot.src.ioslaves.trash Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.src.kpasswdserver Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)
Re: New releases for bugfixes
On 8/25/22 22:59, Albert Astals Cid wrote: c) Who decides which bugs "are important" because for every bug, there's always a person out there that thinks it's the most important bug ever. d) What do we release? i.e. imagine we find one of those "important bugs" in dolphin and we have to release 22.08.0.1. Do we just release the 22.08 branch with any changes it may have had since the 22.08.0 release or do we create a special branch that only contains the new patch and release that? It's always subjective, but I was specifically thinking of bugs like https://bugs.kde.org/show_bug.cgi?id=458099 in which we accidentally introduced an API break and then fixed it. I was going to send out a patch request, but something like this really deserves a new release IMO, just in the interest of our API compatibility promise. Nate
Re: New releases for bugfixes
As a distro packaging it's much easier and more reliable to just let the new version get added automatically to our builds. As a release manager it shouldn't be any harder to automate making a new bugfix release. I do this already for Plasma when requested. It should be the default method. Jonathan On Thu, 25 Aug 2022 at 17:55, Nate Graham wrote: > Hello everyone, > Right now when we fix a significant bug in our software that may take a > while to reach users to to the release schedule of its repo, we contact > distros and ask them to backport it. This puts the burden on distros to > react to us. I'm wondering how people feel about KDE instead making > immediate point releases ourselves. Thus we would take responsibility > for releasing fixes for our own regressions, and distros that monitor > KDE infrastructure for new tarballs could be notified automatically. > > Thoughts? > > Nate >
Re: Loosening the commit limit for work branches
On Thu, Aug 25, 2022 at 11:44 AM Ben Cooksley wrote: > > On Thu, Aug 25, 2022 at 9:27 PM Harald Sitter wrote: >> >> On Wed, Aug 24, 2022 at 8:11 PM Ben Cooksley wrote: >> > >> > On Thu, Aug 25, 2022 at 2:16 AM Harald Sitter wrote: >> >> >> >> On Wed, Aug 24, 2022 at 3:31 PM Noah Davis wrote: >> >> > >> >> > A week ago, I ran into an unexpected issue while working on a QML port >> >> > of Spectacle. There is an undocumented pre-receive hook that sets a >> >> > 100 commit limit for all branches of official repos, including work >> >> > branches. The error message it gave me told me to file a sysadmin >> >> > ticket, so I did that. >> >> > >> >> > The sysadmin ticket link: https://phabricator.kde.org/T15683 >> >> > >> >> > I don't think I can make the ticket public, so here's the conversation: >> >> > >> >> > --- Start of conversation >> >> > >> >> > ndavis (me): >> >> > For normal branches, I would understand this since there were issues >> >> > with spamming #kde-devel in the past. This isn't necessary for work >> >> > branches, right? I thought the point of the work/ naming convention >> >> > was to prevent this issue. >> >> > >> >> > bcooksley: >> >> > Work branches weren't meant to be used for large feature developments >> >> > with 100+ commits in them, which is why this is being blocked. >> >> > In it's current state - even if rebased - the branch will not be able >> >> > to be merged without Sysadmin intervention. >> >> > Will this be squashed prior to being merged? >> >> > >> >> > ndavis: >> >> > > Will this be squashed prior to being merged? >> >> > >> >> > Yes >> >> > >> >> > > Work branches weren't meant to be used for large feature developments >> >> > > with 100+ commits in them, which is why this is being blocked. >> >> > >> >> > Is this documented anywhere? I don't understand why work branches >> >> > would block this. The git message says notifications are the reason >> >> > why the push was blocked, but I thought work branches didn't send >> >> > notifications? >> >> > >> >> > bcooksley: >> >> > The message is a little misleading, but that is mostly because this >> >> > situation isn't supposed to really occur. You are correct that work >> >> > branches don't send notifications. >> >> > As such it is not documented anywhere. >> >> > From a policy perspective the reason why we don't allow work branches >> >> > to grow beyond 100 commits is because if we did then you would never >> >> > be able to merge them in - not without squashing anyway. >> >> > This therefore makes you "squash as you go". >> >> > I would generally recommend that major features be developed in an >> >> > ordinary branch to allow those that monitor kde-commits and other >> >> > commit feeds to chime in with real-time reviews, and then merged using >> >> > a traditional Git merge (vs. our more typical rebase) >> >> > >> >> > ndavis: >> >> > > The message is a little misleading, but that is mostly because this >> >> > > situation isn't supposed to really occur. You are correct that work >> >> > > branches don't send notifications. As such it is not documented >> >> > > anywhere. >> >> > >> >> > If we are going to keep this limitation, we should document it so that >> >> > nobody else makes the same mistake as me. We can't assume that >> >> > something that isn't supposed to happen won't happen because there's >> >> > no reason to assume this limitation would exist. >> >> > >> >> > > From a policy perspective the reason why we don't allow work branches >> >> > > to grow beyond 100 commits is because if we did then you would never >> >> > > be able to merge them in - not without squashing anyway. >> >> > This therefore makes you "squash as you go". >> >> > >> >> > I don't understand why we have this policy. If we can't merge an MR >> >> > with over 100 commits, why can't we just tell the person making an MR >> >> > when they post the MR to squash it? I think it would make more sense >> >> > for this policy to apply only when pushing to master or version >> >> > branches. >> >> > >> >> > > I would generally recommend that major features be developed in an >> >> > > ordinary branch to allow those that monitor kde-commits and other >> >> > > commit feeds to chime in with real-time reviews, >> >> > >> >> > In my experience, nobody does that. Nobody has time to review unless >> >> > you explicitly request help or you post an MR. >> >> > I don't know the protocol for discussing these kinds of things, so let >> >> > me know if this discussion should be moved elsewhere. >> >> > >> >> > --- End of conversation >> >> > >> >> > After this, I decided it would be better to discuss this with the >> >> > broader KDE community and I closed the ticket. >> >> > >> >> > I did try to switch to a normal branch as Ben Cooksley suggested, but >> >> > that had the same limitation. I have not tested using a fork, but some >> >> > of the people I've talked to casually (I can't remember who) seemed to >> >> > be saying that fork branches
