[noetic] Build failed in Jenkins: debian/buster could not resolve rosdep key
I'm getting daily mails about jenkins failing for one of the repositories that I maintain and that I released to noetic: https://github.com/ipa320/cob_command...
The mail points me to failed builds: e.g. for
http://build.ros.org/job/Nsrc_dB__cob...
One of the packages (cob_monitoring) specifies a dependency that is not available for debian/buster (python3-mechanize).
I specify this dependency with a condition on ROS_PYTHON_VERSION:
https://github.com/ipa320/cob_command...
Because python-mechanize is not available for focal and python3-mechanize is not availabe for xenial/bionic.
During the bloom-release step, this was mentioned and I confirmed to skip that generator:
see https://github.com/ipa320/cob_command...
How can I prevent the buildfarm from still trying to build for debian/buster?
Or can I modify the dependency condition so debian/buster also uses python-mechanize instead of python3-mechanize?
Thanks
Edit: thanks for the PR for cob_monitoring - I'm no longer receiving the failure reports for that package anymore
still, I receive failure reports for the other packges included in cob_command_tools repository:
cob_command_gui: http://build.ros.org/job/Nsrc_dB__cob...cob_command_tools: http://build.ros.org/job/Nsrc_dB__cob...cob_dashboard: http://build.ros.org/job/Nsrc_dB__cob...cob_helper_tools: http://build.ros.org/job/Nsrc_dB__cob...cob_script_server: http://build.ros.org/job/Nsrc_dB__cob...cob_teleop: http://build.ros.org/job/Nsrc_dB__cob...cob_generic_throttle: http://build.ros.org/job/Nsrc_dB__gen...cob_service_tools: http://build.ros.org/job/Nsrc_dB__ser...
I can't relate any missing debian/buster dependency to these failures - in contrary to cob_monitoring
Any idea why these packages do not pass?
I see fatal: Remote branch debian/ros-noetic-cob-command-gui_0.6.19-1_buster not found in upstream origin in the logs.
Does that mean I have to re-do a bloom-release?
Should the missing remote branch not disable the buildfarm for this job?
All of those should be blacklisted too. Just like the above if you skipped the step in bloom. Unless they are blacklisted the buildfarm considers it an error and will tell you that you've asked for them to be built(by putting it in the rosdistro and not blacklisting it) but it's missing resources and it tells you the missing resources.
the respective PR is waiting for review/comments: https://github.com/ros-infrastructure...