On Sat, 1 Aug 2026 19:17:52 -0600 Antonio Russo <[email protected]> wrote:
> Hello, > > I'm packaging the dante server, which I inherited, and the git > setup is upstream and debian/ merged, patches un-applied. I want > to exclude more files in Files-Excluded in debian/control (but > there is no new upstream release). I have extended that list and > removed the files from the git repository locally. This change > necessitates a bump to the upstream version, no? Is a new version > of 1.4.4+dfsg2-1 (it is currently 1.4.4+dfsg-1+b1) acceptable? Your changes to Files-Excluded essentially create a new ""upstream"" release with a version such as 1.4.4+dfsg2, so the Debian revision would indeed be 1.4.4+dfsg2-1. > Also, when I upload the new version, I will need to upload a new > source tar. Can I make it using > > git archive -- ':(exclude)debian' > > or is there some reason I must/should use another tool, like uscan? You can use the normal tooling for creating or pulling in the orig tarball, e.g. gbp or uscan, as if you were dealing with an actual new upstream release. With just uscan, you'll probably have to manually rename the new orig tarball to dfsg2; gbp asks what you want the upstream version to be, providing the maintainer with the opportunity to add the extra "2".
pgp19FKObpLDC.pgp
Description: OpenPGP digital signature
