[pkg-bacula-devel] Packaging private libbaculas3?

Sven Hartge sven at svenhartge.de
Mon Jun 15 17:44:59 BST 2020


On 15.06.20 18:12, Carsten Leonhardt wrote:

> I had a look at the diff between the current version on github and the
> version at bacula.org. Bacula changed the license from dual LGPL 3+/GPL
> 2+ to single LGPL 3+ (the choice was given) and added some functions and
> some small changes.
> 
> Due to the licence choice, changes cannot go back to upstream unless
> Bacula submits them themselves. I'd say that makes it a fork.
> 
> I'll prepare an ITP soonish.

OK.

I tried to play around with my old libs3.git on Salsa, bringing the new
code in line and - oh boy - was that ever a nightmare. I didn't even
push it from my local tree to Salsa, I just deleted the branch I made
out of sheer frustration.

Note on that: Bacula Systems went the lazy way to make the code compile
by silencing the compiler on buffer, string and size issues, you might
want to review the patch against that I got in my repository.

Grüße,
Sven.

-------------- 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/20200615/338608dd/attachment-0001.sig>


More information about the pkg-bacula-devel mailing list