Skip to content

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

10 messages · Turaga, Nitesh, Simina Boca

#
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 the same error as I got before when doing "git push upstream
master":
Warning: Permanently added 'git.bioconductor.org,34.192.48.227' (ECDSA) to
the list of known hosts.
Enter passphrase for key '/c/Users/sboca/.ssh/id_rsa':
FATAL: W any packages/swfdr SiminaB 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 submit anything else or should BioC already know that I'm the
same person who is managing these packages?

Thanks so much!

Cheers,
Simina


On Tue, Sep 12, 2017 at 10:17 AM, Turaga, Nitesh <
Nitesh.Turaga at roswellpark.org> wrote:

            

  
    
#
Hi

You are using the wrong key.

The key we have on file for you is

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQDk1ywCtjVfC0wewYRCvzEiAac3so7nnRISC6xj3RkEerAUaOHHSA2RjlrG60TYjnEZGPyeN79oKNDP0NhCelsNR2usgviCVeS04Qs2RhyzQVf5iNP/pJIBt21pwIvsW3CBqB1bTECUG8E9pK3Gtm77uyRAwLImJtH1RioJ1JpGWKZ0r0ZU0O9c//zwr+Ae8OB94kSEuQ0yTXZj1nHfzL3vHsDtI8SsF3UE22RhS/sClW7s3raAlGNbmVdURZ2726JW2jIm40jeLDScdfO8UGEr5bWgVo7bnl6bzYUBsS2l8I2DZZHKIC+A1wBngNFpKNJ6dTpKzadkRudGbvU5qcIoX2zQNGzs/IyTh3LnX1TbCR1TbG/zC1BwoLB64yyjYI0O2nb+ZhhRyXyoljX6AtoMgr16vwUfO+ts3HoD060WTFx29jucqV8rtYXNhDzZmqQs8Z5Ajk++8A0x7fxtuAR1FTVNByaTmH3PAIW6WU9wXXpQEz72mSm7FpQgQDkOfjRBQKqRnGbhaay8qltMYaqzjQLA8pBl7YIa5Km5UvyvV2DbAHS0B1R8w7c8L3kmPj5MPJZdAcRc6Nc0ByE4pYVwv8mosMB4gt12Lzuj0hz5ID9SDUPq8QghGJiWhVybZpKafu8VQ7E5QvqBC6DHhpKhdodt16BymxkEWk380yODUQ==


You should use a private key corresponding to that public key.

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 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.
#
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.Turaga at roswellpark.org> wrote:

            

  
    
#
Hi Simina,

I?m assuming your keys are stored in the folder ?.ssh?. If that is the case, try,

	 ssh-keygen -y -e -f <private_key>

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? ending. If your public key is called ?id_rsa.pub? then your private key is most likely, ?id_rsa?). 

If you have to configure your git login, please follow the link below to make sure that the same key is used

http://bioconductor.org/developers/how-to/git/faq/

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 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.
1 day later
#
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
just used the google form to submit my public key.

Cheers,
Simina

On Fri, Jan 26, 2018 at 12:44 PM, Turaga, Nitesh <
Nitesh.Turaga at roswellpark.org> wrote:

            

  
    
2 days later
#
Hi Nitesh,

I submitted this key as well a couple of days ago:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQDP91Ifm9VtF76jYs4gPwJQx0nU3LBV
rsWwX4Eba1SOIHlHiXb45RHFZ0tvwV4yMNb9IXGAA3Kg0OnJs1YS1ddXTVkK
zyXAk4nlyiwSSSBe8gxhS1wPX5c8Zv8n28T71/bn90z61RKwkZc+hAZjrK/2Xiw/
FwFsnJfcEIrEE3HT86WVDeXdNPDzIxb/MSmjRmjS4MVZ4tHqG5nC6du8SOSXFKgap5Z3YCL0SVO/
2925LSbN4yiVHZQE5cY3iQoRBYtKCSr5/PBgsxrNxQhU8X//foqmLWGO0LVOV9Dk4Z3egHTrLXY+
jVTm6wJICowrTFN5Db07roo66wc9NbRAtb8lzDgc3u/GzYkQ5E2ZxA0r3j+XqrXRqa+qdl+
sZTyBi2WixFEQKQGCs/xUg0AA5DB2mkNZtQpffGdWdHhsuY01ylS5gHaql/
ciF18oMKJcdXIlQUtPTezT1hqHprx99WuHx+1HrBE50kU2rS3jsiFz7L2J1myt8jCq
vpz1UirShD2cnLqmcwOgA7uu/bTx6gIAy/a/fbPGpQ5boYx6hEF5Qxrj0E5ZxcvW6Q
1SxFbtSJsDyFHMvHafdZ3LpJdv9Fb/RtUEYl8zOxKqMZovdQVyy8XK1ZisSE
KZ+FXGcT//cFFcEphSEGnJ04/8u1r4uTn6mHriPQ5zYCr38a9TQPWCeQ==
smb310 at georgetown.edu
Do you have this matched up with my account right now? I'm still getting
the error message when trying to push upstream.

Thanks so much for all your help!

Best,
Simina
On Sun, Jan 28, 2018 at 9:53 AM, Simina Boca <smb310 at georgetown.edu> wrote:

            

  
    
#
Yes, that is the key we have. 

Please send me more information,( output of these commands)


	git remote -v

	ssh -T git at 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.org/developers/how-to/git/faq/ section point 16)


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 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.
#
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)
upstream        git at git.bioconductor.org:packages/MultiMed.git (fetch)
upstream        git at git.bioconductor.org:packages/MultiMed.git (push)

~\Documents\GitHub\MultiMed [master ?]> ssh -T git at git.bioconductor.org |
grep MultiMed
Warning: Permanently added 'git.bioconductor.org,34.192.48.227' (ECDSA) to
the list of known hosts.
 R      packages/MultiMed

The file containing my public key is named id_rsa.pub and the one
containing my private key is id_rsa, so I think that should be OK...

Best,
Simina


On Tue, Jan 30, 2018 at 9:36 PM, Turaga, Nitesh <
Nitesh.Turaga at roswellpark.org> wrote:

            

  
    
#
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
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.
#
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

On Wed, Jan 31, 2018 at 8:15 AM, Turaga, Nitesh <
Nitesh.Turaga at roswellpark.org> wrote: