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
On Tuesday, 26 March 2024 17:39:25 CET, Volker Krause wrote: 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: ... 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. No worries, I didn't mean this as an accusation. Just a hint for future (possible mass) additions. 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? Indeed, we would just loose the conveniently timed rebuild, which seems acceptable and no problem at all with rather active projects. Regards, Heiko
