Re: problems with SSH key

[David Nalesnik]

On Thu, Nov 14, 2019 at 9:23 AM David Kastrup <address@hidden> wrote:
>
> David Nalesnik <address@hidden> writes:
>
> > Hi all,
> >
> > I'm having difficulty getting my LilyDev machine to work with SSH.
> > I've followed the steps in the Contributor's Guide.  Below is what
> > happens.  I've included my config file, too.
> >
> > If anyone can help, I'd be very grateful.  I've got a patch to submit
> > but I've been struggling for days to reinstall LilyDev.
> >
> > Thanks,
> > David
> >
> > BTW: ssh is not installed in the latest LilyDev release; perhaps a
> > note is needed in the manual
> >
> > [dev@lilydev:lilypond-git]$ git pull --verbose
> > The authenticity of host 'git.sv.gnu.org (209.51.188.201)' can't be 
> > established.
> > ECDSA key fingerprint is SHA256:qRLLJ4w/GAeiDyYnbx4yWJbZXwGiYYxgNty7lAfUyuM.
> > Are you sure you want to continue connecting (yes/no)? yes
>
> I read "yes" so this does not look like a problem with the key.

Well, the Contributor's Guide description doesn't match what I got (an
ECDSA instead of an RSA fingerprint), so my "yes" may have been
wishful thinking?

Here's the output the CG quotes:

The authenticity of host 'git.sv.gnu.org (140.186.70.72)' can't
be established.
RSA key fingerprint is
80:5a:b0:0c:ec:93:66:29:49:7e:04:2b:fd:ba:2c:d5.
Are you sure you want to continue connecting (yes/no)?

>
> > Warning: Permanently added 'git.sv.gnu.org,209.51.188.201' (ECDSA) to
> > the list of known hosts.
>
> Again, this looks like the right reaction.  Should work without this
> prompt next time.
>
> > error: object file
> > .git/objects/76/008183503d70d4b37a73f19e60c2438112a5a8 is empty
> > error: object file
> > .git/objects/76/008183503d70d4b37a73f19e60c2438112a5a8 is empty
> > fatal: loose object 76008183503d70d4b37a73f19e60c2438112a5a8 (stored
> > in .git/objects/76/008183503d70d4b37a73f19e60c2438112a5a8) is corrupt
> > [dev@lilydev:lilypond-git]$ fatal: The remote end hung up unexpectedly
>
> Rather sounds like a different problem like a dead server/connection.
> Try again?

Same result....