summaryrefslogtreecommitdiff
path: root/doc/bugs/dropkey_--batch_--json_--force_is_always_succesfull/comment_1_b913175c341d39e6b9d354213677248c._comment
blob: 4e22e90ce403da895b5e92ef5de0bc09b61cd243 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
[[!comment format=mdwn
 username="joey"
 subject="""comment 1"""
 date="2016-05-03T17:03:25Z"
 content="""
Note that dropkey does *not* check if other copies exist, so the --force is
unncessary; eg it's always forced by default.

Anyway, dropkey will indicate a failure if it's actually unable to drop the
content for some reason, eg a permissions problem or the content is locked
to prevent it being dropped right now, or other unanticipated error.
But, if the content of the key is not present, it's successfully
gotten the repo into the requested state.

Similarly, git-annex transferkey will return success if the key it was
supposed to download is already present.

I don't consider this a bug, although am willing to be convinced
otherwise..
"""]]