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

[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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-devel/attachments/20240125/53fc94d5/attachment.sig>