Hi,

i just had the same problem with #15316 (and had to use a similar
workaround):

$ git trac checkout 15316

Loading ticket #15316...
Checking out Trac #15316 remote branch
969de52313ee407d874e9f7b318111c144de534e -> local branch
t/15316/969de52313ee407d874e9f7b318111c144de534e...
Traceback (most recent call last):
        ...
git_trac.git_error.GitError: git returned with non-zero exit code (128)
when executing "git fetch trac 969de52313ee407d874e9f7b318111c144de534e"
    STDERR: fatal: Couldn't find remote ref
969de52313ee407d874e9f7b318111c144de534e
    STDERR: fatal: The remote end hung up unexpectedly

And manually "git fetch trac 969de52313ee407d874e9f7b318111c144de534e"
did not work either.

Ciao,
Thierry


On Sat, Nov 15, 2014 at 06:52:22PM +0100, Clemens Heuberger wrote:
> The release manager recently closed ticket #16747, but it is not yet in 
> develop.
> In that time window, git trac checkout (or the equivalent git fetch trac
> commit_id) fails.
> 
> $ git trac checkout 16747
> Checking out Trac #16747 remote branch 
> ec0aae9358f5204a3db6406b2c2f2818a78f5892
> -> local branch t/16747/ec0aae9358f5204a3db6406b2c2f2818a78f5892...
> Traceback (most recent call last):
> ...
>   File "/local/cheuberg/git/git-trac-command/git_trac/git_interface.py", line
> 263, in _run
>     raise GitError(result)
> git_trac.git_error.GitError: git returned with non-zero exit code (1) when
> executing "git fetch trac ec0aae9358f5204a3db6406b2c2f2818a78f5892"
> 
> One workaround is to browse the trac ticket, find the last branch name before
> the release manager replaced the branch field by the commit id and doing
> a
> $ git fetch trac u/cheuberg/ticket/16747
> 
> The problem does not occur once the ticket in question is in develop.
> 
> Is there a more comfortable work-around?
> 
> (The trac remote was configured with
> $ git remote add -f -t develop -t master trac git://trac.sagemath.org/sage.git
> which might be part of the problem).
> 
> Thanks, CH
> 
> -- 
> 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 http://groups.google.com/group/sage-devel.
> 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 http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to