* Colin Watson <cjwat...@debian.org> [241126 23:34]: > On Tue, Nov 26, 2024 at 09:25:12PM +0100, Simon Josefsson wrote: > > Colin Watson <cjwat...@debian.org> writes: > > > CI for a new-upstream-release commit you've pushed but haven't uploaded > > > to the Debian archive yet, because you're waiting for CI. > > > > > > pristine-tar certainly isn't the only way here (it's true that CI could > > > in principle fetch it directly from upstream), but I find it much easier > > > than the alternatives. > > > > I often wait for CI before making an upload of a new upstream release, > > even without pristine-tar, and Salsa CI hasn't had trouble automatically > > finding a orig.tar.gz to work with for me. So maybe there is some > > additional assumption for your situation? > > Maybe it runs uscan or something in that case;
It runs gbp export-orig (plus some fallbacks). If there is no pristine-tar branch, gbp will use the upstream branch. That won't be bit-identical to the upstream tarball. So, without pristine-tar, salsa CI tests something that might not work. > Still, as long as it's building source packages as part of the > process, conceptually I prefer it having all the information in the > repository rather than having to go out to an upstream site that might > be unreliable. Yeah. Chris
