Buildfarm addon fork requires ros-"my_distribution"-catkin

edit

Hi, me again.

Have achieved great progress last several weeks in deploying a buildfarm. Thanks for the help on my previous questions. I am doing an addon fork with a customized distribution e.g. "my-kinetic". My ros_buildfarm_config/index.yaml is like:

distributions:
  my-kinetic:
    doc_builds:
      default: my-kinetic/doc-build.yaml
      released-packages-without-doc-job: my-kinetic/doc-released-build.yaml
    notification_emails:
    - libo@somewhere
    release_builds:
      default: my-kinetic/release-build.yaml
    source_builds:
      default: my-kinetic/source-build.yaml

My rosdistro/index.yaml is like

distributions:
  my-kinetic:
    distribution: [my-kinetic/distribution.yaml]
    distribution_cache: http://162.243.151.49/rosdistro_cache/my-kinetic-cache.yaml.gz

My rosdistro only contains thirdparty packages, the original packages are imported from official repo and ported to rosdeps using mikepurvis' rosdep-generator.

When I ran a dev job, one of the "generic dependencies", catkin is resolved to ros-my-kinetic-catkin due to [ https://github.com/ros-infrastructure... ]. But there is obviously no ros-"my"-kinetic-catkin anywhere. So I would like to know what the formal way to solve this for an addon fork. (The other ROS dependencies are correctly resolved to ros-kinetic-*, though).

I tried to add catkin into my rosdistro and try to compile a copy for my buildfarm. But this requires the catkin-release repo to have a debian/ros-"my"-kinetic-catkin_0.7.6-0_xenial branch, which obviously not the case.