-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please provide AppImage for download #237
Comments
@albertosottile has been working on AppImage support recently. He can tell you if I'm wrong, but I think the test build for it is currently available from https://bintray.com/syncplay/Syncplay/Syncplay/v1.6.3#files - if you do test it then please let us know how it goes. |
It does not work, how did you produce it?
|
The AppImage is created in our CI system, you can find a log of the latest build here: I just tested the AppImage file on Ubuntu 18.04.2 LTS, it works fine. We also had beta testers of it on Manjaro and Arch (I do not know the versions, sorry), still no issues. We could not manage to make it work on nixos, but I understand that's a known issue (AppImage/AppImageKit#472). @probonopd We plan to release the AppImage to the public when the next Syncplay version (1.6.4) is finalized. In the meantime, can you tell me more details about your test configuration? Thanks. |
I am running |
Could you run the Syncplay AppImage again after setting |
|
|
The CI just published a new AppImage at the same link reported above (https://bintray.com/syncplay/Syncplay/download_file?file_path=Syncplay-1.6.3-x86_64.AppImage). @probonopd If you could test it again, that would be great. Thanks. |
Runs! 👍 What did you change? |
@TheAssassin do you have an idea why |
Because it's not a direct dependency supposedly? Might be |
Version 1.6.4 has just been released, publishing the AppImage on GitHub releases and on AppImageHub. We will soon publish it also on our website. This issue is now resolved. |
Please provide an AppImage (not in a tarball) for download, thanks.
The text was updated successfully, but these errors were encountered: