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

followup and closd

Browse source
This commit is contained in:
Joey Hess 2017-12-11 13:09:28 -04:00
parent 70344d25c0
commit 0ef99f3578
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 29 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/bugs/issue_with_syncing_between_v5_and_v6_repos.mdwn
View file

@ -108,3 +108,5 @@ $ git annex upgrade
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders) ### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Yes Yes
> I don't consider this a bug, so [[done]] --[[Joey]]

27
doc/bugs/issue_with_syncing_between_v5_and_v6_repos/comment_1_4c3468a17c454cb344b3a944c0f71889._comment Normal file
View file

@ -0,0 +1,27 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2017-12-11T16:59:52Z"
content="""
The problem is much simpler than that: Files that are unlocked in v6
repositories are not treated as annexed files at all in v5 repositories.
You cannot `git annex get` them or anything.
So, the simpler reproduction recipe is to `git add` a file to a v6
repository and then in a v5 clone, `git annex get` and it won't say
anything, because that's not an annexed file as far as it's concerned.
It's also very easy to deal with this situation if you've gotten into it --
all you need to do is `git annex lock` the files in a v6 repository and
commit it, and then the v5 repository will be able to access them.
A good way to avoid the problem while still using the features of v6
in your v6 repository is to run `git annex adjust --unlock` in there.
Then commits of unlocked files will automatically be translated to locked
files that are compatible with v5.
git-annex v5 can't possibly treat v6 unlocked files as annexed files.
It could warn about the problem, but this would complicate it with needing
to check if every non-symlink file is a v6 unlocked file. I don't feel
this problem warrants that complication.
"""]]