[Bioc-devel] Access to schex
ntur@g@@b|oc @end|ng |rom gm@||@com
Fri May 21 21:50:46 CEST 2021
I’ve updated your email address to saskia.freytag using perkins.uwa.edu.au.
Please activate your BiocCredentials account again, from https://git.bioconductor.org/BiocCredentials/account_activation.
Another thing that could be happening is the “permissions” on your keys. http://bioconductor.org/developers/how-to/git/faq/ please check FAQ number #14, #15 and #16 to see if those might help as well.
Hopefully this sorts it out.
> On May 20, 2021, at 10:03 PM, Saskia Freytag <saskia.freytag using perkins.uwa.edu.au> wrote:
> Hi Nitesh,
> I have added multiple keys (using both my maintainer addresses), but none of them seem to change anything. Could it be that there is a problem with the email addresses registered to the package? It may be that a year ago we changed these to make them the same between RUVcorr and schex.
>> On 18 May 2021, at 7:46 am, Nitesh Turaga <nturaga.bioc using gmail.com> wrote:
>> Hi Saskia ,
>> Please try to add new keys. It’s possible you aren’t using the correct key pair to access your package.
>> From: Bioc-devel <bioc-devel-bounces using r-project.org> on behalf of Saskia Freytag <saskia.freytag using perkins.uwa.edu.au>
>> Date: Saturday, May 15, 2021 at 8:42 PM
>> To: bioc-devel using r-project.org <bioc-devel using r-project.org>
>> Subject: [Bioc-devel] Access to schex
>> I am the maintainer of the schex package. I tried to update the package but when I get to the step of pushing the changes to upstream, I get the following error message:
>> FATAL: W any packages/schex SaskiaFreytag DENIED by fallthru
>> (or you mis-spelled the reponame)
>> fatal: Could not read from remote repository.
>> Please make sure you have the correct access rights
>> and the repository exists.
>> Do I need to change my ssh keys in Bioccredentials or is there something deeper going on?
>> [[alternative HTML version deleted]]
>> Bioc-devel using r-project.org mailing list
More information about the Bioc-devel