Revision history [back]

I'll take a shot at an answer, although I expect @nuclearsandwich will weigh in later.

Blacklisting is done in the ros_buildfarm_config repo (production branch in this case). Not in the rosdistro. For cartographer specifically, see ros-infrastructure/ros_buildfarm_config#110. Reason given for blacklisting that package on Jessie:

cartographer's dependency libceres-dev doesnt exist on Debian Jessie and we don't plan to backport it as Jessie is almost EOL

The complete blacklist for Jessie is maintained here.

In general Bloom generates release artefacts for all supported target platforms (generators here). Afaik you cannot ask Bloom to not generate for something. Blacklisting is done afterwards.

I'll take a shot at an answer, although I expect @nuclearsandwich will weigh in later.

Blacklisting is done in the ros_buildfarm_config repo (production branch in this case). Not in the rosdistro. For cartographer specifically, see ros-infrastructure/ros_buildfarm_config#110. Reason given for blacklisting that package on Jessie:

cartographer's dependency libceres-dev doesnt exist on Debian Jessie and we don't plan to backport it as Jessie is almost EOL

The complete blacklist for Jessie is maintained here.

In general Bloom generates release artefacts for all supported supported configured target platforms (generators here). As @nuclearsandwich writes:

The release artifacts bloom generates are determined by the actions field of each track in tracks.yaml. If you wish to change what is generated you can modify that list of commands.

Afaik you cannot ask Bloom to not generate for something. Blacklisting is done afterwards.

I'll take a shot at an answer, although I expect @nuclearsandwich will weigh in later.

Blacklisting is done in the ros_buildfarm_config repo (production branch in this case). Not in the rosdistro. For cartographer specifically, see ros-infrastructure/ros_buildfarm_config#110. Reason given for blacklisting that package on Jessie:

cartographer's dependency libceres-dev doesnt exist on Debian Jessie and we don't plan to backport it as Jessie is almost EOL

The complete blacklist for Jessie is maintained here.. See REP-137: Specification/Release build file for the spec on the blacklist.

In general Bloom generates release artefacts for all supported configured target platforms (generators here). As @nuclearsandwich writes:

The release artifacts bloom generates are determined by the actions field of each track in tracks.yaml. If you wish to change what is generated you can modify that list of commands.

Afaik you cannot ask Bloom to not generate for something. Blacklisting is done afterwards.