Hi, Quoting tony mancill (2019-08-06 15:49:06) > After reviewing #902856 and the recent thread, it doesn't feel like a > fix on the dpkg side is in sight, but perhaps I'm just being > pessimistic. This behavior (ignoring -sa and -v$version) has been > driving me crazy, so thank you to Pierre-Elliot for contributing a > patch. > > In my opinion, the options to dpkg-buildpackage are stable enough to > warrant accepting the patch as a work-around until dpkg has been > changed. After all, sbuild doesn't have to support every possible use > case. Here we are talking about some primary use cases. > > In the meantime, could we bump the severity of this bug to > important? Or at least update the manpage to document the limitations > of --force-orig-source and --dpkg-source-opts and --debbuildopts?
I guess we should just apply the temporary (famous last word) patch to sbuild
to close the issue for now.
> By the way, one of the suggestions in that thread is to use
> "dpkg-buildpackage -S" - but that requires that build-deps are installed,
> which is one of the key reasons I am using a chroot in the first place.
You don't need Build-Depends installed for creating a source package. Use:
$ dpkg-source -b .
Thanks!
cheers, josch
signature.asc
Description: signature
