Join Log in
Score:0
Álex avatar Server

git-remote-gcrypt integrity check during clone failing in only one computer

cn flag
Álex

I have a remote git repository using the git-remote-gcrypt remote filter. It works properly and can be cloned normally in one computer (Ubuntu 20.04, with git-remote-gcrypt version 1.3-1). It has been in use for a while, with a few commits.

In another similar computer (same OS and gcrypt version), the clone fails with:

gcrypt: Packfile d799a7de3e9fe63eb76b05fceef0d955b83b4f857de2232e0174114145d6f13c does not match digest!
fatal: early EOF

I have tried rsyncing the remote bare repository locally, verified it is identical to the remote repository, and cloning locally. Both computers behave as before (one succeeds, the other fails with the same error). Also tried rebooting.

I can only think that something locally cached is interfering, but I also don't think gpg/git/gcrypt are caching anything data-wise across a reboot, so I'm stumped.

The only seemingly-related hit I found is https://git-annex.branchable.com/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/ , but I'm experiencing this without git-annex, and the solution described in the last post does not apply as I'm cloning from scratch, before any .git/config file exists.

Thanks for any clues about diagnosing/fixing this problem.

32
0 + 0
git
ธงชาติไทย
Elon Musk
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.