From 6ecc4804f94d4c096a74439bffd8f7efaca6958c Mon Sep 17 00:00:00 2001 From: "alexander+gitannex@2296816092e64c93002644a8af3a4d4c9e6b21c7" Date: Mon, 25 Jan 2016 23:21:12 +0000 Subject: --- ...gnored_in___39__git_annex_sync_--content__39__.mdwn | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/bugs/wanted___61___present_gets_ignored_in___39__git_annex_sync_--content__39__.mdwn 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. -- cgit v1.2.3