Aidan, On Thursday, November 7, 2024 9:13:41 AM MST Aidan wrote: > Whenever I make a change to my program am I meant to run the tar command > before running dpkg-buildpackage. I'm not sure if I'm misunderstanding the > workflow.
It sounds like you have a question about how to best create a Debian package for a program where you are also the upstream maintainer. This is a big topic with lots of different workflows depending on the structure of the actual source code. But by far, the most popular workflow in Debian is git-buildpackage (abbreviated gbp). The easiest way to do this is to keep two separate repositories, one for your upstream code and the other for the Debian packaging. I would recommend you keep the Debian packaging on: https://salsa.debian.org/ Once it is setup, you can update the Debian package using the following commands, which automatically sorts out all the pieces, including the upstream tarball. gbp import-orig --uscan dch gbp buildpackage gbp tag gbp push I wrote a description of this in a previous mail on Mentors, including an explanation of what these commands do, which you might find helpful. https://lists.debian.org/debian-mentors/2024/09/msg00057.html -- Soren Stoutner so...@debian.org
signature.asc
Description: This is a digitally signed message part.
