Hi Chris,

Let’s try it this way.

It seems that the maintainer listed on all the packages is with the email 
“benjamin.haibe.ka...@utoronto.ca <mailto:benjamin.haibe.ka...@utoronto.ca>”. 
I’m guessing you have access to this email address, i.e see the emails which go 
this address (or are forwarded to you by Ben). Right now, the way this email is 
configured is, it has your Github and SSH keys with it. 

I guess the first question is, are you able to log in to the BiocCredentials 
account?

Nitesh 

> On Jun 18, 2020, at 10:51 AM, Chris Eeles <christopher.ee...@outlook.com> 
> wrote:
> 
> Hi Nitesh,
> 
> The only thing I can think of is that I opened my package submission issues 
> under my GitHub account, but listed the maintainer as my PI, Benjamin 
> Haibe-Kains. Is this something the system normally deals with  (a developer 
> submitting on behalf of a PI)? Maybe the maintainer 
> (benjamin.haibe.ka...@utoronto.ca <mailto:benjamin.haibe.ka...@utoronto.ca>) 
> credentials account is getting updated with my user name on package 
> acceptance?
> 
> I can image if this is the case that my credentials account 
> (christopher.ee...@outlook.com <mailto:christopher.ee...@outlook.com>) may 
> get disabled due to a duplicate GitHub username/ID? Access to the accounts 
> was only lost after the recent acceptance of RadioGx and ToxicoGx.
>  
> This is all speculation, but package submission/acceptance is the only action 
> I have taken since I was able to successfully login with both accounts and 
> push using my SSH key.
> 
> Otherwise, maybe the credentials DB got rolled back? Not really sure what 
> else would cause this.
> 
> If you can resolve the issue again this would be appreciated. Our packages 
> are:
> consensusOV
> CoreGx
> genefu
> PharmacoGx
> predictionnet
> RadioGx
> survcomp
> ToxicoGx
> Xeva
>  
> If you think duplicated account public keys may be the cause, could you 
> reinitialize my credentials account without any SSH keys and I will add a 
> different one?
> 
> Thanks for your assistance.
> 
> Best,
> Chris
>  
>  
> From: Nitesh Turaga <nturaga.b...@gmail.com> 
> Sent: June 18, 2020 8:46 AM
> To: Chris Eeles <christopher.ee...@outlook.com>
> Cc: bioc-devel@r-project.org
> Subject: Re: [Bioc-devel] Bioconductor credentials issue
>  
> Hi Chris,
>  
> This is a very strange problem which I haven’t come across before. But let me 
> say this though, the fact that this email "benjamin.haibe.ka...@utoronto.ca 
> <mailto:benjamin.haibe.ka...@utoronto.ca>” is connected to your username, 
> Github ID and has your SSH keys is not correct. 
>  
> I fixed this last time by making you an account and giving you access through 
> an account registered tochristopher.ee...@outlook.com 
> <mailto:christopher.ee...@outlook.com>. I’m not sure what happened there? Any 
> insight? 
>  
> Nitesh
>  
> 
> 
> On Jun 17, 2020, at 10:51 AM, Chris Eeles <christopher.ee...@outlook.com 
> <mailto:christopher.ee...@outlook.com>> wrote:
>  
> Hello Bioconductor team,
> 
> I am having issues accessing our labs Bioconductor repositories and also 
> cannot login to the Bioconductor credentials website.
> 
> I had a similar issue less than a month ago, which Nitesh from the core team 
> helped me resolve. At that time I was able to login to Bioconductor 
> credentials for bothbenjamin.haibe.ka...@utoronto.ca 
> <mailto:benjamin.haibe.ka...@utoronto.ca><mailto:benjamin.haibe.ka...@utoronto.ca
>  <mailto:benjamin.haibe.ka...@utoronto.ca>> (my PI's maintainer email) as 
> well as christopher.ee...@outlook.com 
> <mailto:christopher.ee...@outlook.com><mailto:christopher.ee...@outlook.com 
> <mailto:christopher.ee...@outlook.com>> (my GitHub account) and could push to 
> upstream for all my packages. I can no longer do any of those things and do 
> not get an email when I attempt to reset the password on the credentials 
> account forchristopher.ee...@outlook.com 
> <mailto:christopher.ee...@outlook.com><mailto:christopher.ee...@outlook.com 
> <mailto:christopher.ee...@outlook.com>>.
> 
> Recently, two of my package submissions (RadioGx, ToxicoGx) were accepted. 
> This is the only change I can think of which may be the source of the issue.
> 
> If someone could advise on how to resolve this issue, it would be appreciated.
> 
> I have updates I am waiting to push to RadioGx.
> 
> Thanks for your assistance.
> 
> Best,
> ---
> Christopher Eeles
> Software Developer
> BHK Laboratory<http://www.bhklab.ca/ 
> <https://eur06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.bhklab.ca%2F&data=02%7C01%7C%7C7a0c772ea50d40b2a89508d813859317%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637280811899429986&sdata=D823UmfzHmPnYVmc3FpKxdTEdLubcRiYIBgLbgvCFhs%3D&reserved=0>>
> Princess Margaret Cancer Centre<https://www.pmgenomics.ca/pmgenomics/ 
> <https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.pmgenomics.ca%2Fpmgenomics%2F&data=02%7C01%7C%7C7a0c772ea50d40b2a89508d813859317%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637280811899439980&sdata=f1Kci%2BivEeH%2BPlrXKWmP5W%2FyV76KHByMMna5YLFF%2Bu4%3D&reserved=0>>
> University Health Network<http://www.uhn.ca/ 
> <https://eur06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.uhn.ca%2F&data=02%7C01%7C%7C7a0c772ea50d40b2a89508d813859317%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637280811899439980&sdata=iQEfS45UDWAe6%2F7BahqJMhen075gDDCQTHSyblXLUpk%3D&reserved=0>>
> 
> 
> 
> 
> 
> 
> 
>               [[alternative HTML version deleted]]
> 
> _______________________________________________
> Bioc-devel@r-project.org <mailto:Bioc-devel@r-project.org> mailing list
> https://stat.ethz.ch/mailman/listinfo/bioc-devel 
> <https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstat.ethz.ch%2Fmailman%2Flistinfo%2Fbioc-devel&data=02%7C01%7C%7C7a0c772ea50d40b2a89508d813859317%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637280811899449971&sdata=gxmpj%2BNfnxQlVa%2FzjtxWPM8LOS8DfoAi1f7aOKA%2FwA8%3D&reserved=0>

        [[alternative HTML version deleted]]

_______________________________________________
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel

Reply via email to