installation.rst 9.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246
  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 `Vivid 15.04 (backport PPA)`_ ``apt install borgbackup``
  34. Ubuntu `Trusty 14.04 (backport PPA)`_ ``apt install borgbackup``
  35. ============ ============================================= =======
  36. .. _[community]: https://www.archlinux.org/packages/?name=borg
  37. .. _stretch: https://packages.debian.org/stretch/borgbackup
  38. .. _unstable/sid: https://packages.debian.org/sid/borgbackup
  39. .. _pkgsrc: http://pkgsrc.se/sysutils/py-borgbackup
  40. .. _Xenial 16.04: https://launchpad.net/ubuntu/xenial/+source/borgbackup
  41. .. _Wily 15.10 (backport PPA): https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/borgbackup
  42. .. _Vivid 15.04 (backport PPA): https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/borgbackup
  43. .. _Trusty 14.04 (backport PPA): https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/borgbackup
  44. .. _.nix file: https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/backup/borg/default.nix
  45. .. _Brew cask: http://caskroom.io/
  46. Please ask package maintainers to build a package or, if you can package /
  47. submit it yourself, please help us with that! See :issue:`105` on
  48. github to followup on packaging efforts.
  49. If a package is available, it might be interesting to check its version
  50. and compare that to our latest release and review the :doc:`changes`.
  51. .. _pyinstaller-binary:
  52. Standalone Binary
  53. -----------------
  54. |project_name| binaries (generated with `pyinstaller`_) are available
  55. on the releases_ page for the following platforms:
  56. * **Linux**: glibc >= 2.13 (ok for most supported Linux releases)
  57. * **Mac OS X**: 10.10 (unknown whether it works for older releases)
  58. * **FreeBSD**: 10.2 (unknown whether it works for older releases)
  59. To install such a binary, just drop it into a directory in your ``PATH``,
  60. make borg readable and executable for its users and then you can run ``borg``::
  61. sudo cp borg-linux64 /usr/local/bin/borg
  62. sudo chown root:root /usr/local/bin/borg
  63. sudo chmod 755 /usr/local/bin/borg
  64. Note that the binary uses /tmp to unpack |project_name| with all dependencies. It will fail if /tmp has not enough free space or is mounted with the ``noexec`` option. 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.2.2. 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. llfuse has been tested in version 0.40.x,
  84. 0.41.x might also work, >= 0.42.x does not work (due to API changes in
  85. llfuse). FUSE >= 2.8.0 is required for llfuse 0.40.
  86. In the following, the steps needed to install the dependencies are listed for a
  87. selection of platforms. If your distribution is not covered by these
  88. instructions, try to use your package manager to install the dependencies. On
  89. FreeBSD, you may need to get a recent enough OpenSSL version from FreeBSD
  90. ports.
  91. After you have installed the dependencies, you can proceed with steps outlined
  92. under :ref:`pip-installation`.
  93. Debian / Ubuntu
  94. +++++++++++++++
  95. Install the dependencies with development headers::
  96. sudo apt-get install python3 python3-dev python3-pip python-virtualenv \
  97. libssl-dev openssl \
  98. libacl1-dev libacl1 \
  99. liblz4-dev liblz4-1 \
  100. build-essential
  101. sudo apt-get install libfuse-dev fuse pkg-config # optional, for FUSE support
  102. In case you get complaints about permission denied on ``/etc/fuse.conf``: on
  103. Ubuntu this means your user is not in the ``fuse`` group. Add yourself to that
  104. group, log out and log in again.
  105. Fedora / Korora
  106. +++++++++++++++
  107. Install the dependencies with development headers::
  108. sudo dnf install python3 python3-devel python3-pip python3-virtualenv
  109. sudo dnf install openssl-devel openssl
  110. sudo dnf install libacl-devel libacl
  111. sudo dnf install lz4-devel
  112. sudo dnf install gcc gcc-c++
  113. sudo dnf install fuse-devel fuse pkgconfig # optional, for FUSE support
  114. Mac OS X
  115. ++++++++
  116. Assuming you have installed homebrew_, the following steps will install all the
  117. dependencies::
  118. brew install python3 lz4 openssl
  119. pip3 install virtualenv
  120. For FUSE support to mount the backup archives, you need at least version 3.0 of
  121. FUSE for OS X, which is available as a pre-release_.
  122. .. _pre-release: https://github.com/osxfuse/osxfuse/releases
  123. Cygwin
  124. ++++++
  125. .. note::
  126. Running under Cygwin is experimental and has only been tested with Cygwin
  127. (x86-64) v2.1.0.
  128. Use the Cygwin installer to install the dependencies::
  129. python3 python3-setuptools
  130. python3-cython # not needed for releases
  131. binutils gcc-core
  132. libopenssl openssl-devel
  133. liblz4_1 liblz4-devel # from cygwinports.org
  134. git make openssh
  135. You can then install ``pip`` and ``virtualenv``::
  136. easy_install-3.4 pip
  137. pip install virtualenv
  138. In case the creation of the virtual environment fails, try deleting this file::
  139. /usr/lib/python3.4/__pycache__/platform.cpython-34.pyc
  140. .. _pip-installation:
  141. Using pip
  142. ~~~~~~~~~
  143. Virtualenv_ can be used to build and install |project_name| without affecting
  144. the system Python or requiring root access. Using a virtual environment is
  145. optional, but recommended except for the most simple use cases.
  146. .. note::
  147. If you install into a virtual environment, you need to **activate** it
  148. first (``source borg-env/bin/activate``), before running ``borg``.
  149. Alternatively, symlink ``borg-env/bin/borg`` into some directory that is in
  150. your ``PATH`` so you can just run ``borg``.
  151. This will use ``pip`` to install the latest release from PyPi::
  152. virtualenv --python=python3 borg-env
  153. source borg-env/bin/activate
  154. # install Borg + Python dependencies into virtualenv
  155. pip install 'llfuse<0.41' # optional, for FUSE support
  156. # 0.41 and 0.41.1 have unicode issues at install time
  157. pip install borgbackup
  158. To upgrade |project_name| to a new version later, run the following after
  159. activating your virtual environment::
  160. pip install -U borgbackup
  161. .. _git-installation:
  162. Using git
  163. ~~~~~~~~~
  164. This uses latest, unreleased development code from git.
  165. While we try not to break master, there are no guarantees on anything. ::
  166. # get borg from github
  167. git clone https://github.com/borgbackup/borg.git
  168. virtualenv --python=python3 borg-env
  169. source borg-env/bin/activate # always before using!
  170. # install borg + dependencies into virtualenv
  171. pip install sphinx # optional, to build the docs
  172. pip install 'llfuse<0.41' # optional, for FUSE support
  173. # 0.41 and 0.41.1 have unicode issues at install time
  174. cd borg
  175. pip install -r requirements.d/development.txt
  176. pip install -e . # in-place editable mode
  177. # optional: run all the tests, on all supported Python versions
  178. # requires fakeroot, available through your package manager
  179. fakeroot -u tox
  180. .. note:: As a developer or power user, you always want to use a virtual environment.