Closed nuclearsandwich closed 4 years ago
ros-infrastructure/ros_release_python#33 has nothing to do with this change.
ros-infrastructure/ros_release_python#33 has nothing to do with this change.
--include
doesn't work at all, suite3 or no without that change. This PR won't have the intended effect without it. I updated the PR body to clarify the relationship.
--include
doesn't work at all, suite3 or no without that change. This PR won't have the intended effect without it.
Yes, --include
was broken. Using Suite3
or just Suite
doesn't make any difference. Therefore these two changes are orthogonal.
This configuration option requires two recent changes in stdeb and ros_release_python:
--include
support on the current bootstrap repository.The option allows a different set of suites to be set for Python 3 releases allowing us to forestall releasing Python2 versions of these packages for platforms where we don't plan to support Python 2.