mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Browse source
This commit is contained in:
interfect@b151490178830f44348aa57b77ad58c7d18e8fe7 2020-10-26 20:55:16 +00:00 • committed by admin
parent 64e7bac810
commit 730f67bcc6
1 changed files with 13 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

13
doc/forum/How_are_people_handling_the_v8_repo_upgrade__63__.mdwn Normal file
View file

@ -0,0 +1,13 @@
I noticed today when running `git annex sync` that it was unhappy with one of my remotes:
```
remote: git-annex: Repository /home/anovak/annex/.git is at unsupported version 7. Automatic upgrade exception! actually-broken.log: getSymbolicLinkStatus: does not exist (No such file or directory)
```
Digging in, it looks like that machine is running Ubuntu 20.04, which ships Git Annex 8, which *only* supports repo version 8. The rest of my machines are a mix of Ubuntu 18.04 and other Debian derivatives, which all ship older versions of Git Annex, which *can't* support repo version 8.
Is there a way for me to get out of manually installing Git Annex on every machine to upgrade everything to v8 at the same time?
And, before I've upgraded, is there a way to screw up my repo by e.g. running `git annex sync` from the newer Git Annex and pushing commits in the new format over to machines that still only speak the old format?
How are other people handling this transition where there's no repo format that's speakable by all the machines? Just upgrading everything at once and replacing the distro's git annex with a manually installed version?