Package Details: veloren-bin 0.15.0-1

Git Clone URL: https://aur.archlinux.org/veloren-bin.git (read-only, click to copy)
Package Base: veloren-bin
Description: The last stable release of an open-world, open-source multiplayer voxel RPG
Upstream URL: https://veloren.net/
Keywords: game rpg veloren
Licenses: GPL3
Conflicts: veloren
Provides: veloren
Submitter: Mckol
Maintainer: Mckol
Last Packager: Mckol
Votes: 7
Popularity: 0.65
First Submitted: 2019-08-08 23:47 (UTC)
Last Updated: 2023-12-07 23:24 (UTC)

Latest Comments

1 2 Next › Last »

Nudin commented on 2023-12-07 18:10 (UTC)

This installs Version 0.13 – not 0.15. The URL is hardcoded to this one year old build: https://gitlab.com/veloren/veloren/-/jobs/2761241182/

samhh commented on 2021-07-25 22:05 (UTC) (edited on 2021-07-25 22:06 (UTC) by samhh)

This diff fixes the PKGBUILD for me:

git diff --git a/PKGBUILD b/PKGBUILD index fa73f5c..ac49c01 100644 --- a/PKGBUILD +++ b/PKGBUILD @@ -13,12 +13,12 @@ makedepends=() provides=("$pkgname" 'veloren') conflicts=("$pkgname" 'veloren') source=( - "$pkgname"::"https://veloren-4129.fra1.digitaloceanspaces.com/releases/$pkgver-linux.tar.gz" + "$pkgname"::"https://gitlab.com/veloren/veloren/-/jobs/1341647286/artifacts/download" 'voxygen-wrapper.sh' 'server-cli-wrapper.sh' ) noextract=('voxygen-wrapper.sh' 'server-cli-wrapper.sh') -sha512sums=('0f976794c6d34eb937bbee021b48451139eae3e02fef4c757a7787fa9c06c3095b288522de58f55b6d7b80208f1be9e4300b4ec0dcf39cbb90640517e5a2a8ac' +sha512sums=('098cec46964bd5f851aca1a62282825cbad40ec8eb37904dee550e567cf01274dbdb369b1ecae5951eb20ba3a106a2b4d8c6b0cba781e2359be185340653deb5' 'e35c852bfa8d80a78a4df50c09246e69431efe9ebc208bd3c2a864e7674ee1078ab0d2eb2b2ffc1b67847ab7125a38dd260d8964054f55cdf0305248ece9a11c' 'a1ec4d3590af0f07be59c22de3de9402e7ed20eff7fb2b086773f04e8019a607a843a9ba0cf59df48431a5d9a3eb1d0c79272dced9a812c11ae7ed52e41bb0d2')

The GitLab job number is attached to the 0.10.0 tag.

(Sorry for formatting, no idea why that's happening - only changes are updating the source URL and associated checksum.)

samhh commented on 2021-06-21 21:44 (UTC)

veloren-bin fails sha512sum check for me as of 0.10.0-1.

Mckol commented on 2021-02-02 21:19 (UTC)

Sorry for the delay, I couldn't take care of this earlier due to school. Anyways, as it turns out, while the archive path change was unintended, the other change was intentional. Basically the binaries provided by upstream save the user data next to the executable and that doesn't work for a package. So I've written wrappers for the two executables in POSIX shell and moved the actual ones to /usr/lib/veloren. I also started using the .desktop, .metainfo.xml and icon files from the source tree (gonna port that change to the other Veloren packages soon).

pintert3 commented on 2021-01-22 00:35 (UTC)

Doesn't seem to be updated here is it? Still having that same issue.

Mckol commented on 2020-11-30 10:05 (UTC) (edited on 2020-11-30 10:07 (UTC) by Mckol)

So this was an issue with upstream - basically the paths got changed unintentionally, and a build-time environment variable that should have been present wasn't set. It's now fixed there and I updated the hashes accordingly. I should have caught that when updating it though so I suppose this serves as a reminder to properly test the package before pushing an update in the future :)

nukla commented on 2020-11-29 20:12 (UTC)

It seems the archive for the 0.8.0 build now contains all files in a "linux" directory instead of the root of the archive, but the paths in the PKGBUILD were not changed, causing it to not find the files after downloading. After fixing the paths in the PKGBUILD I can build and install the package, but when starting from the terminal this is all I get:

$ veloren-voxygen 
thread 'main' panicked at 'Failed to save settings: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }', voxygen/src/main.rs:32:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

SuperBoby commented on 2020-08-17 13:08 (UTC)

Confirmed, thanks.

Songtronix commented on 2020-08-17 12:55 (UTC)

Has been fixed!