blacklist cob_command_tools buster

[fmessmer]

blacklisting additional packages from cob_command_tools

follow-up of #187
as suggested in https://answers.ros.org/question/366881/noetic-build-failed-in-jenkins-debianbuster-could-not-resolve-rosdep-key/?answer=367253#post-id-367253

however, I don't see why theses packages cannot be released into Noeteic for debian/buster
Because it was only cob_monitoring that reported an unmet dependency - see https://github.com/ipa320/cob_command_tools/issues/289)

As e.g. cob_interactive_teleop and scenario_test_tools are/can be released into Noetic - which are also part of cob_command_tools

Thus, I'd rather like to find out what other rosdep keys might be missing and add those in order to release (some of) the packages also for debian/buster
But I'll need some help in finding out what's wrong...and what I can do to avoid the blacklisting...

Thanks for your help!

[fmessmer]

e.g. I went through the package.xml of cob_script_server: https://github.com/ipa320/cob_command_tools/blob/indigo_dev/cob_script_server/package.xml
seems like all dependencies listed could be resolved for debian/buster

so I don't know why this should not be relaseable for debian/buster
or am I missing something?

[fmessmer]

@sloretz
any words on this? any hint for me to debug what's going on?

[fmessmer]

friendly ping...

[ros-discourse]

This pull request has been mentioned on ROS Discourse. There might be relevant details there:

https://discourse.ros.org/t/preparing-for-noetic-sync-2021-01-22/18570/2

[tfoote]

@sloretz As the Noetic boss I'm leaving this for you.

[fmessmer]

should not be needed anymore - since https://github.com/ipa320/cob_command_tools/pull/295
ref ros/rosdistro#28071
ref ros/rosdistro#28072