Daniel Markstedt

@sfranzis A [stable 3.2.0 release](https://github.com/Netatalk/netatalk/releases/tag/netatalk-3-2-0) is now available. Do you think it would be possible to upgrade your setup to this version? We have a new manual appendix with build...

Well noted. I have notified the FreeBSD ports maintainer for netatalk3 about the new release, so unless he runs into some roadblocks the port should be updated shortly.

The FreeBSD port has been updated to 3.2.0 https://www.freshports.org/net/netatalk3/

Thanks for letting us know! Let me close this ticket for now. If you run into new reproducible issues, don't hesitate to throw up a new ticket.

In netatalk3 this may be hard to automate with the current setup due to the rigidity of autotools. We can't bootstrap when a single *.in file is missing, so we...

@dgsga There has been an interesting development in this space lately. The now-infamous xz backdoor attack that affected Debian and Red Hat in particular involved seeding a malicious autotools m4...

@dgsga I would be up for postponing this until after we remove the autotools build system. What do you think?

@dgsga Tentatively removing from the 3.2.0 scope. Please add it back if you disagree. :)

It's not wrong. My NetBSD 9.3 VM has both shared libraries... ``` localhost$ find / -name libintl.so.1 2> /dev/null /usr/lib/libintl.so.1 localhost$ find / -name libintl.so.8 2> /dev/null /usr/pkg/lib/libintl.so.8 ```

Akin to https://community.ibm.com/community/user/power/discussion/libintlalibintlso8-conflict It seems the NetBSD OS has one stock gettext library, and then pkg installs another one as a dependency for dbus-glib, and the linker finds both... :/...