On Tue, Jul 28, 2015 at 11:53:48AM +0100, Ghislain Vaillant wrote: > > You can normally do: > > gbp buildpackage --git-upstream-tag=v1.2.1 \ > --git-debian-branch=debian/unstable \ > --git-no-pristine-tar \ > --git-pristine-tar-commit > > The last 2 options explicitly tell gbp that a pristine-tar commit does not > exist yet for this tag and that is should generate a tarball and commit one.
That's probably possible in theory but this is not my problem. I could also easily have copyied the tarball to ../tarballs to work around this. However, *creating* a tarball out of no information would be definitely the wrong way to go since there is such a tarball with a certain MD5sum in the Debian archive and thus chances for creating a second one with a different MD5sum would be quite high and thus this procedure definitely not acceptable in the given situation. > This is a beginning of a documented workflow following DEP-14: > http://blog.mycre.ws/articles/git-packaging-workflow-for-py-lmdb/ I know that there is DEP-14 but Charles has introduced "something else" in a certain set of packages and I keep on trying to warm up with this but failed so far. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
