mirror of
https://github.com/ppy/osu.git
synced 2025-01-18 10:53:21 +08:00
4b69c178c2
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. |
||
|---|---|---|
| .. | ||
| LegacyIpc | ||
| Performance | ||
| Properties | ||
| Security | ||
| Updater | ||
| Windows | ||
| beatmap.ico | ||
| DiscordRichPresence.cs | ||
| lazer.ico | ||
| NVAPI.cs | ||
| osu!.res | ||
| osu.Desktop.csproj | ||
| osu.nuspec | ||
| OsuGameDesktop.cs | ||
| Program.cs | ||
| SDL2BatteryInfo.cs | ||
| SDL3BatteryInfo.cs | ||