Re: KDE Gear projects with failing CI (release/23.08) (23 January 2024)

2024-01-25 Thread Ingo Klöcker
On Mittwoch, 24. Januar 2024 23:03:11 CET Albert Astals Cid wrote:
> El dimecres, 24 de gener de 2024, a les 8:53:45 (CET), Ingo Klöcker va
> escriure:
> > On Dienstag, 23. Januar 2024 23:36:21 CET Albert Astals Cid wrote:
> > > okular - NEW
> > > 
> > >  * https://invent.kde.org/graphics/okular/-/pipelines/589489
> > >  
> > >   * craft android builds are failing
> > 
> > Looks like perl-modules/xml-parser tries to link against the ARM build of
> > libexpat.
> > /usr/bin/ld: skipping incompatible
> > /builds/graphics/okular/android-arm-clang/ lib/libexpat.so when searching
> > for -lexpat
> > Is perl-modules/xml-parser used by the Android build or on the host as
> > build tool?
> 
> I don't know why xml-parser is being pulled for Okular, does craft have some
> sort of "why is this thing being compiled while compiling X" command?

I didn't see anything obvious while looking at craft.py.

Comparing the last successful build
https://invent.kde.org/graphics/okular/-/jobs/1496247#L219
with the failing build
https://invent.kde.org/graphics/okular/-/jobs/1535063#L218
one sees a few new dependencies:
'libs/expat', 'perl-modules/xml-parser', 'dev-utils/intltool', 'dev-utils/
yasm', 'libs/aom', 'python-modules/meson', 'libs/dav1d', 'libs/libavif'

Looks like libavif is a new dependency of kimageformats and it depends on aom 
which needs yasm and perl. And yasm needs intltool which needs xml-parser. I 
think the easiest fix is to disable the libavif dependency in kimageformats for 
Android for now.

https://invent.kde.org/packaging/craft-blueprints-kde/-/merge_requests/773

Regards,
Ingo

signature.asc
Description: This is a digitally signed message part.


Re: KDE Gear projects with failing CI (master) (23 January 2024)

2024-01-25 Thread Ben Cooksley
On Thu, Jan 25, 2024 at 6:04 AM Volker Krause  wrote:

> On Dienstag, 23. Januar 2024 21:35:56 CET Albert Astals Cid 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: 5 repositories got fixed
> >
> > Bad news: 2 repo still failing (1 with a different failure) and *10* new
> > this week
>
> KMime is fixed in all branches now, the test regression in akonadi-search
> in
> master is also fixed, but the general FreeBSD fallout breaking MySQL and
> PostgreSQL Akonadi tests remains.
>

I'll be performing a rebuild of the FreeBSD images shortly following a
patch Tobias has provided to add two additional packages to ensure QtSQL
has the necessary modules available.
That will fix the MySQL tests.

Postgres not working is a known issue with FreeBSD Jails i'm afraid, as by
default FreeBSD disables Sys V IPC support within Jails (as it can't be
namespaced on FreeBSD).
While for conventional FreeBSD Jails this can be re-enabled, i'm not sure
how well that interfaces with the ocijail component used by Podman to
launch our containers.


>
> Regards,
> Volker


Cheers,
Ben


Re: KDE Gear projects with failing CI (master) (23 January 2024)

2024-01-25 Thread Arjen Hiemstra
On Tuesday, 23 January 2024 22:24:45 CET Tobias C. Berner wrote:
> Moin moin
> 
> I'll take a look at krdc -- the main issue there is that cmake does
> not pick up the cmake files from the location they get installed to by
> the freerdp2 package.
> I hot-fixed that on the old builders, but not in the package. An
> update to appstream should also be feasible.


FreeRDP was in fact also missing from the list of packages to install to the 
container image. I made a MR to fix that which has been merged so that is 
resolved. What kind of changes did you have to make to make CMake pick up that 
install?

- Arjen

