Could you push a branch using "plain" git? Assuming the output of
git remote -v contains "trac g...@trac.sagemath.org:sage.git (push)" you should be able to push a branch like this: git push trac HEAD:u/gh-diveshkr-code/test1 On Sun, Feb 23, 2020 at 3:33 PM DIVESH KUMAR <f20170...@pilani.bits-pilani.ac.in> wrote: > > I am able to push and pull now to my repository but still am getting this > error any idea why it's still happening. Thanks a lot for your help so far. >>> >>> Saved trac username. >>> >>> Saved trac password. >>> >>> Trac xmlrpc URL: >>> >>> https://trac.sagemath.org/xmlrpc (anonymous) >>> >>> https://trac.sagemath.org/login/xmlrpc (authenticated) >>> >>> realm sage.math.washington.edu >>> >>> Using token-based authentication with the provided JWT token >>> >>> generated by the Trac server. If a username and password were >>> >>> configured as well, the token takes priority. To unset the >>> >>> token use: >>> >>> >>> git trac config --token= >>> >>> >>> Retrieving SSH keys... >>> >>> Traceback (most recent call last): >>> >>> File "/home/diveshcode/.local/bin/git-trac", line 17, in <module> >>> >>> cmdline.launch() >>> >>> File >>> "/home/diveshcode/.local/lib/python2.7/site-packages/git_trac/cmdline.py", >>> line 284, in launch >>> >>> app.print_config() >>> >>> File >>> "/home/diveshcode/.local/lib/python2.7/site-packages/git_trac/app.py", line >>> 391, in print_config >>> >>> for key in self.trac.get_ssh_fingerprints(): >>> >>> File >>> "/home/diveshcode/.local/lib/python2.7/site-packages/git_trac/trac_server.py", >>> line 111, in get_ssh_fingerprints >>> >>> for key in self.get_ssh_keys(): >>> >>> File >>> "/home/diveshcode/.local/lib/python2.7/site-packages/git_trac/trac_server.py", >>> line 103, in get_ssh_keys >>> >>> return self.authenticated_proxy.sshkeys.getkeys() >>> >>> File "/usr/lib/python2.7/xmlrpclib.py", line 1243, in __call__ >>> >>> return self.__send(self.__name, args) >>> >>> File "/usr/lib/python2.7/xmlrpclib.py", line 1602, in __request >>> >>> verbose=self.__verbose >>> >>> File "/usr/lib/python2.7/xmlrpclib.py", line 1283, in request >>> >>> return self.single_request(host, handler, request_body, verbose) >>> >>> File >>> "/home/diveshcode/.local/lib/python2.7/site-packages/git_trac/token_transport.py", >>> line 35, in single_request >>> >>> raise TracConnectionError(e.reason) >>> >>> git_trac.trac_error.TracConnectionError: CERTIFICATE_VERIFY_FAILED >> >> > > On Saturday, February 22, 2020 at 3:32:36 AM UTC+5:30, Dima Pasechnik wrote: >> >> On Fri, Feb 21, 2020 at 6:19 PM varenyam bakshi <varen...@gmail.com> wrote: >> > >> > i typed the following command >> > $ssh g...@trac.sagemath.org info >> > >> > and here is the output >> > >> > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ >> > @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ >> > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ >> > IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! >> > Someone could be eavesdropping on you right now (man-in-the-middle attack)! >> > It is also possible that a host key has just been changed. >> > The fingerprint for the ECDSA key sent by the remote host is >> > SHA256:HfxdGoZjCYKxyWtGVeElPM8HhSugcRM322WH4qxHBoc. >> > Please contact your system administrator. >> that's what I am geting now: >> >> SHA256:4Op/q3b5792x+F1lHSKRi5UIORAPDlIFVA5cUq9YVXI >> >> weird - or perhaps ir is not as stable as we think. >> >> > Add correct host key in /home/uranium/.ssh/known_hosts to get rid of this >> > message. >> > Offending ECDSA key in /home/uranium/.ssh/known_hosts:1 >> > remove with: >> > ssh-keygen -f "/home/uranium/.ssh/known_hosts" -R "trac.sagemath.org" >> > ECDSA host key for trac.sagemath.org has changed and you have requested >> > strict checking. >> > Host key verification failed. >> > >> > also i am unable to run >> > $git trac try <ticket no.> >> > or >> > $git trac checkout <ticket no.> >> > >> > On Fri, Feb 21, 2020 at 10:12 PM Dima Pasechnik <dim...@gmail.com> wrote: >> >> >> >> I suggest that you try creating a small git repo on github and try to >> >> push to it and pull from it. If it doesn't work then you have a problem >> >> with a firewall or something like that. >> >> >> >> On Fri, 21 Feb 2020, 16:32 DIVESH KUMAR, >> >> <f201...@pilani.bits-pilani.ac.in> wrote: >> >>> >> >>> Hey I am facing a similar problem in configuring git with trac using the >> >>> git trac config --user USERNAME --pass 'PASSWORD >> >>> >> >>> command given in this link but ssh authentications fails. >> >>> while using >> >>> git trac config --user USERNAME --pass 'PASSWORD >> >>> >> >>> I get this error: >> >>>>> >> >>>>> Saved trac username. >> >>>>> >> >>>>> Saved trac password. >> >>>>> >> >>>>> Trac xmlrpc URL: >> >>>>> >> >>>>> https://trac.sagemath.org/xmlrpc (anonymous) >> >>>>> >> >>>>> https://trac.sagemath.org/login/xmlrpc (authenticated) >> >>>>> >> >>>>> realm sage.math.washington.edu >> >>>>> >> >>>>> Using token-based authentication with the provided JWT token >> >>>>> >> >>>>> generated by the Trac server. If a username and password were >> >>>>> >> >>>>> configured as well, the token takes priority. To unset the >> >>>>> >> >>>>> token use: >> >>>>> >> >>>>> >> >>>>> git trac config --token= >> >>>>> >> >>>>> >> >>>>> Retrieving SSH keys... >> >>>>> >> >>>>> Traceback (most recent call last): >> >>>>> >> >>>>> File "/home/diveshcode/git-trac-command/bin/git-trac", line 17, in >> >>>>> <module> >> >>>>> >> >>>>> cmdline.launch() >> >>>>> >> >>>>> File "/home/diveshcode/git-trac-command/git_trac/cmdline.py", line >> >>>>> 284, in launch >> >>>>> >> >>>>> app.print_config() >> >>>>> >> >>>>> File "/home/diveshcode/git-trac-command/git_trac/app.py", line 391, >> >>>>> in print_config >> >>>>> >> >>>>> for key in self.trac.get_ssh_fingerprints(): >> >>>>> >> >>>>> File "/home/diveshcode/git-trac-command/git_trac/trac_server.py", >> >>>>> line 111, in get_ssh_fingerprints >> >>>>> >> >>>>> for key in self.get_ssh_keys(): >> >>>>> >> >>>>> File "/home/diveshcode/git-trac-command/git_trac/trac_server.py", >> >>>>> line 103, in get_ssh_keys >> >>>>> >> >>>>> return self.authenticated_proxy.sshkeys.getkeys() >> >>>>> >> >>>>> File "/usr/lib/python2.7/xmlrpclib.py", line 1243, in __call__ >> >>>>> >> >>>>> return self.__send(self.__name, args) >> >>>>> >> >>>>> File "/usr/lib/python2.7/xmlrpclib.py", line 1602, in __request >> >>>>> >> >>>>> verbose=self.__verbose >> >>>>> >> >>>>> File "/usr/lib/python2.7/xmlrpclib.py", line 1283, in request >> >>>>> >> >>>>> return self.single_request(host, handler, request_body, verbose) >> >>>>> >> >>>>> File >> >>>>> "/home/diveshcode/git-trac-command/git_trac/token_transport.py", line >> >>>>> 35, in single_request >> >>>>> >> >>>>> raise TracConnectionError(e.reason) >> >>>>> >> >>>>> git_trac.trac_error.TracConnectionError: CERTIFICATE_VERIFY_FAILED >> >>>> >> >>>> >> >>> >> >>> >> >>> output of this is >> >>> ls -al ~/.ssh/ >> >>> >> >>> total 20 >> >>> drwx------ 2 diveshcode diveshcode 4096 Feb 8 11:14 . >> >>> drwxr-xr-x 73 diveshcode diveshcode 4096 Feb 21 18:08 .. >> >>> -rw------- 1 diveshcode diveshcode 1675 Feb 8 11:11 id_rsa >> >>> -rw-r--r-- 1 diveshcode diveshcode 401 Feb 8 11:11 id_rsa.pub >> >>> -rw-r--r-- 1 diveshcode diveshcode 444 Feb 8 11:14 known_hosts >> >>> >> >>> >> >>> while output of this is >> >>> ln -s `pwd`/git-trac ~/bin/ >> >>> >> >>> >> >>> ln: target '/home/diveshcode/bin/' is not a directory: No such file or >> >>> directory >> >>> >> >>> >> >>> and the $PATH stores this. >> >>> echo $PATH >> >>> /home/diveshcode/bin:/home/diveshcode/git-trac-command/bin:/home/diveshcode/kde/src/kdesrc-build:/home/diveshcode/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/local/ssl/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin >> >>> >> >>> >> >>> Been stuck on this for days any advice would be very helpful. >> >>> >> >>> On Thursday, February 20, 2020 at 4:11:28 PM UTC+5:30, Dima Pasechnik >> >>> wrote: >> >>>> >> >>>> have you created an ssh key pair? What is the output of >> >>>> >> >>>> ls -al ~/.ssh/ >> >>>> >> >>>> ? >> >>>> >> >>>> On Thu, Feb 20, 2020 at 10:55 AM varenyam bakshi <varen...@gmail.com> >> >>>> wrote: >> >>>> > >> >>>> > sorry but it is still not working >> >>>> > >> >>>> > On Wed, Feb 19, 2020 at 7:16 PM E. Madison Bray <erik...@gmail.com> >> >>>> > wrote: >> >>>> >> >> >>>> >> On Tue, Feb 18, 2020 at 12:17 PM varenyam bakshi >> >>>> >> <varen...@gmail.com> wrote: >> >>>> >> > >> >>>> >> > I followed the instructions given in sage developer's guide but i >> >>>> >> > am not being authenticated. I checked it using the basic gitolite >> >>>> >> > commands given in the guide >> >>>> >> > ssh g...@trac.sagemath.org info >> >>>> >> > >> >>>> >> > it is showing this error >> >>>> >> > please help >> >>>> >> >> >>>> >> Seems to work for me. If you have multiple SSH keys on your system, >> >>>> >> make sure that you are connecting using the correct key for >> >>>> >> identification. This is done by running `ssh -i <identity_file>` >> >>>> >> where `<identity_file>` is the full path to your SSH private key. >> >>>> >> >> >>>> >> You can also add this permanently to your local SSH client >> >>>> >> configuration, typically found in `~/.ssh/config`. This allows >> >>>> >> per-site SSH client configuration, for example: >> >>>> >> >> >>>> >> Host git.sagemath.org >> >>>> >> Hostname git.sagemath.org >> >>>> >> IdentityFile /path/to/correct/ssh-private-key >> >>>> >> >> >>>> >> Ensure also that you have gone to >> >>>> >> https://trac.sagemath.org/prefs/sshkeys and supplied your *public* >> >>>> >> key. >> >>>> >> >> >>>> >> -- >> >>>> >> 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-...@googlegroups.com. >> >>>> >> To view this discussion on the web visit >> >>>> >> https://groups.google.com/d/msgid/sage-devel/CAOTD34axP0un1h5OEmVpicV%3D2m0ZSnRFV0KW4is_3V_Cbhx29w%40mail.gmail.com. >> >>>> > >> >>>> > >> >>>> > >> >>>> > -- >> >>>> > regards >> >>>> > varenyam bakshi >> >>>> > >> >>>> > -- >> >>>> > 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-...@googlegroups.com. >> >>>> > To view this discussion on the web visit >> >>>> > https://groups.google.com/d/msgid/sage-devel/CANcZkcL7OpaJD5LwN_vuDF3ndyOKVe5VQ8FZMv2pf7SRyLYoLw%40mail.gmail.com. >> >>> >> >>> -- >> >>> 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-...@googlegroups.com. >> >>> To view this discussion on the web visit >> >>> https://groups.google.com/d/msgid/sage-devel/92073ab9-625b-4f71-a342-00eab219b364%40googlegroups.com. >> >> >> >> -- >> >> 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-...@googlegroups.com. >> >> To view this discussion on the web visit >> >> https://groups.google.com/d/msgid/sage-devel/CAAWYfq1z4Gz-8r8GWNKBoXhzQivbUQ%3D%2BLC0a458WbJej-bDE6g%40mail.gmail.com. >> > >> > >> > >> > -- >> > regards >> > varenyam bakshi >> > >> > -- >> > 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-...@googlegroups.com. >> > To view this discussion on the web visit >> > https://groups.google.com/d/msgid/sage-devel/CANcZkc%2Bgx5aZc892LKJ_yEETsMmH9w1xx%3DeLw-i%3Dw_F6M%2B4-%3DQ%40mail.gmail.com. > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/3b90e72a-673b-4109-b618-61794b7b6b9f%40googlegroups.com. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq3ZZNSzsAx407LNfmeASoiaGOnB6i7_EES2oL9PHoJtNA%40mail.gmail.com.
