KDE Frameworks with failing CI (master) (23 June 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: Everything passes :) Cheers, Albert
Re: KStars: Cannot change language
El divendres, 21 de juny del 2024, a les 19:53:04 (CEST), Albert Astals Cid va escriure: > El divendres, 21 de juny del 2024, a les 10:31:50 (CEST), Jasem Mutlaq va > > escriure: > > Hello, > > > > We have an issue with the recent versions of KStars is that language > > cannot > > be switched by users. This affects MacOS, Windows, and Linux, whether > > packaged or built from source. > > > > How to debug this issue? I can't see anything in the logs about the > > language switch issue. For example, I tried changing the language to > > German > > but the interface is still in English. Which component of KDE Frameworks > > is > > handling this at the backend? Any environment variables to check or watch > > out for? > > > > Any pointers would be appreciated. > > Starting kstars says > > kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: > "Count of captures stored for the job, based on its sequence job.\nThis is > a summary, additional specific frame types may be required to complete the > job." msgid_plural: "" msgctxt: "" > > > Fixed by > > https://invent.kde.org/education/kstars/-/merge_requests/1266 > > This fixes the issue. Ah i see you fixed it in a bit more rudimentary way, that also works I guess. Cheers, Albert > > Cheers, > Albert > > > -- > > Best Regards, > > Jasem Mutlaq
Re: KStars: Cannot change language
El divendres, 21 de juny del 2024, a les 10:31:50 (CEST), Jasem Mutlaq va escriure: > Hello, > > We have an issue with the recent versions of KStars is that language cannot > be switched by users. This affects MacOS, Windows, and Linux, whether > packaged or built from source. > > How to debug this issue? I can't see anything in the logs about the > language switch issue. For example, I tried changing the language to German > but the interface is still in English. Which component of KDE Frameworks is > handling this at the backend? Any environment variables to check or watch > out for? > > Any pointers would be appreciated. Starting kstars says kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Count of captures stored for the job, based on its sequence job.\nThis is a summary, additional specific frame types may be required to complete the job." msgid_plural: "" msgctxt: "" Fixed by https://invent.kde.org/education/kstars/-/merge_requests/1266 This fixes the issue. Cheers, Albert > > -- > Best Regards, > Jasem Mutlaq
Re: KDE Gear projects with failing CI (master) (18 June 2024)
El dimecres, 19 de juny del 2024, a les 9:07:50 (CEST), Ingo Klöcker va escriure: > On Mittwoch, 19. Juni 2024 00:49:14 CEST Albert Astals Cid wrote: > > kdenlive - 2nd week > > > > * https://invent.kde.org/multimedia/kdenlive/-/pipelines/716283 > > > > * craft_appimage_qt6_x86_64 fails > > > > isoimagewriter - NEW > > > > * https://invent.kde.org/utilities/isoimagewriter/-/pipelines/716655 > > > > * craft_appimage_qt6_x86_64 fails > > > > neochat - NEW > > > > * https://invent.kde.org/network/neochat/-/pipelines/716759 > > > > * craft_appimage_qt6_x86_64 fails > > All of these fail because the tests of kconfig don't build. I'm wondering > why not all AppImage builds of all projects fail. > > The cause for the failing (or highly unstable) builds of the tests of > kconfig is an error in the test design. Here's what I wrote late last night > in #kde-craft:kde.org. > > === > There is a pair of tests, e.g. Test8 and Test8_cmake where the latter is > supposed to test that cmake can generate a .kcfgc file. The problem is that > both tests share the same test8main.cpp which includes a test8a.h. This > test8a.h is generated via test8a.kcfg[c] for Test8, but for Test8_cmake > test8a_cmake.h is generated via a test8a_cmake.kcfg[c]. If for some reason > Test8_cmake is built before Test8 then test8main.cpp doesn't find test8a.h. > I'm not yet sure how to fix this. Maybe we need to create patched copies of > testXmain.cpp which includes a testXx_cmake.h instead of a testXx.h. Or > maybe we put both tests in separate subdirs and don't append _cmake to the > files used for the TestX_cmake tests. That's feels like a cleaner solution > also because it better isolates the two tests from each other. > === > > With make the problem doesn't seem to occur because it looks like the > Makefiles serialize building of Test8 and Test8_cmake so that Test8_cmake > is always built after Test8 where Test8 creates the headers that > Test8_cmake uses. With ninja the builds of both targets don't seem to be > serialized so that Test8_cmake could be built before Test8. -> Fail! With that info, we got a fix in, but that won't fix CI since it uses tarballs, should we get https://invent.kde.org/frameworks/kconfig/-/merge_requests/314/diffs added as a patch to Craft? Cheers, Albert > > Regards, > Ingo
KDE Gear projects with failing CI (release/24.05) (18 June 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. VERY BAD NEWS - neochat Windows tests have been broken for 4 weeks, I have disabled requiring them to pass on CI. VERY BAD NEWS - dolphin Craft Windows build has been broken for 4 weeks, I have removed it from CI. VERY BAD NEWS - ark kerfuffle-extracttest has been broken for 4 weeks, I have commented it out. Good news: 1 repository has been fixed Bad news: 2 repositories are still failing kdenlive - 2nd week * https://invent.kde.org/multimedia/kdenlive/-/pipelines/716280 * craft_windows_qt6_mingw64 fails neochat - NEW * https://invent.kde.org/network/neochat/-/pipelines/716779 * craft_appimage_qt6_x86_64 fails Cheers, Albert
KDE Gear projects with failing CI (master) (18 June 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. VERY BAD NEWS - neochat Windows tests have been broken for 4 weeks, I have disabled requiring them to pass on CI. VERY BAD NEWS - dolphin Craft Windows build has been broken for 4 weeks, I have removed it from CI. VERY BAD NEWS - ark kerfuffle-extracttest has been broken for 4 weeks, I have commented it out. Good news: 1 repository has been fixed Bad news: 2 repositories are still failing, 2 repositories have started failing ark - 3rd week * https://invent.kde.org/utilities/ark/-/pipelines/711184 * kerfuffle-extracttest fails on FreeBSD kdenlive - 2nd week * https://invent.kde.org/multimedia/kdenlive/-/pipelines/716283 * craft_appimage_qt6_x86_64 fails isoimagewriter - NEW * https://invent.kde.org/utilities/isoimagewriter/-/pipelines/716655 * craft_appimage_qt6_x86_64 fails neochat - NEW * https://invent.kde.org/network/neochat/-/pipelines/716759 * craft_appimage_qt6_x86_64 fails Cheers, Albert
KDE Frameworks with failing CI (master) (16 June 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: The 1 failing repo was fixed and everything is passing :) Cheers, Albert
KDE Gear 24.08 release schedule
Hi folks, This is the release schedule the release team agreed on https://community.kde.org/Schedules/KDE_Gear_24.08_Schedule Dependency freeze is in around 4 weeks (July 18) and feature freeze one after that. Get your stuff ready! Cheers, Albert
Re: KDE Gear projects with failing CI (release/24.05) (11 June 2024)
El dijous, 13 de juny del 2024, a les 22:37:04 (CEST), Ingo Klöcker va escriure: > On Mittwoch, 12. Juni 2024 00:22:35 CEST Albert Astals Cid wrote: > > kwalletmanager - 3rd week > > > > * https://invent.kde.org/utilities/kwalletmanager/-/pipelines/711185 > > > > * appstream test fails because https://apps.kde.org/kwalletmanager5 > > > > doesn't exist > > This will be fixed by > https://invent.kde.org/websites/apps-kde-org/-/merge_requests/94 > Proof: > https://invent.kde.org/kloecker/apps-kde-org/-/jobs/1897729/artifacts/ > external_file/public/kwalletmanager5/index.html Can we have someone that knows about that code review it or should i just press the bottom and YOLO it? [ the html_test on CI fails, is that expected when run on a repo fork? ] Cheers, Albert > > Regards, > Ingo
KDE Gear projects with failing CI (release/24.05) (11 June 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. VERY BAD NEWS - kio-gdrive Qt 5.15 CI has been unbuildable and has been removed from CI. Good news: 1 repository has been fixed Bad news: 6 repositories are still failing kwalletmanager - 3rd week * https://invent.kde.org/utilities/kwalletmanager/-/pipelines/711185 * appstream test fails because https://apps.kde.org/kwalletmanager5 doesn't exist neochat - 3rd week * https://invent.kde.org/network/neochat/-/pipelines/711191 * windows tests fail dolphin - 3rd week * https://invent.kde.org/system/dolphin/-/pipelines/711183 * kio-extras fails to compile in craft_windows_qt6_x86_64 ark - 3rd week * https://invent.kde.org/utilities/ark/-/pipelines/711184 * kerfuffle-extracttest fails on FreeBSD kdenlive - NEW * https://invent.kde.org/multimedia/kdenlive/-/pipelines/711186 * craft_appimage_qt6_x86_64 and craft_windows_qt6_mingw64 fail Cheers, Albert
KDE Gear projects with failing CI (master) (11 June 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. VERY BAD NEWS - massif-visualizer appstream test is still failing after 4 weeks, I've disabled requiring the tests to pass until it's fixed. It's very sad this has not been addressed in a month time. VERY BAD NEWS #2 - kio-gdrive Qt 5.15 CI has been unbuildable and has been removed from CI. If this doesn't get resolved before the 24.08 release we will have to drop kio-gdrive from KDE Gear [*] Good news: 3 repositories fixed Bad news: *4* repositories keep failing and 2 new repositories started failing dolphin - 3rd week * https://invent.kde.org/system/dolphin/-/pipelines/711192 * craft_windows_qt6_x86_64 fails to compile kio-extras ark - 3rd week * https://invent.kde.org/utilities/ark/-/pipelines/711195 * kerfuffle-extracttest fails on FreeBSD kwalletmanager - 3rd week * https://invent.kde.org/utilities/kwalletmanager/-/pipelines/711196 * appstreamtest fails because https://apps.kde.org/kwalletmanager5 doesn't exist neochat - 3rd week * https://invent.kde.org/network/neochat/-/pipelines/711208 Tests fail on Windows kdenlive - NEW * https://invent.kde.org/multimedia/kdenlive/-/pipelines/711197 * craft_appimage_qt6_x86_64, craft_macos_qt6_arm64 and craft_windows_qt6_mingw64 fail Cheers, Albert [*] One way of resolving it is making kio-gdrive Qt6 only
KDE Frameworks with failing CI (kf5) (9 June 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: All repos CI is passing Given that we don't do much KF5 development, should I stop sending the "all good" emails for it? Cheers, Albert
KDE Frameworks with failing CI (master) (9 June 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Bad news: 1 repo is still failing kuserfeedback - 2nd week * https://invent.kde.org/frameworks/kuserfeedback/-/pipelines/708801 * The typical problem of requiring an unreleased KF6 Should be fixed "shortly" when https://buildbot.flathub.org/#/builders/6/builds/126970 finishes (and gets imported into our thing I think) Cheers, Albert
KDE Gear projects with failing CI (release/24.05) (4 June 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 6 repository has been fixed Bad news: 6 repositories are still failing kio-gdrive - 3rd week * https://invent.kde.org/network/kio-gdrive/-/pipelines/705063 * Qt 5.15 is unbuildable baloo-widgets - 3rd week * https://invent.kde.org/libraries/baloo-widgets/-/pipelines/705060 * filemetadataitemcounttest failed in Linux Qt 6.7 kwalletmanager - 2nd week * https://invent.kde.org/utilities/kwalletmanager/-/pipelines/705057 * appstream test fails because https://apps.kde.org/kwalletmanager5 doesn't exist neochat - 2nd week * https://invent.kde.org/network/neochat/-/pipelines/705065 * windows tests fail dolphin - 2nd week * https://invent.kde.org/system/dolphin/-/pipelines/705053 * kio-extras fails to compile in craft_windows_qt6_x86_64 ark - 2nd week * https://invent.kde.org/utilities/ark/-/pipelines/705056 * kerfuffle-extracttest fails on FreeBSD Cheers, Albert
KDE Gear projects with failing CI (master) (4 June 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 2 repositories fixed Bad news: *7* repositories keep failing and 2 new repositories started failing kio-gdrive - 3rd week * https://invent.kde.org/network/kio-gdrive/-/pipelines/705078 * Qt 5.15 is unbuildable massif-visualizer - 3rd week * https://invent.kde.org/sdk/massif-visualizer/-/pipelines/705072 * appstreamtest fails because https://apps.kde.org/massif-visualizer doesn't exist baloo-widgets - 3rd week * https://invent.kde.org/libraries/baloo-widgets/-/pipelines/705074 * filemetadataitemcounttest failed in Linux Qt 6.7 dolphin - 2nd week * https://invent.kde.org/system/dolphin/-/pipelines/705067 * craft_windows_qt6_x86_64 fails to compile kio-extras ark - 2nd week * https://invent.kde.org/utilities/ark/-/pipelines/705069 * kerfuffle-extracttest fails on FreeBSD kwalletmanager - 2nd week * https://invent.kde.org/utilities/kwalletmanager/-/pipelines/705070 * appstreamtest fails because https://apps.kde.org/kwalletmanager5 doesn't exist neochat - 2nd week * https://invent.kde.org/network/neochat/-/pipelines/705079 Tests fail on Windows akonadi-notes - NEW * https://invent.kde.org/pim/akonadi-notes/-/pipelines/705075 * reuse fails libgravatar - NEW * https://invent.kde.org/pim/libgravatar/-/pipelines/705076 * reuse fails Cheers, Albert
KDE Frameworks with failing CI (kf5) (2 June 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: All repos CI is passing Cheers, Albert
KDE Frameworks with failing CI (master) (2 June 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Bad news: 1 repo started failing kuserfeedback: * https://invent.kde.org/frameworks/kuserfeedback/-/pipelines/703774 * The typical problem of requiring an unreleased KF6 Cheers, Albert
Re: KDE Gear projects with failing CI (release/24.05) (28 May 2024)
Subject had a typo, should have been 28 May not 21 May El dimecres, 29 de maig del 2024, a les 1:13:51 (CEST), Albert Astals Cid va escriure: > Please work on fixing them, otherwise i will remove the failing CI jobs on > their 4th failing week, it is very important that CI is passing for multiple > reasons. > > > Good news: 4 repository has been fixed > > > Bad news: 10 repositories have started failing and 2 are still failing > > > kio-gdrive - 2nd week > * https://invent.kde.org/network/kio-gdrive/-/pipelines/699399 > * Qt 5.15 is unbuildable > > > baloo-widgets - 2nd week > * https://invent.kde.org/libraries/baloo-widgets/-/pipelines/699361 > * filemetadataitemcounttest failed in Linux Qt 6.7 > > > kwalletmanager - NEW > * https://invent.kde.org/utilities/kwalletmanager/-/pipelines/699296 > * appstream test fails because https://apps.kde.org/kwalletmanager5 > doesn't exist > > > khealthcertificate - NEW > * https://invent.kde.org/pim/khealthcertificate/-/pipelines/699436 > * eudgcparsertest crashes in FreeBSD > > > neochat - NEW > * https://invent.kde.org/network/neochat/-/pipelines/699430 > * windows tests fail > > > dolphin - NEW > * https://invent.kde.org/system/dolphin/-/pipelines/699259 > * kio-extras fails to compile in craft_windows_qt6_x86_64 > > > kdeconnect-kde - NEW > * https://invent.kde.org/network/kdeconnect-kde/-/pipelines/699398 > * Windows fails to compile because dbus issues > > > keditbookmarks - NEW > * https://invent.kde.org/utilities/keditbookmarks/-/pipelines/699252 > * Windows fails to compile because dbus issues > > > kmplot - NEW > * https://invent.kde.org/education/kmplot/-/pipelines/699271 > * Windows fails to compile because dbus issues > > > kturtle - NEW > * https://invent.kde.org/education/kturtle/-/pipelines/699273 > * Windows fails to compile because dbus issues > > > kwordquiz - NEW > * https://invent.kde.org/education/kwordquiz/-/pipelines/699274 > * Windows fails to compile because dbus issues > > > ark - NEW > * https://invent.kde.org/utilities/ark/-/pipelines/699288 > * dbus issues on Windows > * kerfuffle-extracttest fails on FreeBSD > > Cheers, > Albert
KDE Gear projects with failing CI (release/24.05) (21 May 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 4 repository has been fixed Bad news: 10 repositories have started failing and 2 are still failing kio-gdrive - 2nd week * https://invent.kde.org/network/kio-gdrive/-/pipelines/699399 * Qt 5.15 is unbuildable baloo-widgets - 2nd week * https://invent.kde.org/libraries/baloo-widgets/-/pipelines/699361 * filemetadataitemcounttest failed in Linux Qt 6.7 kwalletmanager - NEW * https://invent.kde.org/utilities/kwalletmanager/-/pipelines/699296 * appstream test fails because https://apps.kde.org/kwalletmanager5 doesn't exist khealthcertificate - NEW * https://invent.kde.org/pim/khealthcertificate/-/pipelines/699436 * eudgcparsertest crashes in FreeBSD neochat - NEW * https://invent.kde.org/network/neochat/-/pipelines/699430 * windows tests fail dolphin - NEW * https://invent.kde.org/system/dolphin/-/pipelines/699259 * kio-extras fails to compile in craft_windows_qt6_x86_64 kdeconnect-kde - NEW * https://invent.kde.org/network/kdeconnect-kde/-/pipelines/699398 * Windows fails to compile because dbus issues keditbookmarks - NEW * https://invent.kde.org/utilities/keditbookmarks/-/pipelines/699252 * Windows fails to compile because dbus issues kmplot - NEW * https://invent.kde.org/education/kmplot/-/pipelines/699271 * Windows fails to compile because dbus issues kturtle - NEW * https://invent.kde.org/education/kturtle/-/pipelines/699273 * Windows fails to compile because dbus issues kwordquiz - NEW * https://invent.kde.org/education/kwordquiz/-/pipelines/699274 * Windows fails to compile because dbus issues ark - NEW * https://invent.kde.org/utilities/ark/-/pipelines/699288 * dbus issues on Windows * kerfuffle-extracttest fails on FreeBSD Cheers, Albert
KDE Gear projects with failing CI (master) (28 May 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 3 repositories fixed Bad news: 3 repositories keep failing and 6 new repositories started failing kio-gdrive - 2nd week * https://invent.kde.org/network/kio-gdrive/-/pipelines/699220 * Qt 5.15 is unbuildable massif-visualizer - 2nd week * https://invent.kde.org/sdk/massif-visualizer/-/pipelines/699206 * appstreamtest fails because https://apps.kde.org/massif-visualizer doesn't exist baloo-widgets - 2nd week * https://invent.kde.org/libraries/baloo-widgets/-/pipelines/699215 * filemetadataitemcounttest failed in Linux Qt 6.7 dolphin - NEW * https://invent.kde.org/system/dolphin/-/pipelines/699123 * craft_windows_qt6_x86_64 fails to compile kio-extras kmplot - NEW * https://invent.kde.org/education/kmplot/-/pipelines/699137 * dbus issues on Windows kturtle - NEW * https://invent.kde.org/education/kturtle/-/pipelines/699139 * dbus issues on Windows ark - NEW * https://invent.kde.org/utilities/ark/-/pipelines/699154 * dbus issues on Windows * kerfuffle-extracttest fails on FreeBSD kwalletmanager - NEW * https://invent.kde.org/utilities/kwalletmanager/-/pipelines/699157 * appstreamtest fails because https://apps.kde.org/kwalletmanager5 doesn't exist neochat - NEW * https://invent.kde.org/network/neochat/-/jobs/1857277 Tests fail on Windows Cheers, Albert
KDE Frameworks with failing CI (kf5) (26 May 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: All repos CI is passing Cheers, Albert
KDE Frameworks with failing CI (master) (26 May 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: All repos are passing :) Cheers, Albert
Re: CI fails for KGeoTag
El dimecres, 22 de maig del 2024, a les 21:30:16 (CEST), Tobias Leupold va escriure: > Hi all :-) > > Currently, CI fails for KGeoTag on the systems that are added automatically > (not on the ones added manually), cf. > > https://invent.kde.org/graphics/kgeotag/-/jobs/1842186 > https://invent.kde.org/graphics/kgeotag/-/jobs/1842188 > > It's something about a missing dependency: > > raise Exception(f"Package {identifier} was not found in branch > {branch}") ... > raise Exception("Unable to locate requested dependency in the registry: > {} (branch: {})".format( identifier, branch )) > ... > Exception: Package marble was not found in branch release/23.08 > > I didn't change anything in the CI config. Apparently, I missed some change, > didn't update a config file or such? > > Could somebody give me a hand about this? Thanks a lot in advance! Fixed with https://invent.kde.org/sysadmin/repo-metadata/-/commit/850a57f5015d197437d5f8ce58f350d0e6f4b27e When your .kde-ci.yml file says 'education/marble': '@stable' it goes to that file to figure out which branch to use and the one from marble was outdated. Cheers, Albert > > Cheers, Tobias
KDE Gear projects with failing CI (release/24.05) (21 May 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 1 repository has been fixed Bad news: 8 repositories have started failing and 1 is still failing tokodon - 2nd week * https://invent.kde.org/network/tokodon/-/pipelines/693883 * TimelineTest fails in suse_tumbleweed_qt67 kio-gdrive - NEW * https://invent.kde.org/network/kio-gdrive/-/pipelines/693881 * Qt 5.15 is unbuildable because needs libkgapi and we don't have a Qt5 CI build of libkgapi anymore. This is REAL BAD. baloo-widgets - NEW * https://invent.kde.org/libraries/baloo-widgets/-/pipelines/693871 * filemetadataitemcounttest failed in Linux Qt 6.7 elisa - NEW * https://invent.kde.org/multimedia/elisa/-/pipelines/694075 * craft android build fails kate - NEW * https://invent.kde.org/utilities/kate/-/pipelines/693848 * craft windows time ran out, did it try to compile the whole world? * craft mac has been stuck for hours, builder down? dolphin - NEW * https://invent.kde.org/system/dolphin/-/pipelines/693849 * craft windows time ran out, did it try to compile the whole world? okular - NEW * https://invent.kde.org/graphics/okular/-/pipelines/693860 * craft windows failed, possibly in codesign? * craft mac has been stuck for hours, builder down? kdenlive - NEW * https://invent.kde.org/multimedia/kdenlive/-/pipelines/693861 * craft mac has been stuck for hours, builder down? kdeconnect-kde - NEW * https://invent.kde.org/network/kdeconnect-kde/-/pipelines/693880 * craft mac has been stuck for hours, builder down? Cheers, Albert
KDE Gear projects with failing CI (master) (21 May 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 8 repositories fixed Bad news: 6 new repositories started failing kio-gdrive - NEW * https://invent.kde.org/network/kio-gdrive/-/pipelines/693840 * Qt 5.15 is unbuildable because needs libkgapi and we don't have a Qt5 CI build of libkgapi anymore. This is REAL BAD. massif-visualizer - NEW * https://invent.kde.org/sdk/massif-visualizer/-/pipelines/693832 * appstreamtest fails because https://apps.kde.org/massif-visualizer doesn't exist baloo-widgets - NEW * https://invent.kde.org/libraries/baloo-widgets/-/pipelines/693837 * filemetadataitemcounttest failed in Linux Qt 6.7 tokodon - NEW * https://invent.kde.org/network/tokodon/-/pipelines/693844 * TimelineTest failed in Linux Qt 6.7 okular - NEW * https://invent.kde.org/graphics/okular/-/pipelines/693821 * craft mac and windows failed, possibly in codesign? kdenlive - NEW * https://invent.kde.org/multimedia/kdenlive/-/pipelines/693822 * craft windows failed, possibly in codesign? * craft mac has been stuck for hours, builder down? Cheers, Albert
KDE Frameworks with failing CI (kf5) (19 May 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: All repos CI is passing Cheers, Albert
KDE Frameworks with failing CI (master) (19 May 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: All repos are passing :) Cheers, Albert
KDE Gear projects with failing CI (release/24.05) (14 May 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. VERY BAD NEWS: cantor hit its 4 week of tests failing and I've disabled them https://invent.kde.org/education/cantor/-/commit/864ccca3c494004ec2c9ed74ef5a98b6dcfdcb8b Good news: 7 repositories have been fixed Bad news: 1 repositories has started failing and 1 is still failing tokodon - NEW * https://invent.kde.org/network/tokodon/-/pipelines/688342 * suse_tumbleweed_qt67 test fails * This seems to work on master, can we backport the fix? kimap - 2nd week * https://invent.kde.org/pim/kimap/-/pipelines/688337 * freebsd tests fail * This seems to work on master, can we backport the fix? Cheers, Albert
KDE Gear projects with failing CI (master) (14 May 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 3 repositories fixed Bad news: 7 new repositories started failing dolphin - NEW * https://invent.kde.org/system/dolphin/-/pipelines/688258 * craft_windows_qt6_x86_64 needs newer KF6 than provided flatpak needs newer KF6 than provided * https://invent.kde.org/system/dolphin/-/pipelines/688258 * https://invent.kde.org/accessibility/kontrast/-/pipelines/688311 * https://invent.kde.org/pim/itinerary/-/pipelines/688316 * https://invent.kde.org/network/alligator/-/pipelines/688321 * https://invent.kde.org/utilities/kclock/-/pipelines/688323 * https://invent.kde.org/utilities/krecorder/-/pipelines/688324 * https://invent.kde.org/plasma-mobile/qmlkonsole/-/pipelines/688325 New flatpak SDK are building that should fix stuff when ready https://buildbot.flathub.org/#/apps/org.kde.Sdk~2F6.7 https://buildbot.flathub.org/#/apps/org.kde.Sdk~2F6.6 Do we need to do some sync to import them to our systems or will it just work? Cheers, Albert
KDE Frameworks with failing CI (kf5) (12 May 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: All repos CI is passing Cheers, Albert
KDE Frameworks with failing CI (master) (12 May 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 1 repo was fixed Bad news: 1 repo keeps failing kuserfeedback: * https://invent.kde.org/frameworks/kuserfeedback/-/pipelines/680497 * flatpak fails * Needs a newer ECM than what flatpak SDK has (should be fixed by updating the KF6 in the flatpak SDK) Cheers, Albert
KDE Gear projects with failing CI (release/24.05) (7 May 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Bad news: 9 repositories have started failing and 1 is still failing cantor - 3rd week * https://invent.kde.org/education/cantor/-/pipelines/676922 * suse_tumbleweed_qt515 and windows_qt515 tests fail tokodon - NEW * https://invent.kde.org/network/tokodon/-/pipelines/682468 * craft android fails kimap - NEW * https://invent.kde.org/pim/kimap/-/pipelines/682429 * freebsd tests fail kig - NEW * https://invent.kde.org/education/kig/-/pipelines/682321 * craft_macos_x86_64 fails to compile Qt5 gwenview - NEW * https://invent.kde.org/graphics/gwenview/-/pipelines/682335 * flatpak fails to compile craft_windows_qt6_x86_64 broken in several repos: no easy to understand error * https://invent.kde.org/utilities/kate/-/pipelines/682305 * https://invent.kde.org/system/dolphin/-/pipelines/682309 * https://invent.kde.org/graphics/okular/-/pipelines/682346 * https://invent.kde.org/utilities/filelight/-/pipelines/682349 * https://invent.kde.org/network/neochat/-/pipelines/682465 Cheers, Albert
KDE Gear projects with failing CI (master) (7 May 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Bad news: 1 repository is still failing and 3 new ones started failing tokodon - 3rd week * https://invent.kde.org/network/tokodon/-/pipelines/682294 * suse_tumbleweed_qt67 fails kdenlive - NEW * https://invent.kde.org/multimedia/kdenlive/-/pipelines/682483 * craft_windows_qt6_x86_64 fails to compile kdenlivesettingsdialog.cpp dolphin - NEW * https://invent.kde.org/system/dolphin/-/pipelines/682230 * craft_windows_qt6_x86_64 fails without any discernible error kdeconnect-kde - NEW * https://invent.kde.org/network/kdeconnect-kde/-/pipelines/682282 * craft_windows_qt6_x86_64 fails without any discernible error Cheers, Albert
KDE Frameworks with failing CI (kf5) (5 May 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: All repos CI is passing Cheers, Albert
KDE Frameworks with failing CI (master) (5 May 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 1 repo was fixed Bad news: 2 repo started failing kimageformats: * https://invent.kde.org/frameworks/kimageformats/-/pipelines/680495 * andoid fails * Needs a newer ECM than what the Andoid CI has kuserfeedback: * https://invent.kde.org/frameworks/kuserfeedback/-/pipelines/680497 * flatpak fails * Needs a newer ECM than what flatpak SDK has Cheers, Albert
KDE Gear projects with failing CI (release/24.05) (30 April 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 1 repository was fixed Bad news: 5 repositories have started failing and 2 are still failing cantor - 2nd week * https://invent.kde.org/education/cantor/-/pipelines/676922 * suse_tumbleweed_qt515 and windows_qt515 tests fail tokodon - 2nd week * https://invent.kde.org/network/tokodon/-/pipelines/676936 * suse_tumbleweed_qt67 tests fail neochat - NEW * https://invent.kde.org/network/neochat/-/pipelines/676935 * suse_tumbleweed_qt67 tests fail craft-macos broken in several repos * https://invent.kde.org/utilities/konsole/-/pipelines/676921 * https://invent.kde.org/education/kmplot/-/pipelines/676923 * https://invent.kde.org/graphics/kolourpaint/-/pipelines/676924 * https://invent.kde.org/network/kdeconnect-kde/-/pipelines/676933 Cheers, Albert
KDE Gear projects with failing CI (master) (30 April 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 4 repositories got fixed Bad news: 1 repository is still failing tokodon - 2nd week * https://invent.kde.org/network/tokodon/-/pipelines/676920 * suse_tumbleweed_qt67 fails Cheers, Albert
KDE Frameworks with failing CI (kf5) (28 April 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: All repos CI is passing Cheers, Albert
KDE Frameworks with failing CI (master) (28 April 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Bad news: 1 repo started failing kconfig: * https://invent.kde.org/frameworks/kconfig/-/pipelines/675292 * kconfigcore-kdesktopfiletest fails on Linux * windows fails to compile * There have not been changes lately? Qt/ECM regressions? Cheers, Albert
KDE Gear projects with failing CI (release/24.05) (23 April 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Bad news: 4 repositories have started failing cantor - NEW * https://invent.kde.org/education/cantor/-/pipelines/671601 * suse_tumbleweed_qt515 and windows_qt515 tests fail libkleo - NEW * https://invent.kde.org/pim/libkleo/-/pipelines/671605 * suse_tumbleweed_qt67 tests fail tokodon - NEW * https://invent.kde.org/network/tokodon/-/pipelines/671608 suse_tumbleweed_qt67 tests fail neochat - NEW * https://invent.kde.org/network/neochat/-/pipelines/671682 * craft_appimage_qt6_x86_64 and flatpak fail Cheers, Albert
KDE Gear projects with failing CI (master) (23 April 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 4 repositories got fixed Bad news: 5 new repositories failing this week kimap - NEW * https://invent.kde.org/pim/kimap/-/pipelines/671573 * testsession fails on freebsd14_qt66 tokodon - NEW * https://invent.kde.org/network/tokodon/-/pipelines/671582 * suse_tumbleweed_qt67 fails cantor - NEW * https://invent.kde.org/education/cantor/-/pipelines/671568 * suse_tumbleweed_qt515 and windows_qt515 fail kturtle - NEW * https://invent.kde.org/education/kturtle/-/pipelines/671569 * craft_windows_qt6_x86_64 fails neochat - NEW * https://invent.kde.org/network/neochat/-/pipelines/671651 * craft_appimage_qt6_x86_64 and craft_windows_qt6_x86_64 fail Cheers, Albert
Sun-setting QCA
QCA has served us well for quite some time, but it's time to sunset it. The architecture is quite complex, its plugin based functionality means that you can never be sure if a given feature your app needs will be available or not and the features we use from it are small compared to the huge amount of features QCA actually has meaning the maintainance effort is bigger than it needs to be. I've started https://invent.kde.org/libraries/qca/-/issues/18 to collect the uses of QCA and plan for replacing it with appropriate crypto code/library directly. Best Regards, Albert
Re: Proposal unify back our release schedules
El dilluns, 22 d’abril del 2024, a les 17:12:46 (CEST), Nate Graham va escriure: > Ok, so happily I actually see quite a bit of agreement here, regardless > of what else we do. > > 1. Fibonacci bugfix releases are good, and we could benefit from having > Gear adopt these. > > 2. Severing implicit dependencies is a good idea. Shared libraries in > Gear are especially problematic and could benefit from being moved to > Frameworks. > > 3. Fast frameworks releases in some capacity are a benefit and we don't > want to lose this. > > > All in agreement? If so, that would be amazing. > > --- > > Now, let's say we make Gear use Plasma's current release schedule by > syncing up the feature releases and adopting the Fibonacci bugfix > releases. If we don't end up changing Plasma's own release schedule then > we already make our promo store more coherent by letting the marketing > team do three big glossy announcements of user-facing products a year, > rather than being stretched thin for 6. Even if we make Plasma go down > to 2 releases a year, then we have two synced Gear+Plasma > "mega-releases" and 2 independent Gear releases--down from 6 to 4. Both > of these options would improve the promo story IMO. > > --- > > Moving on, the biggest points of contention I see revolve around > Frameworks. Personally I want to push back a bit on the idea of > developing an app against released frameworks. I disagree. In my ideal world, applications should be able to be built against a one year old frameworks, before the Qt6 port, Okular's minimum requirement was Ubuntu 22.04, which makes sure virtually everyone can contribute to it without having to build the world. There's virtually no need in Okular to depend against any new frameworks shiny feature, the existing features are more than enough. Cheers, Albert > This is only realistic if > you use a rolling release distro and are okay with waiting a month to > use the new Frameworks code. > > For users looking to contribute with common > discrete-release distros, it is not at all realistic as many Frameworks > consumers require versions newer than what those users have on their > system, so they have to build some Frameworks anyway (note: not all of > them; kdesrc-build/kde-builder are smart enough not to do unnecessary > work). The older the distro's packages, the more likely this is to be. > > Furthermore, because Frameworks has time-based releases and no beta > releases, in practice the QA is provided by developers living on master. > If KDE developers deliberately avoid this, they're not participating in > QA. There are of course other ways to improve Frameworks' QA as well, > but continuing to encourage KDE developers to use distro-packaged > Frameworks goes against the larger goal: we can't QA software versions > we're not using. > > While 12 releases a year of Frameworks feels fast, it's actually not. > Gear also has 12 releases a year: 3 feature releases and 9 bugfix > releases. And Plasma currently gets 18: 3 feature releases and 15 bugfix > releases. The lack of bugfix releases is notable. With Plasma if a major > bug is discovered a day after the release (which is common) I can ship a > fix within a week, whereas for Frameworks, it takes a month. This is not > a theoretical problem; it has happened many times over the years. > > To me it has always felt strange that the product that benefits most > from stability gets 4 times as many yearly feature releases as Gear and > Plasma, but no bugfix releases at all. And there have been many > occasions oven the years where new features in Frameworks could have > benefited from a bit more QA time in master before final release. > > In this sense I find Frameworks' release schedule to be both too fast > and too slow: too fast for new features and too slow for bugfixes. > Shouldn't the product with the strongest stability guarantee ship > bugfixes at least as fast as Plasma? > > If Frameworks got a feature release every 2 or 3 months and a guaranteed > bugfix release one week after each feature release, IMO the result would > be much better. We could ship fixes for important bugs faster, > developers would be more incentivized to live on master and therefore > provide their own QA, the period of time during which issues with new > features could be caught before release would be doubled or tripled, and > we could even still have 12 total releases per year. > > --- > > Thus, if we make Gear's release cycle identical to Plasma's to get it > faster bugfixes, and then we also lengthen Frameworks' release cycle so > it gets the bugfix releases it could benefit from while slowing down its > feature releases to improve QA, then the result looks a lot like Carl's > proposal, and that's ultimately why it looks appealing to me. > > This doesn't preclude breaking implicit dependencies and relocating > software into groups/release vehicles more suited for them. I don't find > the argument convincing that
KDE Gear 24.05 branches created
Make sure you commit anything you want to end up in the KDE Gear 24.05 releases to them Next Dates April 25 2024: 24.05 Freeze and Beta (24.04.80) tag & release May 9, 2024: 24.05 RC (24.04.90) Tagging and Release May 16, 2024: 24.05 Tagging May 23, 2024: 24.05 Release https://community.kde.org/Schedules/KDE_Gear_24.05_Schedule Cheers, Albert
Re: AppStream Metadata with our releases
El divendres, 22 de març del 2024, a les 0:37:00 (CEST), Julius Künzel va escriure: > Hi! > > (This mail goes to multiple lists, please reply to kde-devel) > > With Flathub beeing more strict on its AppStream metadata guidlines [1] > there is yet another spotlight on AppStream metadata. > > AppStream metadata are consumed by app stores like Flathub, Snapcraft, > Discover, our scripts to submit apps to the Microsoft Store and last but > not least by apps.kde.org [2]. > > For release info in particular the quality guidelines say: "Make sure all > your releases have release notes, even minor ones." [3] As I think this > makes perfectly sense, I like to propose two things that seem straight > forward to me: > > - We should not remove older releases from the AppStream data as already > suggested by Carl in a merge request [4]. I'd go for https://invent.kde.org/sysadmin/release-tools/-/merge_requests/48/diffs instead. Cheers, Albert > > - Also it would be convenient to add noteworthy changes to the metadata > together with the related code change. However at the moment for KDE Gear > the release is usually only added to the metadata a few days before > tagging. Would it be possible to add the next minor release to the release > branch right after the current one has been released and the next major > release to master ones the upcoming version has been branched? > > I belive this makes it easier for developers to contribute to the release > meta info and I hope it hence raises motivation to do so. > > I am happy to hear your opionions, thoughts and concerns! > > Cheers, > Julius > > [1] https://docs.flathub.org/docs/for-app-authors/metainfo-guidelines > [2] https://apps.kde.org/ > [3] > https://docs.flathub.org/docs/for-app-authors/metainfo-guidelines/quality-g > uidelines/#release-notes [4] > https://invent.kde.org/sysadmin/appstream-metainfo-release-update/-/merge_r > equests/6 > > Julius Künzel > Volunteer KDE Developer, mainly hacking Kdenlive > KDE GitLab: www.invent.kde.org/jlskuz https://invent.kde.org/jlskuz > Matrix: @jlskuz:kde.org https://go.kde.org/matrix/#/@jlskuz:kde.org
KDE Frameworks with failing CI (kf5) (21 April 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: All repos CI is passing Cheers, Albert
KDE Frameworks with failing CI (master) (21 April 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: All repos CI is passing Cheers, Albert
KDE Gear projects with failing CI (master) (16 April 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. VERY BAD NEWS: umbrello craft-windows-x86-64 has been disabled because it failed for 4 consecutive weeks VERY BAD NEWS: kirigami-gallery android has been disabled because it failed for 4 consecutive weeks Good news: 4 repositories got fixed Bad news: 1 repositories still failing and new 5 repositories failing this week kdenlive - 2nd week * https://invent.kde.org/multimedia/kdenlive/-/pipelines/664408 * flatpak fails, shasum changed? kontrast - NEW * https://invent.kde.org/accessibility/kontrast/-/pipelines/664432 * craft android builds fail because kirigami-addons is asking for KF 6.2 keysmith - NEW * https://invent.kde.org/utilities/keysmith/-/pipelines/664439 * craft android builds fail because kirigami-addons is asking for KF 6.2 itinerary - NEW * https://invent.kde.org/pim/itinerary/-/pipelines/664435 * craft android builds fail to compile libquotient kasts - NEW * https://invent.kde.org/multimedia/kasts/-/pipelines/664438 * craft android build fails to compile aom neochat - NEW * https://invent.kde.org/network/neochat/-/pipelines/664524 * flatpak and craft android builds fail Cheers, Albert
KDE Frameworks with failing CI (kf5) (14 April 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. VERY BAD NEWS: kirigami made it to its 4th week with Android build failing and I've removed the CI. Bad news: 1 repository is still failing kcontacts - 2nd week * https://invent.kde.org/frameworks/kcontacts/-/pipelines/662694 * AddressTest fails on FreeBSD (Same as in master) Cheers, Albert
KDE Frameworks with failing CI (master) (14 April 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 1 repository has been fixed Bad news: 2 repositories are still failing kcontacts - 2nd week * https://invent.kde.org/frameworks/kcontacts/-/pipelines/662687 * AddressTest::formatTest fails in FreeBSD kuserfeedback - 2nd week * https://invent.kde.org/frameworks/kuserfeedback/-/pipelines/662688 * Available flatpak images in CI need to be updated Cheers, Albert
Re: Sponsor request for Incubation of LightDM Greeter by KDE
El diumenge, 10 de desembre del 2023, a les 23:23:17 (CEST), Albert Astals Cid va escriure: > El dilluns, 4 de desembre de 2023, a les 8:14:03 (CET), Anton Golubev va > > escriure: > > Hello, > > > > The revival of this project has been discussed earlier[1]. The project > > repository has been unarchived[2], and now it needs to go through > > Incubation for it to become fully functional. > > > > For Incubation, I opened the appropriate issue[3] and now I ask someone > > to become a sponsor of this process. > > I can be your sponsor. https://invent.kde.org/plasma/lightdm-kde-greeter/-/issues/1 After a few months we are almost done with this Only things missing are: * "overwrite" master branch contents with v0.3 branch (and put current master contents somewhere else, this is because master devied from 0.3 and then was abandoned, incubation continues from branch 0.3) * restore the translations. If no one disagrees we will ask sysadmin to do the master "overwriting" in a couple of days. Cheers, Albert > > I'll send you an email in private. > > Cheers, > Albert > > > Regards, > > > > [1]: https://mail.kde.org/pipermail/kde-devel/2023-November/002177.html > > [2]: https://invent.kde.org/plasma/lightdm-kde-greeter > > [3]: https://invent.kde.org/plasma/lightdm-kde-greeter/-/issues/1
KDE Gear projects with failing CI (release/24.02) (2 April 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 1 repository was fixed Bad news: 2 repositories are still failing and 6 repositories has started failing kirigami-gallery - 3rd week * https://invent.kde.org/sdk/kirigami-gallery/-/pipelines/657676 * Android build fails umbrello - 3rd week * https://invent.kde.org/sdk/umbrello/-/pipelines/657665 * craft_windows_qt515_x86_64 fails krdc - NEW * https://invent.kde.org/network/krdc/-/pipelines/657666 * Linux builds fail because of missing dependencies ktrip - NEW * https://invent.kde.org/utilities/ktrip/-/pipelines/657677 * craft builds fail tokodon - NEW * https://invent.kde.org/network/tokodon/-/pipelines/657678 * tokodon-searchtest fails in Linux and FreeBSD dolphin - NEW * https://invent.kde.org/system/dolphin/-/pipelines/657664 * flatpak fails because it is building baloo from master instead of stable arianna - NEW * https://invent.kde.org/graphics/arianna/-/pipelines/657679 * flatpak fails because it is building baloo from master instead of stable pim-sieve-editor - NEW * https://invent.kde.org/pim/pim-sieve-editor/-/pipelines/657670 * flatpak fails because it is building ktexttemplate from master instead of stable Cheers, Albert
KDE Gear projects with failing CI (master) (9 April 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 3 repositories got fixed Bad news: 2 repositories still failing and new 5 repositories failing this week umbrello - 3rd week * https://invent.kde.org/sdk/umbrello/-/pipelines/657654 * craft_windows_qt515_x86_64 fails kirigami-gallery - 3rd week * https://invent.kde.org/sdk/kirigami-gallery/-/pipelines/657659 * Android build fails kdenlive - NEW * https://invent.kde.org/multimedia/kdenlive/-/pipelines/657653 * flatpak fails, shasum changed? kldap - NEW * https://invent.kde.org/pim/kldap/-/pipelines/657656 * Windows build fails because it can't find Qt6Keychain kmailtransport - NEW * https://invent.kde.org/pim/kmailtransport/-/pipelines/657657 * Windows build fails because it can't find Qt6Keychain pim-sieve-editpr - NEW * https://invent.kde.org/pim/pim-sieve-editor/-/pipelines/657658 * Windows build fails because it can't find Qt6Keychain ktrip - NEW * https://invent.kde.org/utilities/ktrip/-/pipelines/657661 * craft_android builds fail Cheers, Albert
Re: KDE Builder: request for review
El dimarts, 9 d’abril del 2024, a les 12:51:50 (CEST), Sune Vuorela va escriure: > On Mon, Apr 8, 2024 at 10:05 AM wrote: > > and deprecating the kdesrc-build. That way we can move forward with new > > tool. > I don't think reviewing or not of kde-builder should have any effect on > kdesrc-build. Yes, i think the original email comes from a bit of misunderstanding on how we work. We are not a top-down organization. There is hardly an "official" anything in KDE. We have dolphin but we also have krusader, sure one ships with KDE Gear and the other doesn't but that's more a release schedule decision than one being more official than the other. We have gwenview and koko, both shipping in KDE Gear. And more and more examples. So unless the people working on kdesrc-build want people to stop using that and no one else steps up to work on it kdesrc-build will be as "official" as it is today, 0% official and 100% official at the same time. Cheers, Albert > > I think also we should be slightly wary of changing a long-running 20y > old tool written by long time kde people who are still around with a > brand new tool written by a brand new contributor. > I wonder if it will have the same shelf life as the ruby version that > was done some years ago and abandoned. > > /Sune
KDE Frameworks with failing CI (kf5) (7 April 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Bad news: 1 repositories is still failing and 1 has started failing kirigami - 3rd week * https://invent.kde.org/frameworks/kirigami/-/pipelines/649285 * Android build fails * Something qt related needs a rebuild? kcontacts - NEW * https://invent.kde.org/frameworks/kcontacts/-/pipelines/655262 * AddressTest fails on FreeBSD (Same as in master) Cheers, Albert
KDE Frameworks with failing CI (master) (7 April 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Bad news: 3 repositories have started failing kconfigwidgets - NEW * https://invent.kde.org/frameworks/kconfigwidgets/-/pipelines/655246 * klanguagenametest fails in Linux * https://invent.kde.org/frameworks/kconfigwidgets/-/merge_requests/234 kcontacts - NEW * https://invent.kde.org/frameworks/kcontacts/-/pipelines/655247 * AddressTest::formatTest fails in FreeBSD kuserfeedback - NEW * https://invent.kde.org/frameworks/kuserfeedback/-/pipelines/655248 * The code requires unreleased versions so flatpak fails Cheers, Albert
KDE Gear projects with failing CI (release/24.02) (2 April 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 1 repository was fixed Bad news: 2 repositories are still failing and 1 repository has started failing kirigami-gallery - 2nd week * https://invent.kde.org/sdk/kirigami-gallery/-/pipelines/650570 * Android build fails * Similar problem to the one in kirigami being discussed in the frameworks mailing list umbrello - 2nd week * https://invent.kde.org/sdk/umbrello/-/pipelines/650565 * craft_windows_qt515_x86_64 fails * Same as in the master report, something is up with qtwebengine? kitinerary - NEW * https://invent.kde.org/pim/kitinerary/-/pipelines/650569 * extractortest fails in FreeBSD Cheers, Albert
KDE Gear projects with failing CI (master) (2 April 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 1 repositories got fixed Bad news: 4 repositories still failing and 1 new repository failing this week kgeography - 3rd week * https://invent.kde.org/education/kgeography/-/pipelines/650531 * craft_macos_qt6_x86_64 fails kig - 2nd week * https://invent.kde.org/education/kig/-/pipelines/650532 * craft_macos_qt6_x86_64 fails umbrello - 2nd week * https://invent.kde.org/sdk/umbrello/-/pipelines/650538 * craft_windows_qt515_x86_64 fails * Something is up with qtwebengine? kirigami-gallery - 2nd week * https://invent.kde.org/sdk/kirigami-gallery/-/pipelines/650557 * Android build fails * Similar problem to the one in kirigami being discussed in the frameworks mailing list calindori - NEW * https://invent.kde.org/plasma-mobile/calindori/-/pipelines/650676 * https://invent.kde.org/plasma-mobile/calindori/-/pipelines/650559 * Craft builds fail * It still had a Qt5 craft build when the code is now Qt6 based I blindly pushed a change to make the craft builds Qt6 based That was probably not a very smart move, the builds still fail Cheers, Albert
KDE Frameworks with failing CI (kf5) (31 March 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 1 repository has been fixed Bad news: 1 repositories is still failing kirigami - 2nd week * https://invent.kde.org/frameworks/kirigami/-/pipelines/649285 * Android build fails * Something qt related needs a rebuild? Cheers, Albert
KDE Frameworks with failing CI (master) (31 March 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: All repositories are passing :) Cheers, Albert
KDE Gear projects with failing CI (release/24.02) (27 March 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Bad news: 3 repositories have started failing korganizer: * https://invent.kde.org/pim/korganizer/-/pipelines/645389 * A function was removed in eventviews and makes korganizer not compile. Why was even a function removed in a stable branch of a library? kirigami-gallery - NEW * https://invent.kde.org/sdk/kirigami-gallery/-/pipelines/645390 * Android build fails * Similar problem to the one in kirigami being discussed in the frameworks mailing list umbrello - NEW * https://invent.kde.org/sdk/umbrello/-/pipelines/645398 * craft_windows_qt515_x86_64 fails * Same as in the master report, something is up with qtwebengine? Cheers, Albert
KDE Gear projects with failing CI (master) (27 March 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 4 repositories got fixed Bad news: 1 repository still failing and 4 new repositories failing this week kgeography - 2nd week * https://invent.kde.org/education/kgeography/-/pipelines/637304 * craft_macos_qt6_x86_64 fails kig - NEW * https://invent.kde.org/education/kig/-/pipelines/645393 * craft_macos_qt6_x86_64 fails umbrello - NEW * https://invent.kde.org/sdk/umbrello/-/pipelines/645398 * craft_windows_qt515_x86_64 fails * Something is up with qtwebengine? kleopatra - NEW * https://invent.kde.org/pim/kleopatra/-/pipelines/645399 * flatpak fails * It wants an unreleased version of KPim6Mime but the flatpak manifest says it should work with release/24.02 one of the two needs fixing kirigami-gallery - NEW * https://invent.kde.org/sdk/kirigami-gallery/-/pipelines/645400 * Android build fails * Similar problem to the one in kirigami being discussed in the frameworks mailing list Cheers, Albert
Re: AppStream Metadata with our releases
El dimarts, 26 de març de 2024, a les 17:39:25 (CET), Volker Krause va escriure: > On Dienstag, 26. März 2024 08:59:29 CET Heiko Becker wrote: > > On Monday, 25 March 2024 23:23:01 CET, Albert Astals Cid wrote: > > > El dissabte, 23 de març de 2024, a les 21:06:46 (CET), Julius Künzel va > > > > > > escriure: > > >> 22.03.2024 17:22:33 Albert Astals Cid : ... > > > > > > It is some extra work (not a lot, but some). > > > > > > You're asking for the workflow of creating to be releases to be changed > > > by > > > creating the entry in the file earlier, that alone is a bit of work, but > > > it > > > > > > has several other consequences: > > > * https://apps.kde.org/okular/ shows releases from the appstream file > > > (i > > > > > > think) meaning that the code should learn to ignore releases in the > > > future. > > > Arguably we would need also now, but given the data is added > > > just a few days > > > before the actual release i think users can understand "this release > > > will > > > happen soon)" compared to a thing one month in the future > > > > > > * What happens if we have to change the release date or release version > > > > > > number (hasn't happened in a good while, but wouldn't be a bad thing to > > > prepare for it). We would need to update the string or date of an > > > existing > > > entry, as far as I know we don't have tooling for that (because we only > > > add > > > the data to the file when we're almost sure abiyt it). > > > > In addition I'm a litte bit wary of conflicts when cherry-picking the > > appstream changes between branches, which the script does after > > incrementing the version. I saw at least conflicts in itinerary's releases > > notes and e.g. kdeconnect's or okular's windows releases in the past, > > which > > isn't that much of a problem but it could become one with the 245 modules > > of gear (to be fair not all have appstream metadata (yet)). > > Sorry about that! I try to keep both branches in sync usually, if there is > anything I can do/do differently to not impact your work I'm happy to do > that of course. > > > Otherwise I'd just miss the opportunity to trigger a CI build for > > everything again shortly before the release, but I'd guess that's easy to > > get over. > > Albert seems to have an alternative way using API (?) for the weekly build > status reports, I guess that could be reused/combined somehow? It's just some lines of python that interact with the gitlab api, they are not very polished, but i can put them on a random repo if you want to have a look at them. Cheers, Albert > > Regards, > Volker
Re: KDE Frameworks with failing CI (kf5) (24 March 2024)
El dilluns, 25 de març de 2024, a les 18:03:27 (CET), Volker Krause va escriure: > On Sonntag, 24. März 2024 23:14:12 CET Albert Astals Cid wrote: > > Please work on fixing them, otherwise i will remove the failing CI jobs on > > their 4th failing week, it is very important that CI is passing for > > multiple reasons. > > > > Bad news: 2 repositories have started failing > > > > kirigami - NEW > > > > * https://invent.kde.org/frameworks/kirigami/-/jobs/1679118 > > > > * Android build fails > > > >* Something qt related needs a rebuild? > > Yep, looks like a version mix due to the patch collection rebase. But why has this happened? I mean how is it that some Qt has different than some other Qt? Was there a rebuild of Android Qt while i was doing the rebase? If I understand that right there's a QtSvg is 5.15.13 but QtWidgets is only 5.15.12? > I'm wondering how we want to proceed here longer term, as this will continue > to need active maintenance while most of our Android apps have meanwhile > moved to Qt 6. > > Pin the Qt version in Craft to a fixed revision? Drop Android KF5 CI builds? > Find volunteers to do the work of keeping this running/working? If we're saying Kirigami works on Android ideally we should keep a CI. Cheers, Albert > > Regards, > Volker
Re: AppStream Metadata with our releases
El dilluns, 25 de març de 2024, a les 19:37:07 (CET), Volker Krause va escriure: > On Freitag, 22. März 2024 00:37:00 CET Julius Künzel wrote: > > AppStream metadata are consumed by app stores like Flathub, Snapcraft, > > Discover, our scripts to submit apps to the Microsoft Store and last but > > not least by apps.kde.org [2]. > > Same for generating the package metadata on Android, both for our F-Droid > repositories and the Google Play store. > > > - Also it would be convenient to add noteworthy changes to the metadata > > together with the related code change. However at the moment for KDE Gear > > the release is usually only added to the metadata a few days before > > tagging. Would it be possible to add the next minor release to the release > > branch right after the current one has been released and the next major > > release to master ones the upcoming version has been branched? > > At least in the past the appstream validator complained about releases dated > (too far) into the future, but that doesn't seem to be a problem anymore > fortunately. > > As Itinerary was mentioned, the process there currently is to run David's KF > changelog script over all repositories in Itinerary's dependency chain and > take the top 5 or so most visible/important changes (which here are > actually often from other repositories). The commit adding the release to > appstream is my reminder for that currently, but there's other ways to do > that, so for Itinerary the proposed change wouldn't make much of a > difference either way. This brings an interesting point, it would seem that the right time to add the release description is at the end of the release cycle when you know all the changes, not when a particular commit is made. Because if there's 400 changes, you will only want to have the 5 more important changes in the description, but if there's only 5 changes, you may as well add them all. Cheers, Albert > > Regards, > Volker
Re: AppStream Metadata with our releases
El dissabte, 23 de març de 2024, a les 21:06:46 (CET), Julius Künzel va escriure: > 22.03.2024 17:22:33 Albert Astals Cid : > > El divendres, 22 de març de 2024, a les 0:37:00 (CET), Julius Künzel va > > > > escriure: > >> Hi! > >> > >> (This mail goes to multiple lists, please reply to kde-devel) > >> > >> With Flathub beeing more strict on its AppStream metadata guidlines [1] > >> there is yet another spotlight on AppStream metadata. > >> > >> AppStream metadata are consumed by app stores like Flathub, Snapcraft, > >> Discover, our scripts to submit apps to the Microsoft Store and last but > >> not least by apps.kde.org [2]. > >> > >> For release info in particular the quality guidelines say: "Make sure all > >> your releases have release notes, even minor ones." [3] As I think this > >> makes perfectly sense, I like to propose two things that seem straight > >> forward to me: > >> > >> - We should not remove older releases from the AppStream data as already > >> suggested by Carl in a merge request [4]. > >> > >> - Also it would be convenient to add noteworthy changes to the metadata > >> together with the related code change. However at the moment for KDE Gear > >> the release is usually only added to the metadata a few days before > >> tagging. Would it be possible to add the next minor release to the > >> release > >> branch right after the current one has been released and the next major > >> release to master ones the upcoming version has been branched? > >> > >> I belive this makes it easier for developers to contribute to the release > >> meta info and I hope it hence raises motivation to do so. > > > > My pessimistic opinion is that no one is going to add release notes, we've > > tried multiple ways to do it, even just asking people to add a keyword to > > the commit log if that commit log was release news worthy and no one did > > it past the first few weeks/months. > > Well, that might happen, but we don't know if we don't try... And as I don't > see this causing any extra work and (yet) can't see any downsides, it is > even worth it if it helps just a single app or developer, no? It is some extra work (not a lot, but some). You're asking for the workflow of creating to be releases to be changed by creating the entry in the file earlier, that alone is a bit of work, but it has several other consequences: * https://apps.kde.org/okular/ shows releases from the appstream file (i think) meaning that the code should learn to ignore releases in the future. Arguably we would need also now, but given the data is added just a few days before the actual release i think users can understand "this release will happen soon)" compared to a thing one month in the future * What happens if we have to change the release date or release version number (hasn't happened in a good while, but wouldn't be a bad thing to prepare for it). We would need to update the string or date of an existing entry, as far as I know we don't have tooling for that (because we only add the data to the file when we're almost sure abiyt it). Would you be able to work on fixing those two? (make the apps.kde.org page not show future releases and have a script in release-tools to change the date/ version-number of a release?) Cheers, Albert > > It seems appstream has finally added the support (or maybe was > > there > > forever?), so my suggestion is that we just add an release+url entry > > pointing to > > https://kde.org/announcements/gear/x.y.z/ > > > > This way we don't have to do the work twice and has the added bonus of > > already translatable. > > This is a nice suggestion too! > However, I don't think this conflicts with my suggestion as the text in the > appstream should usually be just a short summary of the highlights. So > let's do both? > > Only "problem" is that maybe if we get too many people contributing their > > release news the announcements gets too long, but that'd be a nice problem > > to have. > > > > Cheers, > > Albert > > > >> I am happy to hear your opionions, thoughts and concerns! > >> > >> Cheers, > >> Julius > >> > >> [1] https://docs.flathub.org/docs/for-app-authors/metainfo-guidelines > >> [2] https://apps.kde.org/ > >> [3] > >> https://docs.flathub.org/docs/for-app-authors/metainfo-guidelines/quality > >> -g > >> uidelines/#release-notes [4] > >> https://invent.kde.org/sysadmin/appstream-metainfo-release-update/-/merge > >> _r > >> equests/6 > >> > >> Julius Künzel > >> Volunteer KDE Developer, mainly hacking Kdenlive > >> KDE GitLab: www.invent.kde.org/jlskuz https://invent.kde.org/jlskuz > >> Matrix: @jlskuz:kde.org https://go.kde.org/matrix/#/@jlskuz:kde.org
KDE Frameworks with failing CI (kf5) (24 March 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Bad news: 2 repositories have started failing kirigami - NEW * https://invent.kde.org/frameworks/kirigami/-/jobs/1679118 * Android build fails * Something qt related needs a rebuild? kpackage - NEW * https://invent.kde.org/frameworks/kpackage/-/pipelines/640951 * testpackage-appstream fails Cheers, Albert
KDE Frameworks with failing CI (master) (24 March 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Bad news: 1 repository is still failing, on its last week before disabling kpackage - 3rd week * https://invent.kde.org/frameworks/kpackage/-/pipelines/640942 * appstream check fails. Ben had some comments on March 10 report on this, please check them if you want to work on fixing this. Cheers, Albert
Re: AppStream Metadata with our releases
El divendres, 22 de març de 2024, a les 0:37:00 (CET), Julius Künzel va escriure: > Hi! > > (This mail goes to multiple lists, please reply to kde-devel) > > With Flathub beeing more strict on its AppStream metadata guidlines [1] > there is yet another spotlight on AppStream metadata. > > AppStream metadata are consumed by app stores like Flathub, Snapcraft, > Discover, our scripts to submit apps to the Microsoft Store and last but > not least by apps.kde.org [2]. > > For release info in particular the quality guidelines say: "Make sure all > your releases have release notes, even minor ones." [3] As I think this > makes perfectly sense, I like to propose two things that seem straight > forward to me: > > - We should not remove older releases from the AppStream data as already > suggested by Carl in a merge request [4]. > > - Also it would be convenient to add noteworthy changes to the metadata > together with the related code change. However at the moment for KDE Gear > the release is usually only added to the metadata a few days before > tagging. Would it be possible to add the next minor release to the release > branch right after the current one has been released and the next major > release to master ones the upcoming version has been branched? > > I belive this makes it easier for developers to contribute to the release > meta info and I hope it hence raises motivation to do so. My pessimistic opinion is that no one is going to add release notes, we've tried multiple ways to do it, even just asking people to add a keyword to the commit log if that commit log was release news worthy and no one did it past the first few weeks/months. It seems appstream has finally added the support (or maybe was there forever?), so my suggestion is that we just add an release+url entry pointing to https://kde.org/announcements/gear/x.y.z/ This way we don't have to do the work twice and has the added bonus of already translatable. Only "problem" is that maybe if we get too many people contributing their release news the announcements gets too long, but that'd be a nice problem to have. Cheers, Albert > > I am happy to hear your opionions, thoughts and concerns! > > Cheers, > Julius > > [1] https://docs.flathub.org/docs/for-app-authors/metainfo-guidelines > [2] https://apps.kde.org/ > [3] > https://docs.flathub.org/docs/for-app-authors/metainfo-guidelines/quality-g > uidelines/#release-notes [4] > https://invent.kde.org/sysadmin/appstream-metainfo-release-update/-/merge_r > equests/6 > > Julius Künzel > Volunteer KDE Developer, mainly hacking Kdenlive > KDE GitLab: www.invent.kde.org/jlskuz https://invent.kde.org/jlskuz > Matrix: @jlskuz:kde.org https://go.kde.org/matrix/#/@jlskuz:kde.org
KDE Gear 24.05 release schedule
Hi folks, This is the release schedule the release team agreed on https://community.kde.org/Schedules/KDE_Gear_24.05_Schedule Dependency freeze is in less than 4 weeks (April 18) and feature freeze one after that. Get your stuff ready! Cheers, Albert
KDE Gear projects with failing CI (release/24.02) (19 March 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. VERY BAD NEWS: * kimap made it to its 4th week with FreeBSD tests failing * I have disabled them * https://invent.kde.org/pim/kimap/-/commit/f5bc88bbe413feea1c81658579ae425729a39c9f VERY BAD NEWS #2: * neochat made it to the 4th week with craft_appimage_qt6_x86_64 failing * I have removed that build * https://invent.kde.org/network/neochat/-/commit/5ffe6ec59fc4ddb3e03409292bc6513cc39a9bd5 Good News: All CI are passing Cheers, Albert
KDE Gear projects with failing CI (master) (19 March 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 8 repositories got fixed Bad news: 1 repository still failing and 4 new repositories failing this week neochat - 2nd week * https://invent.kde.org/network/neochat/-/pipelines/637429 * craft_appimage_qt6_x86_64 fails kbruch - NEW * https://invent.kde.org/education/kbruch/-/pipelines/637302 * craft_macos_qt6_* fails kgeography - NEW * https://invent.kde.org/education/kgeography/-/pipelines/637304 * craft_macos_qt6_* fails kmplot - NEW * https://invent.kde.org/education/kmplot/-/pipelines/637305 * craft_macos_qt6_* fails kasts - NEW * https://invent.kde.org/multimedia/kasts/-/pipelines/637451 * flatpak fails * craft_windows_qt6_mingw64 fails Cheers, Albert
Re: Markdown Tools - Request for a Sponsor
El diumenge, 17 de març de 2024, a les 18:44:01 (CET), Igor Mironchik va escriure: > On 17.03.2024 18:54, Benson Muite wrote: > > Cannot answer whether the project will be accepted, am not a sponsor. > > It seems you are following the review process. > > Guys, could anybody explain me what does mean "Sponsor" in context of > KDE Incubator? It means a KDE developer that will guide you though the process and help you integrate into the KDE community. Cheers, Albert
KDE Frameworks with failing CI (kf5) (17 March 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: ALL repository are passing (2nd week in a row) Cheers, Albert P.S: Yes it-s still 17 March somewhere
KDE Frameworks with failing CI (master) (17 March 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 1 repository got fixed :) Bad news: 1 repository is still failing kpackage - 2nd week * https://invent.kde.org/frameworks/kpackage/-/pipelines/635146 * appstream check fails. Ben had some comments on March 10 report on this, please check them if you want to work on fixing this. Cheers, Albert
KDE Gear projects with failing CI (release/24.02) (12 March 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. VERY BAD NEWS: * Cantor made it to its 4th week with FreeBSD tests failing * I have disabled them * https://invent.kde.org/education/cantor/-/commit/5b2a8285e2f6ecac28f4ae07c602b9b8f8c7f7fa Good News: 6 failing repositories from previous report got fixed Bad news: 2 repositories are still failing and 2 new repositories started failing kimap - 3rd week * https://invent.kde.org/pim/kimap/-/pipelines/628890 * testsession fails on FreeBSD neochat - 3rd week * https://invent.kde.org/network/neochat/-/pipelines/628898 * craft build fails kdenlive - NEW * https://invent.kde.org/multimedia/kdenlive/-/pipelines/628930 * Qt6 code fails to compile akregator - NEW * https://invent.kde.org/pim/akregator/-/pipelines/628861 * appstreamtest fails Cheers, Albert
KDE Gear projects with failing CI (master) (12 March 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 6 repositories got fixed Bad news: 2 repository still failing and 7 new repositories failing this week filelight - 2nd week * https://invent.kde.org/utilities/filelight/-/pipelines/628855 * craft fails klickety - 2nd week * https://invent.kde.org/games/klickety/-/pipelines/628858 * appstreamtest fails kalgebra - NEW * https://invent.kde.org/education/kalgebra/-/pipelines/628851 * flatpak fails, needs libplasma kig - NEW * https://invent.kde.org/education/kig/-/pipelines/628852 * craft fails kdenlive - NEW * https://invent.kde.org/multimedia/kdenlive/-/pipelines/628926 * Qt6 code fails to compile akregator - NEW * https://invent.kde.org/pim/akregator/-/pipelines/628861 * appstreamtest fails neochat - NEW * https://invent.kde.org/network/neochat/-/pipelines/628957 * craft fails mimetreeparser - NEW * https://invent.kde.org/pim/mimetreeparser/-/pipelines/628865 * core-cryptohelpertest fails francis - NEW * https://invent.kde.org/utilities/francis/-/pipelines/628866 * reuse fails Cheers, Albert
KDE Frameworks with failing CI (kf5) (10 March 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: ALL repository are passing Cheers, Albert
KDE Frameworks with failing CI (master) (10 March 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Bad news: 1 repository is still failing and 1 new has started failing kimageformats - 3rd week * https://invent.kde.org/frameworks/kimageformats/-/pipelines/627271 * kimageformats-read-xcf fails in Linux CI * https://invent.kde.org/frameworks/kimageformats/-/merge_requests/211 fixes it but then breaks the BSD builder (because it is on an older Qt) Can we update Qt in the BSD builder to 6.6.2? kpackage - NEW * https://invent.kde.org/frameworks/kpackage/-/pipelines/627276 * appstream check fails Cheers, Albert
KDE Gear projects with failing CI (release/24.02) (5 March 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good News: 7 failing repositories from previous report got fixed Bad news: 3 repositories are still failing and 6 new repositories started failing cantor - 3rd week * https://invent.kde.org/education/cantor/-/pipelines/622239 * FreeBSD tests fail kimap - 2nd week * https://invent.kde.org/pim/kimap/-/pipelines/622338 * testsession fails on FreeBSD neochat - 2nd week * https://invent.kde.org/network/neochat/-/pipelines/622783 * craft builds fail kwave - 1st week * https://invent.kde.org/multimedia/kwave/-/pipelines/622278 * Linux build fails, complains that neither rsvg nor convert are installed kdebugsettings - 1st week * https://invent.kde.org/utilities/kdebugsettings/-/pipelines/622265 * appstreamtest fails pim-sieve-editor - 1st week * https://invent.kde.org/pim/pim-sieve-editor/-/pipelines/622340 * appstreamtest fails kbackup - 1st week * https://invent.kde.org/utilities/kbackup/-/pipelines/622344 * appstreamtest fails kweather - 1st week * https://invent.kde.org/utilities/kweather/-/pipelines/622781 * flatpak fails, needs libplasma kclock - 1st week * https://invent.kde.org/utilities/kclock/-/pipelines/622372 * The appstream job didn't get a runner, should this be removed? Cheers, Albert
KDE Gear projects with failing CI (master) (5 March 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 6 repositories got fixed Bad news: 1 repository still failing and 7 new repositories failing this week kate - 2nd week * https://invent.kde.org/utilities/kate/-/pipelines/622410 * craft fails filelight - 1st week * https://invent.kde.org/utilities/filelight/-/pipelines/622444 * craft fails. Is this actually a failure? Or did it just run out of "log"? kwave - 1st week * https://invent.kde.org/multimedia/kwave/-/pipelines/622156 * Linux build fails, complains that neither rsvg nor convert are installed klickety - 1st week * https://invent.kde.org/games/klickety/-/pipelines/622160 * appstreamtest fails pim -sieve-editor - 1st week * https://invent.kde.org/pim/pim-sieve-editor/-/pipelines/622188 * appstreamtest fails kbackup - 1st week * https://invent.kde.org/utilities/kbackup/-/pipelines/622198 * appstreamtest fails kclock - 1st week * https://invent.kde.org/utilities/kclock/-/pipelines/622448 * flatpak fails, needs libplasma kweather - 1st week * https://invent.kde.org/utilities/kweather/-/pipelines/622452 * flatpak fails, needs libplasma Cheers, Albert
Re: GSoC: Interested on "Port oss-fuzz tests to QT6"
El dilluns, 4 de març de 2024, a les 7:42:53 (CET), Khalid Masum va escriure: > Dear Albert Astals Cid, Hello > I am Khalid Masum, interested in doing Google Summer of Code with KDE. > The project idea: "Port oss-fuzz tests to QT6" is interesting to me and I > believe I will be able to do it next summer. > > About my knowledge prerequisite: have worked with build tools like Make, > CMake, Libtool, Autoconf, Autoconf etc before and I am positive I have > the necessary knowledge. > > It would be great if you could help me get started with this. Looking > forward to hearing from you. Have you read this? https://community.kde.org/GSoC What do you mean exactly with "help me get started with this"? Cheers, Albert P.S: Don't start an email with "Dear Albert Astals Cid" and then send it to a mailing list that has hundreds of people in it :) > > Best regards, > Khalid Masum
Re: Automation & Systematization sprint in Berlin in late April
El divendres, 1 de març de 2024, a les 5:48:44 (CET), Nate Graham va escriure: > Quick update on this. the dates are now locked in, but we're still > finalizing a venue in Berlin. More information will be provided as it > becomes available. > > Thanks for your patience here, everyone! What's the plan for travel support requests? Should we start filing requestsat https://reimbursements.kde.org ? Should requests include travel and hosting or hosting will be booked centrally? Cheers, Albert > > Nate > > On 1/31/24 16:26, Nate Graham wrote: > > Hello folks! > > > > I'd like to gauge interest in an in-person sprint supporting the > > Automation & Systematization goal. Right now we are targeting Berlin on > > April 19th - April 24th. KDE e.V. has budget available to help with > > travel and lodging costs. > > > > This will be a triple-threat sprint, with the Accessibility and > > Sustainability sprints co-located. People interested in multiple topics > > will be able to jump between them if they want. > > > > Topics for the Automation & Systematization sprint might include: > > - Writing tests > > - Fixing failing tests > > - Making tests mandatory to pass > > - Documenting how to write good tests > > - Updating outdated documentation > > - Transition documentation to code (e.g. making kdesrc-build or the new > > kde-builder tool do more itself, so we don't have to write so much about > > it in our documentation) > > - Make a push for enabling clang-format for more repos > > - Make a push to put release notes in AppStream metadata > > - Improve our AppStream CI job to require or recommend more things > > - Make a CI job to enforce as much of the onboarding/new repo checklist > > as possible, and make enabling it be a part of the process > > > > These are just ideas; the folks who attend will be the ones who guide > > the agenda. > > > > Let me know if you're interested so I can get a sense of the level of > > attendance! > > > > > > Nate
KDE Frameworks with failing CI (kf5) (3 March 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 1 repository was fixed Bad news: 1 NEW repository is failing syntax-highlighting * https://invent.kde.org/frameworks/syntax-highlighting/-/pipelines/620988 * testhighlighter_test and htmlhighlighter_test fail on Linux Cheers, Albert
KDE Frameworks with failing CI (master) (3 March 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 2 repositories has been fixed Bad news: 1 repository is still failing kimageformats - 2nd week * https://invent.kde.org/frameworks/kimageformats/-/pipelines/620978 * kimageformats-read-xcf fails in Linux CI Cheers, Albert
KDE Gear projects with failing CI (release/24.02) (28 February 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good News: 8 failing repositories from previous report got fixed Bad news: 1 repositories are still failing and 9 new repositories started failing cantor - 2nd week * https://invent.kde.org/education/cantor/-/pipelines/611889 * FreeBSD tests fail konversation - 1st week * https://invent.kde.org/network/konversation/-/pipelines/616933 * cmake fails to find dbus on Linux CI kimap - 1st week * https://invent.kde.org/pim/kimap/-/pipelines/616931 * testsession fails on FreeBSD Flatpak/Craft fails because of KF6 version mismatch * https://invent.kde.org/utilities/kate/-/pipelines/616925 * https://invent.kde.org/system/dolphin/-/pipelines/616926 * https://invent.kde.org/pim/itinerary/-/pipelines/616934 * https://invent.kde.org/multimedia/kasts/-/pipelines/616935 * https://invent.kde.org/network/neochat/-/pipelines/616936 * https://invent.kde.org/network/tokodon/-/pipelines/616937 * https://invent.kde.org/graphics/arianna/-/pipelines/616938 Cheers, Albert
KDE Gear projects with failing CI (master) (28 February 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. VERY BAD NEWS: * merkuro made it to its 4th week with FreeBSD tests failing * I have disabled them * https://invent.kde.org/pim/merkuro/-/commit/70fd49012912da95b4259edbfcd92582b0ed971e Good news: 5 repositories got fixed Bad news: 8 new repositories failing this week ark - 1st week * https://invent.kde.org/utilities/ark/-/pipelines/616910 * flatpak fails complaining about KF6BreezeIcons kate - 1st week * https://invent.kde.org/utilities/kate/-/pipelines/616904 * craft and flatpak fail. Seems like it's requesting a too new KF6, hopefully fixed once the release dust settles filelight - 1st week * https://invent.kde.org/utilities/filelight/-/pipelines/616911 * flatpak fails. Seems like it's requesting a too new KF6, hopefully fixed once the release dust settles elisa - 1st week * https://invent.kde.org/multimedia/elisa/-/pipelines/616916 * flatpak fails. Seems like it's requesting a too new KF6, hopefully fixed once the release dust settles kontrast - 1st week * https://invent.kde.org/accessibility/kontrast/-/pipelines/616917 * flatpak fails. Seems like it's requesting a too new KF6, hopefully fixed once the release dust settles itinerary - 1st week * https://invent.kde.org/pim/itinerary/-/pipelines/616919 * flatpak fails. Seems like it's requesting a too new KF6, hopefully fixed once the release dust settles telly-skout - 1st week * https://invent.kde.org/utilities/telly-skout/-/pipelines/616922 * flatpak fails. Seems like it's requesting a too new KF6, hopefully fixed once the release dust settles tokodon - 1st week * https://invent.kde.org/network/tokodon/-/pipelines/616923 * flatpak fails. Seems like it's requesting a too new KF6, hopefully fixed once the release dust settles Cheers, Albert
KDE Frameworks with failing CI (kf5) (25 February 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Bad news: 1 NEW repository is failing extra-cmake-modules - NEW * https://invent.kde.org/frameworks/extra-cmake-modules/-/pipelines/615165 * "This job is stuck because the project doesn't have any runners online assigned to it." for the "docs" job Cheers, Albert
KDE Frameworks with failing CI (master) (25 February 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 1 repository has been fixed Bad news: 3 NEW repository are failing extra-cmake-modules - NEW * https://invent.kde.org/frameworks/extra-cmake-modules/-/pipelines/615155 * "This job is stuck because the project doesn't have any runners online assigned to it." on the "docs" job kimageformats - NEW * https://invent.kde.org/frameworks/kimageformats/-/pipelines/615158 * kimageformats-read-xcf fails in Linux CI kuserfeedback - NEW * https://invent.kde.org/frameworks/kuserfeedback/-/pipelines/615161 * flatpak fails for versioning (why does this even have a flatpak? that's the user case for a kuserfeedback flatpak?) Cheers, Albert
Re: Post-MegaRelease projects
El divendres, 23 de febrer de 2024, a les 11:12:16 (CET), Sune Vuorela va escriure: > On 2024-02-22, Nate Graham wrote: > > I've started pondering post-megarelease projects. We've spent so long on > > porting and bugfixing that I think it might be useful to shift gears to > > feature work, and I'd like to brainstorm potential large-scale projects > > and gauge the level of interest in putting resources into them soon. > > A bit more from the devops end that I'd love to see people tackle: > > - Ensure frameworks and app unit tests interacting with windows can run >on Windows. >More details: The following fails on our windows CI >https://invent.kde.org/sune/windows-test-thingie/-/blob/master/main.cpp >I find it weird that we are spending resources on putting things in >the windows store and making apps available on windows, but we can't >actually have passing tests in our CI. > > - Find a way to run unit tests on android CI. > > - Make autotests guarding on all our CI's. > > - Clazy and clang-tidy and cppcheck on all our repositories in CI And qmllint for the apps that use QML (dreaming is free, right?) Cheers, Albert > > /Sune
KDE Gear projects with failing CI (master) (20 February 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. VERY BAD NEWS: * Cantor made it to its 4th week with FreeBSD tests failing * I have disabled them * https://invent.kde.org/education/cantor/-/commit/0f94f381bda4d8f7f52a432d0a846c2ca6bee1e8 Good news: 8 repositories got fixed Bad news: 2 repo still failing and 5 new this week ark - 3rd week * https://invent.kde.org/utilities/ark/-/pipelines/611869 * tests fail on FreeBSD merkuro - 3rd week * https://invent.kde.org/pim/merkuro/-/pipelines/611879 * tests fail on FreeBSD korganizer - 1st week * https://invent.kde.org/pim/korganizer/-/pipelines/611877 * Fails to compile, complains about Akonadi::CollectionCalendar constructor klickety - 1st week * https://invent.kde.org/games/klickety/-/pipelines/611870 * appstreamtest fails on FreeBSD okular - 1st week * https://invent.kde.org/graphics/okular/-/pipelines/611868 * Android fails to compile * It works for me locally so help needed keysmith - 1st week * https://invent.kde.org/utilities/keysmith/-/pipelines/611882 * craft android builds fail kbruch - 1st week * https://invent.kde.org/education/kbruch/-/pipelines/611867 * craft window build fails, but i don't see any error? Cheers, Albert
KDE Gear projects with failing CI (release/24.02) (20 February 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good News: 11 failing repositories from previous report got fixed Bad news: 3 repositories are still failing and 6 new repositories started failing dolphin - 1st week (was failing with a different error) * https://invent.kde.org/system/dolphin/-/pipelines/611888 * flatpak fails to compile ark - 3rd week * https://invent.kde.org/utilities/ark/-/pipelines/611892 * FreeBSD tests failed kmag - 2nd week * https://invent.kde.org/accessibility/kmag/-/pipelines/611893 * flatpak fails in icon-not-found korganizer - 1st week * https://invent.kde.org/pim/korganizer/-/pipelines/611898 * Linux build has linking problem cantor - 1st week * https://invent.kde.org/education/cantor/-/pipelines/611889 * FreeBSD tests fail okular - 1st week * https://invent.kde.org/graphics/okular/-/pipelines/611891 * Android fails to compile * It works for me locally so help needed keysmith - 1st week * https://invent.kde.org/utilities/keysmith/-/pipelines/611904 * craft android builds fail klickety - 1st week * https://invent.kde.org/games/klickety/-/pipelines/611894 * appstream test fails in FreeBSD arianna - 1st week * https://invent.kde.org/graphics/arianna/-/pipelines/611906 * flatpak build fails (same error as dolphin) Cheers, Albert
Re: Help with installing KArchive
El diumenge, 18 de febrer de 2024, a les 20:30:57 (CET), Eric Ribble va escriure: > I am a new user of Qt (using version 6.6) and Qt Creator I would like to > use KArchive to extract all folders and files from a zip file. I found the > example "karchive/examples/unzipper/main.cpp" source code. However, I > don't know how to download and install KArchive. I added the following to > my project's "CMakeLists.txt" as described on the web > page https://marketplace.qt.io/pages/karchiveinstructionspage : > find_package(KF5Archive) Your are trying to use KF5 KArchive in a Qt6 application. You can't do that, KF5 needs Qt5. You can try using the KF6 beta release of KArchive or wait until we release KF6 at the end of the month. > target_link_libraries(Example4 KF5::Archive) > Attached is my "CMakeLists.txt" file and "Main.cpp" file. > In my "Main.cpp" the syntax-checker indicates that it can't find "kzip.h" > (probably because I don't know how to download/install it). Here is a > screenshot after trying to build: > > Please advise on how to properly download/install KArchive so that this > simple program will build. Thanks for your help! Eric Ribble This is not a KDE question, this is a "I understand how compiling things with cmake works" question. The usual answer is that you run cmake && ninja && ninja install (replace ninja by make or if you really don't have any of those by cmake commands that will build and install) in karchive and then point the cmake of your application to that folder you installed karchive, either via a command line option or by hardcoding the path in the CMakeLists.txt file. But Windows developers don't like that so you may have luck doing a cmake submodule thing, but then you're on your own, that's generally not how we use libraries. Cheers, Albert
KDE Frameworks with failing CI (kf5) (19 February 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: All repositories are passing Cheers, Albert
KDE Frameworks with failing CI (master) (19 February 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 1 repository has been fixed Bad news: 1 NEW repository is failing kconfig - NEW * https://invent.kde.org/frameworks/kconfig/-/pipelines/611171 * kconfigcore-kconfigtest is failing on Windows Cheers, Albert
KDE Frameworks with failing CI (kf5) (11 February 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 1 repository was fixed Bad news: 2 repositories are still failing baloo - 3rd week * https://invent.kde.org/frameworks/baloo/-/pipelines/604706 * Tests fail on FreeBSD kfilemetadata - 3rd week * https://invent.kde.org/frameworks/kfilemetadata/-/pipelines/604707 * Tests fail on FreeBSD * Should we backport the fix made in KF6? Christoph? Cheers, Albert
Re: KDE Frameworks with failing CI (master) (11 February 2024)
Date in the previous message was wrong, sorry ^_^ El diumenge, 11 de febrer de 2024, a les 1:06:53 (CET), Albert Astals Cid va escriure: > Please work on fixing them, otherwise i will remove the failing CI jobs on > their 4th failing week, it is very important that CI is passing for > multiple reasons. > > Good news: 4 repositories have been fixed > > Bad news: 1 repository is still failing > > > kdav - 2nd week > * https://invent.kde.org/frameworks/kdav/-/pipelines/604710 > * davcollectionsmultifetchjobtest fails both in Linux and FreeBSD >* Volker identified a MR that broke it, but needs acting on. Do I > remember that Nico is on holiday? May need someone else to have a look at. > > > Cheers, > Albert
KDE Frameworks with failing CI (master) (4 February 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 4 repositories have been fixed Bad news: 1 repository is still failing kdav - 2nd week * https://invent.kde.org/frameworks/kdav/-/pipelines/604710 * davcollectionsmultifetchjobtest fails both in Linux and FreeBSD * Volker identified a MR that broke it, but needs acting on. Do I remember that Nico is on holiday? May need someone else to have a look at. Cheers, Albert
KDE Gear projects with failing CI (release/23.08) (6 February 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 3 repositories that were failing are fixed :) Bad news: 5 repositories are still failing and 1 new repository is failing gwenview - 3rd week * https://invent.kde.org/graphics/gwenview/-/pipelines/601251 * FreeBSD is missing kImageAnnotator kio-extras - 3rd week * https://invent.kde.org/network/kio-extras/-/pipelines/601283 * thumbnailtest is failing in FreeBSD ark - 3rd week * https://invent.kde.org/utilities/ark/-/pipelines/601257 * kerfuffle-extracttest fails on FreeBSD cantor - 2nd week * https://invent.kde.org/education/cantor/-/pipelines/601240 * testmaxima fails on FreeBSD klickety - 2nd week * https://invent.kde.org/games/klickety/-/pipelines/601267 * appstreamtest fails itinerary - NEW * https://invent.kde.org/pim/itinerary/-/pipelines/601311 * googleplay_apks_qt515 fails Cheers, Albert
KDE Gear projects with failing CI (release/24.02) (6 February 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good News: 7 failing repositories from previous report got fixed Bad news: 3 repositories are still failing and 11 new repositories started failing gwenview - 3rd week * https://invent.kde.org/graphics/gwenview/-/pipelines/601196 * cfitsio SHA doesn't match on flatpak build dolphin - 2nd week * https://invent.kde.org/system/dolphin/-/pipelines/601190 * flatpak fails in icon-not-found ark - 2nd week * https://invent.kde.org/utilities/ark/-/pipelines/601200 * FreeBSD tests failed kdialog - NEW * https://invent.kde.org/utilities/kdialog/-/pipelines/601189 * flatpak fails in icon-not-found kmag - NEW * https://invent.kde.org/accessibility/kmag/-/pipelines/601207 * flatpak fails in icon-not-found kbackup - NEW * https://invent.kde.org/utilities/kbackup/-/pipelines/601223 * flatpak fails in icon-not-found kirigami-gallery - NEW * https://invent.kde.org/sdk/kirigami-gallery/-/pipelines/601366 * flatpak fails in icon-not-found kbounce - NEW * https://invent.kde.org/games/kbounce/-/pipelines/601210 * flatpak fails because code requires an unreleased ECM kdiamond - NEW * https://invent.kde.org/games/kdiamond/-/pipelines/601211 * flatpak fails because code requires an unreleased ECM kmahjongg - NEW * https://invent.kde.org/games/kmahjongg/-/pipelines/601212 * flatpak fails because code requires an unreleased ECM kpat - NEW * https://invent.kde.org/games/kpat/-/pipelines/601213 * flatpak fails because code requires an unreleased ECM ksudoku - NEW * https://invent.kde.org/games/ksudoku/-/pipelines/601215 * flatpak fails because code requires an unreleased ECM kubrick - NEW * https://invent.kde.org/games/kubrick/-/pipelines/601216 * flatpak fails because code requires an unreleased ECM palapeli - NEW * https://invent.kde.org/games/palapeli/-/pipelines/601217 * flatpak fails because code requires an unreleased ECM Cheers, Albert