installation.rst 8.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244
  1. .. include:: global.rst.inc
  2. .. _installation:
  3. Installation
  4. ============
  5. There are different ways to install |project_name|:
  6. - :ref:`distribution-package` - easy and fast if a package is
  7. available from your distribution.
  8. - :ref:`pyinstaller-binary` - easy and fast, we provide a ready-to-use binary file
  9. that comes bundled with all dependencies.
  10. - :ref:`source-install`, either:
  11. - :ref:`pip-installation` - installing a source package with pip needs
  12. more installation steps and requires all dependencies with
  13. development headers and a compiler.
  14. - :ref:`git-installation` - for developers and power users who want to
  15. have the latest code or use revision control (each release is
  16. tagged).
  17. .. _distribution-package:
  18. Distribution Package
  19. --------------------
  20. Some distributions might offer a ready-to-use ``borgbackup``
  21. package which can be installed with the package manager. As |project_name| is
  22. still a young project, such a package might be not available for your system
  23. yet.
  24. ============ ============================================= =======
  25. Distribution Source Command
  26. ============ ============================================= =======
  27. Arch Linux `[community]`_ ``pacman -S borg``
  28. Debian `stretch`_, `unstable/sid`_ ``apt install borgbackup``
  29. NetBSD `pkgsrc`_ ``pkg_add py-borgbackup``
  30. NixOS `.nix file`_ N/A
  31. OS X `Brew cask`_ ``brew cask install borgbackup``
  32. Ubuntu `Xenial 16.04`_, `Wily 15.10 (backport PPA)`_ ``apt install borgbackup``
  33. Ubuntu `Trusty 14.04 (backport PPA)`_ ``apt install borgbackup``
  34. ============ ============================================= =======
  35. .. _[community]: https://www.archlinux.org/packages/?name=borg
  36. .. _stretch: https://packages.debian.org/stretch/borgbackup
  37. .. _unstable/sid: https://packages.debian.org/sid/borgbackup
  38. .. _pkgsrc: http://pkgsrc.se/sysutils/py-borgbackup
  39. .. _Xenial 16.04: https://launchpad.net/ubuntu/xenial/+source/borgbackup
  40. .. _Wily 15.10 (backport PPA): https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/borgbackup
  41. .. _Trusty 14.04 (backport PPA): https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/borgbackup
  42. .. _.nix file: https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/backup/borg/default.nix
  43. .. _Brew cask: http://caskroom.io/
  44. Please ask package maintainers to build a package or, if you can package /
  45. submit it yourself, please help us with that! See :issue:`105` on
  46. github to followup on packaging efforts.
  47. If a package is available, it might be interesting to check its version
  48. and compare that to our latest release and review the :doc:`changes`.
  49. .. _pyinstaller-binary:
  50. Standalone Binary
  51. -----------------
  52. |project_name| binaries (generated with `pyinstaller`_) are available
  53. on the releases_ page for the following platforms:
  54. * **Linux**: glibc >= 2.13 (ok for most supported Linux releases)
  55. * **Mac OS X**: 10.10 (unknown whether it works for older releases)
  56. * **FreeBSD**: 10.2 (unknown whether it works for older releases)
  57. To install such a binary, just drop it into a directory in your ``PATH``,
  58. make borg readable and executable for its users and then you can run ``borg``::
  59. sudo cp borg-linux64 /usr/local/bin/borg
  60. sudo chown root:root /usr/local/bin/borg
  61. sudo chmod 755 /usr/local/bin/borg
  62. Note that the binary uses /tmp to unpack |project_name| with all dependencies.
  63. It will fail if /tmp has not enough free space or is mounted with the ``noexec`` option.
  64. You can change the temporary directory by setting the ``TEMP`` environment variable before running |project_name|.
  65. If a new version is released, you will have to manually download it and replace
  66. the old version using the same steps as shown above.
  67. .. _pyinstaller: http://www.pyinstaller.org
  68. .. _releases: https://github.com/borgbackup/borg/releases
  69. .. _source-install:
  70. From Source
  71. -----------
  72. Dependencies
  73. ~~~~~~~~~~~~
  74. To install |project_name| from a source package (including pip), you have to install the
  75. following dependencies first:
  76. * `Python 3`_ >= 3.4.0. Even though Python 3 is not the default Python version on
  77. most systems, it is usually available as an optional install.
  78. * OpenSSL_ >= 1.0.0
  79. * libacl_ (that pulls in libattr_ also)
  80. * liblz4_
  81. * some Python dependencies, pip will automatically install them for you
  82. * optionally, the llfuse_ Python package is required if you wish to mount an
  83. archive as a FUSE filesystem. FUSE >= 2.8.0 is required for llfuse.
  84. In the following, the steps needed to install the dependencies are listed for a
  85. selection of platforms. If your distribution is not covered by these
  86. instructions, try to use your package manager to install the dependencies. On
  87. FreeBSD, you may need to get a recent enough OpenSSL version from FreeBSD
  88. ports.
  89. After you have installed the dependencies, you can proceed with steps outlined
  90. under :ref:`pip-installation`.
  91. Debian / Ubuntu
  92. +++++++++++++++
  93. Install the dependencies with development headers::
  94. sudo apt-get install python3 python3-dev python3-pip python-virtualenv \
  95. libssl-dev openssl \
  96. libacl1-dev libacl1 \
  97. liblz4-dev liblz4-1 \
  98. build-essential
  99. sudo apt-get install libfuse-dev fuse pkg-config # optional, for FUSE support
  100. In case you get complaints about permission denied on ``/etc/fuse.conf``: on
  101. Ubuntu this means your user is not in the ``fuse`` group. Add yourself to that
  102. group, log out and log in again.
  103. Fedora / Korora
  104. +++++++++++++++
  105. Install the dependencies with development headers::
  106. sudo dnf install python3 python3-devel python3-pip python3-virtualenv
  107. sudo dnf install openssl-devel openssl
  108. sudo dnf install libacl-devel libacl
  109. sudo dnf install lz4-devel
  110. sudo dnf install gcc gcc-c++
  111. sudo dnf install fuse-devel fuse pkgconfig # optional, for FUSE support
  112. Mac OS X
  113. ++++++++
  114. Assuming you have installed homebrew_, the following steps will install all the
  115. dependencies::
  116. brew install python3 lz4 openssl
  117. pip3 install virtualenv
  118. For FUSE support to mount the backup archives, you need at least version 3.0 of
  119. FUSE for OS X, which is available as a pre-release_.
  120. .. _pre-release: https://github.com/osxfuse/osxfuse/releases
  121. Cygwin
  122. ++++++
  123. .. note::
  124. Running under Cygwin is experimental and has only been tested with Cygwin
  125. (x86-64) v2.1.0.
  126. Use the Cygwin installer to install the dependencies::
  127. python3 python3-setuptools
  128. python3-cython # not needed for releases
  129. binutils gcc-core
  130. libopenssl openssl-devel
  131. liblz4_1 liblz4-devel # from cygwinports.org
  132. git make openssh
  133. You can then install ``pip`` and ``virtualenv``::
  134. easy_install-3.4 pip
  135. pip install virtualenv
  136. In case the creation of the virtual environment fails, try deleting this file::
  137. /usr/lib/python3.4/__pycache__/platform.cpython-34.pyc
  138. .. _pip-installation:
  139. Using pip
  140. ~~~~~~~~~
  141. Virtualenv_ can be used to build and install |project_name| without affecting
  142. the system Python or requiring root access. Using a virtual environment is
  143. optional, but recommended except for the most simple use cases.
  144. .. note::
  145. If you install into a virtual environment, you need to **activate** it
  146. first (``source borg-env/bin/activate``), before running ``borg``.
  147. Alternatively, symlink ``borg-env/bin/borg`` into some directory that is in
  148. your ``PATH`` so you can just run ``borg``.
  149. This will use ``pip`` to install the latest release from PyPi::
  150. virtualenv --python=python3 borg-env
  151. source borg-env/bin/activate
  152. # install Borg + Python dependencies into virtualenv
  153. pip install 'llfuse<0.41' # optional, for FUSE support
  154. # 0.41 and 0.41.1 have unicode issues at install time
  155. pip install borgbackup
  156. To upgrade |project_name| to a new version later, run the following after
  157. activating your virtual environment::
  158. pip install -U borgbackup
  159. .. _git-installation:
  160. Using git
  161. ~~~~~~~~~
  162. This uses latest, unreleased development code from git.
  163. While we try not to break master, there are no guarantees on anything. ::
  164. # get borg from github
  165. git clone https://github.com/borgbackup/borg.git
  166. virtualenv --python=python3 borg-env
  167. source borg-env/bin/activate # always before using!
  168. # install borg + dependencies into virtualenv
  169. pip install sphinx # optional, to build the docs
  170. pip install 'llfuse<0.41' # optional, for FUSE support
  171. # 0.41 and 0.41.1 have unicode issues at install time
  172. cd borg
  173. pip install -r requirements.d/development.txt
  174. pip install -e . # in-place editable mode
  175. # optional: run all the tests, on all supported Python versions
  176. # requires fakeroot, available through your package manager
  177. fakeroot -u tox
  178. .. note:: As a developer or power user, you always want to use a virtual environment.