--nextPart22236130.EfDdHjke4D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; protected-headers="v1"
From: Volker Krause <vkrause@kde.org>
To: kde-frameworks-devel@kde.org
Subject: Re: KDE Frameworks with failing CI (kf5) (24 March 2024)
Date: Tue, 26 Mar 2024 17:54:59 +0100
Message-ID: <1967426.PYKUYFuaPT@vkpc5>
Organization: KDE
In-Reply-To: <3279694.zg9BAefHg6@xps15>
MIME-Version: 1.0

On Dienstag, 26. M=E4rz 2024 00:42:53 CET Albert Astals Cid wrote:
> El dilluns, 25 de mar=E7 de 2024, a les 18:03:27 (CET), Volker Krause va
>=20
> escriure:
> > On Sonntag, 24. M=E4rz 2024 23:14:12 CET Albert Astals Cid wrote:
> > > Please work on fixing them, otherwise i will remove the failing CI jo=
bs
> > > on
> > > their 4th failing week, it is very important that CI is passing for
> > > multiple reasons.
> > >=20
> > > Bad news: 2 repositories have started failing
> > >=20
> > > kirigami - NEW
> > >=20
> > >  * https://invent.kde.org/frameworks/kirigami/-/jobs/1679118
> > > =20
> > >   * Android build fails
> > >  =20
> > >    * Something qt related needs a rebuild?
> >=20
> > Yep, looks like a version mix due to the patch collection rebase.
>=20
> But why has this happened? I mean how is it that some Qt has different th=
an
> some other Qt? Was there a rebuild of Android Qt while i was doing the
> rebase?
>=20
> If I understand that right there's a QtSvg is 5.15.13 but QtWidgets is on=
ly
> 5.15.12?

Not sure what caused it specifically here, but this happens as soon as anyt=
hing=20
triggers a rebuild of a part of Qt for whatever reason. That part is then=20
taken from the kde/5.15 head, which is newer than the rest of Qt in the cac=
he.

The effect used to spread/worsen over time as more things in the cache beco=
me=20
outdated (not sure if that got better or worse with the significantly reduc=
ed=20
Qt5-related activity nowadays).

> > 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.
> >=20
> > 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?
>=20
> If we're saying Kirigami works on Android ideally we should keep a CI.

Pinning the Qt5 version might be a good compromise then? Keeping Kirigami=20
working in a fixed environment should be fine, but dealing with the movemen=
t in=20
Qt, Android and Craft for one major version is hard enough already.

Regards,
Volker

--nextPart22236130.EfDdHjke4D
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQQAnu3FVHA48KjZ07R/lszWTRLSRwUCZgL94wAKCRB/lszWTRLS
R7CLAKCyrPPyAWWxI97WNn2sPLKJDeki9gCZAYTyQKuKDF/iKA55Sfj502zEBy4=
=jYqZ
-----END PGP SIGNATURE-----

--nextPart22236130.EfDdHjke4D--