On Monday 19 May 2008 2:18:24 am Guido Günther wrote: > On Sun, May 18, 2008 at 07:17:18PM -0400, Andres Mejia wrote: > > On Sunday 18 May 2008 6:40:38 pm Joey Hess wrote: > > > Andres Mejia wrote: > > > > git-import-orig does use what's supplied by the --upstream-branch > > > > option or what is found in the gbp.conf files and that is what is > > > > passed on to pristine-tar. I suppose this is a problem with > > > > git-buildpackage. I've already cloned this bug and assigned it to > > > > git-buildpackage. http://bugs.debian.org/481806 > > > > > > Right, it would be good for gbp to pass that info on to pristine-tar. > > > > > > I don't see anything I can do in pristine-tar to fix this. Ok if I > > > close #481713? > > What would you expect git-import-orig to do here? Git-import-orig calls > pristine-tar as: > pristine-tar commit tarball upstream_upstream_branch_name > Is there anything else git-import-orig could do. Andres, is this 0.4.23 > or newer? > Cheers, > -- Guido
This is 0.4.28. git-import-orig could call pristine tar as: pristine-tar commit <path_to_tarball> <tag_object> I think it would be better if it called the tag object instead of the upstream branch name, since in the latter case, it will always fail since it's finding a local upstream branch (refs/heads/upstream) and a remote upstream branch (refs/remotes/origin/upstream). -- Regards, Andres
signature.asc
Description: This is a digitally signed message part.
