[Bioc-devel] Switch to SSH protocol for git clone instructions on package landing pages?

Joris Meys Joris.Meys at ugent.be
Sun Apr 29 17:48:50 CEST 2018

Using SSH will only work when they have a public key on the git server
registered. Otherwise they will get the dreaded "Please make sure you have
the correct access rights and the repository exists" error message. The
same happens when I forget to add the correct key to my pageant. In my
humble opinion it doesn't pay off to make it more difficult for general
users to download the source code in order to make the process more simple
for your developers.


On Sun, Apr 29, 2018 at 4:03 PM, Peter Hickey <peter.hickey at gmail.com>

> The one-liner on the package landing page describing how to check out
> a package from the git repo uses HTTPS rather than ssh, e.g.:
> # From https://bioconductor.org/packages/bsseq/
> git clone https://git.bioconductor.org/packages/bsseq
> However, as a developer we should be using the SSH protocol
> (https://bioconductor.org/developers/how-to/git/faq/).
> Is there any reason not to use the SSH protocol (i.e. git clone
> git at git.bioconductor.org:packages/bsseq) in the instructions given on
> the landing page? It seems to me an unnecessary source of friction,
> particularly for new developers who will end up with the dreaded
> "fatal: remote error: FATAL: W any packages/myPackage nobody DENIED by
> fallthru (or you mis-spelled the reponame)" error message if they
> don't know to switch protocols
> (https://bioconductor.org/developers/how-to/git/faq/)
> Cheers,
> Pete
> _______________________________________________
> Bioc-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/bioc-devel

Joris Meys
Statistical consultant

Department of Data Analysis and Mathematical Modelling
Ghent University
Coupure Links 653, B-9000 Gent (Belgium)

tel: +32 (0)9 264 61 79
Biowiskundedagen 2017-2018

Disclaimer : http://helpdesk.ugent.be/e-maildisclaimer.php

	[[alternative HTML version deleted]]

More information about the Bioc-devel mailing list