[Bioc-devel] Difficulty obtaining access to BioC git repository

On Oct 5, 2017, at 12:12 PM, Raborn, R. Taylor <rtraborn at indiana.edu> wrote:

Hi Nitesh;

I see- this makes sense. I apologize for my error and appreciate you providing me with access.

Thank you for your assistance with this.

Best regards,

Taylor

On Oct 5, 2017, at 12:04 PM, Turaga, Nitesh <Nitesh.Turaga at roswellpark.org> wrote:

Hi,

You have submitted multiple times with bad ID?s. This has not gone too well with our application and fails add your key. You first submitted ?rtraborn? with a set of keys, and then with the same set of keys with you valid SVN ID. The system does not add the same key twice with two separate usernames. 

I will manually make changes to give you access. 

Best

On Oct 5, 2017, at 11:49 AM, Raborn, R. Taylor <rtraborn at indiana.edu> wrote:

Hello:

I?m a co-developer and package maintainer for TSRchitect<https://bioconductor.org/packages/release/bioc/html/TSRchitect.html>, a relatively new Bioconductor package.

We wish to push package updates to the Bioconductor git repo, but as of yet I have been unable to do so. This post (link<https://support.bioconductor.org/p/100990/#101170>) on the BioC support page describes the current situation.

Given the previous, is there anything I could be overlooking in my attempts, or is my credential still in the process of being created?

Also, I would like to know if it would be possible to add the co-creater of this package, Dr. Volker Brendel (cc?d on this email), as (another) maintainer of TSRchitect. His GitHub page is here: https://github.com/vpbrendel.

Thank you in advance for your help.

Best regards,

Taylor

--------------------------------
R. Taylor Raborn, PhD
Postdoctoral Fellow, Brendel Group
Computational Genome Science Laboratory
Indiana University, Simon Hall 205B
P:  812.856.9572
rtraborn at indiana.edu<mailto:rtraborn at indiana.edu> | brendelgroup.org<http://brendelgroup.org>




	[[alternative HTML version deleted]]

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.