Hi Sean, I had been wanting to look into tag2upload, and this caused me to want to do so even more :-)
On Mon, Feb 09, 2026 at 01:29:44PM +0000, Sean Whitton wrote: > To get started please see the primary documentation: > - https://wiki.debian.org/tag2upload This says, amongst others: > Discrepancies between git, and the implied source package are not > allowed. It's a fundamental design principle of the system that the > source package and git view of the package are identical. For example, > debian/source/local-options must be removed, or (if appropriate) > renamed to debian/source/options. So, in the git repository for most of my packages, I have a debian/source/local-options that says "single-debian-patch". IMAO, the whole idea of dpkg-source --commit is stupid. It tries to replicate what git already does. Committing changesets to separate package patches with a suboptimal version control system is something that takes away time and effort from me that I could better spend doing something useful. So I tell dpkg to not bother by just setting debian/source/local-options to single-debian-patch. My debian/control file sets the correct Vcs-* headers to point to the git repository; if you need to understand what's happening, you can just look there. However. The fact that this is the best workflow for me doesn't mean it's the best workflow for downstreams. If a downstream distribution wants to modify my package, having single-debian-patch in debian/source/options is probably not a good idea. So it does mean that local-options seems a more appropriate place for this to live. Which is why I leave it in git, so I don't forget. I think that is a proper workflow for me, but that is not supported by tag2upload, apparently. Will tag2upload moan and break if the debian patches are not managed properly? Can I tell it to just deal with things without requiring that I bother with the whole dpkg-source --commit flow? I'm fine with a source package being built differently by tag2upload as opposed to myself, but I'm not fine with test builds failing because I committed something to git but not dpkg. (I suppose I could do a test upload, but I'm a bit afraid that I might break things...) -- "I never had a C in history!" "Yeah, but there was so much less of it when you were my age!" -- Joe Brockmeier recounting a conversation with his father, cfgmgmtcamp 2026, Ghent
