This is a draft of a new section for the [:PPAQuickStart]. This is not yet official Launchpad documentation.

Dealing with build failures in PPAs

Your new build request will be created within 30 minutes after you receive the the ACCEPTED source upload notification. You can check the status of your builds at:

https://launchpad.net/people/+me/+archive/+builds

Build-farm load will determine how long it will take for your package to to be dispatched.

If the build fails, you will receive a build failure notification email containing:

• build URL
• failure state
• build log URL
• binary upload log for FAILED_TO_UPLOAD state.

The failure states can be:

• FAILED_TO_BUILD: known as FTBFS (failed to build from source), usually represents compilation failures or broken control/rules. Requires a new source upload to fix the problem.

• MANUAL_DEP_WAIT: when the builder could not retrieve all build-dependencies mentioned by the source package. Sometimes it is caused by violations of the "ogre-model" (link to explanation) or by really requiring real missing versions either in ubuntu or in the PPA itself. The uploader has to analyze each case.

• FAILED_TO_UPLOAD: when the binaries were successfully built but could not be accepted by the PPA in question. Usually, binary are refused because they do not match the values specified in source control file (hacks done in debian/rules). Most of the times it will require a new source upload.

• CHROOT_WAIT: when the builder encountered a problem to set up the PPA chroot. Usually requires further investigation, please contact a launchpad-buildd-admin member of send email to lp-user list.

In all failures cases a possibility to 'retry' the failed build is offered to PPA owners in the build records page.

• (screenshot of any build page allowing 'retry')