On 12 Jul 2017, at 10:30, Ian Jackson <ijack...@chiark.greenend.org.uk> wrote:
> James Clarke writes ("Re: Bad interaction between
> pbuilder/debhelper/dpkg-buildinfo/dpkg-genchanges and dak on
> security-master"):
>> Having the _amd64.buildinfo included in a _source.changes created by
>> dpkg-genchanges -S in a tree which has done a source+binary build is an
>> intended feature.
>
> Wait, what ? You're telling me that dpkg-genchanges will pick up
> random .buildinfo files it happens to find lying around ? And that
> this is deliberate ?
No, only files mentioned in debian/files, which will be emptied for a
subsequent build.
> There is no way the tools can tell whether the _amd64.buildinfo it
> finds even relates to the same source code, or anything.
Well, the same is true for the .dsc if you modify the source and then do a
dpkg-genchanges :)
James
