netatalk 4.0.8 (new formula)

[rdmark]

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>? (see caveat below)

---

Please note that brew audit --new netatalk throws non-compliance as per the below. However, the native macOS berkeley-db and openldap libraries are both unusable: The former lacks required symbols, and the latter (represented by LDAP.Framework) isn't fork safe while netatalk is a forking application.

brew audit --new netatalk                                                  
netatalk
  * Dependency 'berkeley-db' is provided by macOS; please replace 'depends_on' with 'uses_from_macos'.
  * Dependency 'openldap' is provided by macOS; please replace 'depends_on' with 'uses_from_macos'.

[github-actions]

Thanks for contributing to Homebrew! 🎉 It looks like you're having trouble with a CI failure. See our contribution guide for help. You may be most interested in the section on dealing with CI failures. You can find the CI logs in the Checks tab of your pull request.

[rdmark]

The remaining CI failures are triggered by the brew audit checks, AFAICT.

As mentioned in the summary, complying with them and using the macOS supplied libraries will break the software. Can these CI failures be ignored?

[carlocab]

Thanks for the PR; a few comments.

[EricFromCanada]

I've filed a PR to fix the launchd item not being able to stop the netatalk process: Netatalk/netatalk#1859

For now, I'd suggest adding a patch stanza to integrate the above fix, unless the next netatalk release is imminent.

Side note: what's it take to get its user authentication working in modern macOS? With the server running on Sonoma on M3 and logging enabled in afp.conf, clicking "Connect As…" on another Mac and entering my credentials just logs (info:ad): DHX2: PAM_Error: authentication error.

[rdmark]

@EricFromCanada Thanks for filing the PR. Let me follow up over there. The next stable netatalk release is about a week out.

Authentication should work out of the box on any host, as long as the Mac client is running Mac OS 8.6, 9.x, or any version of OSX / macOS. What OS is the client Mac running?

My first guess would be some kind of PAM library failure on Sonoma. Alternatively, you're using a password that the DHX2 UAM doesn't like for some reason. If you like, you can open up a Discussion thread over at the netatalk GitHub project and we can dig into it.

[rdmark]

@EricFromCanada Patch applied to the formula. The brew services control works so much better this way. Great idea!

[carlocab]

Thanks!

[github-actions]

@carlocab has requested bottles to be published to this PR.