Control: reassign -1 dpkg-dev Control: found -1 1.21.22 On Sat, 10 May 2025, Johannes Schauer Marin Rodrigues wrote: > > 6. Observe the presence of the buildinfo in the resulting source.changes: > > grep buildinfo ../*_source.changes > > This is something that dpkg-genchanges does. Sbuild runs this: > > dpkg-genchanges --build=source > > And that will include a reference to the buildinfo if before running this > command, the package was already built. If you run "debian/rules clean" before > running above command, then the resulting .changes file will *not* contain a > reference to the buildinfo. > > If you think that this is a bug, you should re-assign this to dpkg.
Thanks, doing so as I ran your reproducer and I confirm that the binary buildinfo is there. $ grep buildinfo hello_2.10-3_source.changes 807907dc2f97b2a089e6b05e697eaf157f57767b 5813 hello_2.10-3_amd64.buildinfo 15285c44b8509fb01454f419171170f9e6468c866df5e59e65036bc9cd35062c 5813 hello_2.10-3_amd64.buildinfo 7fd5124a2508e44589040f769a152da1 5813 devel optional hello_2.10-3_amd64.buildinfo Guillem, the issue reported here is that running "dpkg-genchanges --build=source" in a freshly built tree will include the _<arch>.buildinfo from the source+binary build run just before, whereas a source-only build will properly generate a .changes that references a _source.buildinfo. This introduces a difference in what's generated between users of "sbuild --source-only-changes" and "sbuild --source --no-arch-any --no-arch-all" (or plain dpkg-buildpackage -S). Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog <hert...@debian.org> ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋ The Debian Handbook: https://debian-handbook.info/get/ ⠈⠳⣄⠀⠀⠀⠀ Debian Long Term Support: https://deb.li/LTS
