mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

improve docs and close incorrect bug report

Browse source
This commit is contained in:
Joey Hess 2020-06-16 13:45:00 -04:00
parent a76b1ba3d6
commit f3010afbf6
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 30 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/bugs/checkpresentkey_false_negatives_in_bare_repos.mdwn
View file

@ -45,3 +45,5 @@ Debian Testing, git annex version 8.20200330-1
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Oh it's great, especially the low level plumbing commands. I use it for all my backups by first backup up each machine into a Bup repo, and then storing the bup packs/indices in git-annex, which I use for sync'ing across machines.
> [[notabug|done]] --[[Joey]]

24
doc/bugs/checkpresentkey_false_negatives_in_bare_repos/comment_1_a081b3e4bd25f6d18fe8cdcd3385ae94._comment Normal file
View file

@ -0,0 +1,24 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2020-06-16T16:37:24Z"
content="""
git-annex checkpresentkey checks if a key is present in remotes.
Your bare repository does not have any remotes that contain the key
(due to not having any remotes at all). This is why checkpresentkey is
behaving like this.
The same behavior happens if you remove the origin remote from the nonbare
repo and run the command there.
The documentation seems clear enough about this behavior, although there
is the use of "somewhere" in this part:
When no remote is specified, it verifies if the key's content is
present somewhere, checking accessible remotes until it finds the con‐
tent.
Which I suppose could be interpreted to mean, if the key
is present in the local repo, it's "somewhere".
"""]]

8
doc/git-annex-checkpresentkey.mdwn
View file

@ -12,11 +12,11 @@ This plumbing-level command verifies if the specified key's content
is present in the specified remote.
When no remote is specified, it verifies if the key's content is present
somewhere, checking accessible remotes until it finds the content.
in any accessible remotes.
Exits 0 if the content is verified present, or 1 if it is verified to not
be present. If there is a problem, the special exit code 100 is used,
and an error message is output to stderr.
Exits 0 if the content is verified present in the remote, or 1 if it is
verified to not be present in the remote. If there is a problem,
the special exit code 100 is used, and an error message is output to stderr.
# OPTIONS