updateproxy, updatecluster check annexobjects=yes
updateproxy, updatecluster: Prevent using an exporttree=yes special remote that does not have annexobjects=yes, since it will not work.
This commit is contained in:
parent
8864a9e353
commit
6d96734128
5 changed files with 55 additions and 11 deletions
|
@ -41,9 +41,6 @@ Planned schedule of work:
|
|||
export not supported
|
||||
failed
|
||||
|
||||
* Prevent `updateproxy` from enabling an exporttree=yes special remote
|
||||
that does not have annexobjects=yes, to avoid foot shooting.
|
||||
|
||||
* Handle cases where a single key is used by multiple files in the exported
|
||||
tree. Need to download from the special remote in order to export
|
||||
multiple copies to it. (In particular, this is needed when using
|
||||
|
@ -69,6 +66,10 @@ Planned schedule of work:
|
|||
* When getting from a P2P HTTP remote, prompt for credentials when
|
||||
required, instead of failing.
|
||||
|
||||
* Prevent `updateproxy` and `updatecluster` from adding
|
||||
an exporttree=yes special remote that does not have
|
||||
annexobjects=yes, to avoid foot shooting.
|
||||
|
||||
## items deferred until later for p2p protocol over http
|
||||
|
||||
* `git-annex p2phttp` should support serving several repositories at the same
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue