On 07/05/2026 13:51, Nicolas Peugnet wrote:
On 07/05/2026 00:42, Juan wrote:Question on the gbp workflow for +ds packages: I'm creating the orig tarball manually (upstream subtree archive + LICENSE file), importing with gbp import-orig --pristine-tar, and relying on the Salsa CI fallback path (pristine-tar +--git-overlay).Is this the expected workflow, or is there a better approach for packages where the orig tarball is a manual repack?IMO it is better if uscan directly produces the expected orig tarball, so that it is possible to import new versions with "gbp import-orig -- uscan".I never did it myself, but you should be able to call a script at the end of uscan execution to produce the exact tarball that you need, see the "Update-Script" option of debian-watch(5) [1] and the "Custom script" section of uscan(1) [2] (the uscan man page has more information about the scripts in the "Examples" section).By the way, your debian/watch file currently looks incorrect, it advertises version=5 but it in the version 4 format.[1] https://manpages.debian.org/trixie-backports/devscripts/debian- watch.5.en.html#Common_options [2] https://manpages.debian.org/trixie/devscripts/ uscan.1.en.html#Custom_script
Reading a bit more about this feature, it seems I was wrong about it allowing one to modify the orig tarball. It it possible to do it but it looks more like a hack than an intended feature of uscan:
https://bugs.debian.org/748474#10 -- Nicolas Peugnet
OpenPGP_signature.asc
Description: OpenPGP digital signature
