Package Details: jellyfin 10.4.3-2

Git Clone URL: (read-only, click to copy)
Package Base: jellyfin
Description: The Free Software Media System
Upstream URL:
Licenses: GPL2
Submitter: z3ntu
Maintainer: z3ntu
Last Packager: z3ntu
Votes: 31
Popularity: 3.81
First Submitted: 2019-01-09 16:59
Last Updated: 2020-02-08 10:26

Latest Comments

1 2 3 Next › Last »

cobol72 commented on 2020-02-23 18:57

I had build issues as well but, as @doctorzeus suggested, I added dotnet-sdk to the makedepends in addition to dotnet-sdk-2.2 and it worked fine. No idea why this is the case but I agree that it should be added.

user110 commented on 2020-02-16 11:25

@CountMurphy dotnet 2.2 (runtime&sdk) now flagged as out-of-date and not available to install from community. I was trying to change PKGBUILD deps of dotnet 2.1. but got error first similar to those @brando56894 had, but know receiving error

node_modules/bin/webpack: Permission denied

doctorzeus commented on 2020-02-09 04:19

This also seems to fail to build when dotnet-sdk and/or its dependencies are not installed (even though it should only require dotnet-sdk 2.2)..?

Could we possibly this as a dependency for the benefit of other users please?

xente commented on 2020-02-06 04:54

Even though the error message says version 2.1 is required, version 2.2 appears to work. Version 2.2 is in the official repos as a binary package. To build, change makedepend to dotnet-sdk-2.2 as well.

brando56894 commented on 2020-01-15 16:26

The dependency for dotnet should be set to dotnet-runtime-2.1 instead of dotnet-runtime because the latter points to v3 while jellyfin (currently) requires v2.1 in order to work properly.

Jan 15 11:07:03  systemd[1]: Started Jellyfin Media Server.
Jan 15 11:07:03  dotnet[10970]: It was not possible to find any compatible framework version
Jan 15 11:07:03  dotnet[10970]: The framework 'Microsoft.NETCore.App', version '2.1.0' was not found.
Jan 15 11:07:03  dotnet[10970]:   - The following frameworks were found:
Jan 15 11:07:03  dotnet[10970]:       3.1.0 at [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Jan 15 11:07:03  dotnet[10970]: You can resolve the problem by installing the specified framework and/or SDK.
Jan 15 11:07:03  dotnet[10970]: The specified framework can be found at:
Jan 15 11:07:03  dotnet[10970]:   -
Jan 15 11:07:03  systemd[1]: jellyfin.service: Main process exited, code=exited, status=150/n/a
Jan 15 11:07:03  systemd[1]: jellyfin.service: Failed with result 'exit-code'.

nac commented on 2020-01-13 21:40

It seems possibly some recent change to jellyfin is causing a build failure:

Entrypoint main [big] = bundle.js
[3] ./bundle.js 928 bytes {0} [built]
    + 21 hidden modules

WARNING in asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
This can impact web performance.
  bundle.js (849 KiB)
  components/themes/purple-haze/bg.jpg (293 KiB)
  components/themes/blueradiance/bg.jpg (933 KiB)

WARNING in entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
  main (849 KiB)

WARNING in webpack performance recommendations: 
You can limit the size of your bundles by using import() or require.ensure to lazy load some parts of your application.
For more info visit
Done in 252.93s.
Did you mean to run dotnet SDK commands? Please install dotnet SDK from:
==> ERROR: A failure occurred in build().
Error making: jellyfin

CountMurphy commented on 2020-01-13 17:31

@user110, you don't have to uninstall anything. Just install dotnet-runtime-2.2 from community

user110 commented on 2019-12-23 19:44

@satcom886 I've installed jellyfin with dotnet > 3 since installation with dotnet 2.1 failed with error in node.js modules.Received then error similar to your (required framework version 2.1). Resolved by installing dotnet 2.1 ( and removing dotnet 3 (dotnet-rc) without deleting jellyfin. Do not know whether it is a correct approach but it works now.

z3ntu commented on 2019-11-04 19:33

Version 10.4.1 has a potentially breaking change, see for details!

z3ntu commented on 2019-10-08 19:55

@cirlo Thanks for the info, jellyfin started up fine and the web interface loaded so I didn't check further. Updated!