Lubuntu Desktop images failed to build

[Walter Lapchynski]

I have errors like so:

Traceback (most recent call last):
  File "/usr/share/launchpad-buildd/slavebin/buildlivefs", line 198, in main
    builder.build()
  File "/usr/share/launchpad-buildd/slavebin/buildlivefs", line 159, in build
    self.run_build_command(["lb", "build"], env=base_lb_env)
  File "/usr/share/launchpad-buildd/slavebin/buildlivefs", line 108,
in run_build_command
    self.chroot(["/bin/sh", "-c", command], echo=echo)
  File "/usr/share/launchpad-buildd/slavebin/buildlivefs", line 89, in chroot
    "/usr/bin/sudo", "/usr/sbin/chroot", self.chroot_path] + args)
  File "/usr/lib/python2.7/subprocess.py", line 511, in check_call
    raise CalledProcessError(retcode, cmd)
CalledProcessError: Command '['/usr/bin/sudo', '/usr/sbin/chroot',
'/home/buildd/build-LIVEFSBUILD-19030/chroot-autobuild', 'linux64',
'/bin/sh', '-c', 'cd /build && env PROJECT=lubuntu ARCH=amd64 lb
build']' returned non-zero exit status 1

…in all of my build logs. That exit status isn't very telling, but to
be expected.

I'm not sure it's related, but debian-installer has been unhappy with
us in our other images:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1417251

I'm guessing no, since the logs suggest that there were no packaging
problems, but I'm all ears.

We rebuild at 1529 UTC tomorrow, so if we can get this resolved by
then, that would be great! ☺

-- 
@wxl
Lubuntu Release Manager, Head of QA
Ubuntu PPC Point of Contact
Ubuntu Oregon LoCo Team Leader