and the -e option is probably new with the version from buster and given that the parallel build option isn't critical we never noticed that it wasn't working.
Makes sense. Can you close this please? I am not familiar with this bug tracker software. Thank you very much. On 3/2/20 5:01 PM, Adam D. Barratt wrote: > On 2020-03-02 14:53, Maximilian Philipps wrote: >> When calling debuild with the -e parameter the arguments gets >> interpolated into the Changed-By field of the .changes file. >> >> From our build job: >> >> debuild -b -us -uc -eDEB_BUILD_OPTIONS=parallel=2 -ai386 >> >> >> grep 'Changed-By:' *.changes >> >> Changed-By: DEB_BUILD_OPTIONS=parallel=2 >> >> >> Followed by lintian complaining: >> >> changes: changed-by-address-missing DEB_BUILD_OPTIONS=parallel=2 > > This is actually behaving as per the documentation, although it's > possibly not immediately obvious. > > debuild(1) says: > > "Note the order of options here: the debuild options come first, then > the dpkg-buildpackage ones, then finally the checker options" > > In this case, neither -us nor -uc is a debuild option, so they are > being assumed to be dpkg-buildpackage options. As a result, -e is also > being passed to dpkg-buildpackage, where: > > > -e, --build-by=maintainer-address > Passed unchanged to dpkg-genchanges. See its manual page. > > > Rearranging your option list so that the debuild-specific options are > listed first should resolve this. > > Regards, > > Adam
