[Bioc-devel] push access to bioconductor repository-reg.

Hi Shweta,

I?m cc-ing bioc-devel on this as well. There are other members of the team
in the future who could possibly help you with your questions.

You seem to have three public keys on our

find . -name "shwetagopaul92.pub" -exec cat {} \;

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDRU2oyo0iT2qVP3d8ciLYMbpPjkoVy
S06AdJDvEcV7MUqHaTTRtz6TEIoVchQPskYn7D3c+UDxYty8pOXQ5M7gETRhbeewuEabSHV
77jmzdgXj3AizE77bffAz3KA98Ibz1up+z065/qHMR8hZUpm3hw1kAVMyeiOvk2bRrow
cJoewP7KtArgMTNBaecFLcV2xmOncHGBlC2FM7svwwRxa0zfhiMtV0RRlb9totAl+A/
WrdVoHkHpPl96Jm9yvHN4FoZyD0acaXpQiKVEamhyANegZ/J+2pNan9JkMiqTF8Rdh/
e6LHLBwxd3mpnMkJOOIYwexixWHUZtuAeNot53P

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCfQ+7dozCd9jrQ+
nPnzfAAa9Nf4KjfDP1oXSFc8hHE+0UZZHxqSdubzZvrfJaNUT95Z2Uey17
GRy4OYtd4ven2qTY3wWNI4Vgpjs/olqNqHQLyIF/uIe2LsiLwUzFh/
rQQiOfHJkLvOcOU1CqiuAfqqHLPK4lP1X8vrnnMhA7oEAaJGBbIOEDlcCyJf
Fc8IY05UJsoxut61APZ4SowiVyhWfLYoQKh8R5OeQOj0h0ARTbkQvHIWE20Z
UY0XPpz5Bm9kmjtavwhkTcrapKFJ527PTiPYjgWQwqVvkBus9JJv+
zodkdumMNdDEuji498pDWsCNy7TH5BG10pr18AJel5

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDCSq5kTCW4ObxX83RAwgi7eQRpWxMs
OQxRdVooWRa+5NygGLA7OkLBkqgF8b5zdfQ+vSBGHgSDRFnINqAd313wQ/V9f2VoCNXxo/
FGhkpc6nrdtVUTCHL2rtihY/KZNS1V6/16b6GWmsUE2yux8PRxYtbnK5TMNFAG
kt4s2eBJYH8FEGVLYk0De4K+mQDDlXvKPDgGvoUYHVlCKXijvvLN4R
nUw4FtGles8fa8XBEtZz574kYqUWo5RhwNgCiRVysKhpp/
FUs3RqYRZCwDhnLOdvbQYCBAz7efcMAjuXheVwXAYWdh8wpZcGyftimvZy38
0UgWnoZuER1Hl9rWUDip


Again, it?s all about using the correct private key. Look into
http://bioconductor.org/developers/how-to/git/faq/ , specifically #15 to
set up your config file to access the correct private key.

Best,

Nitesh

On Oct 26, 2017, at 11:04 AM, Shweta Gopaulakrishnan <

reshg at channing.harvard.edu> wrote:

Hi Nitesh,

I updated my public key on github yesterday. I have also submitted the

google form with the new public key to bioconductor. I am still not having
the permission to fetch contents from the Bioconductor repository.

Please could you let me know the public key you have on your database

now?

Thank you!

On Wed, Oct 25, 2017 at 12:15 PM, Shweta Gopaulakrishnan <

reshg at channing.harvard.edu> wrote:

Hi Nitesh,

Thank you for your response.
I did have a private key corresponding to a different public key. I have

updated github and Bioconductor with the new public key.

Thank you!

On Wed, Oct 25, 2017 at 9:49 AM, Turaga, Nitesh <

Nitesh.Turaga at roswellpark.org> wrote:

Hi Vincent,


The RELEASE_3_6 branch does not exist yet, it is still called ?master?.

You may push your changes there. You can see all the available branches by
trying

        `git branch -a`

We will notify bioc-devel once the new branch is created, towards end of

the month.

