`.deb` unnecessarily depends on `pulseaudio` explicitly (not `pipewire-pulse` compatible)

[fallingcats]

Description The debian package built with cargo deb isn't compatible with systems that run PipeWire (and compatibility through pipewire-pulse) , since it depends on the pulseaudio package. This isn't necessary, usually (according to my research) clients would just depend on the PulseAudio client libraries from libpulse0 (which spotifyd does also, too)

Expected behavior Don't depend on pulseaudio, keep depending on libpulse0

Logs From the package control file: Depends: libasound2 (>= 1.0.16), libc6 (>= 2.34), libdbus-1-3 (>= 1.9.14), libpulse0 (>= 0.99.1), pulseaudio, systemd

Click to show logs

# dpkg -i spotifyd_0.4.1-1_arm64.deb
Selecting previously unselected package spotifyd.
(Reading database ... 111576 files and directories currently installed.)
Preparing to unpack spotifyd_0.4.1-1_arm64.deb ...
Unpacking spotifyd (0.4.1-1) ...
dpkg: dependency problems prevent configuration of spotifyd:
 spotifyd depends on pulseaudio; however:
  Package pulseaudio is not installed.

dpkg: error processing package spotifyd (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 spotifyd

Versions:

• OS: Raspberry Pi OS (bookworm)
• Spotifyd: 4.1.0

Additional context It's possible other deps are also unneccesary, like systemd which probably shouldn't be required (suggested might fit?) if we want to throw a bone to the devuan folks or similar "init freedom".

Off-topic question: Any reason deb's aren't being built for releases?

[eladyn]

Thanks for reporting that! As far as I know, no one has really bothered updating / maintaining the cargo deb metadata in a while. And since I'm not running Debian myself, my expertise is also not great in that direction.

If you'd be willing to update those lines in Cargo.toml such that they better match the current state of the project, that would be greatly appreciated!