OK it works for me now.
Thanks a lot Erik,
Julien
--
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,
Hi Erik,
I am still having the same error everytime i use git trac.
On Tuesday, July 5, 2016 at 4:03:10 PM UTC+5:30, Erik Bray wrote:
>
> On Tue, Jul 5, 2016 at 10:50 AM, Julien Lavauzelle
> > wrote:
> > Hi,
> >
> > I made the git-trac update and I got the same 'Permission denied'
> problem
On Tue, Jul 5, 2016 at 10:50 AM, Julien Lavauzelle
wrote:
> Hi,
>
> I made the git-trac update and I got the same 'Permission denied' problem
> with my new keys (new laptop also), when trying to push or to use 'ssh -T
> g...@trac.sagemath.org'. But I didn't understand how tara or eviatar fixed
> i
Mine suddenly started working overnight. I know this was the case for at
least one other person. I assume something was done on the server.
Eviatar
On Jul 5, 2016 2:12 AM, "Julien Lavauzelle"
wrote:
> Hi,
>
> I made the git-trac update and I got the same 'Permission denied' problem
> with my new
Hi,
I made the git-trac update and I got the same 'Permission denied' problem
with my new keys (new laptop also), when trying to push or to use 'ssh -T
g...@trac.sagemath.org'. But I didn't understand how tara or eviatar fixed
it. Could someone tell me ?
Best,
Julien (login jlavauzelle)
--
It is now working for me! Not sure what happened.
Eviatar
On Thursday, 30 June 2016 23:34:49 UTC-7, Dima Pasechnik wrote:
>
> perhaps adding an invalid ssh key still breaks the communication between
> git server and trac...
> Can they still push changes to the git server?
>
> On Friday, July 1,
On Thu, 30 Jun 2016, Viviane Pons wrote:
I'm with two new sage git users: eviatarbach and avenrias and they seem to
have a similar problem. They have put their ssh key on trac (I've checked),
but it keeps saying "Permission denied (publickey)" when they try
I got the same error.
(Not that it
perhaps adding an invalid ssh key still breaks the communication between
git server and trac...
Can they still push changes to the git server?
On Friday, July 1, 2016 at 12:35:55 AM UTC+1, Viviane Pons wrote:
>
> Hi,
>
> I'm with two new sage git users: eviatarbach and avenrias and they seem to
Hi,
I'm with two new sage git users: eviatarbach and avenrias and they seem to
have a similar problem. They have put their ssh key on trac (I've checked),
but it keeps saying "Permission denied (publickey)" when they try
ssh -T g...@trac.sagemath.org info
Here is what they get:
OpenSSH_7.2p2 Ub
Thanks everyone, I am able to push changes to trac now.
Tara
--
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 t
On Wed, Jun 29, 2016 at 11:02 AM, Volker Braun wrote:
> I think the posts get a bit maimed because google anonymizes the email
> addresses to prevent spam harvesting. You need to use "git at" in front of
> the hostname to test your ssh keys. As for the hostname, both
> git.sagemath.org and trac.sa
I think the posts get a bit maimed because google anonymizes the email
addresses to prevent spam harvesting. You need to use "git at" in front of
the hostname to test your ssh keys. As for the hostname, both
git.sagemath.org and trac.sagemath.org work. But you can't use "myusername
at {git,trac
On Wed, Jun 29, 2016 at 9:19 AM, Volker Braun wrote:
> You can't ssh into trac. What should work is:
>
> $ ssh g...@git.sagemath.org
> PTY allocation request failed on channel 0
> hello vbraun, this is git@trac running gitolite3 3.5.3.1-2 (Debian) on git
> 1.9.1
>
> R W sage
I'm not so sure if t
You can't ssh into trac. What should work is:
$ ssh g...@git.sagemath.org
PTY allocation request failed on channel 0
hello vbraun, this is git@trac running gitolite3 3.5.3.1-2 (Debian) on git
1.9.1
R W sage
On Tuesday, June 28, 2016 at 11:26:32 PM UTC+2, tara fife wrote:
>
> I wasn't able t
I ran ssh -v k...@trac.sagemath.org. It also fails :-) But I have no
problem in pushing changes to trac...
On Wednesday, June 29, 2016 at 11:49:31 AM UTC+9, tara fife wrote:
>
> Thanks,
>
> I went into the known_host file, and deleted everything, since I should
> only have things for Sage. Then
Thanks,
I went into the known_host file, and deleted everything, since I should only
have things for Sage. Then I reran ssh -v g...@trac.sagemath.org, and got the
same error message as before. I already pasted my new public key into the text
box in the ssh preferences tab and saved it. I don't
Perhaps you had the same issue with mine. Then the correct fix was just to
remove the line for trac.sagemath.org in the file .ssh/known_hosts, not
resetting your own ssh keys. Now that you seem to have changed your ssh
private/public key pair, you need to register your new ssh public key to
tra
17 matches
Mail list logo
