KDE Gear projects with failing CI (master) (21 January 2025)

Ben Cooksley bcooksley at kde.org
Wed Jan 22 17:52:46 GMT 2025


On Thu, Jan 23, 2025 at 5:49 AM Volker Krause <vkrause at kde.org> wrote:

> On Dienstag, 21. Januar 2025 23:11:56 Mitteleuropäische Normalzeit Albert
> Astals Cid wrote:
> > neochat - NEW
> >  * https://invent.kde.org/network/neochat/-/pipelines/869365
> >   * flatpak build fails
>
> Same as https://invent.kde.org/network/neochat/-/merge_requests/2127 I
> guess,
> looks like an API change in libQuotient with the corresponding version
> change
> still pending (ie. a similar problem we occasionally hit with Poppler).
>
> The quick solution for this would probably be (temporarily) switching
> Flatpak
> to the latest release of libQuotient. The IMHO proper solution would be to
> have version bumps at the beginning of a development cycle that changes
> API.
>

This also raises another question though - should we be strongly
discouraging use of heavily moving targets like upstream dev / master
branches and instead favouring the use of stable branches?
Not really ideal if upstream can essentially break our builds without us
doing anything.


>
> Regards,
> Volker


Cheers,
Ben
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-devel/attachments/20250123/dfc140e4/attachment.htm>


More information about the kde-devel mailing list