Package: git-remote-gcrypt
Version: 1.0.1-1
Severity: important
Hi,
* What led up to the situation?
I was no longer able to use an encrypted git repo after the fingerprint
for the RSA key sent by the remote host changed, and the failure message
did not help me to understand why.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I tried to fetch updates from an encrypted git repository I've been
using for a while.
* What was the outcome of this action?
gcrypt: Repository not found: "my encrypted git repo"
gcrypt: ..but repository ID is set. Aborting.
* What outcome did you expect instead?
An indication of the cause of the failure.
I discovered that the fingerprint had changed by trying to clone the
repository somewhere else.
Cheers,
-- System Information:
Debian Release: 9.5
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages git-remote-gcrypt depends on:
ii git 1:2.11.0-3+deb9u4
ii gnupg 2.2.10-3
ii gnupg2 2.1.18-8~deb9u2
Versions of packages git-remote-gcrypt recommends:
ii curl 7.52.1-5+deb9u8
ii rsync 3.1.2-1+deb9u1
git-remote-gcrypt suggests no packages.
-- no debconf information
