Jellyfin 10.9.x #6101
Merged
Jellyfin 10.9.x #6101
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1. Update jellyfin to 10.9.1 2. Update dotnet to 8.0.4.
update nodejs version 20.0.0
update nodejs 20.0.0
update jellyfin 10.9.1 update dotnet 8.0.4 update nodejs 20.0.0
1. Update jellyfin to 10.9.2 2. Update dotnet to 8.0.4. 3.Update nodejs 20.0.0
… into jellyfin-10.9.2
|
@hgy59 Can you help me merge? |
|
If you have updated the 10.9.1 version, you can test the 10.9.2 version package at the address: https://drive.google.com/drive/folders/1eO6483FsyDdxc-lFQ46uWVbCYSyqLHH8?usp=sharing |
would straight installing the 10.9.2 cause an issue ? if it would i can try upgrading through 10.9.1 this evening first, :) |
|
The official website of jellyfin says that 10.9.1 has a bug where the
service cannot be logged in. It is recommended to upgrade to 10.9.2
directly.
C2gl ***@***.***> 于2024年5月20日周一 17:05写道：
… If you have updated the 10.9.1 version, you can test the 10.9.2 version
package at the address:
https://drive.google.com/drive/folders/1eO6483FsyDdxc-lFQ46uWVbCYSyqLHH8?usp=sharing
would straight installing the 10.9.2 cause an issue ?
if it would i can try upgrading through 10.9.1 this evening first, :)
—
Reply to this email directly, view it on GitHub
<#6101 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA63RQTYX53BZIIY2J2UW4DZDG4FPAVCNFSM6AAAAABH7CBETGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRQGAYDSMBWGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Very well, ill try upgrading the package in the dsm package manager(dsm 7.1) via a manual upload. I have already a jellyfin 10.8.13 running from the synocomunity, it will just upgrade that one using the manual upload right ? |
|
Yes, because the master branch has not yet merged the code. If you want to
wait to see it in the Synology suite, you can only update it after the
master merge and package. The above 10.9.2 package is currently in the
testing stage.
C2gl ***@***.***> 于2024年5月20日周一 17:16写道：
… @stevenliuit <https://github.com/stevenliuit>
Very well, ill try upgrading the package in the dsm store (dsm 7.1) via a
manual upload.
I have already a jellyfin 10.8.13 running from the synocomunity, it will
just upgrade that one using the manual upload right ?
—
Reply to this email directly, view it on GitHub
<#6101 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA63RQR5MRX7KN23CQMMY43ZDG5NXAVCNFSM6AAAAABH7CBETGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRQGAZDSMBYGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
amazing , ill try it out and have users use it too , thank you for your amazing work ^^ |
|
thx
C2gl ***@***.***> 于2024年5月20日周一 17:37写道：
… amazing , ill try it out and have users use it too , thank you for your
amazing work ^^
—
Reply to this email directly, view it on GitHub
<#6101 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA63RQVLPL6LYTXZZ4MOVXLZDG733AVCNFSM6AAAAABH7CBETGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRQGA3DKNJQHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
for issues i find (that seem to be related with the APK and not with jellyfin itself) |
If it is related to the spk package, mention an overall problem in issues and it will be solved by the spksrc framework. |
|
已经测试dsm7.1不好使，可以安装无法运行，原因是dsm7.1没有nodejs20套件，最高只到18，我升到dsm7.2并安装nodejs20后，jellyfin10.9.1完美运行了，英文不好sorry，楼主应该看得懂吧 |
hgy59
reviewed
May 26, 2024
hgy59
reviewed
May 26, 2024
hgy59
reviewed
May 26, 2024
update jellyfin 10.9.2
|
jellyfin now depends on DSM 7.2 and is not built by the github build action @th0ma7, @publicarray should we adapt the CI/CD scripts to build jellyfin for DSM 7.2 instead of DSM 7.1 or is it ok, that only manual/local builds can be used to create and deploy jellyfin packages? |
update jellyfin 10.9.3 version
The construction of jellyfin depends on the 20.0.0 version of nodejs, but the running environment does not require nodejs. |
Is this correct and has it been tested under DSM 7.1? If I translate the comment above correctly, we see this feedback:
What do you make of this? |
|
@stevenliuit further to my previous comment, you may be correct that the issue is not with nodejs. From the log it seems more related to this:
Below are the full install and service logs for reference. Running on DS916+ with DSM 7.1.1-42962 Update 4. Install LogService Log |
Install Log
Service Log
This error seems to be related to Synology's sqllite3. I have only tested it on 7.2 and have not tested the older version. |
|
@hgy59
The times I have seen this error with glibc is when a lower version of glibc is used during runtime than the one the software was compiled with. Strange as I expect this to be included in the toolkit from Synology.
|
已转移 刷新下里面就有了 |
|
Thanks for 10.9.4 which allowed me to remove ffmpeg package and use ffmpeg6 and also resolved quite a few blocker issues I ran into with 10.9.3. However those issues were Jellyfin issues not packaging / Synology package issues. |
update jellyfin 10.9.5
|
Just putting together an argument to help move this forward...
@hgy59 my understanding is that if this is added, it will not build successfully and give the following:
@publicarray, based on the release notes from Jellyfin Server 10.9.0, I don't think going back to an earlier dotnet version is feasible. Also based on comments from @hgy59, there are a number x13 to x16 series models that support DSM 7.1.1 but not DSM 7.2 so dropping DSM 7.1 support does not seem to be the solution either. So where do we go from here? I'm looking at this:
I think in the short term, we can go the direction of a manual build and upload to the repo for now as a number of users are waiting to move to Jellyfin v10.9.x. This manual build would have the minimum DSM as 7.2 as has been done by @hgy59. Setting this minimum is required to ensure that users with DSM 7.1 don't upgrade to the newer package and be unable to start it. Once this is published and out in the world we can re-look at the CI/CD scripts to consider a more long-term solution. Perhaps we can continue to build for DSM 7.1 but add an exception to use the DSM 7.2 toolchain if the |
|
While i hate hacks, in the automated build scripts we could have a workaround to call for |
|
Thanks @mreid-tt I was hoping there was a simple solution but you make good points. Agreed on manual upload. The build/action scrips will need to be updated at some point so accommodate for this but that can wait. Thanks for everyones work on this |
update jellyfin 10.9.6 version
update jejllyfin 10.9.6
What else do I need to do? Currently, Jellyfin is updating very quickly. It was updated to version 10.9.6 yesterday. |
Just wait for a stable release (i.e. no updates for about 2 to 4 weeks). Since we still define “REQUIRED_MIN_DSM = 7.1” and are not yet restricting to 7.2, users who want to upgrade can use the packages created by the GitHub build action. |
okay thank you |
So we can still upgrade our Jellyfin from this PR or we still have to wait ? |
Yes, if you are on DSM 7.2 and have an x64 or aarch64 model, you can manually download and install the package created by github build action. Just be informed that jellyfin recommends to create a backup before updates. I just don't know whether you can create a backup from within the jellyfin web UI or need to backup the package data folder in a DSM shell. And after a manual update, there is no problem with further updates from the SynoCommunity repository in the DSM package center. |
hey @publicarray, I may be looking at this very simplistically, but I believe this is the line the defines which DSM versions to build for: Line 174 in d946e75 Could we not wrap this in a check to determine if Again, I'm not that familiar with the deep workings of the |
@mreid-tt the defintion in This is independent of any package to build. |
10 tasks
hgy59
added
the
status/published
|
Thank you all for this work ! |
10 tasks
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Closes #6138
Checklist
all-supportedcompleted successfullyType of change