Re: [RFC] General Resolution to deploy tag2upload

[Ansgar 🙀 <ansgar@43-1.org>]

Hi,

On Fri, 2024-06-21 at 15:58 +0200, Matthias Urlichs wrote:
> On 21.06.24 14:33, Ansgar 🙀 wrote:
> > I think you misunderstand my question: I would like to know which
> > packages*could not*  provide an integrity hash for the archive.
> 
> Ah, sorry.
> 
> Answer: Lots of them. AFAIK you can simply click on a package in 
> https://browse.dgit.debian.org/ and check whether the latest 
> "archive/debian/*" and "debian/*" tags are different.
> 
> Of the last 50 uploads, I counted 42. Thus, >80%.

I checked for the first best package (all-knowing-dns):

commit b6b75815debd86053a3a09feb4ae4fc619292473 (tag: archive/debian/1.7-6)
vs
commit 26dbc900af3493f7626d1ec333b26fbd1b4cefc6 (tag: debian/1.7-6)

So the tags are different, but:

all-knowing-dns % git rev-parse 'archive/debian/1.7-6^{tree}'
539fd2433304ec4e06ade8272baab31c6b299a69
all-knowing-dns % git rev-parse 'debian/1.7-6^{tree}' 
539fd2433304ec4e06ade8272baab31c6b299a69

So your suggested method of measurement and the resulting 80% seem very
questionable and only usable as a very generous upper boundary.

(Please also consider in your reply the suggested changes to make
hashing possible/easier...)

Ansgar