[Bioc-devel] Issue when fetching upstream

Hi H?l?ne,

That?s good to hear.

I?m not aware of emails being sent out by the build machine. But you can follow your build at your package landing page http://secure-web.cisco.com/1K8bZUv2jC_MzuYxS0V6NU7tZf8xj9tFzzoB7-TlCsN45WBt7lsQa408pNJPQDCVUhP3SKU7BWf4uy50SxnkhrnqJko8LDwQQVchJTqeJzHmdjFR9OZhE_io-dv7-TOrWGHuWrqDVC8mGOCJMSoP4wbpmKIoyysNvlncZEPS4JGUL4kKOUK9eb0Bw5OS9dFek4tyDyxfyT6DM6knfO3wyBM-J6R7rjgrfVAUEcNf-flC_gt7MszrsoRkwxlOatj8dYwBA3TA-qN5oygwJC4IIVA-h_q05Xq0R2UWxXvqtA-DW3q6zm8jCN7o82oGbMF7B/http%3A%2F%2Fbioconductor.org%2FcheckResults%2Fdevel%2Fbioc-LATEST%2Fwpm%2F <http://secure-web.cisco.com/1K8bZUv2jC_MzuYxS0V6NU7tZf8xj9tFzzoB7-TlCsN45WBt7lsQa408pNJPQDCVUhP3SKU7BWf4uy50SxnkhrnqJko8LDwQQVchJTqeJzHmdjFR9OZhE_io-dv7-TOrWGHuWrqDVC8mGOCJMSoP4wbpmKIoyysNvlncZEPS4JGUL4kKOUK9eb0Bw5OS9dFek4tyDyxfyT6DM6knfO3wyBM-J6R7rjgrfVAUEcNf-flC_gt7MszrsoRkwxlOatj8dYwBA3TA-qN5oygwJC4IIVA-h_q05Xq0R2UWxXvqtA-DW3q6zm8jCN7o82oGbMF7B/http%3A%2F%2Fbioconductor.org%2FcheckResults%2Fdevel%2Fbioc-LATEST%2Fwpm%2F> .

But note that it takes about 24 hours for a new build to occur.

Best,

Nitesh