Shweta, has access to restfulSE and restfulSEData, with the public key

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDRU2oyo0iT2qVP3d8ciLYMbpPjkoVy

S06AdJDvEcV7MUqHaTTRtz6TEIoVchQPskYn7D3c+UDxYty8pOXQ5M7gETRhbeewuEabSHV
77jmzdgXj3AizE77bffAz3KA98Ibz1up+z065/qHMR8hZUpm3hw1kAVMyeiOvk2bRrow
cJoewP7KtArgMTNBaecFLcV2xmOncHGBlC2FM7svwwRxa0zfhiMtV0RRlb9totAl+A/
WrdVoHkHpPl96Jm9yvHN4FoZyD0acaXpQiKVEamhyANegZ/J+2pNan9JkMiqTF8Rdh/
e6LHLBwxd3mpnMkJOOIYwexixWHUZtuAeNot53P

It is important that Shweta use the private key, which corresponds to

that public key. This often happens when people change computers, or
delete/overwrite the keys in their `~/.ssh` folder.

Best,

Nitesh

On Oct 25, 2017, at 5:56 AM, Vincent Carey <stvjc at channing.harvard.edu>

wrote:

Hi Nitesh -- could you have a look at this?  I think since the

submission process was successful

Shweta's key must be known to the system.

For my own parody package I wanted to try to push a change to current

3.6 build system but found

 * [new branch]      RELEASE_3_4  -> upstream/RELEASE_3_4

 * [new branch]      RELEASE_3_5  -> upstream/RELEASE_3_5

 * [new branch]      master       -> upstream/master

%vjcair> git checkout -b RELEASE_3_5 upstream/RELEASE_3_5

Branch RELEASE_3_5 set up to track remote branch RELEASE_3_5 from

upstream.

Switched to a new branch 'RELEASE_3_5'

%vjcair> git checkout -b RELEASE_3_6 upstream/RELEASE_3_6

fatal: 'upstream/RELEASE_3_6' is not a commit and a branch

'RELEASE_3_6' cannot be created from it

%vjcair> git branch

* RELEASE_3_5

  master




---------- Forwarded message ----------
From: Shweta Gopaulakrishnan <reshg at channing.harvard.edu>
Date: Tue, Oct 24, 2017 at 5:17 PM
Subject: push access to bioconductor repository-reg.
To: Vincent Carey <stvjc at channing.harvard.edu>


Hi Dr.Carey,

restfulSE an rhdf5client build and install OK now. They are failing

tests, cause the changes on github are not reflected on the package build.

The steps are to push into the bioconductor restfulSE repository by

adding it as a remote to the local repository. When I try fetching the
contents of the bioconductor repo [ git fetch upstream ] , it says
permission denied. I have added my SSH keys to my github and submitted my
github id using Bioconductor's google form.

Am I missing something ?

I am following this link :
https://bioconductor.org/developers/how-to/git/new-package-workflow/

Thank you !
--
Shweta Gopaulakrishnan,
Bioinformatician,
Channing Division of Network Medicine,
Brigham and Women's Health Hospital,
Boston,MA 02115

This email message may contain legally privileged and/or confidential

information.  If you are not the intended recipient(s), or the employee or
agent responsible for the delivery of this message to the intended
recipient(s), you are hereby notified that any disclosure, copying,
distribution, or use of this email message is prohibited.  If you have
received this message in error, please notify the sender immediately by
e-mail and delete this email message from your computer. Thank you.

--
Shweta Gopaulakrishnan,
Bioinformatician,
Channing Division of Network Medicine,
Brigham and Women's Health Hospital,
Boston,MA 02115



--
Shweta Gopaulakrishnan,
Bioinformatician,
Channing Division of Network Medicine,
Brigham and Women's Health Hospital,
Boston,MA 02115

This email message may contain legally privileged and/or confidential
information.  If you are not the intended recipient(s), or the employee or
agent responsible for the delivery of this message to the intended
recipient(s), you are hereby notified that any disclosure, copying,
distribution, or use of this email message is prohibited.  If you have
received this message in error, please notify the sender immediately by
e-mail and delete this email message from your computer. Thank you.