Re: KDE Gear projects with failing CI (master + stable) (9 June 2026)
Volker Krause <[email protected]> Sun, 14 Jun 2026 16:13:29 +0200
| Newsgroups | gmane.comp.kde.devel.general |
|---|---|
| Organization | KDE |
| Message-ID | <[email protected]> |
On Donnerstag, 11. Juni 2026 09:27:44 Mitteleuropäische Sommerzeit Ben Cooksley wrote: > On Thu, Jun 11, 2026 at 3:53 AM Ingo Klöcker <[email protected]> wrote: > > On Mittwoch, 10. Juni 2026 00:19:41 Mitteleuropäische Sommerzeit Albert > > Astals > > > > Cid wrote: > > > Craft jobs failing because of kmime - NEW > > > > > > * https://invent.kde.org/pim/akregator/-/pipelines/1259947 > > > * https://invent.kde.org/pim/grantlee-editor/-/pipelines/1259948 > > > * https://invent.kde.org/pim/kalarm/-/pipelines/1259949 > > > * https://invent.kde.org/pim/kmail-account-wizard/-/pipelines/1259961 > > > * https://invent.kde.org/pim/kontact/-/pipelines/1262245 > > > * https://invent.kde.org/pim/pim-sieve-editor/-/pipelines/1259959 (This > > > > > > also has a flatpak failing in kmime) > > > > Collateral damage of the migration of kmime to KF. The PIM projects > > request > > kmime master (actually pim/* master) and kmime master (now being a KF) > > requires unreleased ECM 6.27.0 (as all other KFs do). The problem will be > > fixed > > when Craft has been switched to KF 6.27 (which is expected to be released > > on > > Friday this week). I don't think it's worth doing anything now. With KF 6.27 having landed in Craft now, this should help: https://invent.kde.org/packaging/craft-blueprints-kde/-/merge_requests/1558 We'll see the same issue with Flatpak in some form as well, the ultimate fix is getting KF 6.27 with KMime into the runtime there. > Is it expected that PIM projects are going to continue to request KMime > master? No. Part of the motivation for this is to reduce the amount of master dependencies. Regards, Volker
signature.asc
(application/pgp-signature, 232 B)
-----BEGIN PGP SIGNATURE----- iHkEABECADkWIQQAnu3FVHA48KjZ07R/lszWTRLSRwUCai63CRsUgAAAAAAEAA5t YW51MiwyLjUrMS4xMSwyLDIACgkQf5bM1k0S0kf0dACfeClWo+HnTYELqe1Q+ey2 PFDXVkUAn1Yv07SeFX1h18Y+emBojMXZMoA+ =bjZP -----END PGP SIGNATURE-----