diff options
author | Joey Hess <joeyh@joeyh.name> | 2018-01-15 14:39:26 -0400 |
---|---|---|
committer | Joey Hess <joeyh@joeyh.name> | 2018-01-15 14:39:26 -0400 |
commit | 3ec28a339851c7274c91f3460bfc7d7c1b7a230e (patch) | |
tree | f6d0196c7940027fad56c99be9c645fdb004240a | |
parent | 9dcc9f151217469105184d87d90a46964deab3f8 (diff) |
response
-rw-r--r-- | doc/forum/Why_does_git_annex_does_not_want_that_file__63__/comment_1_44cd6ca1f7215395e19ce654513197a9._comment | 38 |
1 files changed, 38 insertions, 0 deletions
diff --git a/doc/forum/Why_does_git_annex_does_not_want_that_file__63__/comment_1_44cd6ca1f7215395e19ce654513197a9._comment b/doc/forum/Why_does_git_annex_does_not_want_that_file__63__/comment_1_44cd6ca1f7215395e19ce654513197a9._comment new file mode 100644 index 000000000..709bc80fd --- /dev/null +++ b/doc/forum/Why_does_git_annex_does_not_want_that_file__63__/comment_1_44cd6ca1f7215395e19ce654513197a9._comment @@ -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! +"""]] |