I'd have made this on GitLab but don't have access right now - why ditch
the upstream systemd units and hardcore them?
Wouldn't it be better to source the new packaging repo instead?
https://github.com/jellyfin/jellyfin-packaging/
Martin
On Mon, May 27, 2024, 19:09 Florian Wetzel wrote:
> Hi,
Hi,
I just wanted to add a follow-up to anyone reading this and wanting to
update to the new version.
I created a MR here:
https://gitlab.archlinux.org/archlinux/packaging/packages/jellyfin-server/-/merge_requests/1
Feel free to try it if you want!
Regards,
Florian
On 27.05.24 11:40, Flo
> this still brings some new features that might be required by other packages
There are zero required-by's on those two packages, except between themselves.
>What would be the appropriate action if the current maintainer does not
>release a update soon?
https://wiki.archlinux.org/title/Package
May 27, 2024 05:40:39 Florian Wetzel :
> Hi there,
>
> I am not sure how to handle this problem, but I know that I am not the only
> person that has this problem.
>
> Currently, the packages /jellyfin-server/ and /jellyfin-web /are one stable
> release (10.8.13 -> 10.9.0) and multiple bugfix v
Hi there,
I am not sure how to handle this problem, but I know that I am not the
only person that has this problem.
Currently, the packages /jellyfin-server/ and /jellyfin-web /are one
stable release (10.8.13 -> 10.9.0) and multiple bugfix versions (latest
version is 10.9.3) behind. While 10
