Package Details: osu-lazer 2019.930.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: 24
Popularity: 1.616396
First Submitted: 2018-06-21 12:34
Last Updated: 2019-10-01 21:32

Latest Comments

1 2 3 4 Next › Last »

zeroxfourc commented on 2019-08-18 06:48

I've not been able to compile this since 2019.719.0. I'm not getting any error message, the build just fails:

env LC_ALL=C makepkg -si
==> Making package: osu-lazer 2019.809.0-1 (Sun Aug 18 08:46:14 2019)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating osu-2019.809.0 git repo...
Fetching origin
  -> Found CC-BY-NC-4.0
  -> Found osu-launcher
  -> Found osu-lazer.desktop
  -> Found osu-lazer.png
  -> Found x-osu-lazer.xml
==> Validating source files with sha256sums...
    osu-2019.809.0 ... Skipped
    CC-BY-NC-4.0 ... Passed
    osu-launcher ... Passed
    osu-lazer.desktop ... Passed
    osu-lazer.png ... Passed
    x-osu-lazer.xml ... Passed
==> Extracting sources...
  -> Creating working copy of osu-2019.809.0 git repo...
Reset branch 'makepkg'
==> Removing existing $pkgdir/ directory...
==> Starting build()...
Microsoft (R) Build Engine version for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

==> ERROR: A failure occurred in build().

Has anybody else had this error and if so, what did you do to fix it?

ppy commented on 2019-08-13 13:05

just a note that ffmpeg is now a prereq. luckily it was already added ;)

Morguldir commented on 2019-08-01 14:54

My guess is that you forgot to reboot after updating your drivers and kernel.

Uumas commented on 2019-08-01 14:32

I get this error when launching after the latest update:

Worked fine previously.

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.