Friday, 9 February 2018

Trying to make my SSH work with Bioconductor...


OK, so today, I am trying to see if I can make sure that my master branch in Github and the drawProtein master branch on Bioconductor are synced.

I have to do this through Terminal because I want to link two upstream repos to my computer.

So it's an attempt to follow the New Package Workflow page...
http://bioconductor.org/developers/how-to/git/new-package-workflow/
According to the page:
"Bioconductor needs to know your SSH ‘public key’."

I have submitted this or at least I thought I did...
Today, I created a new SSH key for Github and Bioconductor and I submitted it again to Bioconductor:
So that's good.

A key step to submitting the SSH keys is copying id_rsa.pub to clipboard
On this page:
https://help.github.com/articles/adding-a-new-ssh-key-to-your-github-account/

Code for copying id_rsa.pub to clipboard
$ pbcopy < ~/.ssh/id_rsa.pub
# Copies the contents of the id_rsa.pub file to your clipboard



Some useful git commands to check remotes:

git remote show

In my case this gives two:
origin

upstream

So then:

git remote show upstream

and it returns:
* remote origin
  Fetch URL: https://github.com/brennanpincardiff/drawProteins.git
  Push  URL: https://github.com/brennanpincardiff/drawProteins.git
  HEAD branch: master
  Remote branches:
    devel  tracked
    master tracked
  Local branches configured for 'git pull':
    devel  merges with remote devel
    master merges with remote master
  Local refs configured for 'git push':
    devel  pushes to devel  (up to date)

    master pushes to master (up to date)

Good news! :-)

So try:

git remote show upstream

and it returns:
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights

and the repository exists.

So this is not so good!
Try again tomorrow or Monday in the hope that the SSH key has been accepted and that I have some access rights.

As added info:
More here: https://git-scm.com/book/be/v2/Git-Basics-Working-with-Remotes















No comments:

Post a Comment