Created attachment 229842 [details] GIT diff In order to enable cloud functionalities Bacula needs a separate S3 library.
So not only did I let this languish for many months, I now neglet to include the PR in the commit. My apologies. https://cgit.freebsd.org/ports/commit/?id=661403a5a14390fa0210f3b0a60c7d8c28cdc43a
(In reply to ml from comment #0) Is there any reason not to rename this port to bacula-libs3 instead of bacula11-libs3? I ask because I built bacula13-server and it works. I'm tempted
(In reply to Dan Langille from comment #2) *Sigh* It's so hard to find decent documentation on Bacula community edition cloud functionalities... Last note about this I see is in 9.6 release notes, which is said to now use the latest libs3 version. Nothing in release notes for 11 o 13. So yes, it's possible it works, but I haven't tested it.
(In reply to ml from comment #3) Bacula 9 does not build with the S3 libs, so I'll do just 9 and 13 Thanks
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=dd8d93a918b9f922883323abb08fb352a1e1310a commit dd8d93a918b9f922883323abb08fb352a1e1310a Author: Dan Langille <dvl@FreeBSD.org> AuthorDate: 2023-09-10 12:45:08 +0000 Commit: Dan Langille <dvl@FreeBSD.org> CommitDate: 2023-09-10 14:13:59 +0000 sysutils/bacula11-libs3: move to sysutils/bacula-libs3 This libray builds with both Bacula 11 and Bacula 13. New commits to those ports are coming soon. PR: 260170 MOVED | 1 + sysutils/Makefile | 2 +- sysutils/{bacula11-libs3 => bacula-libs3}/Makefile | 0 sysutils/{bacula11-libs3 => bacula-libs3}/distinfo | 0 sysutils/{bacula11-libs3 => bacula-libs3}/files/patch-GNUmakefile | 0 sysutils/{bacula11-libs3 => bacula-libs3}/pkg-descr | 0 sysutils/{bacula11-libs3 => bacula-libs3}/pkg-plist | 0 7 files changed, 2 insertions(+), 1 deletion(-)