Le jeudi 11 juillet 2019 21:53:03 UTC+2, E. Madison Bray a écrit : > > On Thu, Jul 11, 2019 at 4:54 PM Emmanuel Charpentier > <emanuel.c...@gmail.com <javascript:>> wrote: > > > > FWIW : > > > > after getting back to a Python2-based Sage, I have been able to get my > ticket, patch Sage, check it, commit and push to Trac. THEN AND ONLY THEN, > I have been able to return to my Python3-based sage, manually create a > branch based on the Trc branch, check it out and compile to check the > results under Python3. > > I'm surprised that this is problem since I thought git-trac would use > the system Python, and not the one actually installed in Sage, but I'm > not sure. Is that how you have it set up?
Yep. My git-trac-command clone of the repository lives somewhere in my personal tree, and its git-trac file is symlinked to /usr/local/bin. And my default Python is still Python2 (Debian dixit). > I suspect it's not > necessary. But maybe it is. Either way it should definitely be fixed > to work on Python 3 if it doesn't. > Hmmm... I'm no longer sure that this is a 2vs3 problem (see my newer post). > > > > > This workaround is a bit heavy for my taste... > > Not to be glib, but another very simple workaround would be to simply > not use `git trac` if it's just for one thing. If your goal was just > to check out a branch My goal was to check out the ticket, work on it, check it, commit *and bush it back at the right place*. The latter task is eased by git track : no guessing where I should put my new shiny branch, no question on how to update the ticket... > it's really not necessary, and for the purposes > of working on other projects I think it behooves anyone to work on > learning git (which I will fully admit is not often fun to do, though > I enjoy this tutorial: https://learngitbranching.js.org/ > I did learn git (or, more precisely, started to learn it). I was able to *guess* the right name of the brach created for my ticket. But this dance around Trac infrastructure shouldn't have been necessary. > Le jeudi 11 juillet 2019 11:18:56 UTC+2, Emmanuel Charpentier a écrit : > >> > >> I think that something is havoc : using a sage tree compiled with > Python 3, > >> another attempt ti git trac checkout 28151 fails as before, > >> another attempt to create a new ticket fails as before (but a newly > created tickets (28163) appears on the Web interface to trac). > >> > >> Furthermore : > >> > >> charpent@p-202-021:/usr/local/sage-python3$ git branch --remote | grep > 2815 > >> origin/u/chapoton/28153 > >> origin/u/embray/ticket-28154 > >> > >> However, perusing the Web interface shows that *all* tickets > #2815[[:digit:]] are accessible... > >> > >> Going back to my last Python2 compilation of Sage (and re-symlinking to > it), git checkout 28151 works like a charm. > >> > >> The problem seems to be that git-trac isn't compatible with Python 3 or > whatever happens in a Python 3-based Sage... I'm filing an issue against it > on its Github repository. > >> > >> Any hints or advice ? > >> > >> Le mercredi 10 juillet 2019 15:55:05 UTC+2, Emmanuel Charpentier a > écrit : > >>> > >>> trac.sagemath.org is accessible via its Web interface. However, a > (correctly configured) "git trac" command is inable to checkout a > (currently empty) ticket : > >>> > >>> charpent@p-202-021:/usr/local/sage-python3$ git trac checkout 28151 > >>> Loading ticket #28151... > >>> Newly created local branch: t/28151/upgrade_r_to_3_6_1 > >>> Traceback (most recent call last): > >>> File "/usr/local/bin/git-trac", line 17, in <module> > >>> cmdline.launch() > >>> File "/home/charpent/Dev/git-trac-command/git_trac/cmdline.py", line > 220, in launch > >>> app.checkout(args.ticket_or_branch, args.branch_name) > >>> File "/home/charpent/Dev/git-trac-command/git_trac/app.py", line > 118, in checkout > >>> self._checkout_ticket(int(ticket_or_branch), branch_name) > >>> File "/home/charpent/Dev/git-trac-command/git_trac/app.py", line > 136, in _checkout_ticket > >>> self.repo.create(local) > >>> File > "/home/charpent/Dev/git-trac-command/git_trac/git_repository.py", line 144, > in create > >>> self.git.fetch('trac', starting_branch) > >>> File > "/home/charpent/Dev/git-trac-command/git_trac/git_interface.py", line 340, > in meth > >>> return self.execute(git_cmd, *args, **kwds) > >>> File > "/home/charpent/Dev/git-trac-command/git_trac/git_interface.py", line 327, > in execute > >>> popen_stderr=subprocess.PIPE) > >>> File > "/home/charpent/Dev/git-trac-command/git_trac/git_interface.py", line 262, > in _run > >>> raise GitError(result) > >>> git_trac.git_error.GitError: <exception str() failed> > >>> > >>> Server problem ? > >>> > >>> Same results after refreshing my git-trac-command directory (via git > fetch and git pull...).. > >>> > >>> Hints ? > >>> > > -- > > 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 <javascript:>. > > To post to this group, send email to sage-...@googlegroups.com > <javascript:>. > > Visit this group at https://groups.google.com/group/sage-devel. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/010c52e9-7108-4630-b284-417a27e215e4%40googlegroups.com. > > > > 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. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/ec95bbad-4bab-4ef5-872d-4f5d5b6339b3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
