00_README.txt 2.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778
  1. Binary BorgBackup builds
  2. ========================
  3. The binaries are supposed to work on the specified platform without installing
  4. any dependencies.
  5. Download the correct files
  6. --------------------------
  7. amd64 / x86_64 architecture
  8. ~~~~~~~~~~~~~~~~~~~~~~~~~~~
  9. borg-linux-glibc236 Linux (built on Debian 12 "Bookworm" with glibc 2.36)
  10. borg-linux-glibc231 Linux (built on Debian 11 "Bullseye" with glibc 2.31)
  11. Note: you can also try them on other Linuxes with other glibc
  12. versions - as long as the glibc is compatible, they will work.
  13. If it doesn't work, try a borg 1.4.x or 1.2.x binary.
  14. borg-macos1012 macOS (built on macOS Sierra 10.12 with latest macFUSE from brew)
  15. To avoid signing issues download the file via command line OR
  16. remove the "quarantine" attribute after downloading:
  17. $ xattr -dr com.apple.quarantine borg-macos.tgz
  18. borg-freebsd14 FreeBSD (built on FreeBSD 14)
  19. *.tgz similar to above, but built as a directory with files,
  20. not as a single self-extracting binary.
  21. *.asc GnuPG signatures for *
  22. Verifying your download
  23. -----------------------
  24. Please check the GPG signature to make sure you received the binary as I have
  25. built it.
  26. To check the GPG signature, download both the binary and the corresponding
  27. *.asc file and then (on the shell) type, e.g.:
  28. gpg --recv-keys 9F88FB52FAF7B393
  29. gpg --verify borg-freebsd14.asc borg-freebsd14
  30. The files are signed by:
  31. Thomas Waldmann <tw@waldmann-edv.de>
  32. GPG key fingerprint: 6D5B EF9A DD20 7580 5747 B70F 9F88 FB52 FAF7 B393
  33. My fingerprint is also in the footer of all my borgbackup mailing list posts.
  34. Installing
  35. ----------
  36. It is suggested that you rename or symlink the binary to just "borg".
  37. On UNIX-like platforms, /usr/local/bin/ or ~/bin/ is a nice place for it,
  38. but you can invoke it from every place by giving a full path to it.
  39. Make sure the file is readable and executable (chmod +rx borg on UNIX-like
  40. platforms).
  41. Reporting issues
  42. ----------------
  43. If you find issues, please open a ticket on our issue tracker:
  44. https://github.com/borgbackup/borg/issues/
  45. There, please give:
  46. - the version number (it is displayed if you invoke borg -V)
  47. - the sha256sum of the binary
  48. - a good description of what the issue is
  49. - a good description of how to reproduce your issue
  50. - a traceback with system info (if you have one)
  51. - your precise platform (CPU, 32/64bit?), OS, distribution, release
  52. - your python and (g)libc version