Re: [Bioc-devel] updating Bioconductor package that is already on Github

Hi Simina, I think the missing information was your package name. There was also the fact that your initial google sheet submission was wrong. You were supposed to give your SVN ID “s.boca” to the google sheet, which would have automatically linked all your packages and your Github ID’s SSH ke

Re: [Bioc-devel] updating Bioconductor package that is already on Github

Excellent, thank you so much, it worked now! I had specified the package name but perhaps should have started another email thread. What was the issue though, was it the public key or was there something that needed to be changed on your end? (Trying to remember for the next time) Cheers, Simina

Re: [Bioc-devel] updating Bioconductor package that is already on Github

Hi Simina, You should have access now. The missing information in all the previous communications was the name of the package you were trying to access. Nitesh > On Jan 30, 2018, at 10:51 PM, Simina Boca wrote: > > Sure! This is for the MultiMed package, not swfdr, so I made that change > bel

Re: [Bioc-devel] updating Bioconductor package that is already on Github

Sure! This is for the MultiMed package, not swfdr, so I made that change below: ~\Documents\GitHub\MultiMed [master ≡]> git remote -v origin https://github.com/SiminaB/MultiMed.git (fetch) origin https://github.com/SiminaB/MultiMed.git (push) upstreamg...@git.bioconductor.org:packages/Mu

Re: [Bioc-devel] updating Bioconductor package that is already on Github

Yes, that is the key we have. Please send me more information,( output of these commands) git remote -v ssh -T g...@git.bioconductor.org | grep swfdr You might want to make sure you are using correct private key by setting up a config file in your SSH. (http://bioconductor.or

Re: [Bioc-devel] updating Bioconductor package that is already on Github

Hi Nitesh, I submitted this key as well a couple of days ago: ssh-rsa B3NzaC1yc2EDAQABAAACAQDP91Ifm9VtF76jYs4gPwJQx0nU3LBV rsWwX4Eba1SOIHlHiXb45RHFZ0tvwV4yMNb9IXGAA3Kg0OnJs1YS1ddXTVkK zyXAk4nlyiwSSSBe8gxhS1wPX5c8Zv8n28T71/bn90z61RKwkZc+hAZjrK/2Xiw/ FwFsnJfcEIrEE3HT86WVDeXdNPDzIxb/MSmjRmjS4

Re: [Bioc-devel] updating Bioconductor package that is already on Github

Thanks so much Nitesh! I had submitted my public key last time I did this (a few months ago) so I thought I didn't have to do it again. However, for whatever reason, the public key you sent is a bit different from mine (not sure why, since I haven't generated any more since then). In any case, I ju

Re: [Bioc-devel] updating Bioconductor package that is already on Github

Hi Simina, I’m assuming your keys are stored in the folder “.ssh”. If that is the case, try, ssh-keygen -y -e -f That command will print out a public key. If that public key is the same as the one I’ve sent you, they you can use that. (Remember that public keys, don’t have “.pub” en

Re: [Bioc-devel] updating Bioconductor package that is already on Github

Hi You are using the wrong key. The key we have on file for you is ssh-rsa B3NzaC1yc2EDAQABAAACAQDk1ywCtjVfC0wewYRCvzEiAac3so7nnRISC6xj3RkEerAUaOHHSA2RjlrG60TYjnEZGPyeN79oKNDP0NhCelsNR2usgviCVeS04Qs2RhyzQVf5iNP/pJIBt21pwIvsW3CBqB1bTECUG8E9pK3Gtm77uyRAwLImJtH1RioJ1JpGWKZ0r0ZU0O9c//zwr+Ae

Re: [Bioc-devel] updating Bioconductor package that is already on Github

Thank you Nitesh! Where should I use the private key? I only see the public key mentioned here: http://bioconductor.org/developers/how-to/git/maintain-github-bioc/ Sorry if I'm missing something very obvious! Best, Simina On Fri, Jan 26, 2018 at 12:23 PM, Turaga, Nitesh < nitesh.tur...@roswellpar

Re: [Bioc-devel] updating Bioconductor package that is already on Github

Dear all, Thank you to Sean, Lori, and Nitesh for helping me out with a package update last year. I'm now trying to update another package, MultiMed. I have it set up on Github https://github.com/SiminaB/MultiMed - you can see that the contributors are Marc, Herve, and Dan Tenenbaum. However, I get

Re: [Bioc-devel] updating Bioconductor package that is already on Github

Hi Simina, Please try again now. The issue was you didn’t submit your SVN ID “s.boca”. This is needed for people who have been maintainers before the Git transition, to associate your key to the package. For new packages this issue doesn’t apply, because we just collect their Github IDs. Ho

Re: [Bioc-devel] updating Bioconductor package that is already on Github

Thank you again Sean and Lori! I am now past that initial stage. I now have to resolve merge conflicts, primarily in the DESCRIPTION file. When following the instructions here http://bioconductor.org/ developers/how-to/git/resolve-conflicts/ however, I ended up getting the error below: ~\Documents

Re: [Bioc-devel] updating Bioconductor package that is already on Github

Thank you so much Sean and Lori! For some reason I thought the ssh key part was only relevant if the package was submitted via svn, which is why i had overlooked those instructions initially. Cheers, Simina On Wed, Sep 6, 2017 at 7:01 AM, Shepherd, Lori < lori.sheph...@roswellpark.org> wrote: >

Re: [Bioc-devel] updating Bioconductor package that is already on Github

Have you submitted your ssh key https://docs.google.com/forms/d/e/1FAIpQLSdlTbNjsQJDp0BA480vo4tNufs0ziNyNmexegNZgNieIovbAA/viewform [https://lh6.googleusercontent.com/aTIh4yWF4TsFYR95qIA_lBuCgvLJ88Q4WzDmdBuie6ndQirxWI0jhfRBF7eO-n3W6SE=w1200-h630-p]

Re: [Bioc-devel] updating Bioconductor package that is already on Github

Hi, Simina. On Tue, Sep 5, 2017 at 11:40 PM, Simina Boca wrote: > Dear all, > > I hope this isn't a duplicate of another question. Here goes: > > - I would like to update my swfdr package, which is already on > Bioconductor. It is also on Github and my submission process was via > opening an iss