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

Added a comment

Browse source
This commit is contained in:
branch 2023-10-23 09:57:00 +00:00 • committed by admin
parent fe3b85a744
commit 079323e846
1 changed files with 23 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_16_2139bcb34591be137ff3da959f08bc76._comment Normal file
View file

@ -0,0 +1,23 @@
[[!comment format=mdwn
username="branch"
subject="comment 16"
date="2023-10-23T09:56:59Z"
content="""
This issue is still present, when using the assistant with git-remote-gcrypt.
Although one can recover from this issue by resetting the repository, this is handicaping, as we have to continuously monitor whether pushes have been successful, which contradicts the idea of the assistant.
This may be anecdotal, but the push before the 'Packfile *** does not match digest!' error, have had some network issues, as follows:
```
gcrypt: Due to a longstanding bug, this push implicitly has --force.
gcrypt: Consider explicitly passing --force, and setting
gcrypt: gcrypt's require-explicit-force-push git config key.
gcrypt: Encrypting to: -r ***
gcrypt: Requesting manifest signature
error: src refspec refs/gcrypt/gitception+ does not match any
fatal: the remote end hung up unexpectedly
error: failed to push some refs to ***
error: failed to push some refs to ***
```
"""]]