Bug 260171 - sysutils/bacula11-server: enable cloud functionalities
Summary: sysutils/bacula11-server: enable cloud functionalities
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Dan Langille
URL:
Keywords:
Depends on: 260170
Blocks:
  Show dependency tree / graph
 
Reported: 2021-12-02 15:57 UTC by ml
Modified: 2023-09-10 14:18 UTC (History)
2 users (show)

See Also:
bugzilla: maintainer-feedback? (dvl)

Attachments
GIT diff (1.37 KB, patch)
2021-12-02 15:57 UTC, ml 		no flags Details | Diff
Revised patch (1.58 KB, patch)
2022-07-13 14:49 UTC, ml 		no flags Details | Diff
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ml 2021-12-02 15:57:07 UTC 
Created attachment 229843 [details]
GIT diff

Bacula has the ability to use cloud object storage (S3) as backend, but this is currently not enabled in the port.
This patch adds this support as an (off by default) option.
Notice this will bring another new port: sysutils/bacula11-libs3.
Comment 1 ml 2022-07-13 14:49:54 UTC 
Created attachment 235238 [details]
Revised patch

Previous patch had port version hardcoded and would not work with latetest upgrade.
Now %%LIB_VERSION%% is used.
Comment 2 Dan Langille freebsd_committer freebsd_triage 2023-09-01 16:30:46 UTC 
Is https://www.freshports.org/sysutils/bacula11-libs3/ relevant?

I have not reviewed the patch. I’m on my phone.
Comment 3 ml 2023-09-01 17:29:43 UTC 
(In reply to Dan Langille from comment #2)

Hi Dan.

I had filled two bugs:
_ one for a new port: bacula11-libs3;
_ one to enable S3 support in bacula-server.

I see bacula11-libs3 was commited, but it's completely useless, unless bacula-server supports it.

I've been using this for a long time with no problems; OTOH, no one else showed interest, so I can't say it was widely tested.
Comment 4 Dan Langille freebsd_committer freebsd_triage 2023-09-09 14:48:24 UTC 
(In reply to ml from comment #3)

FYI, the attached patch contained trailing ^M on each line. I stripped them via :

perl -pi -e "s:^M::g" ~/tmp/bacula-cloud

Where ^M is actually ctrl-v ctrl-m

The failing patch confounded me for a while. I tried patch -p2, still failed... Then I started looking in the .rej file and that's where the ^M was visible

No action required by you.
Comment 5 Dan Langille freebsd_committer freebsd_triage 2023-09-09 20:29:59 UTC 
I have this building with both bacula11-server and bacula13-server.

I'm tempted to rename sysutils/bacula11-libs3 to sysutils/bacula-libs3
Comment 6 commit-hook freebsd_committer freebsd_triage 2023-09-10 14:15:14 UTC 
A commit in branch main references this bug:

URL: https://cgit.FreeBSD.org/ports/commit/?id=18f5c0eb55c34fc7ecdd422b7c323746ea797a0e

commit 18f5c0eb55c34fc7ecdd422b7c323746ea797a0e
Author:     Dan Langille <dvl@FreeBSD.org>
AuthorDate: 2023-09-10 14:10:50 +0000
Commit:     Dan Langille <dvl@FreeBSD.org>
CommitDate: 2023-09-10 14:14:00 +0000

    sysutils/bacula11-server: Add S3 cloud option

    Allow a bacula-sd node to use S3 for storage

    This uses the recently added sysutils/bacula-libs3 port

    While here, also add S3 to bacula13-server
    PR:             260171

 sysutils/bacula11-server/Makefile  | 10 ++++++++--
 sysutils/bacula11-server/pkg-plist |  4 ++++
 sysutils/bacula13-server/Makefile  | 10 ++++++++--
 sysutils/bacula13-server/pkg-plist |  4 ++++
 4 files changed, 24 insertions(+), 4 deletions(-)
Comment 7 Dan Langille freebsd_committer freebsd_triage 2023-09-10 14:18:45 UTC 
Thank you