Search Criteria
Package Details: osu-lazer-git latest-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/osu-lazer-git.git (read-only, click to copy) |
---|---|
Package Base: | osu-lazer-git |
Description: | A free-to-win rhythm game. Rhythm is just a *click* away! |
Upstream URL: | https://osu.ppy.sh/ |
Keywords: | arcade game |
Licenses: | MIT AND CC-BY-NC-4.0 |
Conflicts: | osu-lazer |
Provides: | osu-lazer |
Submitter: | emmieaur |
Maintainer: | neeshy |
Last Packager: | neeshy |
Votes: | 40 |
Popularity: | 0.000000 |
First Submitted: | 2017-03-25 04:24 (UTC) |
Last Updated: | 2024-04-15 19:08 (UTC) |
Dependencies (6)
- dotnet-runtime (dotnet-runtime-2.2AUR, dotnet-runtime-3.0AUR, dotnet-runtime-2.1AUR, dotnet-runtime-5.0-binAUR, dotnet-runtime-7.0-binAUR, dotnet-runtime-6.0-binAUR, dotnet-runtime-preview-binAUR, dotnet-runtime-binAUR, dotnet-runtime-8.0-binAUR)
- ffmpeg (ffmpeg-nvcodec-11-1-gitAUR, ffmpeg-amd-full-gitAUR, ffmpeg-cudaAUR, ffmpeg-full-gitAUR, ffmpeg-gitAUR, ffmpeg-fullAUR, ffmpeg-decklinkAUR, ffmpeg-headlessAUR, ffmpeg-amd-fullAUR, ffmpeg-libfdk_aacAUR, ffmpeg-obsAUR, ffmpeg-ffplayoutAUR)
- libgl (nvidia-340xx-utilsAUR, libglvnd-gitAUR, amdgpu-pro-oglpAUR, amdgpu-pro-oglp-legacyAUR, libglvnd)
- sdl2 (sdl2-gitAUR, sdl2-compat-gitAUR)
- dotnet-sdk (dotnet-sdk-2.2AUR, dotnet-sdk-2.2-vs2017AUR, dotnet-sdk-3.0AUR, dotnet-sdk-2.1AUR, dotnet-sdk-5.0-binAUR, dotnet-sdk-6.0.110-binAUR, dotnet-sdk-7.0-binAUR, dotnet-sdk-8.0.300-binAUR, dotnet-sdk-6.0-binAUR, dotnet-sdk-preview-binAUR, dotnet-sdk-binAUR, dotnet-sdk-8.0-binAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
Required by (1)
- llin-git (requires osu-lazer)
Latest Comments
1 2 3 4 5 6 .. 13 Next › Last »
<deleted-account> commented on 2024-02-05 16:03 (UTC)
build process now depends on dotnet 8, trying to build with 6 just fails with sdk error
atticf commented on 2022-04-08 02:42 (UTC) (edited on 2022-04-08 02:54 (UTC) by atticf)
Should the
ffmpeg
depedency be changed toffmpeg4.4
? While osu!lazer uses whatever the system's ffmpeg is, videos still don't work and there are random crashes when usingffmpeg
(5.0). However, if this change was made, osu!lazer would still use ffmpeg 5.0 because it searches for/usr/lib/libavcodec.so
etc. which are symlinks to the ffmpeg 5.0 libraries. I run osu!lazer in a container, so I just binded the ffmpeg 4.4 libraries to the generic/usr/lib/libavcodec.so
etc. files to override the symlinks for that sandbox, but I wonder if there's a more elegant way to handle something like this.Edit: After writing this, I just remembered that setting the
LD_LIBRARY_PATH
is probably a better option. Now instead of binding each ffmpeg 4.4 library to the generic symlink I just run osu!lazer withLD_LIBRARY_PATH
set to/usr/lib/ffmpeg4.4:"${LD_LIBRARY_PATH}"
to make osu!lazer use the ffmpeg 4.4 libraries. I'm still open to hearing other options.ppy commented on 2022-01-28 16:11 (UTC)
We will not be targeting dotnet 6 for a while more. The dependencies should be pinned to 5.
NaAlOH4 commented on 2022-01-28 04:25 (UTC)
It seems like ppy is using dotnet 5 and the package will install dotnet 6?
catlover2 commented on 2021-10-31 07:29 (UTC)
@huupoke12 yes, I have installed
ca-certificates
version20210603-1
huupoke12 commented on 2021-10-31 07:26 (UTC)
@catlover2 Do you have
ca-certificates
installed?catlover2 commented on 2021-10-31 03:59 (UTC)
I'm getting the errors about
again. I have dotnet-runtime 5.0.8.sdk205-1 installed, well past version 5.0.5 mentioned below.
huupoke12 commented on 2021-08-07 04:06 (UTC) (edited on 2021-08-07 04:09 (UTC) by huupoke12)
@puyo This is a VCS package, meaning that the
pkgver
variable shouldn't be used as-is, but to be updated by thepkgver()
function in thePKGBUILD
. You should report this problem to theaurutils
developers instead.puyo commented on 2021-08-07 01:54 (UTC)
my aur helper
aurutils
doesn't want to update this unless i specifically tell it to rebuild since line 10pkgver='2021.416.0.r73.e227c076e5'
and the version the package actually has (from line 30'spkgver()
i think?) is newer than 2021.416.0huupoke12 commented on 2021-04-07 11:01 (UTC) (edited on 2021-04-07 11:11 (UTC) by huupoke12)
@prokoprandacek It's an upstream issue that will be resolved by the release of .NET 5.0.5. See this article for more information.
1 2 3 4 5 6 .. 13 Next › Last »