On Fri, May 24, 2024 at 4:13 AM Volker Krause <vkra...@kde.org> wrote:
> On Mittwoch, 22. Mai 2024 10:27:07 CEST Ben Cooksley wrote: > > On Wed, May 22, 2024 at 9:24 AM Albert Astals Cid <aa...@kde.org> 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. > > > > > > 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. > > > > Looks like kio-gdrive needs to drop the support it has for Qt 5? > > Can't really see another path forward as libkgapi has no support for Qt 5 > > anymore. > > > > This is alas one of those very difficult to solve issues, especially when > > semi-leaf projects like libkgapi are used more widely. > > Would it work to have a kf5 branch rule for libkgapi pointing to the last > branch with Qt 5 support (and similar for all its dependencies)? Unfortunately not possible i'm afraid - as release/23.08 is no longer supported (as no further releases are being made). I therefore terminated all CI support for that branch to ensure that any issues like this one were forced to the surface. The dependency chain is also @same as both are part of KDE Gear so from a technical perspective that doesn't work either. >From a practical perspective, i'm not sure you can really release something as part of a bundle that needs something from an older release of that same bundle in order to build... The only fix is to either drop Qt 5 support from kio-gdrive, or to restore Qt 5 support to libkgapi. > > > Regards, > Volker > Cheers, Ben
