From 38a7d7e779ec99c589dd2ed22ddeb8d7a67b5bf2 Mon Sep 17 00:00:00 2001 From: andrew Date: Tue, 1 Jan 2019 19:00:08 +0000 Subject: [PATCH] Added a comment --- ...comment_9_ab4b7a243f9d1dfddf1c2c2609863d99._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/MacOSX__58___archive_folders_not_working_as_expected/comment_9_ab4b7a243f9d1dfddf1c2c2609863d99._comment diff --git a/doc/bugs/MacOSX__58___archive_folders_not_working_as_expected/comment_9_ab4b7a243f9d1dfddf1c2c2609863d99._comment b/doc/bugs/MacOSX__58___archive_folders_not_working_as_expected/comment_9_ab4b7a243f9d1dfddf1c2c2609863d99._comment new file mode 100644 index 0000000000..0a40fc698d --- /dev/null +++ b/doc/bugs/MacOSX__58___archive_folders_not_working_as_expected/comment_9_ab4b7a243f9d1dfddf1c2c2609863d99._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="andrew" + avatar="http://cdn.libravatar.org/avatar/acc0ece1eedf07dd9631e7d7d343c435" + subject="comment 9" + date="2019-01-01T19:00:07Z" + content=""" +I believe all repos are created at v5 by default currently both from the command-line and the assistant webapp, but there is no guarantee that will always be the case. With the latest version of git-annex a v6 repo will automatically be upgraded to a v7 repo whenever you run any git-annex command (or start the assistant or webapp). + +Also just for help troubleshooting Joey: I just tested this with `6.20180914-g13dc117e9` and v6 indirect repos. Same issue, files moved to an archive folder (unlocked and locked) are never dropped by the assistant even after they have reached an archive repo. As with v7 repos, running `git-annex drop --auto` does drop them. +"""]]