[pkg-bacula-devel] Contribution

[Mario Pranjic]

On 9/16/20 10:50 AM, Mario Pranjic wrote:
> But, first thins is first... Let me figure out this config part.
> I'd like to see Bacula actually starts writing to S3 bucket and verify
> this setup works as is.
>
> Then we can agree on some next steps and how to proceed.
>
Hi,

Sorry for delay. I was busy finishing another small project.

I still play with Bacula config to get data written to S3 bucket.
At least, Bacula throws no errors on me when loading modules and
configuration so I take that as a good sign.

As for packaging of libs3 fork and cloud driver, what would be a proper
location to use?
Sven, you mentioned:
/usr/lib/bacula
/usr/include/bacula

Would that be something approved by Debian or approval is yet to be
obtained?
In other words: does it make sense to build it and package it using
these locations at this stage?

Is there any communication with Bacula Enterprise in regards to
possibility for them to let the source code for cloud driver to
community and when than might happen?

Should we do something now in regards to code for cloud driver (as we
have it now) or is it better to wait with it?

Best regards,

--
Mario.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-bacula-devel/attachments/20200918/4108aae6/attachment.sig>