-
Notifications
You must be signed in to change notification settings - Fork 3
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 update workflows and tooling to move to v10.9.x #359
Comments
Just wanted to say that the flatpak at the drive worked perfectly! thank you so much!! (FYI anyone using it also might need to get the firewall to let in incoming connections to the jellyfin port ) |
Bumped to v10.9.10 b8ab8c2 |
Hey there! I've been on your 10.9.10 flatpak for a bit, but my android tv client just told me that ill get unable to connect soon unless server updates to 10.11, any idea when/if that update will be releasable in flatpak either at the gdrive or flathub? Thank you so much for your work and time it really helps the community out! |
If you meant 10.9.11, then please have a look at: #354 (comment) I added the update to the branch, which then built this test release to my surprise. I wanted to create a local build and upload it to google drive, but I got busy with many other tasks. :( 10.11 is another 6 months in the future, the next release is 10.10, which I will be looking into soon. |
the url at the pr gives a 404 when i curl it and flatpak install is giving same issue, are flathub/github creds needed for access to test build? |
Bumped to v10.9.11 and uploaded to Google Drive. No you don't need any credentials. I was not sure if these builds get deleted or not. The documentation says builds get published after 3 hours automatically, but I have not found a statement yet about what happens to test builds. |
For PR #354 to succeed workflows / tooling / cache need to be updated
I will continue working on improvements, but this is a blocker now. The Jellyfin team plans to release the next version in October.
Until I can spend more time on the build system, to work around these issues, I will publish the builds I created locally for testing here:
https://drive.google.com/drive/u/2/folders/1Ap2MMHWX2DMmJpKvbsQJOu67aK2DDGWR
The text was updated successfully, but these errors were encountered: