jellyfin/fedora, branch v10.8.0-alpha3

Fix builds for dotnet6 (#6595)

2021-09-25T12:21:48Z

* Target net6.0 * Use new Enum.TryParse(ReadOnlySpan) overload * Replace RNGCryptoServiceProvider with RandomNumberGenerator * ci - target net6.0 (#6594) * Update deployment for dotnet6 * Use generic 6.0.x preview for CI * Update direct dotnet download links Co-authored-by: Bond_009

Merge pull request #4615 from strugee/fix-restart.sh

2021-09-06T11:53:23Z

Merge pull request #5606 from lmnotran/feature/delay-service-start

2021-08-18T06:25:54Z

Delay starting service until after network is online

Enable Workstation GC mode

2021-04-11T10:57:28Z

Delay starting services until after network is online

2021-03-24T06:35:44Z

Merge pull request #4663 from joshuaboniface/bump-version-10.8.0

2021-02-09T02:38:31Z

Bump version to 10.8.0 for next release

Use variables for version, and fix conflict

2021-01-05T05:32:46Z

Bump version to 10.8.0 for next release

2020-12-05T02:56:24Z

Use a service unit, not a scope unit, to restart

2020-12-05T00:33:24Z

Reportedly `systemd-run --scope` still got killed by the service manager; see #4615. The suspected cause is that `scope` units are run by the `systemd-run` process itself and inherit the caller's execution environment (see systemd-run(1)). To fix this, we use a systemd `service` unit instead, which is run and managed by PID 1 - hopefully this will isolate us sufficiently so that we don't get terminated along with `jellyfin.service`.

Use systemd-run(1) in restart.sh

2020-12-05T00:18:26Z

systemd-run(1) runs `systemctl restart` in an isolated systemd unit that is not subject to process termination as jellyfin.service is shut down. We adjust the sudoers configuration for this new usage, removing the old config, since restart.sh is the only user of the sudoers policy. Additionally we change `systemctl start` to `systemctl restart` since there was a race condition where jellyfin.service was not fully stopped by the time this ran, so `systemctl start` became a noop. `systemctl restart` on the other hand works whether jellyfin.service is stopped or not. The at(1) hack (and the usage of `start` instead of `restart`) is left in for other init systems since I cannot test on those systems, and because I don't know of any systemd-run(1) equivalent (although it may be a non-issue since alternate init systems do not keep track of daemon children nearly as aggressively as systemd does).