Bug#1116530: git-debpush: fact of a sponsored upload/push gets lost
Hi,
On 28/09/25 at 20:39 +0100, Ian Jackson wrote:
> Hi. We (the tag2upload team) received the following report:
>
> Sven Geuer writes ("Bug#1116530: git-debpush: fact of a sponsored upload/push gets lost"):
> > doing a sponsored upload/push via "git debpush" works, while the fact
> > it was sponsored is not mentioned by tracker.debian.org [1], no "signed
> > by:" annotation, and DDPO [2], the package in question is not listed
> > under "Sponsored/other uploads".
> ...
> > [1] https://tracker.debian.org/pkg/scalpel
> > [2] https://qa.debian.org/developer.php?login=sge%40debian.org
>
> I believe both of these services are getting their data from UDD.
I don't think that's correct.
I believe that tracker.d.o is doing its own parsing of the
debian-devel-changes mailing list, unrelated to UDD's.
According to the discussion in
https://salsa.debian.org/qa/distro-tracker/-/issues/86, UDD is the
source for qa.debian.org.
The code that populates the upload_history table in UDD is
https://salsa.debian.org/qa/udd/-/blob/master/udd/upload_history_gatherer.py?ref_type=heads
But there's a pre-processing phase, see:
https://salsa.debian.org/qa/udd/-/blob/master/scripts/README.upload-history?ref_type=heads
https://salsa.debian.org/qa/udd/-/blob/master/scripts/Makefile.upload-history?ref_type=heads
https://salsa.debian.org/qa/udd/-/blob/master/scripts/upload_history_extractor.py?ref_type=heads
Unfortunately that's not very nice code. It's painful that the source we
are using for this information is email archives. Maybe that problem is
a good opportunity for reworking all of it...
Lucas
Reply to: