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> username), and if you've saved the same SSH key with
both accounts, then the push authorization scripts can fail.
This is because "<username>" and "gh-<username>" 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 <egourgoul...@gmail.com> 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
> 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 firstname.lastname@example.org.
> 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
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to email@example.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.