summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2012-12-19 14:31:53 -0400
committerGravatar Joey Hess <joey@kitenet.net>2012-12-19 14:31:53 -0400
commit07217cc15e22bf9fe572db2d3a5452a450391109 (patch)
tree27ed43dff8224bcd7988b614f1e9ce02126b2dbb
parent8029e1875e5aca2475dca7f337e620245f5a363e (diff)
update
-rw-r--r--doc/bugs/glacier_with_assistant_bugs.mdwn21
1 files changed, 12 insertions, 9 deletions
diff --git a/doc/bugs/glacier_with_assistant_bugs.mdwn b/doc/bugs/glacier_with_assistant_bugs.mdwn
index 3709fedf0..f6ef2a4ac 100644
--- a/doc/bugs/glacier_with_assistant_bugs.mdwn
+++ b/doc/bugs/glacier_with_assistant_bugs.mdwn
@@ -1,11 +1,14 @@
-* When a file is moved into archive/, the assistant that sends it to
- glacier is able to trust that it's in glacier and remove the local copy.
- But other assistants that also have a copy cannot trust that, and so
- don't remove their copies.
+glacier-cli currently relies on a local cache of
+inventory information, and so other git-annexes using the same glacier
+repository are not able to access stuff in it, unless and until
+`glacier vault sync` is run.
-* For that matter, glacier-cli currently relies on a local cache of
- inventory information, and so other git-annexes using the same glacier
- repository are not able to access stuff in it, unless and until
- `glacier vault sync` is run.
+An example of this causing trouble is with the assistant. When a file is
+moved into archive/, the assistant that sends it to glacier is able to
+trust that it's in glacier and remove the local copy. But other assistants
+that also have a copy cannot trust that, and so don't remove their copies.
-[[!tag /design/assistant]]
+I've discussed with glacier-cli's author making git-annex store enough info
+in its branch to be able to bootstrap glacier-cli to know about a file.
+This seems doable and he had a design; waiting on movement
+on the glacier-cli side.