Bug#1127616: developers-reference: should document using git-debpush to upload

On Wed, Feb 11, 2026 at 02:27:12PM +0100, Jochen Sprickerhof wrote:
> Hi Santiago,
> 
> * Santiago Vila <[email protected]> [2026-02-11 14:19]:
> > Hi. When I started to put my packages in salsa, I was skeptical about this
> > pristine-tar thing. But one day I noticed that it helps Salsa CI
> > to build the package in some cases, especially when it's a -1 version.
> 
> Can you give some examples here?
> 
> I assume those are cases where the upstream git branch does not contain the
> same data as the orig tarball and we should probably look into that before
> moving away from pristine-tar.

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.

Thanks.