On Thu, 22 Jan 2026, Ian Jackson wrote:
Another consideration is that we might want to make them match what you get from git forges' tarball download features.
I have done some experiments. My conclusion is that at the gzip level, Salsa and GitHub both do exactly what git-deborig currently does.
But at the tar level they're slightly different. Both Salsa and GitHub name the top-level directory in the tar file after the repository and tag name. So if I'm generating a tar file for the tag "upstream/3.252" from the repository "bedstead", the top-level directory will be called "bedstead-upstream-3.252". Meanwhile, git-deborig names that directory after the Debian source package and the upstream version.
What this means is that in the common case where the forge repository and the Debian source package have the same name and the upstream tags are bare version numbers, git-deborig will currently produce identical results to both Salsa and GitHub (and I've tested this and got identical compressed tarballs out of all three)
That suggests that git-deborig should not change its behaviour and it would be better for uscan to change. Except that maybe git-deborig could name its top-level directory after the tag that it uses. I'm not sure how I feel about that.
-- Ben Harris
