Hi all, This list has had plenty of discussions regarding best practices in packaging. I noticed some of the views stemmed out of misunderstandings or unawareness of certain easy to use solutions and techniques exist. Hence, I am glad to see that Guido just uploaded git-buildpackage 0.9.36, which has contributions from 6 people, including a bunch of updates to both the manual and man pages.
I invite you to check out the latest version of the manual and the latest version of the key man pages: https://gbp.sigxcpu.org/manual/ https://manpages.debian.org/unstable/git-buildpackage/gbp.1.en.html https://manpages.debian.org/unstable/git-buildpackage/gbp-clone.1.en.html https://manpages.debian.org/unstable/git-buildpackage/gbp-import-orig.1.en.html https://manpages.debian.org/unstable/git-buildpackage/gbp-pq.1.en.html https://manpages.debian.org/unstable/git-buildpackage/gbp-dch.1.en.html https://manpages.debian.org/unstable/git-buildpackage/gbp-buildpackage.1.en.html https://manpages.debian.org/unstable/git-buildpackage/gbp-push.1.en.html We have also been discussing on the git-buildpackage mailing list which commands and parameters exactly to use for the most optimal basic workflow when dealing with an upstream that has signed tarballs and git tags and Debian packaging hosted on Salsa. I distilled it into these settings and README on how to work with the package: https://salsa.debian.org/mariadb-team/galera-4/-/blob/debian/latest/debian/gbp.conf https://salsa.debian.org/mariadb-team/galera-4/-/blob/debian/latest/debian/README.source.md Even if this isn't exactly 100% what you want to do, being aware of one complete example of a real package hopefully helps you grasp what the ideal process for yourself could be.
