summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar alexander+gitannex@2296816092e64c93002644a8af3a4d4c9e6b21c7 <alexandergitannex@web>2016-01-25 23:21:12 +0000
committerGravatar admin <admin@branchable.com>2016-01-25 23:21:12 +0000
commit6ecc4804f94d4c096a74439bffd8f7efaca6958c (patch)
treeb19f8664277871d4d3675907caa4576fd27495c9
parent150b128f34b3c83ef1b227e4da94354c89c2e10d (diff)
-rw-r--r--doc/bugs/wanted___61___present_gets_ignored_in___39__git_annex_sync_--content__39__.mdwn18
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/bugs/wanted___61___present_gets_ignored_in___39__git_annex_sync_--content__39__.mdwn b/doc/bugs/wanted___61___present_gets_ignored_in___39__git_annex_sync_--content__39__.mdwn
new file mode 100644
index 000000000..557b1f13f
--- /dev/null
+++ b/doc/bugs/wanted___61___present_gets_ignored_in___39__git_annex_sync_--content__39__.mdwn
@@ -0,0 +1,18 @@
+### Please describe the problem.
+
+The 'present' flag in the wanted files flag for a repository is ignored when doing a `git annex sync --content`, which causes git annex to (try to) drop all files. E.g. the line
+
+ wanted $repoid = lackingcopies=1 or present
+
+in `git annex vicfg` tries to drop all files if enough copies are available. `git annex drop --auto` works as expected and doesn't try to drop files.
+
+### What steps will reproduce the problem?
+Use 'present' in the 'wanted' option of a repo and do a `git annex sync --content`. `wanted $repouuid = present` was enough to trigger that behaviour.
+
+### What version of git-annex are you using? On what operating system?
+git-annex version 6.20160114 on Arch Linux.
+
+
+### 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)
+
+This behaviour is relatively recent. Until some time ago everything worked as expected with the expression above.