pipewire: 1.4.9 -> 1.5.84

[c6rg0]

Changelog: https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/1.5.84

Things done

• Updated finalAttrs.version from 1.4.9 -> 1.5.84 and the hashes accordingly,

• Renamed meson option systemd -> libsystemd to match upstream changes,

• Disabled meson option bluez5-codec-ldac-dec(not previously enabled, requires separate library; libldac),

• Disabled meson option bluez5-plc-spandsp(not previously enabled, however, spandsp is in nixpkgs but wasn't used before),

• Disabled meson option onnxruntime (not previously enabled)

• Tested with:

  • ./result/bin/pipewire --version ("Compiled with libpipewire 1.5.84 Linked with libpipewire 1.5.84")
  • nix-build --attr pipewire.passthru.tests passed 23/24.
    The failing test spa-benchmark-aec.test requires sample files. Debian also skips this test (1.5.81). Should it be disabled in Nix as well?

• Built on platform:

  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin

• Tested, as applicable:

  • NixOS tests in nixos/tests.
  • Package tests at passthru.tests.
  • Tests in lib/tests or pkgs/test for functions and "core" functionality.

• Ran nixpkgs-review on this PR. See nixpkgs-review usage.

• Tested basic functionality of all binary files, usually in ./result/bin/.

• Nixpkgs Release Notes

  • Package update: when the change is major or breaking.

• NixOS Release Notes

  • Module addition: when adding a new NixOS module.
  • Module update: when the change is significant.

• Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other READMEs.

---

Add a 👍 reaction to pull requests you find important.

[K900]

This is an RC version, we are not shipping it.

[K900]

Please wait until 1.6 stable.

[c6rg0]

Thanks for the feedback, I understand now that 1.5.84 is a release candidate. I noticed that I included a separate package update here (#468216). Should I keep this pr open for when 1.6 stable comes out (also removing the pastel update I left) or should I close it? Happy to do whichever you prefer.

[K900]

If the pastel update gets merged before this, it should just disappear from this PR because of how git merges work, or you can rebase on top of master. Also, this needs to target staging because of the rebuild count. We can keep this open though, 1.6 stable should hopefully be soon-ish.

[flokli]

1.5.85 got released, https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/0a27618cd4f43017c8e2aa7b68172e64ba48eb23:

This is the fifth and hopefully last 1.6 release candidate that
is API and ABI compatible with previous 1.4.x, 1.2.x and 1.0.x
releases.

Looks like it won't be too long anymore. We can probably update this PR to see if there's any surprises.

[K900]

Wim said a few more weeks.

[c6rg0]

1.5.85 got released, https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/0a27618cd4f43017c8e2aa7b68172e64ba48eb23:

This is the fifth and hopefully last 1.6 release candidate that
is API and ABI compatible with previous 1.4.x, 1.2.x and 1.0.x
releases.

Looks like it won't be too long anymore. We can probably update this PR to see if there's any surprises.

I was curious so I made sure that the new update doesn't change anything.
The new RC built by just changing the version number and hash.
nix-build -A pipewire.tests ends up successful (besides that one broken test):
SUMMARY: total=24; passed=23; skipped=0; failed=1; user=137.6s; system=14.6s; maxrss=4612
FAIL: pipewire-0.3/spa-benchmark-aec.test (Child process exited with code 255)

[xdenotte]

Stable 1.6 version released https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/1.6.0

[K900]

We'll have to get that into the next staging cycle.

[c6rg0]

Closing in favor of #492490.