Hi, Quoting Vagrant Cascadian (2017-01-23 22:40:13) > Package: sbuild > Version: 0.73.0-2 > Severity: normal > User: reproducible-bui...@lists.alioth.debian.org > Usertags: toolchain > X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org > > When building a package, I wanted to test the build and do a > source-only upload after testing the package: > > sbuild -d unstable -c sid --arch-all --source-only --run-lintian > > This produced the buildinfo file epoptes_0.5.10-2_amd64.buildinfo. > > Which is awesome! Thanks for the work on supporting buildinfo files! > Very Exciting! > > > Then I ran: > > sbuild -d UNRELEASED -c sid --arch-all --no-source \ > --maintainer='Vagrant Cascadian <vagr...@debian.org>' \ > --append-to-version=~20170123~12.1 epoptes_0.5.10-2.dsc > > It also created epoptes_0.5.10-2_amd64.buildinfo, overwriting the > .buildinfo created with the build. I would have expected it to > generate a buildinfo with the --append-to-version appended, rather than > overwriting the file matching the .dsc's version.
I wouldn't because that's not what dpkg-buildpackage is doing. See the man page of dpkg-genbuildinfo. The filename of the .buildinfo file is generated from the source version, not the binary version. So this bug seems to be a WONTFIX. Do you agree? Thanks! cheers, josch
signature.asc
Description: signature
