Dear Kenneth,
Kenneth Hoste <[email protected]> writes:
> Dear Loris,
>
> On 29/01/2021 08:55, Loris Bennett wrote:
>> Hi,
>>
>> My GitHub integration is failing:
>>
>> * GitHub user...mygithubusername => OK
>> Please enter password for encrypted keyring: * GitHub token...
>> 18b..089 (len: 40) => OK (validated)
>> * git command...OK ("git version 1.8.3.1; ")
>> * GitPython module...OK (GitPython version 2.1.15)
>> * push access to mygithubusername/easybuild-easyconfigs repo @
>> GitHub...FAIL (unexpected exception: 'Checking out branch \'master\' from
>> [email protected]:mygithubusername/easybuild-easyconfigs.git failed: "Failed to
>> fetch branch \'master\' from
>> [email protected]:mygithubusername/easybuild-easyconfigs.git: Cmd(\'git\')
>> failed
>> due to: exit code(128)\\n cmdline: git fetch -v
>> pr_target_account_mygithubusername_qZpiz\\n stderr: \'fatal: Could not read
>> from remote repository.\\n\\nPlease make sure you have the correct access
>> rights\\nand the repository exists.\'"')
>> * creating gists...OK
>> * location to Git working dirs... OK (~/git)
>>
>> This has worked in the past.
>>
>> Any ideas?
>
>
> First thing that comes to mind is the SSH public key that is tied to your
> GitHub
> account (see https://github.com/yourgithubusername.keys).
>
> The corresponding private key has to be available, either in a standard
> location
> or 'active' in your SSH agent (via ssh-add).
Thanks for the swift reply. The key is
~/.ssh/id_rsa.pub
and matches the one shown in the GitHub settings.
Does this issue
https://github.com/easybuilders/easybuild-framework/issues/2109
about the scheme used for checking out have any relevance? The code
referenced there seems to imply that HTTPS should by default be tried
first, IIUC.
Cheers,
Loris
--
Dr. Loris Bennett (Hr./Mr.)
ZEDAT, Freie Universität Berlin Email [email protected]
