Bump runtime to 42 and oomox to 1.14

[bbhtt]

• Update resvg to 0.23.0, add cargo manifest and add new build commands
• Update Pillow to 9.2.0, haishoku to 1.1.8
• Add pystache and pyyaml for Base16 format
• Update libsass to 3.6.1 and sassc to 3.6.1
• Update ImageMagick to 7.1.0.43
• Update oomox to 1.14

This built and ran fine locally but I don't use the app, so needs testing to see if it still works.

It ran fine in native wayland, so I added support for it. If there are issues or wayland is unsupported entirely I can drop that change. :)

Ping @actionless, please review when you have time, thanks!

[bbhtt]

com.github.themix_project.Oomox/flathub.json

Line 2 in 95182c1

"skip-appstream-check": true

Is skipping appstream validation still needed? There's no reason specified on why it is being skipped and the build logs from that time are gone

Running flatpak run --env=G_DEBUG=fatal-criticals org.freedesktop.appstream-glib validate *.xml locally, it passes. So I'm removing it. If there are issues I'll re-add.

[bbhtt]

bot, build

[flathubbot]

Queued test build for com.github.themix_project.Oomox.

[flathubbot]

Started test build 101336

[flathubbot]

Build 101336 failed

[actionless]

if i understood the log right, it's failing on this:

appstream-compose --prefix=/srv/buildbot/worker/build-x86_64/build/.flatpak-builder/rofiles/rofiles-FbyLAP/files --origin=flatpak --basename=com.github.themix_project.Oomox com.github.themix_project.Oomox

with many errors, main of which probably:

cannot open display: 

[actionless]

mb return back that appstream check thing

[flathubbot]

Started test build 101362

[hfiguiere]

if i understood the log right, it's failing on this:

appstream-compose --prefix=/srv/buildbot/worker/build-x86_64/build/.flatpak-builder/rofiles/rofiles-FbyLAP/files --origin=flatpak --basename=com.github.themix_project.Oomox com.github.themix_project.Oomox

with many errors, main of which probably:

cannot open display: 

these are harmless.

[hfiguiere]

I'm pretty this part:

                "mkdir -p /app/usr/share/",
                "ln -s /app/share/applications /app/usr/share/applications",
                "ln -s /app/share/appdata /app/usr/share/appdata",
                "ln -s /app/share/icons /app/usr/share/icons"

is part of the problem. /app/usr trigger bugs in appstream and has no reason to exist.

[actionless]

@hfiguiere i've tried to remove it - let's see

[actionless]

or mb actually this is the problem, not symlinks:

Error loading desktop file: Failed to find icon: Failed to find icon com.github.themix_project.Oomox
Error: ERROR: appstream-compose failed: Child process exited with code 1

but let's see if rebuilding without symlinks would help

[actionless]

bot, build

[flathubbot]

Queued test build for com.github.themix_project.Oomox.

[flathubbot]

Started test build 101365

[actionless]

thanks @hfiguiere it apparently helped

fixed

[actionless]

please fix sass related libs to aforementioned versions and check if everything still works

[hfiguiere]

thanks @hfiguiere it apparently helped

as I said, it triggers unfixed bugs in appstream-glib, and that's the root of the problems with icons when they actually are installed.
In general /app/usr remain a bad idea, and is totally off the filesystem standards. (/app/opt as well btw)

[flathubbot]

Build 101362 failed

[flathubbot]

Build 101365 successful
To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/99087/com.github.themix_project.Oomox.flatpakref

[flathubbot]

Started test build 101374

[bbhtt]

I squashed the i386 commits and cleaned up the remaining i386 build options. Hope you don't mind.

Thank you, both, for the reviews and suggestions!

[actionless]

thanks! please let me know if it will work for you after the build

[flathubbot]

Build 101374 successful
To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/99096/com.github.themix_project.Oomox.flatpakref

[bbhtt]

Hi, I've tested it out with the bluloco theme, it can export those to ~/.themes and the icon theme in ~/.icons. Let me know if this is fine.

[actionless]

thanks @bbhtt let's see :)