Package Details: downlords-faf-client 0.10.7-1

Git Clone URL: https://aur.archlinux.org/downlords-faf-client.git (read-only)
Package Base: downlords-faf-client
Description: Forged Alliance Forever - Lobby Client. Community-driven client system for Supreme Commander: Forged Alliance. Downlord's Java client reimplementation.
Upstream URL: http://www.faforever.com/
Licenses: MIT
Submitter: sandwormsurfer
Maintainer: sandwormsurfer (dcelasun)
Last Packager: dcelasun
Votes: 0
Popularity: 0.000000
First Submitted: 2019-01-03 19:34
Last Updated: 2019-07-09 18:15

Latest Comments

dcelasun commented on 2019-06-29 11:20

0.10.7 is out

dcelasun commented on 2019-05-27 13:05

@sandwormsurfer, no worries I just thought you weren't checking AUR anymore so I submitted the orphan request. Yes, co-maintainer works, I've already updated the package :)

sandwormsurfer commented on 2019-05-27 13:01

@dcelasun sorry for not taking care enough of this package. I'm unexperienced in AUR, but I tried to make you co-maintainer. Does it work?

dcelasun commented on 2019-05-27 12:57

0.10.6 is out.

dcelasun commented on 2019-05-06 08:29

0.10.5-beta is out and the permissions issue is fixed. http://dpaste.com/2K0V0AC

dcelasun commented on 2019-04-24 06:05

PKGBUILD for 0.10.4-beta: http://dpaste.com/0V06NK4

Note that you still need to chown the install directory until that issue is fixed.

sandwormsurfer commented on 2019-04-23 11:48

I just created another issue and a PR to try to fix this stuff. But I don't have a Java dev environment nor a license for their install4j tool. https://github.com/FAForever/downlords-faf-client/issues/1162 https://github.com/FAForever/downlords-faf-client/pull/1163

dcelasun commented on 2019-04-21 18:40

Turns out downlords's client now expects the installation directory to be owned by the user running FAF (see here).

A quick sudo chown dcelasun.users /usr/share/java/downlords-faf-client -R fixed the problem but is clearly a bad hack.

dcelasun commented on 2019-04-20 18:59

I've tried updating the PKGBUILD to v0.10.0-beta and fixed the path to faf-uid, but FAF fails to launch with UIDF binary could not be executed. It might have been removed, not found or inaccessible. and natives/faf-uid: Operation not permitted.

I've tried chmod 777 on faf-uid and it still didn't work.