jellyfin{,-web}: 10.10.1 → 10.10.2 → 10.10.3

[vikanezrimaya]

Resolves #356716. Requires .NET SDK update, therefore depends on aa319c6 (part of #355753)

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[vikanezrimaya]

To test:

# Fetch dotnet updates
git fetch https://github.com/corngood/nixpkgs dotnet-next
git checkout FETCH_HEAD
# [OPTIONAL] Rebase on top of trunk
git fetch https://github.com/nixos/nixpkgs master
git rebase FETCH_HEAD

# (Optionally, instead you could do:)
# git checkout <whatever branch you want>
# git fetch https://github.com/corngood/nixpkgs dotnet-next
# git cherry-pick upstream/master..FETCH_HEAD

# Cherry-pick Jellyfin update commit
git fetch https://github.com/vikanezrimaya/nixpkgs jellyfin-10.10.2
git cherry-pick FETCH_HEAD
# Build
nix build .#jellyfin

[vikanezrimaya]

Dependent pull request was merged, this is ready for review now.

[minijackson]

Looks good, thanks. Jellyfin 10.10.3 was released recently, could you update your PR?

[vikanezrimaya]

@minijackson done! should I squash, or leave two commits sequentially updating the version?

[minijackson]

Looks good, thanks!

Tested by building the smoke-test, and running the smoke-test interactively for a few minutes.

---

Result of nixpkgs-review pr 356897 run on x86_64-linux 1

2 packages built:

• jellyfin
• jellyfin-web

[minijackson]

should I squash, or leave two commits sequentially updating the version?

@vikanezrimaya I think either is fine, you can leave it as is.