Arch Linux User Repository

@amingirl If you want to use a custom Wine build, you can just prepend the PATH environment variable with the custom Wine's path.

But I have written this script with the idea of not to directly edit /usr/bin/osu-stable, but to create your own script if you want to override any of the value.

This is my ~/bin/osu-stable file (/usr/bin/osu-stable is unmodified, and ~/bin is added to my PATH)

#!/bin/sh
export PATH="${HOME}/build/wine:${PATH}"
export OSU_STABLE_DATA_DIRECTORY="${HOME}/osuStableDir"
/usr/bin/osu-stable "$@"

williewillus, that GitHub repo you linked is for lazer, this package is for stable. If lazer is the version you want, you should use the osu-lazer package.

The problem here with the SHA's is that the installer download link just points directly at whatever happens to be the latest release on the mirror at the moment, which is not guaranteed to match pkgver at all.

It should really point to a fixed URL such as the GitHub release, like so:

diff --git a/PKGBUILD b/PKGBUILD
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,8 +1,9 @@
 # Maintainer: Rodney van den Velden <rodney@dfagaming.nl>

 pkgname='osu'
-pkgver='20240607'
+pkgver='2025.225.0'
 pkgrel=1
+epoch=1
 pkgdesc='A free-to-win rhythm game'
 _terms_commit='b8a98fb740ed8251958f16d719138e96afa6e299'
 arch=('i686' 'x86_64')
@@ -11,12 +12,12 @@
 depends=('wine' 'winetricks' 'lib32-gnutls' 'lib32-libxcomposite' 'lib32-gst-plugins-base-libs')
 makedepends=('icoutils')
 optdepends=('pipewire-pulse: low-latency audio backend')
-source=("${pkgname}-installer-${pkgver}.exe::https://m1.ppy.sh/r/osu!install.exe"
+source=("${pkgname}-installer-${pkgver}.exe::https://github.com/ppy/osu/releases/download/${pkgver}/install.exe"
         "${pkgname}-terms-${_terms_commit}.md::https://raw.githubusercontent.com/ppy/osu-wiki/${_terms_commit}/wiki/Legal/Terms/en.md"
         "${pkgname}.sh"
         "${pkgname}.desktop"
         "${pkgname}.xml")
-sha256sums=('a4b1a450cada1b25b74b8decfb92f77c64a04f0b4ec8ddaf1a3c0f962a364c0a'
+sha256sums=('d5e6378acf54f39aef475b1476a5741c7d714815ef4e920bbcef926e6ae68a0b'
             '0fc6b18923db85b82fa5da1cb40ccc8c0ffcaf65ee7e325af8969baa150a9fd2'
             'e02f43b256575f2f1ae54ce3383246350a6a60acc966f02a3c896521b6632822'
             '3d98f5811539d652bf6378c2c76bff7b6d5ac82e6322942bb287ff9082f1715b'

(I bumped epoch because 2025 would be seen as < 20240607, for example). Hope maintainer updates this.

There's also issues with the icons due to resources shifting around with wrestool. I think a better approach here is to just download the logos/icons from https://osu.ppy.sh/wiki/en/Brand_identity_guidelines and commit them to the PKGBUILD repo.

Pls update the SHA256 for the installer. The current one won't pass the validity check.

New SHA265 for the installer: 3ed27cf4495655428ccf0cdcc6ad58d31e8c843074dd1c774ddb992d6dba92d3

Due to updates the game will no longer connect to the game servers (bancho). I fixed it by installing .NET4.5 via winetricks.

As others have said, the SHA256 for the installer is incorrect at the moment. Here's the fix:

diff --git a/PKGBUILD b/PKGBUILD
index 5063dc3..ff79987 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -16,7 +16,7 @@ source=("${pkgname}-installer-${pkgver}.exe::https://m1.ppy.sh/r/osu!install.exe
         "${pkgname}.sh"
         "${pkgname}.desktop"
         "${pkgname}.xml")
-sha256sums=('83d716ec0700b343f06e8fb78062fa08962ebddf9f1d0fca14e79778cde421e7'
+sha256sums=('8d73e298cbfd2ab3a3748c3512b6ad6ce4784aeaedc3f050b5bc48d51bddd651'
             '0fc6b18923db85b82fa5da1cb40ccc8c0ffcaf65ee7e325af8969baa150a9fd2'
             'b689540a3f856e9429429e7477641e161ff75748eb4909a0a00b8cda5d34e76e'
             '3d98f5811539d652bf6378c2c76bff7b6d5ac82e6322942bb287ff9082f1715b'

Please update the osu-installer sha-sum.

Update the SHA-SUMS, please.

==> Validating source files with sha256sums... osu-installer-20231106.exe ... FAILED

==> Validating source files with sha256sums... osu-installer-20231106.exe ... FAILED cannot pass validation

One file did not pass validity check

==> Validating source files with sha256sums...
    osu-installer-20230401.exe ... FAILED

The new versioning scheme is a super bad idea. Suppose the next update happens on 1 February. Then pacman will think it’s a downgrade because 20230102 < 20230401. With the old versioning scheme, it would (correctly) be recognised as an upgrade because 20230201 > 20230104.