diff options
| author |  openmedi <openmedi@web> | 2016-11-18 13:57:49 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2016-11-18 13:57:49 +0000 |
| commit | 8a55c58350addd79d13e5e8700dbb98d648d3ddc (patch) | |
| tree | 610165c58b1b9428fe54e3d09c34697b0c6ba9dd | |
| parent | 1c14d09352a4208925c14621011cd66273bdb597 (diff) | |
| -rw-r--r-- | doc/forum/What_to_do_if_special_remotes_refuses_drops__63__.mdwn | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/forum/What_to_do_if_special_remotes_refuses_drops__63__.mdwn b/doc/forum/What_to_do_if_special_remotes_refuses_drops__63__.mdwn new file mode 100644 index 000000000..512e89528 --- /dev/null +++ b/doc/forum/What_to_do_if_special_remotes_refuses_drops__63__.mdwn @@ -0,0 +1,9 @@ +I have a special remote that I would like to delete and have marked it as such in the assistant. Although this was before my myriad of problems with git annex itself wanting to repair the repo all the time. Right now if I take a loog into my daemon.log I see the following error over and over again: + +``` +drop skydrive foo.bar + This file could not be removed +failed +``` + +I checked if I can login into my account and it works just fine. So I assume that this might be a bug? Is it somehow possible to forego the cleaning out of the special remote and just mark it as deleted for good? Thanks in advance! |