Package Details: osu-lazer 2019.616.0-1

Git Clone URL: (read-only)
Package Base: osu-lazer
Description: The new open source version of osu!, the free-to-win rhythm game
Upstream URL:
Keywords: game lazer osu peppy ppy rhythm
Licenses: MIT, custom:CC-BY-NC 4.0
Conflicts: osu-lazer-git
Provides: osu-lazer
Submitter: Morguldir
Maintainer: Morguldir (ppy)
Last Packager: Morguldir
Votes: 21
Popularity: 3.496293
First Submitted: 2018-06-21 12:34
Last Updated: 2019-06-18 20:56

Latest Comments

1 2 3 Next › Last »

tleydxdy commented on 2019-06-16 01:12

suprisingly, I can't seem to find info on how to disable telemetry at build time, or change it to opt-in. I'm not very familiar with anything microsoft at all. so maybe someone have better ideas.

Morguldir commented on 2019-06-15 15:08

Sounds like a good idea, although i recommend taking it up with the maintainer of the dotnet arch package, so that it applies to every dotnet program.

tleydxdy commented on 2019-06-15 12:30

Could you change the PKGBUILD to build with DOTNET_CLI_TELEMETRY_OPTOUT=true to opt-out of microsoft telemetry by default? people who want it could opt-in instead


kazimazi commented on 2019-06-15 03:01

Won't install. fatal: '2019.618.0' is not a commit and a branch 'makepkg' cannot be created from it ==> ERROR: Failure while creating working copy of osu-2019.618.0 git repo Aborting... Error making: osu-lazer

HyperFrame commented on 2019-06-02 11:41

If you want to have the latest version, just downlao the snapshot and the edit the makepkg file change the version number of osu to the actuel one. PLZ ENJOY GAME

Morguldir commented on 2019-05-05 04:47

Hi, the AUR is usually not a place for binaries, with some exceptions, for example when there is no source available, and when the package has the -bin suffix. The way the aur usually works is that no suffix is the stable version, and -git is the latest version from git.

As for doing this "properly", I'm not interested in working on programs where you can't verify what code you're actually running, or at least have the ability to, which won't be possible in the future.

I'll add you as a co-maintainer for now so you can change it as you like. Until then, i'll be updating the package like i have been, as the package in it's current state is still useful.

In the future it might be ideal to do something like VS Code and Chromium where you have unbranded source-based packages, and official binaries.

ppy commented on 2019-05-04 04:52

Could this please be delisted or transferred to me? Could those responsible for making this happen please help correctly adding deployment to our official means so this can be done properly?

This should be using published binary releases as other platforms are.

mkroening commented on 2019-03-08 10:36

The issue with libbass and libbass_fx has been fixed with 2019.308.0.

See my comment at osu-lazer-git:

If you are to busy to maintain the package, I'd be happy to take over.

Leeo97one commented on 2019-03-07 19:50

I also had to install the libbass_fx package for the game to start and play songs (tried with the 2019.305.0 version).

Morguldir commented on 2019-02-11 00:05

DarioTD: Because of the way the bass packages work, they will stop functioning on every upstream update until they are updated, so i won't be using them. Either way, there isn't anything that should be preventing it from working as long as you use the script placed in /usr/bin/osu-lazer