Package Details: osu-lazer 2019.518.0-1

Git Clone URL: https://aur.archlinux.org/osu-lazer.git (read-only)
Package Base: osu-lazer
Description: The new open source version of osu!, the free-to-win rhythm game
Upstream URL: https://osu.ppy.sh/
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: 19
Popularity: 3.686061
First Submitted: 2018-06-21 12:34
Last Updated: 2019-05-19 02:50

Latest Comments

1 2 3 Next › Last »

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?

https://github.com/ppy/osu https://github.com/ppy/osu-deploy

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: https://aur.archlinux.org/packages/osu-lazer-git/#comment-685032

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

DarioTD commented on 2019-02-10 23:00

Make libbass and libbass_fx AUR packages dependence in the new version both are required for osu-lazer to work, at least in my case.

Morguldir commented on 2019-01-21 23:14

ShayBox: I doubt that was what broke it, you can test by removing the quotes in /usr/bin/dotnet. What exactly is happening?

ShayBox commented on 2019-01-21 21:46

Since the dotnet package fixed spaces in file names, I can not import ant beatmaps, with or without spaces, the only way is the in-game osu!direct page, not even with the osu!direct button in browsers.

Morguldir commented on 2018-12-21 15:32

edit: Upstream has started using a nuget package instead of a git submodule, so this isn't needed anymore.

Updating from a version from before 2018.1219.0, to a version at or above 2018.1219.0 will require manual intervention due to the package now using https instead of the git protocol. You will have to do:

git remote set-url origin https://github.com/ppy/osu-resources.git

inside osu-resources

Or remove the osu-resources directory.

This is the osu-resources directory inside of SRCDEST, usually the same directory as the one the PKGBUILD is in.

Morguldir commented on 2018-12-21 04:19

Could you post some bencmarks using time?