shairport-sync (5.6.2-2) unstable; urgency=medium The shairport-sync system and user services now use systemd sandboxing options; run "systemctl cat shairport-sync" to see them. Commands run by the run_this_* hooks in /etc/shairport-sync.conf run in the same sandbox. For the system service the restrictions are chosen so as not to affect typical hooks: they may still use sudo, access devices and write to /tmp, /home, /var and /sys. Hooks can no longer write below /usr, /boot or /etc, load kernel modules, set the clock or hostname, or use socket families other than IPv4, IPv6, Unix and netlink. The user service, used with "systemctl --user", also sets NoNewPrivileges=yes, so its hooks can no longer use sudo or other setuid programs. If a hook needs more access, relax the restrictions with a drop-in created by "systemctl edit shairport-sync" (add --user for the user service). For example, to lift the file system and socket restrictions: [Service] ProtectSystem=no RestrictAddressFamilies= Applying these restrictions to a service that runs as a non-root user requires the CAP_SYS_ADMIN capability. Containers created by Podman or Docker do not grant it by default; there the system service fails to start with status 217/USER. Either grant the capability to the container, or turn off the affected restrictions with a drop-in: [Service] ProtectKernelModules=no ProtectKernelLogs=no ProtectClock=no ProtectHostname=no LockPersonality=no RestrictNamespaces=no RestrictSUIDSGID=no RestrictAddressFamilies= SystemCallArchitectures= SystemCallFilter= -- Chris Boot Sun, 08 Nov 2026 12:36:43 +0000 shairport-sync (5.6.2-1) unstable; urgency=medium The Jack Audio Connection Kit output backend, deprecated in the previous release, has been removed upstream. Users with output_backend = "jack" in /etc/shairport-sync.conf must switch to another backend, such as "pipewire", before shairport-sync will start. Environment variable references of the form ${NAME} in /etc/shairport-sync.conf are now expanded before the file is parsed. A reference to an unset variable, or a malformed reference, is a fatal error at start-up, and a literal "${" must now be written as "$${". This may affect settings that contain shell commands, such as run_this_before_play_begins. The shared memory interface between shairport-sync and nqptp has been updated to version 11. AirPlay 2 operation now requires nqptp 1.2.9 or later; package relationships ensure matching versions are installed together. A locally built nqptp must also implement interface version 11. -- Chris Boot Fri, 06 Nov 2026 15:08:36 +0000 shairport-sync (5.1~dev~git20260518-1) unstable; urgency=medium The shairport-sync package has been rebuilt with AirPlay 2 support. This is a significant change from previous versions, which supported AirPlay 1 only. AirPlay 2 support is automatically enabled when the nqptp service is running. Converseley, if nqptp is not running, shairport-sync starts up in AirPlay 1 mode. The mode can be forced using the new service_type setting in shairport-sync.conf. Note also that the nqptp package does not currently provide a System V init script. Users not using systemd will be unable to use AirPlay 2 support at this time. The PulseAudio back-end has been renamed from "pa" to "pulseaudio". Users with "pa" specified in the output_backend setting in /etc/shairport-sync.conf should update this to "pulseaudio". Several configuration file settings have been renamed in this version. The old names are deprecated but currently still honoured: convolution_ir_file -> convolution_ir_files (now accepts a list) convolution -> convolution_enabled convolution_max_length -> convolution_max_length_in_seconds loudness -> loudness_enabled The settings audio_backend_buffer_desired_length_in_seconds and audio_backend_latency_offset_in_seconds have been moved from their individual backend stanzas (e.g. the "alsa" stanza) to the "general" stanza, where they now apply to all backends. The Jack Audio backend is deprecated upstream and will be removed in a future release. Users of this backend should consider migrating to the PipeWire backend. For a full list of changes, see /usr/share/doc/shairport-sync/RELEASENOTES.md.gz. -- Chris Boot Sat, 23 May 2026 21:34:04 +0100 shairport-sync (3.1.7-1) unstable; urgency=medium The deprecated PulseAudio output plugin ("pulse") has been removed. If you are using this output module, please migrate to the new PulseAudio module called "pa". -- Chris Boot Sun, 21 Jan 2018 12:44:34 +0000 shairport-sync (3.1.3-1~exp1) experimental; urgency=medium Shairport Sync 3.1 introduces a new PulseAudio output module called "pa". The old module, called "pulse", is deprecated and will likely be removed in a future release. If you are using the PulseAudio output you should migrate to the new driver which, unlike the old module, supports synchronised audio. -- Chris Boot Thu, 23 Nov 2017 12:13:27 +0000