> On Oct 6, 2020, at 11:44 AM, H?l?ne Borges <borges.helene.sophie at gmail.com> wrote:
>
> Hi,
> Thanks for the suggestion, now the push worked!
> But it's weird I still have not received the email for the follow-up of the build, yet I made a bump version (from 0.99.13 to 0.99.14) ...
> Should I wait a little longer?
> cheers,
> H?l?ne
>
> Le mar. 6 oct. 2020 ? 17:18, Nitesh Turaga <nturaga.bioc at gmail.com <mailto:nturaga.bioc at gmail.com>> a ?crit :
> Hi,
>
> Easiest solution is to upload a new key. I?ve checked our system and everything is correct, and you seem to be doing things right on your end as well.
>
> The most likely problem is, when you ?fetch? the wrong key is being used.
>
> Best,
>
> Nitesh
>
>> On Oct 6, 2020, at 11:15 AM, H?l?ne Borges <borges.helene.sophie at gmail.com <mailto:borges.helene.sophie at gmail.com>> wrote:
>>
>> Hello,
>> I am the maintainer of the wpm package  (currently in devel
>> on Bioconductor).
>> I have fixed an issue, but when I push to the upstream, permission is
>> denied. I have the correct output when I check the command "git remote -v":
>> origin  https://secure-web.cisco.com/1z7SWowMV_8xOS8J_d_a4Q-F35EUysngS6V7ISWTNuZ3yRyL2sBbqkjgwPq4zJiqSoxrqE3OdR05q2GFzAgQcxOo738uhMCXmfqgQArWBEvn18WKS9W3LGZP7FRPfd4jyzStKMscYl2P6OiKmitcPJYhIwsDxefP4UiAdj7gMtca1sL5on0zv7Q-yAs_RDJXOq23dMfG9Atrm3H0xuvHKDM0O-x9tw5FJ2txqe-JgHpJ_ZJ2ioyG-W-nRH-wQZU3RJ0-_YDZoJGGlSVtZIsKOT7Scdu2GyD6ZhZLe_j_mLcqp1eUIXRl_oaWBCzk560B5/https%3A%2F%2Fgithub.com%2FHelBor%2Fwpm.git <https://secure-web.cisco.com/1z7SWowMV_8xOS8J_d_a4Q-F35EUysngS6V7ISWTNuZ3yRyL2sBbqkjgwPq4zJiqSoxrqE3OdR05q2GFzAgQcxOo738uhMCXmfqgQArWBEvn18WKS9W3LGZP7FRPfd4jyzStKMscYl2P6OiKmitcPJYhIwsDxefP4UiAdj7gMtca1sL5on0zv7Q-yAs_RDJXOq23dMfG9Atrm3H0xuvHKDM0O-x9tw5FJ2txqe-JgHpJ_ZJ2ioyG-W-nRH-wQZU3RJ0-_YDZoJGGlSVtZIsKOT7Scdu2GyD6ZhZLe_j_mLcqp1eUIXRl_oaWBCzk560B5/https%3A%2F%2Fgithub.com%2FHelBor%2Fwpm.git> (fetch)
>> origin  https://secure-web.cisco.com/1z7SWowMV_8xOS8J_d_a4Q-F35EUysngS6V7ISWTNuZ3yRyL2sBbqkjgwPq4zJiqSoxrqE3OdR05q2GFzAgQcxOo738uhMCXmfqgQArWBEvn18WKS9W3LGZP7FRPfd4jyzStKMscYl2P6OiKmitcPJYhIwsDxefP4UiAdj7gMtca1sL5on0zv7Q-yAs_RDJXOq23dMfG9Atrm3H0xuvHKDM0O-x9tw5FJ2txqe-JgHpJ_ZJ2ioyG-W-nRH-wQZU3RJ0-_YDZoJGGlSVtZIsKOT7Scdu2GyD6ZhZLe_j_mLcqp1eUIXRl_oaWBCzk560B5/https%3A%2F%2Fgithub.com%2FHelBor%2Fwpm.git <https://secure-web.cisco.com/1z7SWowMV_8xOS8J_d_a4Q-F35EUysngS6V7ISWTNuZ3yRyL2sBbqkjgwPq4zJiqSoxrqE3OdR05q2GFzAgQcxOo738uhMCXmfqgQArWBEvn18WKS9W3LGZP7FRPfd4jyzStKMscYl2P6OiKmitcPJYhIwsDxefP4UiAdj7gMtca1sL5on0zv7Q-yAs_RDJXOq23dMfG9Atrm3H0xuvHKDM0O-x9tw5FJ2txqe-JgHpJ_ZJ2ioyG-W-nRH-wQZU3RJ0-_YDZoJGGlSVtZIsKOT7Scdu2GyD6ZhZLe_j_mLcqp1eUIXRl_oaWBCzk560B5/https%3A%2F%2Fgithub.com%2FHelBor%2Fwpm.git> (push)
>> upstream        git at git.bioconductor.org <mailto:git at git.bioconductor.org>:packages/wpm.git (fetch)
>> upstream        git at git.bioconductor.org <mailto:git at git.bioconductor.org>:packages/wpm.git (push)
>>
>> the trouble comes with git fetch --all: permission denied for upstream.
>> I don't really understand what's happening here, because when I check on my
>> Bioc Credentials, I can see that I have permission for the wpm package, and
>> that the SSH key is also here...
>> What should I do?
>> Thanks for your help!
>>
>>       [[alternative HTML version deleted]]
>>
>> _______________________________________________
>> Bioc-devel at r-project.org <mailto:Bioc-devel at r-project.org> mailing list
>> https://secure-web.cisco.com/1vF1K5jCjp1S4fSCBXNDJx5xIxpE7Eh508TzpfGGAYLWY-dhwjhU2vvjQjKNW4uYZ_HfWInZv587gDMJZJAVisIXfGjvu-T5kRaIsVyqfmpaIBdTqXF0IzN36CnLYJzQkjxKuAxuEhqoA3eRglvlmLp9EqP0YwyXRURNRNWJP4DRrqCjJceexr3cXPeWiMdCdegIK8LLQ85L49l11XdUu1A4hy7NfvyG6ORgPwJopfkfymG_bWVfDXjxf7my6FHQ8aO31uDMVnFkwXgzT6Kez-btZBIjLcS3W-8QrBb_ZcpCszmHa9FNEcKv91zmOJvTa/https%3A%2F%2Fstat.ethz.ch%2Fmailman%2Flistinfo%2Fbioc-devel <https://secure-web.cisco.com/1vF1K5jCjp1S4fSCBXNDJx5xIxpE7Eh508TzpfGGAYLWY-dhwjhU2vvjQjKNW4uYZ_HfWInZv587gDMJZJAVisIXfGjvu-T5kRaIsVyqfmpaIBdTqXF0IzN36CnLYJzQkjxKuAxuEhqoA3eRglvlmLp9EqP0YwyXRURNRNWJP4DRrqCjJceexr3cXPeWiMdCdegIK8LLQ85L49l11XdUu1A4hy7NfvyG6ORgPwJopfkfymG_bWVfDXjxf7my6FHQ8aO31uDMVnFkwXgzT6Kez-btZBIjLcS3W-8QrBb_ZcpCszmHa9FNEcKv91zmOJvTa/https%3A%2F%2Fstat.ethz.ch%2Fmailman%2Flistinfo%2Fbioc-devel>
>


        [[alternative HTML version deleted]]

_______________________________________________
Bioc-devel at r-project.org mailing list
https://secure-web.cisco.com/1vF1K5jCjp1S4fSCBXNDJx5xIxpE7Eh508TzpfGGAYLWY-dhwjhU2vvjQjKNW4uYZ_HfWInZv587gDMJZJAVisIXfGjvu-T5kRaIsVyqfmpaIBdTqXF0IzN36CnLYJzQkjxKuAxuEhqoA3eRglvlmLp9EqP0YwyXRURNRNWJP4DRrqCjJceexr3cXPeWiMdCdegIK8LLQ85L49l11XdUu1A4hy7NfvyG6ORgPwJopfkfymG_bWVfDXjxf7my6FHQ8aO31uDMVnFkwXgzT6Kez-btZBIjLcS3W-8QrBb_ZcpCszmHa9FNEcKv91zmOJvTa/https%3A%2F%2Fstat.ethz.ch%2Fmailman%2Flistinfo%2Fbioc-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.