Hi! On Tue, 2025-05-13 at 06:33:49 +0000, Holger Levsen wrote: > On Tue, May 13, 2025 at 02:28:57AM +0200, Guillem Jover wrote: > > With the .buildinfo support introduction, one current requirement is > > that any .changes file includes at least one .buildinfo file (so > > there's currently no filtering based on build type, nor any counting > > to not break on potentially old tooling). > > can't we change this requirement? .buildinfo files for _source.changes > don't make sense, so we shouldn't create nor distribute them.
(I think we have discussed this in the past. :) If someone uses dpkg-buildpackage, then build dependencies need to be satisfied (even for source-only builds), where code gets executed from the package itself (clean targets etc), so this is also a build that generates an upload represented in a .changes file. Those can also affect source package generation, so I still think it does make sense that they generate a .buildinfo file. I also think reproducible source packages are an important thing that we already have (at least tooling wise), which I'd rather not regress support on. Thanks, Guillem
