Arch Linux User Repository

For all people flagging the package out of date: This is a -git package that pulls down the latest sources from the git repository, so unless the build process is broken, don't flag this package out of date! Just rebuild it.

ffmpeg parameter won't work.

I added it to conf file, and the argument is in the process, but has no effect. Build it now based on PKGBUILD from the extra repo and it works.

I think we need to hold off on building until SkiaSharp gets updated and the hls.js sourcing PR gets merged - the devs currently note that the newer patched release of SkiaSharp segfaults, but sticking with the older build errors out due to the security vulnerability (tried from the latest stable commits as a test):

/src/jellyfin/Jellyfin.Drawing.Skia/Jellyfin.Drawing.Skia.csproj : error NU1903: Warning As Error: Package 'SkiaSharp' 2.88.2 has a known high severity vulnerability, https://github.com/advisories/GHSA-j7hp-h8jx-5ppr

Time fixes all things!

@digital_mystik: I can reproduce, but seems to be fixed with this PR: https://github.com/jellyfin/jellyfin-web/pull/5060, I assume "npm ci" somehow fails to download the lib from that other source. Maybe the ssh url doesn't get liked inside npm?

Has anyone been able to successfully build jellyfin-web lately? I think something may be borked upstream.. hls.js missing is causing build failure (at least on my end)

As of today (December 5th 2023), this jellyfin-git package is severely out of date.

• According to the release notes on the latest release from jellyfin's github, https://github.com/jellyfin/jellyfin/releases/tag/v10.8.13
  • The customizable FFmpeg binary path in the WebUI/API has been REMOVED for security reasons. Please see the corresponding blog post here for further details.
  • This bugfix release contains two GHSA security fixes; the details of these vulnerabilities will be released publicly on December 5th 2023. Please ensure you update your systems as soon as possible.

On top of my previous comment it should be noted that the newest release of v10.8.13 has requirements for dotnet-sdk>=8 and aspnet-runtime>=8 as digital_mystik pointed out.

For now, these dependencies can be met by installing dotnet-sdk-bin and aspnet-runtime-bin from the AUR.

I believe the PKGBUILD needs to bump to dotnet 8.0 as upstream fails to build when 7.0 is forced (global.json command)

Edit: Nevermind. I realized there's up-to-date jellyfin packages in the official extra repository.

As cubitoom pointed out, this package pulls a very old version.

It would be nice if the package could be fixed to pull the actual current release. (10.8.12 at the moment)

The minor changes suggested by cubitoom work great at doing just that. Thanks!

@cubitoom: The package is pulling the latest sources from the default branch (so now master) when you run makepkg. So based on this it seems, the last tag reachable from master branch is 10.8.0.alpha5, final 10.8.0 and the patch releases on top live on a different branch. pkgver is just cosmetic anyways (see also pinned comment).

This -git package has not been pulling the latest sources for the git repo.

As of writing this, it is pulling an outdated release of 10.8.0.alpha5.r1656.g2ce08eb184.

I am not an AUR maintainer and I do not know if the pkgver variable must be a specific version, or how it gets rendered when stated in the PKGBUILD file, however making this change allowed me to install the latest release of jellyfin 10.8.11 (which currently has the latest label applied to it).

https://github.com/CubitOom/jellyfin-git/commit/481958567034d3cb4056c61b8c8587399abacf03

Since commit af611367c14e2d56e6346b03bda7d75ab6f04b96, build failed:

...
==> Starting package_jellyfin-web-git()...
cp: cannot stat 'jellyfin-web/dist': No such file or directory
==> ERROR: A failure occurred in package_jellyfin-web-git().
    Aborting...