From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] shairport-sync: Update to version 5.6.3
Date: Wed, 11 Nov 2026 13:44:37 +0100 [thread overview]
Message-ID: <20261111124438.3198459-4-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20261111124438.3198459-1-adolf.belka@ipfire.org>
- Update from version 5.6.2 to 5.6.3
- No change in rootfile
- Changelog
5.6.3
Bug Fixes
Register the libsoxr exit handler before Shairport Sync's own to ensure it
runs after the main exit handler on program exit.
Remote Control: Allow VolumeUp/VolumeDown commands to be sent over DACP in
Classic AirPlay.
D-Bus/MPRIS: prevent a data access race by exporting interface objects
before the bus name becomes visible to ensure the objects are visible
when the bus name appears.
Metadata: Ensure stale connection information is not retained on new
connections.
MPRIS: Set the MPRIS Rate property to 1.0.
If frames are skipped at the start of play, use the timing of the first
frame that is actually played rather than that of a skipped frame.
tinysvcmdns: set multicast Time-To-Live (TTL) to 255. The default
multicast TTL is usually 1, which some access points discard.
Note: tinysvcdns is still deprecated for security reasons. This bug fix
does not change that.
D-Bus/MPRIS: when the volume changes, send the new level rather than the
previous (stale) value.
Mac/Homebrew: Fix a build error on macOS by removing a stray from
get_info_response.xml.
Enhancements
Add a "metadata" mDNS backend for apps with their own responder. This new
backend sends mDNS information as metadata with thessnc / svrg type
and code.
Add an optional D-Bus name tag to enable multiple Shairport Sync instances
to have distinguished D-Bus bus names.
Other Changes
Move mDNS and dns-sd files into a separate subdirectory.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
lfs/shairport-sync | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lfs/shairport-sync b/lfs/shairport-sync
index af68ab0b4..8cfae13b9 100644
--- a/lfs/shairport-sync
+++ b/lfs/shairport-sync
@@ -26,7 +26,7 @@ include Config
SUMMARY = An AirPlay audio player
-VER = 5.6.2
+VER = 5.6.3
THISAPP = shairport-sync-$(VER)
DL_FILE = $(THISAPP).tar.gz
@@ -34,7 +34,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = shairport-sync
-PAK_VER = 22
+PAK_VER = 23
DEPS = alsa avahi ffmpeg libdaemon libplist nqptp soxr
@@ -48,7 +48,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = 6017dd15818ae3f561d8f2a6572bf9368f970d29ec394e7e3041726474e8fb66a9a421aac36159ee8287c03ddb06a185688b913602dbef969eb3906f7654aaa5
+$(DL_FILE)_BLAKE2 = 1c86e3b97d3f41f1e6adb59796f943e9e390f2928fe7f2fe45144cf9112ce6c040b74c1f0a8bb1e766b97dcf70e876cbe50ad3dc86b506e5a57e799e2488e33b
install : $(TARGET)
--
2.56.0
next prev parent reply other threads:[~2026-11-11 12:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 12:44 [PATCH] core207: Ship intel-micrcode Adolf Belka
2026-11-11 12:44 ` [PATCH] git: Update to version 2.56.1 Adolf Belka
2026-11-11 12:44 ` [PATCH] intel-microcode: Update to version 20261110 Adolf Belka
2026-11-11 12:44 ` Adolf Belka [this message]
2026-11-11 12:44 ` [PATCH] vim: Update to version 9.2.1320 Adolf Belka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261111124438.3198459-4-adolf.belka@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox