Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'System.Runtime, Version=4.2.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) about jellyfin-rpm HOT 6 CLOSED

Rolling back to jellyfin-3.5.2.gitf8a720d-1.fc29.x86_64 allows Jellyfin to start again.

from jellyfin-rpm.

That's strange since this commit addressed #2 which is mostly about the sudo policy so the jellyfin binarys should stay the same.

Im trying to reproduce this.

I can't exactly see what changes went in between those two releases as there are no tags to indicate which revs were used to generate the corresponding RPMs.

I just started really using git/github to support jellyfin, so i have a lot to learn about how to git in a meaningful way.

from jellyfin-rpm.

That's strange since this commit addressed #2 which is mostly about the sudo policy so the jellyfin binarys should stay the same.

Indeed. That would be my expectation also. Clearly something is amiss however.

I just started really using git/github to support jellyfin, so i have a lot to learn about how to git in a meaningful way.

No worries. This might not be useful/relevant for much longer as you are trying to upstream the RPM building, which is great. But generally speaking, in your working copy (of the repo), at the point where you use the RPM specfile to push a build to COPR, it would be helpful to do a git tag version where version is the RPM's version-release. That way others can see exactly what was used to create the given binary RPM.

from jellyfin-rpm.

Interesting when i upgrade from jellyfin-3.5.2.gitf8a720d-1.fc29.x86_64 to jellyfin-3.5.2.gitf8a720d-2.fc29.x86_64 it crashes with the same error.

But when i upgrade to jellyfin-3.5.2.gitf8a720d-3.fc29.x86_64 the latest build from copr it works.

I have no idea where this comes from since in the gitf8a720d-3 i added the update-db.sh script, and fixed the spec file afterwards since CentOS had no Recommends tag and only the CentOS build where failing.

Can you please try to upgrade to jellyfin-3.5.2.gitf8a720d-3.fc29.x86_64 ?

from jellyfin-rpm.

Im puzzled, the build-log look ok on closer inspection and after i used the same .src.rpm to rebuild this package it works.

from jellyfin-rpm.

Eeeew. That's ugly. In any case jellyfin-3.5.2.gitf8a720d-3.fc29.x86_64 does work.

from jellyfin-rpm.