Overview

First, please skim the architecture page -- none of this will make sense unless you understand the pipeline.

There are three debian repositories and the system status page charts the life of a release as it propagates into those repositories.

• Source deb missing; Not in any repository. The stack's release information has been submitted via create.py, but the Debian source deb has not been created yet. The source deb job is automatically started by the create.py script. Experts only: Clicking on the [+] sign next to the stack's name will trigger the source deb job manually, which is only necessary when you are working outside the create.py script.

• In shadow-fixed, but not in shadow, waiting on dependency. The shadow version of the stack needs to be rebuilt. The shadow version of the stack cannot be built yet because the dependencies have not been built yet.

• In shadow-fixed, but not in shadow. The shadow version of the stack needs to be rebuilt. All of the dependencies of the stack have been built in shadow, so this stack is ready to build.

• Missing from repositories; New or Broken. The stack is missing from all repositories, most likely because it did not build correctly. This can also happen with a new stack that has not been built yet. The current system is 'best effort', so it will push a new set of debs to the next repository in the pipeline when it is done building.

• All is well. White is used for (a) released stacks that are in shadow-fixed and (b) unreleased stacks that are recorded in the rosdistro file. In either case, white represents that all is as it should be.