Skip to content

[Bioc-devel] Upstream permission denied

7 messages · Vladimir Kiselev, Simina Boca, Turaga, Nitesh

Original
Vladimir Kiselev
# 
Hello,

I am trying to push a new version of my package to git.bioconductor.org. I
was able to do that in the past. But I've recently changed my public key
and not sure whether this causes a problem. However, I can see my new
public key here - https://github.com/wikiselev.keys - and it is the first
one in the list.

When I look at the remote I can see git.bioconductor.org there but when I
try to push to upstream I get an error:

git remote -v
origin  git at github.com:hemberg-lab/scmap.git (fetch)
origin  git at github.com:hemberg-lab/scmap.git (push)
upstream        git at git.bioconductor.org:packages/scmap.git (fetch)
upstream        git at git.bioconductor.org:packages/scmap.git (push)

git push origin master
Everything up-to-date

git push upstream master
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.

Could anyone please help?
Many thanks in advance,
Kind regards,
Vladimir
Simina Boca
# 
Hi Vladimir,
This seems like the same error I was getting. Here is the helpful advice I
got from Sean:

Hi, Simina.

On Mon, Sep 11, 2017 at 12:55 PM, Vladimir Kiselev <
vladimir.yu.kiselev at gmail.com> wrote:

            

      
      
      
    

        

      
      
    

        
-- 
Simina M. Boca
Assistant Professor
Innovation Center for Biomedical Informatics  (ICBI)
Department of Oncology | Georgetown University Medical Center
Department of Biostatistics, Bioinformatics and Biomathematics | Georgetown
University Medical Center
Cancer Prevention and Control Program | Lombardi Comprehensive Cancer Center

2115 Wisconsin Ave NW, Suite 110
Washington, DC 20007
Phone: (202) 687-1545
Fax: (202) 687-5011
http://icbi.georgetown.edu/boca


On Mon, Sep 11, 2017 at 12:55 PM, Vladimir Kiselev <

        
vladimir.yu.kiselev at gmail.com> wrote:

        

            

      
      
      
    

        

      
      
    

        

  
    

      
      
    

  


  


      

    

    

      
      

        


  

        

      Vladimir Kiselev
    

    

      
      #
    

  


  

      
Hi Simina,

Thanks for your quick reply, but it looks like to forgot to paste your
response from Sean (at least I couldn't find it in your email).

Cheers,
Vlad

        
On Mon, Sep 11, 2017 at 5:58 PM Simina Boca <smb310 at georgetown.edu> wrote:

        

            

      
      
      
    

        

      
      
    

            

      
      
      
    

        

      
      
    

            

      
      
      
    

  
    

      
      
    

  


  


      

    

    

      
      

        


  

        

      Simina Boca
    

    

      
      #
    

  


  

      
Hi, Simina.

Take a look at the FAQ, #3, here:

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

Have you submitted an SSH key somehow?

            

      
      
      
    

        
When everything is working, you will "own" the bioconductor git repo, so
working it will be roughly equivalent to working with github. Opening an
issue on the package submission repo will not get you what you want and is
only for new packages.

Sean


On Mon, Sep 11, 2017 at 1:01 PM, Vladimir Kiselev <

        
vladimir.yu.kiselev at gmail.com> wrote:

        

            

      
      
      
    

        

      
      
    

            

      
      
      
    

        

      
      
    

            

      
      
      
    

        

  
    

      
      
    

  


  


      

    

    

      
      

        


  

        

      Vladimir Kiselev
    

    

      
      #
    

  


  

      
Thanks Simina,

I think I've done all the steps described there before and was able to push
to upstream. I can't do it anymore and try to figure out why.

Could anyone else please help?

Cheers,
Vlad

        
On Mon, 11 Sep 2017, 18:03 Simina Boca <smb310 at georgetown.edu> wrote:

        

            

      
      
      
    

        

      
      
    

            

      
      
      
    

        

      
      
    

            

      
      
      
    

  
    

      
      
    

  


  


      

    

    

      
      

        


  

        

      Turaga, Nitesh
    

    

      
      #
    

  


  

      
Hi

Your key will be added in the next run of our script. You can change your GitHub keys, our script will take in the new one, and you don?t have to resubmit on the google-form.

It is run manually at the moment at noon EST everyday.

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.

  
  


  


      

    

    

      
      

        


  

        

      Vladimir Kiselev
    

    

      
      #
    

  


  

      
Hi Nitesh,

Many thanks, I will check it in a couple of days.

Cheers,
Vlad

On Mon, 11 Sep 2017, 19:01 Turaga, Nitesh <Nitesh.Turaga at roswellpark.org>
wrote: