Hi, Quoting Otto Kekäläinen (2026-02-12 04:56:24) > Hi, > > > all the additions found in the tarball are generated automatically I > > assume. Why can't they be simply added to the Git repo while creating > > the tag in a classic "Releasing version foo" commit? (A common pattern > > Isn't the obvious solution to use dual git+tarball imports? > > That way you have the upstream tag in your Debian packaging > repository, and from the tag contents are imported to upstream/latest > branch. Note that branch does not represent the upstream git contents, > but the Debian import contents. If the Debian package is commit and > tree same with what upstream release git tag, that branch will have no > extra changes. However, is there are any special stuff going on in the > tarball due to upstream practices, that will show up in the import > commit, or if Debian has extra things going on (such as applying > copyright:Files-Excluded removals) they too will show up in that > commit, and from upstream/latest things are merged on the > debian/latest branch.
and then the stuff that is not DFSG compliant and got removed via copyright:Files-Excluded will show up in the import commit and thus be part of my git history, no? I would like to love the git-only approach but I fail to see a way which makes me want to re-use the upstream git for projects where upstream contains files which we do not allow ourselves to ship. Removing non-DFSG files with a git change is like removing non-DFSG files with a quilt patch in debian/patches. The non-free content will still be there. My current understanding is that this only works if we agree that: * our packaging git can have all sorts of nasty stuff in it and * the DFSG-clean thing is the orig tarball we dput into the archive with a dsc But with that view, my packaging git can never become the thing which we consider "the thing Debian ships which honors the DFSG" and anybody who would like to derive from us in a DFSG-compliant way still will have to use tarballs when they want to import from us, no? Thanks! cheers, josch
signature.asc
Description: signature
