FS#78916 - [exim] Match Arch's path for the saslauthd socket

Attached to Project: Arch Linux
Opened by Giovanni Bottaro (bgiovanni) - Wednesday, 28 June 2023, 18:07 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:18 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No


It seems like the saslauthd socket path might be hardcoded at build time and can't be subsequently changed at runtime.
Currently Arch has the saslauthd socket path option commented out in the relevant build configuration file.

The attached patch adds the saslauthd socket path and matches it with the default one used by Arch's saslauthd package.
This task depends upon

Closed by  Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:18 GMT
Reason for closing:  Moved
Additional comments about closing:  https://gitlab.archlinux.org/archlinux/p ackaging/packages/exim/issues/4
Comment by loqs (loqs) - Wednesday, 28 June 2023, 18:56 GMT
/var/run is a symlink to ../run so perhaps the path should use /run instead of the /var/run compatibility symlink and the cyrus-sasl package updated to match?
Comment by Giovanni Bottaro (bgiovanni) - Wednesday, 28 June 2023, 19:36 GMT
I didn't know about it! Sure, I guess it's better to use /run rather than its symbolic link in /var. I have updated the patch (attached to this post) accordingly.
Thank you for the tip!

About cyrus-sasl, I see that in the tmpfiles.conf file they're creating the saslauthd folder in /run, however in the PKGBUILD they're handing to ./configure '--with-saslauthd=/var/run/saslauthd'. So yes, I think that for consistency's sake it should be '--with-saslauthd=/run/saslauthd' instead.

EDIT: Oh, I see it's already an open issue. ( https://bugs.archlinux.org/task/78402)