Re: [Bioc-devel] pushing changes to an existing package

2019-05-06 Thread Turaga, Nitesh
Hi Simina, This is an issue with Github. So just to walk through what might be happening, this is a case when users set up 2FA (two factor authentication). You might want to to set up SSH keys for GitHub as well, and use the SSH protocol (given below instead of HTTPS) as your remote origin.

Re: [Bioc-devel] pushing changes to an existing package

2019-05-06 Thread Simina Boca
Thank you again Nitesh! I'm now having some issues with pushing the origin master: C:\Users\smb310\Documents\GitHub\MultiMed [master ↑]> git push upstream master Warning: Permanently added 'git.bioconductor.org,34.192.48.227' (ECDSA) to the list of known hosts. Counting objects: 16, done. Delta

Re: [Bioc-devel] pushing changes to an existing package

2019-05-02 Thread Simina Boca
Thank you, it seems to work now! Do you have any idea of why the ".git" had been moved to ".g?" Just curious if it was something on my end. Cheers, Simina On Thu, May 2, 2019 at 2:15 PM Turaga, Nitesh wrote: > Once your access works you should see yourself as maintainer with Read and > Write ac

Re: [Bioc-devel] pushing changes to an existing package

2019-05-02 Thread Turaga, Nitesh
No idea Simina. Maybe a typo? Best, Nitesh 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 notif

Re: [Bioc-devel] pushing changes to an existing package

2019-05-02 Thread Turaga, Nitesh
Once your access works you should see yourself as maintainer with Read and Write access on MultiMed and CancerMutationAnalysis. Best Nitesh This email message may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent r

Re: [Bioc-devel] pushing changes to an existing package

2019-05-02 Thread Turaga, Nitesh
Hi Simina, Now that the RELEASE_3_9 branch and pushes are available to everyone, I can help you with this. It seems like your upstream branch is a little funny looking, is this how it got pasted in or maybe it's a mistake. What you gave: (I understand that the mailto: stuff may have been added

Re: [Bioc-devel] pushing changes to an existing package

2019-05-02 Thread Simina Boca
No worries, thanks for letting me know! Cheers, Simina On Thu, May 2, 2019, 1:02 PM Turaga, Nitesh wrote: > Hi Simina, > > We are going through the release process for Bioc 3.9 now, so all commits > are blocked until further notice. > > I can get back to helping you debug this issue once we are

Re: [Bioc-devel] pushing changes to an existing package

2019-05-02 Thread Turaga, Nitesh
Hi Simina, We are going through the release process for Bioc 3.9 now, so all commits are blocked until further notice. I can get back to helping you debug this issue once we are done with the release. https://stat.ethz.ch/pipermail/bioc-devel/2019-May/015050.html Best, Nitesh On May 2, 2019

Re: [Bioc-devel] pushing changes to an existing package

2019-05-02 Thread Simina Boca
Thank you Nitesh and sorry for missing this initially! This one seems fine: C:\Users\smb310\Documents\GitHub\MultiMed [devel]> git remote -v origin https://github.com/SiminaB/MultiMed.git (fetch) origin https://github.com/SiminaB/MultiMed.git (push) upstreamg...@git.bioconductor.org:pack

Re: [Bioc-devel] pushing changes to an existing package

2019-04-30 Thread Turaga, Nitesh
Hi Simina, http://bioconductor.org/developers/how-to/git/faq/ #14 to help us out a little more please. Best, Nitesh On Apr 30, 2019, at 10:45 AM, Simina Boca mailto:smb...@georgetown.edu>> wrote: Hello, I am trying to update my package MultiMed https://www.bioconductor.org/packages/release/