Bug#869184: dpkg: source uploads including _amd64.buildinfo cause problems

[Guillem Jover]

On Fri, 2018-11-09 at 11:55:38 +0100, Guillem Jover wrote:
> Actually, I guess the other option that might be an option for stable is
> to make dpkg-buildpackage generate the buildinfo file itself, and on
> source-only uploads force the name to be _source.buildinfo regardless
> of the options passed down to dpkg-genbuildinfo (even if the contents
> will end up not matching the name).
> 
> This would seem rather less intrusive, as that only changes the
> behavior in a "corner-case" (even though documented and recommended
> one), when using «dpkg-buildpackage --changes-option=-S». And while it
> could be considered to produce confusing filenames, it sticks to the
> current pattern. It would also fix the other bug where running
> dpkg-genbuildinfo leaves debian/files around, even on source only
> builds.

Err, ugh, disregard all the above. This would still generate the
_<arch>.buildinfo pattern, because we are under a full build, and
the only option passed is for .changes, an option which we do not
parse from dpkg-buildpackage anyway. If the .changes file was generated
by dpkg-genchanges itself then it could end up generating
_source.changes, but that would not help here at all anyway…

Thanks,
Guillem