Hi Sean and moire, Sean Whitton: > I think the best option might simply be if git-remote-gcrypt > stops hiding the output from git when this failure occurs?
Agreed (modulo I've not seen how that would look like yet; happy to test patches :) Actually I would go as far as: " stop hiding the output from git when any failure occurs that would produce this error: gcrypt: Repository not found: "my encrypted git repo" gcrypt: ..but repository ID is set. Aborting. " Rationale: one also gets this not-quite-useful error message in other failure modes such as Internet connectivity issues; then, in my experience, users think that either they have misconfigured things the Git remote URL on their side, or the repo disappeared on the server side; in both cases, in practice this results to folks sending non-actionable support request to project engineers or sysadmins, which is somewhat frustrating to everyone involved. Cheers, -- intrigeri
