Bug#843470: mergechanges: doesn't know about new .buildinfo files

[Simon McVittie]

On Tue, 22 Nov 2016 at 15:05:10 -0500, James McCoy wrote:
> Shouldn't it always be kept in the resulting changes file?  It's just
> build metadata like the changes/dsc files.

Hmm. I think it would be unexpected to include the buildinfo in a
source-only changes file (mergechanges --source), since (per
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763822>)
it is metadata about a binary build.

I can see an argument for keeping *.buildinfo (even if not *_all.buildinfo)
in mergechanges --indep, because it's difficult for mergechanges to know
whether hello_1.0_amd64.buildinfo refers to an amd64-only binary build
or an amd64+all binary build (it could be either).

As a maintainer who uses mergechanges --indep for source+all uploads
to stable, and mergechanges --source for source-only uploads to unstable,
my main concern is to not make broken uploads by using a filename that will
clash with one that is produced by the buildds. In particular, I don't
want to do a source-only or source+all upload, that contains
hello_1.0_amd64.buildinfo because I happen to have built on amd64,
and then have the amd64 buildd unable to add its binaries to the archive
because its buildinfo file clashes with mine.

But perhaps this won't really happen in practice, because in practice
either I'll be doing a source-only build for >= stretch, or a
source+all build with no .buildinfo produced for <= jessie?

    S