This has been fixed in Debian with the following patch: https://salsa.debian.org/debian/cyrus- sasl2/-/commit/0be440a13f438c70c5ad73ed923dc794cec65c40
The new version in Debian ships a new saslcache binary, so I am unsure if we want a merge at this point in the cycle. But we could consider shipping the fix in resolute. Full changelog of the latest 2 Debian revisions: cyrus-sasl2 (2.1.28+dfsg1-11) unstable; urgency=medium * Team upload [ Praveen Arimbrathodiyil ] * Update file sasl2-bin.saslauthd.service [ Peter Wienemann ] * d/rules: Build and install saslcache (Closes: #1132010) -- Bastian Germann <[email protected]> Sat, 04 Apr 2026 21:56:58 +0200 cyrus-sasl2 (2.1.28+dfsg1-10) unstable; urgency=medium * Team upload * d/copyright: Remove superfluous asterisks * Add compatibility for gcc 15 (Closes: #1096495) [ Helmut Grohne ] * Fix FTCBFS: Annotate python3-sphinx dependency :native (Closes: #1101329) -- Bastian Germann <[email protected]> Mon, 06 Oct 2025 22:34:22 +0200 ** Tags added: server-triage-discuss -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2098601 Title: saslauthd.service should take PIDFile path from /etc/default/saslauthd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2098601/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
