Re: lilypond-git from older LilyDev

[Thomas Morley]

Am Mo., 1. März 2021 um 12:18 Uhr schrieb David Kastrup <dak@gnu.org>:
>
> Thomas Morley <thomasmorley65@gmail.com> writes:
>
> > Am So., 28. Feb. 2021 um 19:16 Uhr schrieb David Kastrup <dak@gnu.org>:
> >>
> >> Thomas Morley <thomasmorley65@gmail.com> writes:
> >>
> >> > Hi,
> >> >
> >> > for hunting a bug I revived an older LilyDev in Virtual Box (based
> >> > on Debian-8).
> >> >
> >> > To get access to GitLab (formerly git was connected to savannah) I did:
> >> > $ git remote set-url origin git@gitlab.com:lilypond/lilypond.git
> >> >
> >> > And to update git I tried:
> >> > $ git fetch
> >> > ->
> >> > The authenticity of host 'gitlab.com (172.65.251.78)' can't be 
> >> > established.
> >> > ECDSA key fingerprint is f1:d0:fb:46:73:7a:70:92:5a:ab:5d:ef:43:e2:1c:35.
> >> > Are you sure you want to continue connecting (yes/no)? yes
> >> > Warning: Permanently added 'gitlab.com,172.65.251.78' (ECDSA) to the
> >> > list of known hosts.
> >> > Permission denied (publickey,keyboard-interactive).
> >> > fatal: Could not read from remote repository.
> >> >
> >> > Please make sure you have the correct access rights
> >> > and the repository exists.
> >> >
> >> >
> >> > What am I missing?
> >>
> >> The file
> >>
> >> $HOME/.ssh/id_ed25519
> >>
> >> or wherever you are supposed to store the secret key corresponding to
> >> your SSH key pair.
> >>
> >> For R/O (public) access, there will be different credentials you can use
> >> without your personal secret key copy.
> >>
> >> --
> >> David Kastrup
> >
> > I had to create a new key, there was none in .ssh-folder.
>
> Uh, you had write access on Gitlab previously, didn't you?  That would
> have required a working key.  I'd have copied it from the prevously
> working installation instead of creating a new, different one.
>
> > Then following gitlab-docs was successful.
>
> Ok.
>
> --
> David Kastrup

Well, I use this repository (inside an old LilyDev based on 32-bit
Debian 8) for testing and researching only, because I can't compile
2.19.2x up to 2.19.37 on my main repo (on 64-bit Ubuntu 20.04).
I never tried or intend to commit from it, thus it may have been not
set up properly.

Thanks,
  Harm