Paul Gevers <[email protected]> writes: > Hi Simon > > On 5/25/26 16:25, Simon Josefsson wrote: >> Third, some testing migration blocking >> check that ends up visible in the PTS. Maybe the third really ought to >> be implemented anyway. >> But how to implement such a check? > > Helmut and I already exchanged some ideas how to do that. But IIRC > helmut is a bit reluctant to run a service that provides that > information.
Yet another service up seems undesirable indeed. Is it really needed? This existing query reveals the problem: https://packages.debian.org/search?lang=en&suite=sid&arch=any&mode=path&searchon=contents&keywords=%2Fusr%2Finclude%2Fref_array.h Iterating that online query over all filenames in a newly built package from a Salsa job seems excessive though. A smaller tool that merely downloads Contents-* files doesn't seem entirely unreasonable? The Contents* files are <<100MB each, which isn't a lot compared to all the rest of network noise during a Salsa build pipeline. Is there a tool that finds file conflicts like this already? This is a fairly simple and basic query. Doesn't 'apt' have something already? jas@frallan:~$ rm Contents-amd64* jas@frallan:~$ wget -nv https://deb.debian.org/debian/dists/testing/main/Contents-amd64.gz 2026-05-25 17:21:52 URL:https://deb.debian.org/debian/dists/testing/main/Contents-amd64.gz [12728599/12728599] -> "Contents-amd64.gz" [1] jas@frallan:~$ gzip -d Contents-amd64.gz jas@frallan:~$ grep usr/include/ref_array.h Contents-amd64 usr/include/ref_array.h libdevel/libini-config-dev jas@frallan:~$ rm Contents-amd64* jas@frallan:~$ wget -nv https://deb.debian.org/debian/dists/trixie/main/Contents-amd64.gz 2026-05-25 17:22:35 URL:https://deb.debian.org/debian/dists/trixie/main/Contents-amd64.gz [12616459/12616459] -> "Contents-amd64.gz" [1] jas@frallan:~$ gzip -d Contents-amd64.gz jas@frallan:~$ grep usr/include/ref_array.h Contents-amd64 usr/include/ref_array.h libdevel/libref-array-dev jas@frallan:~$ /Simon
signature.asc
Description: PGP signature
