Tracking down scons FTBFS issues.

[Matt Zimmerman]

On Tue, Jul 10, 2007 at 01:15:10AM +0200, Michael Bienia wrote:
> On 2007-05-16 16:40:41 +0100, Matt Zimmerman wrote:
> > On Wed, May 16, 2007 at 05:14:10PM +0200, Michael Bienia wrote:
> [...]
> > > https://bugs.launchpad.net/launchpad-buildd/+bug/87077
> [...]
> > That environment value looks like a bug in a Perl program.  It shouldn't
> > break sbuild, but it shouldn't be there either.
> 
> Here is another build log for a package using scons and failing on the
> buildds:
> http://librarian.dogfood.launchpad.net/7747184/buildlog_ubuntu-gutsy-i386.ardour_1%3A2.0.2-2ubuntu2%7Eppa2_FAILEDTOBUILD.txt.gz
> 
> The failure is once again:
> /bin/sh: Syntax error: "(" unexpected
> 
> Using env in debian/rules to print the environment gives:
> [...]
> SUDO_USER=buildd
> HASH(0x82d9204)=
> LOGNAME=buildd
> [...]
> 
> Hope that helps you further to track down why only packages using scons
> have this problem.

Packages using scons have this problem because they attempt to pass the
environment on the command line to env(1) without quoting it.  This is a bug
in scons.

-- 
 - mdz