* Santiago Vila <[email protected]> [2026-02-11 14:37]:
Sorry, I can't give examples because I did not take notes, but I remember that it was not a mismatch between orig tarball and git branch (I am usually quite careful about that) but rather some difficulty from Salsa CI to create an orig tarball. I believe it had something to do with uscan and the flaky network connectivity of ftp.gnu.org some weeks/months ago.I know Salsa CI uses some heuristics to create the orig.tar.gz and it uses uscan and the watch file in some cases. I assume there is a high overlap between Salsa CI having to do that and lack of a pristine-tar branch.
salsa-ci uses gbp export-orig and falls back to origtargz in case that fail:
https://salsa.debian.org/salsa-ci-team/pipeline/-/blob/master/salsa-ci.yml?ref_type=heads#L440gbp export-orig uses only git and does not use pristine-tar by default. origtargz can fallback to uscan. So it would be even more interesting where it failed for you.
signature.asc
Description: PGP signature
