pkg-plist claims: %%SERVER_ONLY%%%%ETCDIR%%/amanda-security.conf while Makefile via CONFIGURE_ARGS claims: --with-security-file=${ETCDIR}/security.conf So, which one is it? It's the latter. Make it so. Engage! Energize!
the amanda-client-3.3.9,1 bin package is compiled to require /usr/local/etc/amanda/security.conf but does not install it(!) - so, after an upgrade of a client-only (no amanda-server installed), all backups fail.
(In reply to Gert Doering from comment #1) Short term remedy is to do this on each client: mkdir -p /usr/local/etc/amanda touch /usr/local/etc/amanda/security.conf I hope the maintainer decides on whether this files should be named amanda-security.conf or security.conf, and arranges for this file to be created iff(!) it doesn't exist on the clients.
non-committers are not assignee's/assigned, request maintainer feedback instead. It appears 'amanda-security.conf' is the canonical name for the file [1], and is the filename that is used/isntalled by the build system (the port does not manually install it with a custom name). I would suggest in the interests of user experience that the 'default' and well-known filename be used rather than a custom name. [1] https://wiki.zmanda.com/man/amanda-security.conf.5.html
Maintainer timeout
A commit references this bug: Author: riggs Date: Thu Apr 12 19:41:15 UTC 2018 New revision: 467194 URL: https://svnweb.freebsd.org/changeset/ports/467194 Log: Fix install location of security configuration file PR: 219665 Submitted by: Trond.Endrestol@ximalas.info Approved by: maintainer timeout Changes: head/misc/amanda-server/Makefile