update
This commit is contained in:
parent
433607c8a5
commit
3c002e4f5c
1 changed files with 12 additions and 9 deletions
|
@ -1,11 +1,14 @@
|
||||||
* When a file is moved into archive/, the assistant that sends it to
|
glacier-cli currently relies on a local cache of
|
||||||
glacier is able to trust that it's in glacier and remove the local copy.
|
inventory information, and so other git-annexes using the same glacier
|
||||||
But other assistants that also have a copy cannot trust that, and so
|
repository are not able to access stuff in it, unless and until
|
||||||
don't remove their copies.
|
`glacier vault sync` is run.
|
||||||
|
|
||||||
* For that matter, glacier-cli currently relies on a local cache of
|
An example of this causing trouble is with the assistant. When a file is
|
||||||
inventory information, and so other git-annexes using the same glacier
|
moved into archive/, the assistant that sends it to glacier is able to
|
||||||
repository are not able to access stuff in it, unless and until
|
trust that it's in glacier and remove the local copy. But other assistants
|
||||||
`glacier vault sync` is run.
|
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.
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue