[Pkg-security-team] Failure running git ls-remote HEAD

Gianfranco Costamagna locutusofborg at debian.org
Mon Aug 22 13:07:39 UTC 2016


Hi Raphael

>So if you use the "setup-repository" script of our team to create the

>initial repository, then you have HEAD pointing to debian/master
>and you obviously need a debian/master branch so that it works.


yes indeed, correct
>Our documentation on https://wiki.debian.org/Teams/pkg-security tells to
>use this script and indicates that we should follow DEP-14 on this topic.


yep, I think I mentioned it too :)
>Seriously? This has nothing to do with "workflow". It's just a matter of
>doing the work in the correct branch.

>

I know that... but for *existing* packages, it means: move the repo, create
a debian/gbp.conf file (with the correct syntax, I have to find/check an existing one)
create a branch, upload it and check if everything works.

this is what I mean with "workflow" :)

I moved them but I didn't create any gbp file, neither change the default branch

>Or to use --debian-branch=debian/master with git-buildpackage (personally
>I need it only for gbp import-orig as otherwise I have configured
>git-buildpackage to not complain about usage of non-default branches).
>
>$ cat ~/gbp.confg
>[DEFAULT]
>pristine-tar = True
>cleaner = /bin/true
>
>[buildpackage]
>sign-tags = True
>export-dir = ../build-area/
>ignore-branch = True
>ignore-new = True
>
>[import-orig]
>filter-pristine-tar = True
>
>[pq]
>patch-numbers = False


> In case somebody has a "clone-convert-upload-changeHEAD" script, I'll be happy to use it :)
>
>(not need to clone a new repo and upload)


I don't have all the repositories of pkg-security on my laptop :)
>On your current clone:
>$ git checkout master
>$ git checkout -b debian/master
>$ git branch -D master
>$ git push origin debian/master :master
>
>On git.debian.org (withing the corresponding repository), you need to run
>"git symbolic-ref HEAD refs/heads/debian/master" if you want to change
>HEAD to point to debian/master.


thanks, I'm an old-still-used-to-vi-the-correct-file man :)
>Please let's try to use debian/master everywhere. And the next time you
>don't know how to deal with something, just ask for help. :-)


I'll try to do some find on the repositories and try to fix the workflow,
do you think you can do it? it would be really appreciated, so I don't have
risk to break stuff (this is the first reason for me not changing branch on
sqlmap and binwalk, w3af and similar tools)

thanks in advance for the great answers, I hope we will unify all the repositories soon :)

Gianfranco



More information about the Pkg-security-team mailing list