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

response

Browse source
This commit is contained in:
Joey Hess 2018-01-15 14:39:26 -04:00
parent 37d7a1b768
commit 56b56033a4
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 38 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

38
doc/forum/Why_does_git_annex_does_not_want_that_file__63__/comment_1_44cd6ca1f7215395e19ce654513197a9._comment Normal file
View file

@ -0,0 +1,38 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2018-01-15T18:20:20Z"
content="""
The problem is that you have the repository in two groups.
The way that `standard` works is that the repository has to be in
exactly one group and then it will use the preferred content for that
group. It does not know what to do when there are two groups being
combined.
Solution for you is to run:
git annex wanted . anything
Since backup repositories have a copy of every file, matching anything is
what you want it to do. Since it's also in the archive group, other archive
repositories will treat it as an archive too, so once a file reaches your
combo backup and archive repository, it will be removed from other
archives.
Of course, you could also OR the preferred content expression for backup
with the preferred content expression for archive, but that would have the
same result since "anything OR archive" matches anything.
But we can't just OR the two preferred content expressions for two groups
in general. Consider the client and archive preferred content expressions:
(include=* and ((exclude=*/archive/* and exclude=archive/*) or (not (copies=archive:1 or copies=smallarchive:1)))) or approxlackingcopies=1
(not (copies=archive:1 or copies=smallarchive:1)) or approxlackingcopies=1
These are contradictory when a repository is in both the client and archive
groups; the client doesn't want anything that's in an archive, but if the
repository is both a client and an archive, it doesn't want any content
that it has!
"""]]