On Sat, 24 Dec 2022 at 01:15:15 +0000, Ian Jackson wrote:
> Simon McVittie writes ("Bug#1026918: dgit: shows warnings if
> debian/source/include-binaries mentions files in debian/"):
> > According to dpkg-source(1), all non-text files in a 3.0 (quilt) package[1]
> > need to be listed in debian/source/include-binaries, whether they're
> > additions to the upstream source or part of the debian/ directory
>
> I don't think this behaviour by dpkg-source serves any
> kind of purpose (if indeed it still does this thing)
The only purpose I can think of is that it's a safety-catch against
the maintainer accidentally including built binaries, vim swapfiles
and other binary detritus in the source package, which seems a lot
less likely to happen anyway with a package that's maintained in a VCS,
particularly with dgit and `gbp buildpackage --git-export-dir` providing
two orthogonal methods to ensure we're working with a clean git tree -
but I've seen such files added by mistake by an overzealous `git add`,
so perhaps there is still value in having that safety-catch.
smcv
