Hi Kern,
Thanks very much. At the moment the Sourceforge site still shows the
sig file as the old date and it still comes up as a Bad signature (fresh
download of both files). I also cleared the cache in my browser in case
that was causing a problem but no change.
Not sure if there is a delay
Hello,
Yes, I did update the binary since the version had an annoying typo in
it, and as you found out, I forgot to release a new signature file.
Sorry for the inconvenience. I am really please to see people checking
it. Please continue to do so. I have now updated the source code
signature
Hi Adolf,
I can offer you the md5sum of the tar.gz file so you can compare it to
yours using md5sum-command:
-bash-4.1$ md5sum bacula-7.4.4.tar.gz
*aed11c1eef1198ffc76c6fca55cea3ad* bacula-7.4.4.tar.gz
Best regards,
Daniel
Am 26.11.2016 um 11:30 schrieb Adolf Belka:
Hi All,
Can anyone help
Hi All,
Can anyone help on this. The bacula-7.4.4.tar.gz file still has a
modification date after the signature file so still getting a bad
signature result from it.
I suspect the file is probably OK but the whole point of doing the
signature check is to get confirmation that the file on the
Hello,
We are working on it. Many of the binaries are already prepared,
but the project is being held up because I must first finish an
important programming task, then organize the upload and the hard
part is making both deb and rpm based repos (probably
