On July 24, 2017 8:39:48 PM GMT+02:00, "Tomas Martišius" <[email protected]> wrote: >2017 m. liepa 24 d., pirmadienis 19:25:20 UTC+3, Tom Weber rašė: >> Am Montag, den 24.07.2017, 08:58 -0700 schrieb Tomas Martišius: >> > >> > May be you find solution for this problem? >> >> actually I'm rather disappointed that none of the developers seems to >> care about such a severe bug. Did you open a bug report in appropriate place ? Personaly I didn't see a number reported here
>I am somehow not surprised by this, because Bareos GmbH & Co., in the >some way as Bacula Systems S.A., makes from that business, and to fix >open source version is in low priority. > Which is complete non sense and wrong. All patches are there on github truly open. They are committed before you have the shbs riptio binaries available. >> >> like 30 minutes ago I might have found something. >> >> do you happen to have >> signature = SHA1 >> in your fileset definition? >> Still it was not clear to me from where you pick your binaries. >> change this to MD5 and try again. >> >> Tom > btw I never seem this kind of trouble (I'm using openSUSE as os) >Thanks for solution. With MD5 it seems all works right. But trust in >the project has fallen. > >Best regards, > >Tomas sha1 or md5 are used for checksum calculation. I don't think they have something to do with internal content of files. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
