Package: dpkg-dev Version: 1.19.0.5 Severity: wishlist Hi,
sbuild supports a convenience feature, where it creates a source-only .changes file in addition to the normal .changes file created by dpkg-buildpackage. It does so, by calling $(dpkg-genchanges --build=source) directly. The problem with this approach is, that the options that the user passed to dpkg-buildpackage are not taken into consideration when generating the source-only .changes file. Already two bugs (#891247 and #884428) got filed against sbuild about this issue. One way to solve this issue, would be to parse the options passed to dpkg-buildpackage and try to find all the options that have an effect on dpkg-genchanges. But such an approach is fragile because it would mean that sbuild would have to keep playing catch up with any interface changes of dpkg-buildpackage. Another way to solve this issue, would be if dpkg-buildpackage would gain the functionality to generate a source-only .changes file in addition to the normal .changes file. Though on IRC Guillem mentioned a third way: by using the changes hook of dpkg-buildpackage. If the changes hook would somehow (maybe via an environment variable) have access to all the dpkg-genchanges-specific options, then sbuild would just need to set --build=source and pass the remaining options as they are to dpkg-genchanges. Thanks! cheers, josch
