Sean Whitton <[email protected]> writes: > The recommended thing to do here is create an upstream/foo tag yourself.
That works, and gbp does it for me. I suppose this ought to be a documented limit of the "--upstream=v1.2.3" workflow style, which I guess this bug report now serve as. There are two other limits of that style that I've ran into: 1) Packages that repack upstream orig.tar using, e.g., Files-Excluded. 2) Packages whose upstream uses .gitattributes export-subst to modify source in git compared to release tarballs. So maybe this workflow is flawed after all, although I do like having upstream SHA1 git commit ids recorded in the debian tag2upload tag. /Simon
signature.asc
Description: PGP signature
