Creating Debian packages from upstream Git

a year ago

Optimal workflow for creating new Debian packages in 2025, preserving upstream git history.
Key elements include using Git fork/clone of upstream repository, consistent git-buildpackage commands, DEP-14 tag and branch names, pristine-tar and upstream signatures, and efficient use of Salsa.
Demonstration using the command-line tool Entr, covering steps from creating a packaging repository to posting a Merge Request on Salsa.
Detailed instructions on setting up the repository structure, using dh_make for initial packaging, and identifying build dependencies.
Building Debian sources with dpkg-buildpackage and git-buildpackage, including handling upstream releases and patches.
Guidance on opening Merge Requests for review, submitting fixes upstream, and using language-specific dh-make alternatives.
Explanation of the difference between source git repositories, source packages, and binary packages.
Options for repackaging source packages with Files-Excluded lists and handling multiple upstream source packages.
When not to start the Debian packaging repository as a fork of the upstream one.
Conclusion highlighting the evolution of Debian packaging and the importance of standardized workflows.

Hasty Briefsbeta