Jellyfin fails to start after recent dotnet updates
Description:
After the recent updates to the dotnet stack which jellyfin server requires to run. Jellyfin fails to start from its systemd service unit.
The packages that were update are aspnet-runtime, dotnet-runtime, and dotnet-host.
Jellyfin depends on version 8 of this stack and they were updated to version 9. I am unsure if it is possible for it to work with version 9 with a rebuild, but the solution to this was to simply install version 8 of these packages which are in the repos as separate packages.
Installing dotnet-runtime-8.0 and aspnet-runtime-8.0 solves the problem. However there does not seem to be a separate package for dotnet-host at the 8.0 branch and so it still gets updated to the 9.0 branch. For now it still works, but I don't know enough about this stack to know if this is wise or if it will continue to work.
The reason for this bug report is simply that this transition was not handled gracefully. Pacman did not prompt for manual intervention here to solve the problem as I have above or to replace those packages with the required versions. I'm just bringing this to your attention, so that it may be handled however you best see fit. Again I don't know if a simple rebuild of jellyfin-server, jellyfin-web, et al would also suffice here or whether or not dotnet-host not having an 8.0 package is a problem.
Steps to reproduce:
- Update the above mentioned packages.
- Try to start jellyfin via systemd service.
- ...