[Bioc-devel] cannot git (the package Pi)

[Turaga, Nitesh]

We name our release branches in the manner `RELEASE_3_6`. There is no branch `1.6.0`. As a maintainer you can only push to `master` and `RELEASE_3_6`.

You need to do something like, 

	git checkout RELEASE_3_6

	## Fix the bugs

	git commit <changes>

	git push origin RELEASE_3_6


Maintainers are not allowed to create random branches on the Bioconductor git repository like `1.6.0`. It’s a hook that is rejecting your push.

Best,

Nitesh 


> On Feb 7, 2018, at 5:58 AM, Hai Fang <hfang at well.ox.ac.uk> wrote:
> 
> Hi Nitesh
> 
> Following the instructions at http://bioconductor.org/developers/how-to/git/maintain-bioc-only/, I have successfully made changes to the development version (1.7.0 in my case). 
> 
> However, following the instructions at https://bioconductor.org/developers/how-to/git/bug-fix-in-release-and-devel/, I am unable to make change to the release version (1.6.0 in my case)
> 
> $ git checkout 1.6.0
> Switched to branch '1.6.0'
> $ git push origin 1.6.0
> Counting objects: 3, done.
> Delta compression using up to 4 threads.
> Compressing objects: 100% (3/3), done.
> Writing objects: 100% (3/3), 332 bytes | 0 bytes/s, done.
> Total 3 (delta 2), reused 0 (delta 0)
> remote: FATAL: W refs/heads/1.6.0 packages/Pi h.fang DENIED by fallthru
> remote: error: hook declined to update refs/heads/1.6.0
> To git at git.bioconductor.org:packages/Pi
>  ! [remote rejected] 1.6.0 -> 1.6.0 (hook declined)
> error: failed to push some refs to 'git at git.bioconductor.org:packages/Pi'
> 
> The error message shows it is denied by fallthru. Any ideas?
> 
> Best wishes,
> Hai
> 
> 
>> On 5 Feb 2018, at 15:00, Turaga, Nitesh <Nitesh.Turaga at roswellpark.org> wrote:
>> 
>> Hi,
>> 
>> We have that key on file for you. But if you never got access using that key, it is possible because you submitted an “ssh-dss” key instead of an “ssh-rsa”. 
>> 
>> To solve this, please submit another key, with https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/. The “-t rsa” tells keygen to create an RSA key instead of a DDS.
>> 
>> ssh-keygen -t rsa -b 4096 -C "your_email at example.com"
>> 
>> It’s either that, or you are using the wrong private key which corresponds to that public key.
>> 
>> Best,
>> 
>> Nitesh 
>> 
>>> On Feb 2, 2018, at 11:58 AM, Hai Fang <hfang at well.ox.ac.uk> wrote:
>>> 
>>> Dear Lori,
>>> I have an issue accessing my package called ‘Pi’.
>>> Following the instruction detailed at http://bioconductor.org/developers/how-to/git/maintain-bioc-only/, I have submit my SSH public key (shown in red):
>>> 
>>> $ cat ~/.ssh/id_dsa.pub
>>> ssh-dss AAAAB3NzaC1kc3MAAACBAJ1mqc5oq6taXNH6yQv8gFEgrYel/stqOon38vsrcNxZChSBkC7CY9S7zVuZwTgGXFT+qrQMQyMKkHWcgXH/1m+ZHwddBNa7ONNmytsJjgoHPb/Ku0LKlVL1Khv7NDX7fPua+BcNHG4/b5ThmY7nX6w8df085vN8cdWD1lP8kWHNAAAAFQCddUtZrX/P3xr+faddgKdPeqRBHQAAAIEAgXdO9WFyaAwASMDHYrdd1NfInCX/1VFMQT/UsxGbIzH7kpyQ1PSKRPGRymKqkUHUM62j8uy3lxq3Hi5OIwTw63A1pRipMfiKf7sm7C6lBHuRTjiYpXXEfJao9XsBmeoYPxWgA5eq1pHbjEaU7Fqubp8A46dsjE7NnPoDKu79N5kAAACAXI+zPRu1266IVZBB2ZHq44Le2FrEgnW882xV8KisrNJV0p3MCXNQoaOIz2w+XQT9n9/J06IiSuxagKuvGcO51pS/L7+pWGxWxTQLHNFFw+ubNHsVR39IIWyUUDNluUds5hlMWYDhC8YnuCZ17H9OqQVwxGzkEj2u/sUsjYm3goE= hfang at eduroam-219-092.nomadic.bris.ac.uk<mailto:hfang at eduroam-219-092.nomadic.bris.ac.uk>
>>> 
>>> When clone it into my local machine (OS X EI Capitan version 10.11.6), it said the permission denied (shown in pink).
>>> 
>>> $ git clone git at git.bioconductor.org:packages/Pi
>>> Cloning into 'Pi'...
>>> Permission denied (publickey).
>>> fatal: Could not read from remote repository.
>>> 
>>> Please make sure you have the correct access rights
>>> and the repository exists.
>>> 
>>> I wonder whether my SSH was indeed added into the system or should I regenerate the key or something else.
>>> 
>>> Many thanks,
>>> Hai
>>> 
>>> [[alternative HTML version deleted]]
>>> 
>>> _______________________________________________
>>> Bioc-devel at r-project.org mailing list
>>> https://stat.ethz.ch/mailman/listinfo/bioc-devel
>> 
>> 
>> 
>> 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.
> 
> 



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.