Package: qa.debian.org Severity: normal Hi,
as discussed today on #debian-qa, there is an issue with vcswatch working on a Git repository that has more than branch pointing to the same commit as HEAD: 12:47 < micha> I would like to know why vcswatch has issues with abtransfers 12:47 < micha> https://qa.debian.org/cgi-bin/vcswatch?package=abtransfers .... 15:05 < jamessan> micha: and the error is what it says -- Failure getting HEAD. You have no HEAD ref in your repo. Looks like you need to run "git symbolic-ref HEAD …" to specify what branch you want to be the default branch when someone clones 15:05 < jamessan> I'm guessing it should be pointing at unstable, so “git symbolic-ref HEAD refs/heads/unstable” 15:06 < jcristau> hmm? 15:06 < jcristau> $ git ls-remote git://source.lenk.info/git/abtransfers.git | grep HEAD 15:06 < jcristau> 2ad5a5e2fdb69742703b1a37de8dda594e153729 HEAD 15:08 < jamessan> oh, the problem is rather that it's ambiguous 15:08 < jamessan> 2ad5a5e2fdb69742703b1a37de8dda594e153729 HEAD 15:08 < jamessan> 2ad5a5e2fdb69742703b1a37de8dda594e153729 refs/heads/master 15:08 < jamessan> 2ad5a5e2fdb69742703b1a37de8dda594e153729 refs/heads/unstable 15:09 < micha> hmm, but is this then my fault? 15:10 < micha> would deleting one of the two branches solve the issue? 15:11 < jamessan> maybe, but vcswatch could probably be improved to just get the sha that HEAD points to and use that instead of trying to parse HEAD out of “git remote show origin” Cheers, Micha -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org