Re: [sage-devel] Re: Git push issues

[Erik Bray]

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 adding that restriction to the SSH keys plugin for the next updated.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Git push issues

[Luca De Feo]

> 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 Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Git push issues

[Erik Bray]

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, 2018 at 9:01:56 PM UTC+5:30, Eric Gourgoulhon wrote:
>>
>> Hi,
>>
>> Le mardi 6 mars 2018 13:17:56 UTC+1, Meghana.M Reddy a écrit :
>>>
>>>  ! [remote rejected] HEAD -> t/24909/boruvka_algorithm_for_mst (hook
>>> declined)
>>> error: failed to push some refs to 'g...@trac.sagemath.org:sage.git'
>>>
>>
>> The target on trac does not seem correct; the syntax of the push command
>> should be
>>
>> git push trac HEAD:u/user_name/branch_name
>>
>>
>>
>> where user_name is the user name of your trac account. It seems that you
>> used the ticket number instead (24909), which of course, is not a valid user
>> name. If you want the latter to appear, you should put it after the
>> user_name:
>>
>>
>>
>> git push trac HEAD:u/user_name/24909/branch_name
>>
>> Best wishes,
>>
>> Eric.
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Git push issues

[Meghana.M Reddy]

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 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 
> > 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 
> > distinct users.  However, the way SSH authentication for git works is 
> > that your "username" is determined by your SSH key.  So if two users 
> > have the same SSH key, it's arbitrary which user you get authenticated 
> > as when you authenticate to the git server. 
> > 
> > Please associate your SSH key with one account or the other, but not 
> > both (or use different SSH keys with each account).  In most cases you 
> > don't even need both... 
> > 
> > On Tue, Mar 6, 2018 at 4:37 PM, Eric Gourgoulhon  > wrote: 
> >> 
> >> Le mardi 6 mars 2018 16:31:56 UTC+1, Eric Gourgoulhon a écrit : 
> >>> 
> >>> 
> >>> The target on trac does not seem correct; the syntax of the push 
> command 
> >>> should be 
> >>> 
> >>> git push trac HEAD:u/user_name/branch_name 
> >>> 
> >>> 
> >> 
> >> For more details, see 
> >> 
> http://doc.sagemath.org/html/en/developer/manual_git.html#pushing-your-changes-to-a-ticket
>  
> >> 
> >> Eric. 
> >> 
> >> -- 
> >> You received this message because you are subscribed to the Google 
> Groups 
> >> "sage-devel" group. 
> >> To unsubscribe from this group and stop receiving emails from it, send 
> an 
> >> email to sage-devel+...@googlegroups.com . 
> >> To post to this group, send email to sage-...@googlegroups.com 
> . 
> >> Visit this group at https://groups.google.com/group/sage-devel. 
> >> For more options, visit https://groups.google.com/d/optout. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Git push issues

[Meghana.M Reddy]

This was the mistake I made. It worked now. Thanks a lot for helping me out.

On Tuesday, March 6, 2018 at 9:01:56 PM UTC+5:30, Eric Gourgoulhon wrote:
>
> Hi,
>
> Le mardi 6 mars 2018 13:17:56 UTC+1, Meghana.M Reddy a écrit :
>>
>>  ! [remote rejected] HEAD -> t/24909/boruvka_algorithm_for_mst (hook 
>> declined)
>> error: failed to push some refs to 'g...@trac.sagemath.org:sage.git'
>>
>>
> The target on trac does not seem correct; the syntax of the push command 
> should be
>
> git push trac HEAD:u/user_name/branch_name
>  
>

> where user_name is the user name of your trac account. It seems that you 
> used the ticket number instead (24909), which of course, is not a valid 
> user name. If you want the latter to appear, you should put it after the 
> user_name:
>  
>

> git push trac HEAD:u/user_name/24909/branch_name
>
> Best wishes,
>
> Eric. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Git push issues

[Erik Bray]

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
> 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
> distinct users.  However, the way SSH authentication for git works is
> that your "username" is determined by your SSH key.  So if two users
> have the same SSH key, it's arbitrary which user you get authenticated
> as when you authenticate to the git server.
>
> Please associate your SSH key with one account or the other, but not
> both (or use different SSH keys with each account).  In most cases you
> don't even need both...
>
> On Tue, Mar 6, 2018 at 4:37 PM, Eric Gourgoulhon  
> wrote:
>>
>> Le mardi 6 mars 2018 16:31:56 UTC+1, Eric Gourgoulhon a écrit :
>>>
>>>
>>> The target on trac does not seem correct; the syntax of the push command
>>> should be
>>>
>>> git push trac HEAD:u/user_name/branch_name
>>>
>>>
>>
>> For more details, see
>> http://doc.sagemath.org/html/en/developer/manual_git.html#pushing-your-changes-to-a-ticket
>>
>> Eric.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-devel" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to sage-devel+unsubscr...@googlegroups.com.
>> To post to this group, send email to sage-devel@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-devel.
>> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Git push issues

[Erik Bray]

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
distinct users.  However, the way SSH authentication for git works is
that your "username" is determined by your SSH key.  So if two users
have the same SSH key, it's arbitrary which user you get authenticated
as when you authenticate to the git server.

Please associate your SSH key with one account or the other, but not
both (or use different SSH keys with each account).  In most cases you
don't even need both...

On Tue, Mar 6, 2018 at 4:37 PM, Eric Gourgoulhon  wrote:
>
> Le mardi 6 mars 2018 16:31:56 UTC+1, Eric Gourgoulhon a écrit :
>>
>>
>> The target on trac does not seem correct; the syntax of the push command
>> should be
>>
>> git push trac HEAD:u/user_name/branch_name
>>
>>
>
> For more details, see
> http://doc.sagemath.org/html/en/developer/manual_git.html#pushing-your-changes-to-a-ticket
>
> Eric.
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Git push issues

[Eric Gourgoulhon]

Le mardi 6 mars 2018 16:31:56 UTC+1, Eric Gourgoulhon a écrit :
>
>
> The target on trac does not seem correct; the syntax of the push command 
> should be
>
> git push trac HEAD:u/user_name/branch_name
>
>
>
For more details, see 
http://doc.sagemath.org/html/en/developer/manual_git.html#pushing-your-changes-to-a-ticket

Eric.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Git push issues

[Eric Gourgoulhon]

Hi,

Le mardi 6 mars 2018 13:17:56 UTC+1, Meghana.M Reddy a écrit :
>
>  ! [remote rejected] HEAD -> t/24909/boruvka_algorithm_for_mst (hook 
> declined)
> error: failed to push some refs to 'g...@trac.sagemath.org:sage.git'
>
>
The target on trac does not seem correct; the syntax of the push command 
should be

git push trac HEAD:u/user_name/branch_name

where user_name is the user name of your trac account. It seems that you 
used the ticket number instead (24909), which of course, is not a valid 
user name. If you want the latter to appear, you should put it after the 
user_name:

git push trac HEAD:u/user_name/24909/branch_name

Best wishes,

Eric. 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.