On 20.12.18 12:08, Kern Sibbald wrote: > I wrote this code about 2 years ago, so I think I had forgotten a > few things that are starting to come back. I do remember having to > patch libs3 to bring it more up to date, but what I did not remember > was that apparently I installed it in /usr/local. > > It appears that I downloaded libs3-20161222 from github and > installed it. This is what I have in my <bacula>/depkgs directory. > However, there might be a newer version.
I see. I threw together a version based on libs3-20161214.06a4683 from Github, adding two patches to be able to compile with a newer libcurl and to fix some buffer overflows. You can find my work here: https://salsa.debian.org/hartge-guest/libs3/ This version allows the cloud-driver to compile and link but I have not idea if it works or is safe to use. This is just a proof of concept at the current moment. The real shame is the upstream developer of libs3 stopped doing releases in 2011 and now one has to guess which commit to use. Red Hat seem to have just arbitrarily used the HEAD state of the master branch in 2016 and based their version of the libs3 package on that, same as you did, apparently. Which is why I used those commits for my version as well. Problem is: if the version one uses is too new, it again stops working. It all is a real mess, IMHO. Grüße, Sven.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
