Santiago Vila <[email protected]> writes: > On Fri, May 29, 2026 at 10:28:01AM +0800, Otto Kekäläinen wrote: > >> I am resurrecting this old discussion from 2024 and 2025: I don't like >> how Go builds currently use `_build/` as the build directory, and as a >> consequence lots of Debian Go packages end up modifying the upstream >> `.gitignore` to exclude `_build/`. >> >> I'd rather have build artifacts in `debian/_build` and exclude this >> directory in `debian/.gitignore`. > > Beware with debian/.gitignore. Packages having such file are not > "source-reproducible", i.e. "apt-get source package" followed by > "dpkg-buildpackage -S" may result in a source package which is > different than the original one in the archive.
That would be solved by removing debian/.gitignore from git, right? The file is incompatible with tag2upload quilt=unapplied, which is how I prefer to use tag2upload. I see no strong reason for having a debian/.gitignore at all these days. I see mild reasons for not having the file, because it breaks source package reproducibility. I'd like this to be the default Go team style, and for us to care about binary/source reproducibility generally. /Simon > [ While the reproducible-builds effort is mainly about binary packages, > I don't see why source packages should not be reproducible as well]. > > If you absolutely need to do that and remain source-reproducible, it > would be possible to prevent such effect by adding yet another file > (debian/source/options) telling dpkg-source to treat the .gitignore > file differently. > > I see requiring two files for this as noise and would much prefer if > people could just use the clean target in debian/rules or use some > other means to have clean packages. > > Thanks. >
signature.asc
Description: PGP signature
