summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/GitPython/hardcode-git-path.patch
diff options
context:
space:
mode:
authorTobias Geerinckx-Rice <tobias.geerinckx.rice@gmail.com>2016-01-07 23:43:52 +0100
committerTobias Geerinckx-Rice <tobias.geerinckx.rice@gmail.com>2016-01-08 01:36:32 +0100
commitf036c069ed56db36f22a9ba01fd4042a1dc2373a (patch)
tree064424634cff0308631f34402d468444f48ed285 /pkgs/development/python-modules/GitPython/hardcode-git-path.patch
parent3d3ccd4a1500c9e7acc3e3c377edcc5bbd0618f3 (diff)
borgbackup: 0.27.0 -> 0.29.0
‘When upgrading to 0.29.0 you need to upgrade client as well as server installations due to the locking and commandline interface changes otherwise you’ll get an error msg about a RPC protocol mismatch or a wrong commandline option. if you run a server that needs to support both old and new clients, it is suggested that you have a “borg-0.28.2” and a “borg-0.29.0” command. clients then can choose via e.g. “borg –remote-path=borg-0.29.0 ...”.’ ‘The default waiting time for a lock changed from infinity to 1 second for a better interactive user experience. if the repo you want to access is currently locked, borg will now terminate after 1s with an error message. if you have scripts that shall wait for the lock for a longer time, use –lock-wait N (with N being the maximum wait time in seconds).’ All changes: http://borgbackup.readthedocs.org/en/stable/changes.html
Diffstat (limited to 'pkgs/development/python-modules/GitPython/hardcode-git-path.patch')
0 files changed, 0 insertions, 0 deletions