[Bioc-devel] Unable to access repository

Clare Pacini cep46 at cam.ac.uk
Wed Apr 11 18:48:51 CEST 2018


Hi Nitesh,

There was a query about ssh keys for this package and another that I am maintainer on. See email chain below. I think I have been accidentally removed from DrugVsDisease would you be able to fix this given the information in the attached ?

Thanks

Clare

—


From: "Obenchain, Valerie" <Valerie.Obenchain at RoswellPark.org>
Subject: Re: Bioconductor package access
Date: 6 February 2018 at 22:23:39 GMT
To: Clare Pacini <clarepacini at gmail.com>
Cc: "saezrodriguez at ebi.ac.uk" <saezrodriguez at ebi.ac.uk>

On 02/06/2018 02:19 PM, Obenchain, Valerie wrote:
> Thanks Clare.
> 
> I have change the ssh key over to c.pacini and will add your github username to the new account. You should now have access to both packages with that key.
> 
> Now that the key is moved over, j.saezrodriguz will have no access. Julio, please go to the link below and add your github username or ssh key. Be sure to use the email saezrodriguez at ebi.ac.uk <mailto:saezrodriguez at ebi.ac.uk> and username j.saezrodriguz.

Oops, forgot the 'e'.  I meant 'j.saezrodriguez'.

Valerie
> 
> https://docs.google.com/forms/d/e/1FAIpQLSdlTbNjsQJDp0BA480vo4tNufs0ziNyNmexegNZgNieIovbAA/viewform <https://docs.google.com/forms/d/e/1FAIpQLSdlTbNjsQJDp0BA480vo4tNufs0ziNyNmexegNZgNieIovbAA/viewform>
> 
> Valerie
> 
> 
> 
> 
> 
> 
> On 02/06/2018 01:48 PM, Clare Pacini wrote:
>> Hi Valerie,
>> 
>> Thanks for your email. Yes I would like to keep access to both packages, Julio will require access just to DrugVsDisease.
>> The ssh key is mine and my GitHub username is clarepacini.
>> 
>> Thanks,
>> 
>> Clare
>>> On 6 Feb 2018, at 21:18, Obenchain, Valerie <Valerie.Obenchain at roswellpark.org <mailto:Valerie.Obenchain at roswellpark.org>> wrote:
>>> 
>>> Hi Clare,
>>> 
>>> There is some confusion between credentials for users c.pacini and j.saezrodriguz. A number of combinations of usernames, emails and ssh keys for these 2 users were entered in the Google Sheet. We also have historical data for these users from svn. I'd like to clean this up if possible.
>>> 
>>> 1) accounts 
>>> 
>>> Do you want accounts for both c.pacini and j.saezrodriguez? For each account, we need several pieces of information. Here is what we currently have:
>>> 
>>> username : c.pacini
>>> email: clarepacini at gmail.com <mailto:clarepacini at gmail.com>
>>> github username: none
>>> ssh keys: none
>>> 
>>> username: j.saezrodriguez
>>> email: saezrodriguez at ebi.ac.uk <mailto:saezrodriguez at ebi.ac.uk>
>>> github username: none
>>> ssh keys: ssh-rsa AAAAB3NzaC1yc2EA ... 5pTvNvU2MiGd1BaJw== clarepacini at gmail.com <mailto:clarepacini at gmail.com>
>>> 
>>> 2) package access
>>> 
>>> Currently user c.pacini has access to covEB and user j.saezrodriguez has access to DrugVsDisease. Is this correct? Because we only have keys for j.saezrodriguez and none for c.pacini, no one can access covEB.
>>> 
>>> If you are both active maintainers you should have separate accounts and both be listed on both packages. If you have a github usernames please provide those so we can get ssh keys from there.
>>> 
>>> Let me know if you have questions.
>>> 
>>> Valerie
>>> 
>>> 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. 


> On 11 Apr 2018, at 17:40, Turaga, Nitesh <Nitesh.Turaga at RoswellPark.org> wrote:
> 
> Hi, 
> 
> The only key available on that package is “j.saezrodriguez”, and there is no key available with that username.
> 
> I’m not sure how you’ve had previous access to this package after we’ve moved the Git repository. 
> 
> Can you upload a key under the username: clarepacini, and please have Julio Saez-Rodriguez provide confirmation regarding access. It might be useful for Julio to provide a key too.
> 
> Best,
> 
> Nitesh 
> 
> 
> 
>> On Apr 10, 2018, at 7:23 AM, Clare Pacini <cep46 at cam.ac.uk> wrote:
>> 
>> Hi all,
>> 
>> I am the maintainer for DrugVsDisease package and am trying to push new changes. However, I am getting the following error:
>> 
>> Permission denied (publickey).
>> fatal: Could not read from remote repository.
>> 
>> Please make sure you have the correct access rights
>> and the repository exists.
>> 
>> I have previously provided an ssh key for my GitHub account with username clarepacini and have been able to push changes previously. I am unsure as to what has changed/what else I need to do?
>> 
>> Thanks
>> 
>> Clare
>> 	[[alternative HTML version deleted]]
>> 
>> _______________________________________________
>> 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.


	[[alternative HTML version deleted]]



More information about the Bioc-devel mailing list