Bug ID: 6335
Summary: Review request: jellyfin - The Free Software Media
Product: Package Reviews
Component: Review Request
SPEC URL: https://michael.cronenworth.com/RPMS/jellyfin.spec
SRPM URL: https://michael.cronenworth.com/RPMS/jellyfin-10.8.0-1.fc36.src.rpm
(Note: Due to being 700MB in size I will be removing the SRPM after the
Description: Jellyfin is a media system based on .NET and has ships a web UI
client by default. There are many other clients that offer interfaces on
numerous devices. It is a fork of Emby, but the code base has changed
significantly since the fork.
- I started with upstream's SPEC so there may be a stray problem. It was almost
- Upstream has a modified ffmpeg with non-upstream patches. They are mainly for
hardware acceleration fixes. This package still works against RPMFusion's
ffmpeg. It will take some extra investigation if they are upstreaming their
patches. Upstream may reject users asking for help if they find out they are
using our package without the ffmpeg "upgrades".
- A library shipped by the .NET runtime depends on an older library for F36+.
I've stripped the library until the issue is resolved. Noted in SPEC.
- Since it is a .NET and NodeJS app it requires Internet access to build. I've
put together a script to provide an offline cache of required dependencies.
$ rpmlint jellyfin.spec
============================ rpmlint session starts
checks: 32, packages: 1
jellyfin.spec: W: invalid-url Source4: jellyfin-npm.tar.xz
jellyfin.spec: W: invalid-url Source3: jellyfin-nupkgs2.tar.xz
jellyfin.spec: W: invalid-url Source2: jellyfin-nupkgs.tar.xz
0 packages and 1 specfiles checked; 0 errors, 3 warnings, 0 badness; has taken
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.