On 2026-02-12 11:56:24 +0800 (+0800), Otto Kekäläinen wrote: [...]
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.
[...]Yes, for example that's essentially how https://bugs.debian.org/990337 was fixed, albeit in an ad-hoc manual fashion I think. I didn't know there was an established Debian packaging workflow and tools that would automatically patch the upstream branch state with a diff against the upstream release tarball, but that does sound like it would be an effective solution.
-- Jeremy Stanley
signature.asc
Description: PGP signature
