Johannes Schauer, on Wed 12 Oct 2016 15:35:29 +0200, wrote:
> we can apply a smarter fix by properly escaping the
> command string. Here is a patch:
It's working fine in my tests.
> When I try this out, then many commands seem to be executed correctly. My
> fails as soon as sbuild attempts to execute something inside the chroot not as
> the root user but as the user running sbuild. So I end up getting:
> User Environment
> sudo: no tty present and no askpass program specified
> E: read_command failed to execute env
> E: unable to open pipe
Perhaps you are missing adding your user to sudo without password?