Revision history [back]

Are you releasing packages from a forked rosdistro database or trying to apply a custom buildfarm configuration to the upstream rosdistro database?

I think this is a general challenge for "add-on" style rosdistros which are a case that we aim to support but rely primarily on community feedback to know what works. https://github.com/ros-infrastructure/ros_buildfarm/blob/master/doc/custom_rosdistro.rst#add-on-fork

I'm making the assumption that you're using a custom rosdistro repository to release packages that aren't available on the official buildfarm. For that to work there's two friction points:

1. Your buildfarm repository needs to import packages from ROS upstream. That's described here https://github.com/ros-infrastructure/ros_buildfarm/blob/master/doc/custom_rosdistro.rst#import-ros-packages-which-are-not-built-by-the-custom-build-farm

2. Dependencies of your package need to be treated as "outside" your rosdistro so that your buildfarm does not expect to build them. @tfoote may have a lighter-touch solution here. The last work I remember in this space is https://github.com/ros-infrastructure/ros_buildfarm/pull/501 which unmakes the assumption that the "catkin" package always comes from the current rosdistro. When running bloom on your released packages, you'll need to use a rosdep database that resolves the "missing" dependencies using the upstream rosdistro. I have a stale branch of rosdep that might help with this process. https://github.com/nuclearsandwich/rosdep/tree/get-deps-from-rosdistro