This is important as the format will be used more when lazer beatmap
submission comes online, and its stability is a useful property for
that.
Included archive contains an `.osu` with a few fractional-millisecond
timing points and objects, as well as a multi-segment-type slider. That
should cover the range of all possible modifications that the
compatibility exporter currently performs.
Didn't really work to fix these tests due to the sticky nature of the
failure. Also I can no longer reproduce locally, so the hope is that
these are fixed by https://github.com/ppy/osu/pull/30634.
Because even if you somehow bypass the breakage that bricks your install
by installing the missing libssl-1.0 or whatever
(https://github.com/ppy/osu/issues/30648#issuecomment-2478856055),
there's another brick upstream
(https://github.com/ppy/osu/issues/30648#issuecomment-2478926177,
https://github.com/velopack/velopack/issues/355).
Can we even downgrade like this? No idea. How does one test this? No
idea. At this point I am like a headless chicken, screaming into the
void trying to restore any semblance of order into my crumbling
universe.
If this is tried and linux is still broken with the libssl garbage, then
the `osulazer-2024.1115.1-linux-x64-*.nupkg` assets should be pulled
from the release, which should be enough to stop the game from
auto-updating. Maybe the appimage itself can stay up and people can
upgrade manually if they so desire. Or maybe not. Who knows.