[Bioc-devel] Fwd: Re: failing Biocondcutor package STAN

[campos]

Dear Bioconductor team,

I am having some problems with pushing the changes of the package STAN 
to the master brunch.

I recently have changed my PC and I am trying to connect to the 
bioconductor package but I get the following error:

Permission denied (publickey).
fatal: Could not read from remote repository.

my remote origin is: git at git.bioconductor.org:packages/STAN 
<mailto:git at git.bioconductor.org:packages/STAN>

my username is r.campos

and my github account is rfael0cm


Could you help me?

I am really sorry but I am not experienced in github.

Regards,

Rafael






-------- Forwarded Message --------
Subject: 	Re: failing Biocondcutor package STAN
Date: 	Fri, 16 Mar 2018 17:47:53 +0000
From: 	Shepherd, Lori <Lori.Shepherd at RoswellPark.org>
To: 	campos <campos at mpipz.mpg.de>



No problem at all but please post to


bioc-devel at r-project.org


Include the commands you are trying with relevant output



Lori Shepherd

Bioconductor Core Team

Roswell Park Cancer Institute

Department of Biostatistics & Bioinformatics

Elm & Carlton Streets

Buffalo, New York 14263

------------------------------------------------------------------------
*From:* campos <campos at mpipz.mpg.de>
*Sent:* Friday, March 16, 2018 1:45:04 PM
*To:* Shepherd, Lori
*Subject:* Re: failing Biocondcutor package STAN

Hi Lori,


I am really sorry but I got completely lost again. I connected my 
account but somehow pushed don't work... it says that my remote origin 
is: git at git.bioconductor.org:packages/STAN 
<mailto:git at git.bioconductor.org:packages/STAN>

Could you help me?

Thank you very much,

Rafael


On 16.03.2018 14:52, Shepherd, Lori wrote:
>
> You'll have to submit the new key to the form
>
>
> https://docs.google.com/forms/d/1CCwUhjtG82rnmcTWYqY43WcmBx5YyQm5UD4pcs1dhEs/viewform?edit_requested=true
>
> with the username r.campos
>
>
> There is a link for key generation at the top of the form.
>
>
> For further key assistance please ask on the bioc-devel at r-project.org 
> <mailto:bioc-devel at r-project.org> mailing list as there are other 
> members on the team that are better apt to handle key questmy remote 
> origin is: git at git.bioconductor.org:packages/STAN 
> <mailto:git at git.bioconductor.org:packages/STAN>ions.
>
>
>
> Lori Shepherd
>
> Bioconductor Core Team
>
> Roswell Park Cancer Institute
>
> Department of Biostatistics & Bioinformatics
>
> Elm & Carlton Streets
>
> Buffalo, New York 14263
>
> ------------------------------------------------------------------------
> *From:* campos <campos at mpipz.mpg.de> <mailto:campos at mpipz.mpg.de>
> *Sent:* Friday, March 16, 2018 9:40:49 AM
> *To:* Shepherd, Lori
> *Subject:* Re: failing Biocondcutor package STAN
>
> Hi Lori,
>
>
> I just realized that I am on a new PC now and my public Key does not 
> work anymore. Could you please guide me through creating a new one so 
> I can push the changes/
>
> Thank you very much,
>
> Rafael
>
>
> On 16.03.2018 14:39, Shepherd, Lori wrote:
>>
>> Yes the normal process:
>>
>>
>> You would `git rm` any offending files
>>
>> Do a version bump in the Description file
>>
>> Commit the changes `git commit -a`
>>
>> Then `git�push upstream master`
>>
>>
>> Lori Shepherd
>>
>> Bioconductor Core Team
>>
>> Roswell Park Cancer Institute
>>
>> Department of Biostatistics & Bioinformatics
>>
>> Elm & Carlton Streets
>>
>> Buffalo, New York 14263
>>
>> ------------------------------------------------------------------------
>> *From:* campos <campos at mpipz.mpg.de> <mailto:campos at mpipz.mpg.de>
>> *Sent:* Friday, March 16, 2018 9:36:47 AM
>> *To:* Shepherd, Lori
>> *Subject:* Re: failing Biocondcutor package STAN
>>
>> Do I have to do a normal commit or push them as well?
>>
>>
>> On 16.03.2018 14:35, Shepherd, Lori wrote:
>>>
>>> I don't see any changes on our git server?
>>>
>>> Did you push to upstream?
>>>
>>>
>>> Lori Shepherd
>>>
>>> Bioconductor Core Team
>>>
>>> Roswell Park Cancer Institute
>>>
>>> Department of Biostatistics & Bioinformatics
>>>
>>> Elm & Carlton Streets
>>>
>>> Buffalo, New York 14263
>>>
>>> ------------------------------------------------------------------------
>>> *From:* campos <campos at mpipz.mpg.de> <mailto:campos at mpipz.mpg.de>
>>> *Sent:* Friday, March 16, 2018 8:52:40 AM
>>> *To:* Shepherd, Lori
>>> *Subject:* Re: failing Biocondcutor package STAN
>>>
>>> Hello Lori,
>>>
>>> thank you very much for your email. I just made the changes you have 
>>> told me it should work now hopefully. Please let me know if it is 
>>> not working
>>>
>>> Best,
>>>
>>> Rafael
>>>
>>>
>>> On 14.03.2018 15:49, Shepherd, Lori wrote:
>>>> Hello STAN maintainer:
>>>>
>>>>
>>>> It looks like you may have inadvertently added some build products 
>>>> (.o and .so files) to the git tree of your package.� This will 
>>>> cause compilation/installation ERRORS. �Please use `git rm` to 
>>>> remove these files from your package tree and a version bump.� In 
>>>> the future if you would like to have these files locally please 
>>>> enter them in a .gitignore file so they are not in version control.
>>>>
>>>>
>>>> Thank you.
>>>>
>>>>
>>>>
>>>> Lori Shepherd
>>>>
>>>> Bioconductor Core Team
>>>>
>>>> Roswell Park Cancer Institute
>>>>
>>>> Department of Biostatistics & Bioinformatics
>>>>
>>>> Elm & Carlton Streets
>>>>
>>>> Buffalo, New York 14263
>>>>
>>>>
>>>> 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. 
>>
>>
>> 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. 


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.

	[[alternative HTML version deleted]]