The second test rebuild of Yakkety Yak was started on September 16 for all architectures, all components (main component and seeded packages mostly finished, unseeded packages still building).
Results (please also look at the superseded builds) can be found at
http://qa.ubuntuwire.org/ftbfs/test-rebuild-20160916-yakkety.html
Additional build failures for packages in yakkety-proposed (not yet in yakkety) can be found at http://qa.ubuntuwire.com/ftbfs/
Please help fixing the build failures.
Another test rebuild using the Linaro-GCC 6 as the default (planning the defaults change around the end of October) can be found at
http://qa.ubuntuwire.org/ftbfs/test-rebuild-20160916-linaro-yakkety.html
The corresponding compiler can be found in the ubuntu-toolchain-r/test PPA.
Matthias
Responding for ubuntu-server packages...
On 22.09.2016 [14:17:23 +0200], Matthias Klose wrote:
The second test rebuild of Yakkety Yak was started on September 16 for all architectures, all components (main component and seeded packages mostly finished, unseeded packages still building).
Results (please also look at the superseded builds) can be found at
http://qa.ubuntuwire.org/ftbfs/test-rebuild-20160916-yakkety.html
cinder, nova, nova-lxd, python-eventlet, python-taskflow should all be handled by packages in -proposed by the openstack team. Thanks to them!
libewebp and memcached still have undetermined cause on armhf -- need to find time next week to debug live, I think.
llvm-toolchain-3.6 has a build-fix in debian, but it then still fails to pass two tests, still investigating.
python-cffi on ppc64el, reproduced, debugging live.
python-docutils should be fixed on the next test rebuild, as it was a bug in xml-core. This will probably fix a few other build failures with the same signature ("dh_installxmlcatalogs: Unexpected debhelper version format").
xen is fixed per Stefan Bader in the -proposed version.
Additional build failures for packages in yakkety-proposed (not yet in yakkety) can be found at http://qa.ubuntuwire.com/ftbfs/
I believe juju team will need to look at the juju-core failure and will ping the lxc folks on that failure.
Thanks, Nish