Hello again Sven,
I have heard back from Radek, and indeed a binary file did accidentally become committed to the git repository. This is now corrected in the repo, but the 9.6.2 release does include that binary. It will not appear in the next release though.
As far as I can tell there is no GPL violation because all the source files needed to build that binary have been released, it is simply a matter of deleting the binary prior to re-distribution.
Thanks for pointing this out. If you still believe that there is a problem, please let me know.
Best regards,
Kern
Hello Sven,
I have taken a quick look, and it does not seem to me that there is any license violation here. Could you please confirm? If there is a license violation (or a potential one), please be more specific as I would like to correct that immediately.
On the other hand it does look like some binary or binaries have been committed to the git repo, and perhaps they should not be there. I have asked the developer (Radek) to look at it and let me know how to proceed.
I will get back to you after I hear from Radek.
Best regards,
Kern
On 2/26/20 7:49 PM, Sven Hartge wrote:
On 26.02.20 19:47, kern wrote:I am not the developer of the plugin, but I can assure you that my plan was to release the full source code.I will look into this and get back to you hopefully tomorrow.The createimage.sh script pulls the needed sources from GitHub and (re)builds the needed static tar, there should be no need to ship a precompiled binary inside the Bacula sources. Grüße, Sven.
_______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
_______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
