while Makefile via CONFIGURE_ARGS claims:
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
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 , 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.
A commit references this bug:
Date: Thu Apr 12 19:41:15 UTC 2018
New revision: 467194
Fix install location of security configuration file
Submitted by: Trond.Endrestol@ximalas.info
Approved by: maintainer timeout