On 01/02/26 at 17:19 +0100, Lucas Nussbaum wrote: > On 01/02/26 at 12:08 +0000, Simon McVittie wrote: > > I've seen comments elsewhere saying that it should be considered to be a bug > > if a source package can't be successfully built by the latest dpkg-source, > > and I think that's valid (albeit possibly a bug in dpkg rather than in the > > source package, if dpkg regresses); but that isn't the same as saying that > > it's a bug if *the specific source package that was uploaded* wasn't > > generated by the latest dpkg-source. > > > > A possible way to mitigate that class of false positives would be if git2dsc > > did this: > > > > - take the .dsc from the archive, A > > - take the .dsc that it produces from git, B > > - unpack A > > - repack A with the same dpkg-source version that it used for B, to get C > > - compare B with C > > That's a good idea indeed. I will do that, it's actually cleaner than > the current normalization step.
This has been implemented, and relevant packages have been reprocessed. https://debaudit.debian.net/git2dsc/regressions/forky is up to date. Lucas
