LINUX SUPPORT IS HERE

[tatsu]

It still failed to find / execute faf-uid. Did you remember to make it executable, or made sure it's name is exactly 'faf-uid'? The client will throw the above error as long as it can't find it, but if you can execute it by typing just 'faf-uid' into console window, you should be good.

I'm not though that's the way it already was :

Screenshot from 2017-07-08 00-33-12.png (14.88 KiB) Viewed 3478 times

Screenshot from 2017-07-08 00-33-31.png (27.54 KiB) Viewed 3478 times

should it no longer be under lib???

[Wesmania]

You should add execute access for everyone. It doesn't matter where it is, as long as it can be found in your PATH.

[tatsu]

You should add execute access for everyone. It doesn't matter where it is, as long as it can be found in your PATH.

that's what it looks like when it's executable for everyone in that ui

proof :

Screenshot from 2017-07-08 19-21-58.png (4.48 KiB) Viewed 3460 times

plus this is a new issue i always had it working with just

Code: Select all

wget https://github.com/FAForever/uid/releases/download/v4.0.5/faf-uid -O lib/faf-uid
chmod +x lib/faf-uid


before

[tatsu]

You should add execute access for everyone. It doesn't matter where it is, as long as it can be found in your PATH.

that's what it looks like when it's executable for everyone in that ui

proof :

Screenshot from 2017-07-08 19-21-58.png

plus this is a new issue i always had it working with just

Code: Select all

wget https://github.com/FAForever/uid/releases/download/v4.0.5/faf-uid -O lib/faf-uid
chmod +x lib/faf-uid


before

NEVERMIND!!!!

i needed to reboot for it to work for some reason!
sorry!

[Wesmania]

That's *really* weird, but I'm glad it's fixed

[tatsu]

That's *really* weird,

tell me about it
I'm now trying to see if i can reproduce my steps in a new virtual ubuntu in an effort to prepare a .deb ... but i can't.

I dunno why :
I've run the only list of dependecy installs even though they're no longer required since we're now doing everything vitualenv side
but it stil gives me a CXFreeze compile crash because of missing Python.h :

Screenshot from 2017-07-08 23-08-50.png (79 KiB) Viewed 3441 times

for clarification : FAF still works fine on my local ubuntu machine but now I don't know WHY.

And if I were to reinstall I couldn't reproduce this functionality again.
we SHOULD be down to :

Code: Select all

#!/bin/sh
sudo apt install virtualenv -y
wget https://github.com/Wesmania/client/archive/0.15.0.tar.gz
tar -xzf 0.15.0.tar.gz
mv client-0.15.0 faf-client
rm 0.15.0.tar.gz
cd faf-client
virtualenv venv -p python3
source venv/bin/activate
pip install -U --force-reinstall pip
pip install PyQt5
pip install -r requirements.txt
echo "0.15.0" > res/RELEASE-VERSION
wget https://github.com/FAForever/uid/releases/download/v4.0.4/faf-uid-hotfix -O lib/faf-uid
chmod +x lib/faf-uid
python src/__main__.py


but it doesn't work

and adding :

Code: Select all

sudo apt install jq git autoconf libtool python-qt4 python-pyside pkg-config python-opengl python-imaging python-pyrex idle-python2.7 qt4-dev-tools qt4-designer libqtgui4 libqtcore4 libqt4-xml libqt4-test libqt4-script libqt4-network libqt4-dbus python-pip python-qt4 python-qt4-gl python-numpy python-matplotlib libgle3 python-dev libssl-dev libffi-dev libxslt1-dev libxml2-dev libxslt1-dev zlib1g-dev python-ipaddress python-enum34 python-pathlib python-py python-pycparser python-dateutil python-cffi libappindicator1 python-gpgme libindicator7 libgl1-mesa-dri:i386 libgl1-mesa-glx:i386 libc6:i386 liblua5.1-0-dev liblua50-dev liblualib50-dev libgnutls30 libgnutls30:i386 virtualenv build-essential dh-make -y

does no good.

oh yes and the first thing i did on this machine is run a full set of updates and now even with partners source and 32bit enabled there are no new updates so updates are not the issue.

[Wesmania]

Linux shouldn't need cx_freeze at all - we use it to build the msi for Windows. You don't need qt5 packages either, just qt5. How exactly does it fail to work?

[Wesmania]

Also, I'm sure you don't need a virtualenv to build the package in any way - it should use with existing system packages. All that needs to be done is to pack the client however a python package is packed into a deb, make __main__.py available as an executable somehow and set its dependencies properly. You can check my ebuild I linked earlier as a hint what dependencies are needed.

[tatsu]

Also, I'm sure you don't need a virtualenv to build the package in any way - it should use with existing system packages. All that needs to be done is to pack the client however a python package is packed into a deb, make __main__.py available as an executable somehow and set its dependencies properly. You can check my ebuild I linked earlier as a hint what dependencies are needed.

no because as we've seen getting qtwebkit (for example) on ubuntu is a literal impossibility.

and the cxfreeze thing triggers on the use of the requirements.txt file.

[Wesmania]

We moved from qtwebkit to qtwebengine, maybe it's less troublesome to install? And again, instead of setting up virtualenv, try installing all client dependencies for your system Python instead, and running the client from your system env (that's how the deb will need to work anyway). Some python modules might not have corresponding packages (like trueskill), I worked around it for gentoo by packing them too.