Hi Daniel! On Wed, Aug 11, 2010 at 11:45:58PM +0200, Daniel Fanjul wrote: > The package is not usable. Any update operation (like 'ti new') corrupts the > file .git/HEAD. > > This is the first and unique ticgit command I have launched to test this bug: > rayado:~/tmp/testing.git$ ti new > I, [2010-08-11T23:35:30.157073 #23721] INFO -- : saving 1281562530_foo_55 > /usr/lib/ruby/1.8/git/lib.rb:643:in `command': git branch -a 2>&1:fatal: > Failed to resolve HEAD as a valid ref. (Git::GitExecuteError) > from /usr/lib/ruby/1.8/git/lib.rb:615:in `command_lines' > from /usr/lib/ruby/1.8/git/lib.rb:209:in `branches_all' > from /usr/lib/ruby/1.8/ticgit/base.rb:241:in `load_tickets' > from /usr/lib/ruby/1.8/ticgit/base.rb:72:in `reset_ticgit' > from /usr/lib/ruby/1.8/ticgit/base.rb:67:in `ticket_new' > from /usr/lib/ruby/1.8/ticgit/cli.rb:348:in `handle_ticket_new' > from /usr/lib/ruby/1.8/ticgit/cli.rb:41:in `execute!' > from /usr/lib/ruby/1.8/ticgit/cli.rb:12:in `execute' > > After this command, the HEAD file is not pointing to any valid ref: > rayado:~/tmp/testing.git$ cat .git/HEAD > ref: refs/heads/
Thanks a lot for your report. I can indeed reproduce the bug if the ref .git/HEAD is pointing to does not exist beforehand, which happens with an empty repository, for example. Is this what you are describing? Try “git commit --allow-empty -m'initial commit'” before running “ti new” for the first time if this is a new repo. In case that this is indeed what you are reporting, would you be fine if I downgraded this bug to important for now? After all, most people will want to start tracking bugs well after the inital development, and the problem is easy to work around. If your case is different, I’m afraid I’ll need a little more information to understand and handle this issue. Cheers, -- Michael Schutte <mi...@uiae.at>
signature.asc
Description: Digital signature
