Expand explanation of borg version pinning
In our install-borg role, we try to pin to a specific version of the software, but that's not always possible (case in point, the version of Python on Ubuntu 24.04 LTS won't work with the version of borg we're running elsewhere). Clarify this in the introductory comment. Change-Id: I4947e5cb78a14ea078ea998f43bb52673129a1cf
This commit is contained in:
@@ -1,5 +1,6 @@
|
||||
# We install into a virtualenv here for two reasons; we want a
|
||||
# specific version pinned between server and client -- borg has had
|
||||
# specific version pinned between server and client (at least as far
|
||||
# as possible with the Python versions available) -- borg has had
|
||||
# updates that required transitions so we don't want to use system
|
||||
# packages where thing might get out of sync. Secondly we want to
|
||||
# keep as few things as possible to go wrong when running backups.
|
||||
|
||||
Reference in New Issue
Block a user