[Bioc-devel] Fwd: git svn permissions

[Turaga, Nitesh]

Begin forwarded message:

From: Thomas Lawson <thomas.nigel.lawson at gmail.com<mailto:thomas.nigel.lawson at gmail.com>>
Subject: Re: [Bioc-devel] git svn permissions
Date: October 3, 2017 at 12:37:14 PM EDT
To: "Turaga, Nitesh" <Nitesh.Turaga at roswellpark.org<mailto:Nitesh.Turaga at roswellpark.org>>

Great! Seems to work now.

Thanks Nitesh,

Tom

On Tue, Oct 3, 2017 at 4:35 PM, Turaga, Nitesh <Nitesh.Turaga at roswellpark.org<mailto:Nitesh.Turaga at roswellpark.org>> wrote:
Hi Thomas,

As far the password goes, that is happening from your “origin” i.e Github. You set a password for your SSH key there, and we have no way of knowing what it is. It is prompting for a password because you are using your HTTPS protocol for GitHub, i.e it is not using you SSH key.  This would be your GitHub password.

The second attempt you have another issue, you seem to have submitted keys again under t.lawson. I just processed the form, and added the keys to Bioconductor.

See if that fixes your “fetch upstream” issue.

Best,

Nitesh


> On Oct 3, 2017, at 11:04 AM, Thomas Lawson <thomas.nigel.lawson at gmail.com<mailto:thomas.nigel.lawson at gmail.com>> wrote:
>
> Hi all,
>
> I have been trying to link my existing github repository to my bioconductor
> repository but I am having a bit of trouble...
>
> I have been following: https://master.bioconductor<https://master.bioconductor/>
> .org/developers/how-to/git/sync-existing-repositories/
>
> I have the an existing github repository (github.com/viant-metabolomics/<http://github.com/viant-metabolomics/>
> msPurity) that I would like to use maintain my bioconductor repository
> (https://bioconductor.org/packages/release/bioc/html/msPurity.html)
>
> I have created a SSH key with github and used the git /svn form
> https://docs.google.com/forms/d/e/1FAIpQLSdlTbNjsQJDp0BA480vo4tNufs0ziNyNmexegNZgNieIovbAA/
> viewform
>
>   - Using my old svn account username (t.lawson) for the "enter your SVN
>   user id" section
>
>
>   - Using a my github username (tomnl) for the "SSH public key or your
>   GitHub id" section
>
> I can then run the following command OK "git remote add upstream git at git.
> bioconductor.org<http://bioconductor.org>:packages/msPurity.git"
>
> And when I run "git remote -v" I get:
>
> # origin    https://github.com/Viant-Metabolomics/msPurity (fetch)
> # origin    https://github.com/Viant-Metabolomics/msPurity (push)
> # upstream    git at git.bioconductor.org<mailto:git at git.bioconductor.org>:packages/msPurity.git (fetch)
> # upstream    git at git.bioconductor.org<mailto:git at git.bioconductor.org>:packages/msPurity.git (push)
>
> But when I run "git fetch --all" I get a prompt for a password for thomas.
> nigel.lawson at gmail.com<mailto:nigel.lawson at gmail.com>
>
> I tried the password that I set for the SSH key but I couldn't get access.
>
>
>
> In case I made a mistake somewhere, I have just repeated the process. I
> have just created a new SSH key following https://help.github<https://help.github/>
> .com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/
>
> The resubmitted the new SSH public key with Github and resubmitted the git/
> svn form (03/10/2017  approx 14:00).
>
> I now get another error when I run 'git fetch upstram':
>
> # Permission denied (publickey).
> # fatal: Could not read from remote repository.
>
> # Please make sure you have the correct access rights and the repository
> exists.
>
>
> Apologies if I have missed something straightforward
>
> Kind regards,
>
> Tom
>
>       [[alternative HTML version deleted]]
>
> _______________________________________________
> Bioc-devel at r-project.org<mailto:Bioc-devel at r-project.org> mailing list
> https://stat.ethz.ch/mailman/listinfo/bioc-devel



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.




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.
	[[alternative HTML version deleted]]