Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

What to do with bloom when dependency unavailable on Debian

asked 2016-05-18 13:53:19 -0500

130s

10937 ●203 ●339 ●330 http://www.linkedin.co...

From ROS Kinetic looks like Debian (Jessie for Kinetic) will be official supported OS.

I had an issue when I made a release of a package into Kinetic where one of the dependencies was not yet available on Jessie at that time so that build on ROS buildfarm failed only for Jessie.

Looks like @tfoote fixed it by re-running bloom, but what magic with bloom we could use for this kind of problem?

edit retag flag offensive close merge delete

add a comment

1 Answer

Sort by » oldest newest most voted

answered 2016-05-18 14:15:33 -0500

tfoote

58457 ●128 ●550 ●526 http://www.ros.org/

If the dependencies are not available you'll have to do like you did and tell bloom to skip that action.

If you skip an action for a target like debian it needs to be added to the blacklist on the buildfarm so that the buildfarm will not try to repeatedly build.

We are refactoring the buildfarm config to allow a higher level of granularity on the blacklisting: https://github.com/ros-infrastructure... without that landed we could not easily blacklist a package for debian only. Once that's merged we will be able to do so.

edit flag offensive delete link

add a comment

Question Tools

1 follower

Stats

Asked: 2016-05-18 13:53:19 -0500

Seen: 89 times

Last updated: May 18 '16

What to do with bloom when dependency unavailable on Debian edit

1 Answer

Question Tools

Stats

Related questions

What to do with bloom when dependency unavailable on Debian