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

On 13/02/26 at 10:57 +0000, Sean Whitton wrote:
> Lucas Nussbaum [12/Feb 10:25pm +01] wrote:
> > I added some statistics about fetishism^Hpristine-tar usage (SCNR) on
> > https://udd.debian.org/cgi-bin/dep14stats.cgi
> >
> > 72.8% of packages with a working salsa project have a pristine-tar
> > branch.
> >
> > Among salsa groups with more than 200 packages in testing, the following
> > have more than 80% of group-maintained packages that have a pristine-tar
> > branch:
> 
> I would really appreciate knowing whether these branches are in use --
> whether they have the most recent upstream versions imported to them.
> 
> For example I often find pristine-tar branches but just ignore them,
> where team policy allows me to.  So the fact that someone used it once
> may not mean much statistically.
> 
> git-debpush has code in it to detect whether the current release in
> d/changelog is represented in the pristine-tar branch if you want to
> crib from somewhere.

Hi,

I ended up extending https://debaudit.debian.net/ with a new checker,
'git2orig', that checks whether a matching tarball can be extracted from
the Vcs-Git repository.
See https://debaudit.debian.net/git2orig/

I got the following results for the packages in sid:
 has_pristine_tar_branch | pristine_tar_worked | tarball_identical_using_pristine_tar | count
-------------------------+---------------------+--------------------------------------+-------
 true                    | false               | false                                |  2077
 true                    | true                | false                                |   386
 true                    | true                | true                                 | 25007

So, out of 27470 packages with a pristine-tar branch, 25007 have an
up-to-date pristine-tar branch that can generate the orig tarball in the
archive. I think that's quite good.

Lucas