Am Di., 12. Mai 2020 um 09:19 Uhr schrieb Thomas Morley <thomasmorle...@gmail.com>: > > Am Di., 12. Mai 2020 um 08:47 Uhr schrieb Jonas Hahnfeld <hah...@hahnjo.de>: > > > > Am Dienstag, den 12.05.2020, 08:43 +0200 schrieb Thomas Morley: > > > Am Di., 12. Mai 2020 um 08:32 Uhr schrieb Jonas Hahnfeld > > > <hah...@hahnjo.de>: > > > > Am Dienstag, den 12.05.2020, 08:24 +0200 schrieb Thomas Morley: > > > > > Hi, > > > > > > > > > > currently I've very little time to work on LilyPond or to monitor the > > > > > mailing-lists at all, thus I apologize if this is already answered > > > > > elsewhere. > > > > > For now I'll expect me getting familiar with GitLab very slowly... > > > > > > > > > > Nevertheless, I just did: > > > > > $ git remote set-url origin g...@gitlab.com:lilypond/lilypond.git > > > > > > > > > > Next I wanted to do: > > > > > $ git fetch > > > > > returning: > > > > > The authenticity of host 'gitlab.com > > > > > (2606:4700:90:0:f22e:fbec:5bed:a9b9)' can't be established. > > > > > ECDSA key fingerprint is > > > > > SHA256:HbW3g8zUjNSksFbqTiUWPWg2Bq1x8xdGUrliXFzSnUw. > > > > > Are you sure you want to continue connecting (yes/no)? > > > > > > > > > > What to do? > > > > > > > > It prompts you to confirm that it's really gitlab.com that you're > > > > connecting to. As SSH uses no certificates, that's on the user to do. > > > > The usual way is to verify the fingerprint, which are published here: > > > > https://docs.gitlab.com/ee/user/gitlab_com/index.html#ssh-host-keys-fingerprints > > > > > > > > As they match, you probably want to continue (unless you consider the > > > > possibility that somebody hijacked both the website for both of us and > > > > the SSH connection to a spoofed host...) > > > > > > > > Jonas > > > > > > I now get: > > > $ git fetch > > > The authenticity of host 'gitlab.com > > > (2606:4700:90:0:f22e:fbec:5bed:a9b9)' can't be established. > > > ECDSA key fingerprint is > > > SHA256:HbW3g8zUjNSksFbqTiUWPWg2Bq1x8xdGUrliXFzSnUw. > > > Are you sure you want to continue connecting (yes/no)? yes > > > Warning: Permanently added > > > 'gitlab.com,2606:4700:90:0:f22e:fbec:5bed:a9b9' (ECDSA) to the list of > > > known hosts. > > > Connection closed by 2606:4700:90:0:f22e:fbec:5bed:a9b9 port 22 > > > fatal: Could not read from remote repository. > > > > > > Please make sure you have the correct access rights > > > and the repository exists. > > > > Did you add the SSH key to your GitLab account? If not, see this > > documentation page: > > https://docs.gitlab.com/ee/ssh/README.html#adding-an-ssh-key-to-your-gitlab-account > > > > Regards > > Jonas > > Well, as far as I can tell, I did as you adviced. > Though: > $ git fetch > now wants a password, though I never set one for this repo. > > I give up for now, probably I wait for the updated CG, please make > sure it's written for very dumb dummies... > > Many thans for your advice, best > Harm
I think I've found the culprit. Previously I had a couple of lilypond-git-repos (mainly because I could switch between compilations with different guile-versions very conveniant), but only one, protected by a password, for doing serious work, patches, push etc. The others were not set up for push. Looks like the repo I took for testing access to GitLab is now the main, password-protected repo. Which is ok for me. Seems it's time for some clean up with my repos ... well ... if I find the time ... Many thanks again. Harm
