parsec-bin: 150-90c -> 150-91a

[pabloaul]

Description of changes

package 150-90c -> 150-91a
ffmpeg_4 -> ffmpeg_5
add pabloaul as maintainer

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/)
• 23.11 Release Notes (or backporting 23.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.

[arcnmx]

The .so that comes with the package then wouldn't work with it (even once updated to 150_90c it won't be new enough), which makes this feel wrong, but it's also likely to be replaced and auto-updated to 150-91 anyway... Including both ffmpeg_4 and ffmpeg_5 is technically also an option but seems overly excessive.
Given that it still works with ffmpeg_4, it's not necessarily a problem to wait to do this until the next package update past 150-91, and one could override until then if desired but... Not sure, that makes me feel a bit torn here.

[pabloaul]

The .so that comes with the package then wouldn't work with it (even once updated to 150_90c it won't be new enough), which makes this feel wrong, but it's also likely to be replaced and auto-updated to 150-91 anyway... Including both ffmpeg_4 and ffmpeg_5 is technically also an option but seems overly excessive. Given that it still works with ffmpeg_4, it's not necessarily a problem to wait to do this until the next package update past 150-91, and one could override until then if desired but... Not sure, that makes me feel a bit torn here.

Checked their debian binary which was still on 150-90c right now. How long does the binary usually lag behind the actual current version?
I was told that the rollout for 91 should complete somewhen around this or next week. We can hold off on this before getting the version bumped, else people might be stuck on 90c with ffmpeg5.

[Kodikuu]

Parsec dev here, made aware this exists by @pabloaul mentioning it in the Discord 😅

Our rollout is complete, y'all can use ffmpeg_5

[Atemu]

Could you squash the two update commits and follow the contributing message guidelines on your maintainer commits?

[Atemu]

(Interpreting the link above as implicit approval by @arcnmx. Please explicitly agree going forward to make things clearer/get things merged quicker.)