Closed Viliansh closed 7 months ago
Build 83384 successful To test this build, install it from the testing repository:
flatpak install --user https://dl.flathub.org/build-repo/66019/sh.ppy.osu.flatpakref
it don't update the outdated modules for the build, that's not good, because i cant see it the pattern for the url for the libevdev is correct, it only shows that's outdated :/
Started test build 83406
ok, now, i'm more confident it's working, it gave the correct SHA and version when running flatpak-external-data-checker locally
Build 83406 successful To test this build, install it from the testing repository:
flatpak install --user https://dl.flathub.org/build-repo/66040/sh.ppy.osu.flatpakref
Started test build 88579
Build 88579 successful To test this build, install it from the testing repository:
flatpak install --user https://dl.flathub.org/build-repo/71251/sh.ppy.osu.flatpakref
Can you explain what this is doing in the OP or somewhere?
The osu! flatpak vendors in libevdev
at version 1.12.1 currently, with flathub/flatpak-external-data-checker and this added data updates to it can be checked which it does by scraping https://www.freedesktop.org/software/libevdev/ with the pattern specified and reports anything new found so it can be updated at times instead of forgotten about.
After this is merged since the repo already appears to be using flatpak-external-data-checker
an update of libevdev from 1.12.1 to 1.13.1 should be included alongside the osu AppImage next time if I understand it correctly similar to https://github.com/flathub/net.rpcs3.RPCS3/commit/7aa20cc263c518a543175c52225b3b25cd1d7112.
Fwiw the RPCS3 fatpak uses a different approach but both should be ok really https://github.com/flathub/net.rpcs3.RPCS3/blob/cf2610f/net.rpcs3.RPCS3.yaml#L42-L46
Thanks
Started test build 89817
Build 89817 successful To test this build, install it from the testing repository:
flatpak install --user https://dl.flathub.org/build-repo/72497/sh.ppy.osu.flatpakref
Started test build 83384