> 
> I'll try to get to both tomorrow.
> 
> 
> mfg Tobias
> 
> On Tue, 23 Jan 2024 at 22:11, Ben Cooksley  wrote:
> > On Wed, Jan 24, 2024 at 9:36 AM Albert Astals Cid  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: 5 repositories got fixed
> >> 
> >> Bad news: 2 repo still failing (1 with a different failure) and *10* new
> >> this week
> >> 
> >> 
> >> krecorder - 2nd week
> >> 
> >>  * https://invent.kde.org/utilities/krecorder/-/pipelines/589469
> >>  
> >>   * All the craft_android builds are broken
> > 
> > Looks like kirigami-addons is doing something the CMake in the Android
> > image doesn't like.
> > 
> > Interesting - perhaps the CMake (which is built from source I think)
> > version in the Android image needs updating?> 
> >> krdc - different issue
> >> 
> >>  * https://invent.kde.org/network/krdc/-/pipelines/589457
> >>  
> >>   * FreeBSD builder is missing dependencies
> > 
> > KRDC developers should submit a MR to sysadmin/ci-images for the two
> > FreeBSD 14 images please.> 
> >> akonadi-serach - NEW
> >> 
> >>  * https://invent.kde.org/pim/akonadi-search/-/pipelines/589458
> >>  
> >>   * multiple tests failing
> >> 
> >> kmail - NEW
> >> 
> >>  * https://invent.kde.org/pim/kmail/-/pipelines/589460
> >>  
> >>   * appstreamtest fails on FreeBSD
> >> 
> >> kasts - NEW
> >> 
> >>  * https://invent.kde.org/multimedia/kasts/-/pipelines/589466
> >>  
> >>   * appstreamtest fails on FreeBSD
> >> 
> >> keysmith - NEW
> >> 
> >>  * https://invent.kde.org/utilities/keysmith/-/pipelines/589467
> >>  
> >>   * appstreamtest fails on FreeBSD
> >> 
> >> neochat - NEW
> >> 
> >>  * https://invent.kde.org/network/neochat/-/pipelines/589470
> >>  
> >>   * appstreamtest fails on FreeBSD
> >> 
> >> cantor - NEW
> >> 
> >>  * https://invent.kde.org/education/cantor/-/pipelines/589452
> >>  
> >>   * testmaxima fails on FreeBSD
> > 
> > These appstream failures are all the fault of the Appstream developers for
> > deprecating something with too high a severity level. While we do need to
> > fix it the issue is not critical yet.
> > 
> > Tobias - can we please update to 1.0.1 in FreeBSD (See
> > https://github.com/ximion/appstream/blob/main/NEWS#L12)?
> > 
> > For Linux this does not appear as we are pinned to a self-compiled version
> > in the image that is patched to align with the Flatpak requirements which
> > are stricter in some areas (because appstream politics *sigh*)> 
> >> konsole - NEW
> >> 
> >>  * https://invent.kde.org/utilities/konsole/-/pipelines/589450
> >>  
> >>   * flatpak build complains about icon-not-found
> >> 
> >> dolphin - NEW
> >> 
> >>  * https://invent.kde.org/system/dolphin/-/pipelines/589451
> >>  
> >>   * flatpak build complains about icon-not-found
> > 
> > Both likely a case of Flatpak becoming more strict, as the version lock we
> > had in place due to Docker incompatibilities was lifted following the
> > move to Podman.> 
> >> gwenview - NEW
> >> 
> >>  * https://invent.kde.org/graphics/gwenview/-/pipelines/589454
> >>  
> >>   * cfitsio SHA doesn't match on flatpak build
> >> 
> >> kipi-plugins - NEW
> >> 
> >>  * https://invent.kde.org/graphics/kipi-plugins/-/pipelines/589461
> >>  
> >>   * CI fails to find libmediawiki
> > 
> > Do we know how much this is still used, and whether KIPI can be retired?
> > 
> >> Cheers,
> >> 
> >>   Albert
> > 
> > Cheers,
> > Ben