On Tue, Mar 6, 2018 at 11:24 PM, Luca De Feo wrote:
>> No problem. And this was a mistake *I* made. This is a side-effect I
>> did not consider and might want to think more about how to prevent...
>
> GitHub forbids using an ssh key twice. It seems the only reasonable thing to
> do.
Yes, I'm add
> No problem. And this was a mistake *I* made. This is a side-effect I
> did not consider and might want to think more about how to prevent...
GitHub forbids using an ssh key twice. It seems the only reasonable thing to do.
--
You received this message because you are subscribed to the Google Gr
On Tue, Mar 6, 2018 at 7:29 PM, Meghana.M Reddy wrote:
> This was the mistake I made. It worked now. Thanks a lot for helping me out.
No problem. And this was a mistake *I* made. This is a side-effect I
did not consider and might want to think more about how to prevent...
> On Tuesday, March 6,
Dear Erik,
I'm able to push my branch now. Thank you for your quick reply and helping
me with the SSH key.
Regards,
Meghana
On Tuesday, March 6, 2018 at 9:35:01 PM UTC+5:30, Erik Bray wrote:
>
> Hi Meghana,
>
> I've manually deleted your duplicate SSH key, so you should be able to
> push agai
Hi Meghana,
I've manually deleted your duplicate SSH key, so you should be able to
push again for now.
Best,
E
On Tue, Mar 6, 2018 at 5:02 PM, Erik Bray wrote:
> There's also an issue that if you've made both a local account on the
> Trac server, and you have logged in with GitHub (i.e. your
>
There's also an issue that if you've made both a local account on the
Trac server, and you have logged in with GitHub (i.e. your
gh- username), and if you've saved the same SSH key with
both accounts, then the push authorization scripts can fail.
This is because "" and "gh-" are treated as
distinc
