Hmmm... The web page of the ticket  created via the Web interface exists 
<https://trac.sagemath.org/ticket/28151> ; ditto 
<https://trac.sagemath.org/ticket/28157> for the one created from my system 
via git trac create, but the corresponding git branch doesn't seem to have 
been created :

charpent@p-202-021:/usr/local/sage-python3$ git fetch
charpent@p-202-021:/usr/local/sage-python3$ git branch --remote | grep 3_6
  origin/public/packages/openblas_0_3_6
  origin/u/charpent/upgrade_r_to_3_6_0
  origin/u/jdemeyer/aborted_tests_on_macos_10_13_6
  origin/u/vbraun/openblas_0_3_6
  origin/u/vbraun/openblas_0_3_6_vs__os_x
  origin/u/vbraun/upgrade_to_python_3_6_6

Still stuck. Oh, well...

Le mercredi 10 juillet 2019 17:03:12 UTC+2, E. Madison Bray a écrit :
>
> The problems you're experiencing don't appear to have anything to do with 
> Trac, but rather with the `git trac` command's attempts to run commands in 
> your local git repository. 
>
> Unfortunately, due to a different bug (which I've seen before but I don't 
> think has been fixed) instead of seeing what the error message was from 
> git, you just a useless
> <exception str() failed>
>
>
> You could try inserting a breakpoint where it's running the git command, 
> and see what command it's actually running, then run it manually yourself 
> and see what's up. 
>
> Or just manually do 
>
> $ git fetch
> $ git checkout --track origin/<branch-name>
>
> which is likely all it's doing anyways. 
>
>
>
>
>
>
> On Wed, Jul 10, 2019, 16:38 Emmanuel Charpentier <emanuel.c...@gmail.com 
> <javascript:>> wrote:
>
>> I don't understand : I created (successfully) 
>> https://trac.sagemath.org/ticket/28151 but I can't check it out as I did 
>> usually. This behaviour isn't the one described in the Developer's guide 
>> <http://doc.sagemath.org/html/en/developer/git_trac.html#check-out-an-existing-ticket>,
>>  
>> which I've successfully used in the past.
>>
>> BTW, trying to create a "private" ticket (u/charpent/whatever...) as 
>> described here 
>> <http://doc.sagemath.org/html/en/developer/git_trac.html#create-a-ticket>, 
>> I get another error :
>>
>> charpent@p-202-021:/usr/local/sage-python3$ git trac create 'Upgrade R to 
>> 3.6.1'
>> Remote branch: u/charpent/upgrade_r_to_3_6_1
>> Newly-created ticket number: 28157
>> Ticket URL: https://trac.sagemath.org/28157
>> Local branch: t/28157/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 
>> 237, in launch
>>     app.create(args.summary, args.branch_name)
>>   File "/home/charpent/Dev/git-trac-command/git_trac/app.py", line 239, 
>> in create
>>     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>
>>
>> This new ticket *can* be accessed from the Web interface to Trac and is 
>> totally virgin.
>>
>> BTW : none of my attempts has created any local branch :
>>
>> charpent@p-202-021:/usr/local/sage-python3$ git branch
>> * develop
>>   master
>>
>>
>> I'm stuck... Without further information, I can but conclude that Trac is 
>> somehow hosed...
>>
>>
>> Le mercredi 10 juillet 2019 16:08:04 UTC+2, Dima Pasechnik a écrit :
>>>
>>> On Wed, Jul 10, 2019 at 3:55 PM Emmanuel Charpentier 
>>> <emanuel.c...@gmail.com> wrote: 
>>> > 
>>> > 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...).. 
>>>
>>>
>>> One cannot checkout an empty branch, IMHO. I can certainly fetch 
>>> branches from trac's git server, i.e. (with ssh) 
>>> g...@trac.sagemath.org:sage.git 
>>>
>>>
>>> > 
>>> > 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. 
>>> > To post to this group, send email to sage-...@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/a3179157-cfd4-46bb-ae7a-c51cdcd6e968%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-...@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/a89df51c-b1de-4444-96c9-0a251ce2edd0%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/sage-devel/a89df51c-b1de-4444-96c9-0a251ce2edd0%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> 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/5e83e12b-208d-4be2-8ae8-9c30e126a421%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to