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

close as not a bug

Browse source
This commit is contained in:
Joey Hess 2022-06-09 13:23:33 -04:00
parent 9f1765b32a
commit bfdbf59536
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 16 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
doc/bugs/10.20220525_cannot_probe_for_untrusted_remote_key.mdwn
View file

@ -23,3 +23,4 @@ That however, is substantially more complex than looking at the exit code -- giv
99.9% are just splendid. Wondering here whether this particular consequence of the change was intentional and avoidable? 99.9% are just splendid. Wondering here whether this particular consequence of the change was intentional and avoidable?
> [[notabug|done]] --[[Joey]]

15
doc/bugs/10.20220525_cannot_probe_for_untrusted_remote_key/comment_1_e35bef8fb0b9a40938022c43c87df597._comment Normal file
View file

@ -0,0 +1,15 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2022-06-09T17:19:07Z"
content="""
That was a fix for an old reversion, so trying to use fsck for that would
have also failed before 8.20201129.
Fsck is not the right tool for the job. Fscking can fail for any of a
variety of reasons, including probably reasons that have not been thought
of or implemented yet, so taking failure to mean only one possible thing is
doomed.
A better tool exists: `git-annex checkpresentkey`
"""]]