Its because the ticket is closed but not yet released; you can't fetch
commits by sha1. It works if you happen to have the commit in your local
copy of the trac repo; e.g. run
git fetch trac public/ticket/18594
Then afterwards both
git fetch trac f257d8224aa79c85a84ced0e69f378fafedbe546
and
Was this every able to get fixed? I'm getting the same problem here on a
different ticket
aram:/media/ubuntudata/Programming/sage (develop)$ git trac checkout 18594
Loading ticket #18594...
Checking out Trac #18594 remote branch
f257d8224aa79c85a84ced0e69f378fafedbe546 -> local branch
t/18594/f
$ git fetch trac e070dd191bb189b83bae5a2a5c12bf4d70981040
>From trac.sagemath.org:sage
* branche070dd191bb189b83bae5a2a5c12bf4d70981040 -> FETCH_HEAD
$ echo $?
0
Interesting, I get return code 0. Did it actually fetch anything (ie.
FETCH_HEAD is set)? Why didn't it print anything to
Hi,
Please consider this question low priority -- I can just directly make
the changes to upgrade sage-6.5 to IPython 3 for now, then wait for
sage-6.6, which should appear any minute now anyways.
That said, shouldn't git fetch trac actually display some sort of
error rather than just exiting wit
