Ask Your Question
1

Release only on certain Ubuntu platform?

asked 2016-02-11 12:21:15 -0500

130s gravatar image

updated 2016-02-11 12:30:07 -0500

For example on Indigo, can I exclude certain Ubuntu distro, say Saucy, upon making a release? Well it looks like it's not possible at this momement, but is it planned to become possible in the future? I don't mean it's necessary for any of my purpose for now but I'm just curious and sounds like it's convenient.

While releasing a package into Indigo, I found a DEB of one of the dependencies, python-termcolor (ticketed), is not available only on Saucy (ie. available on Trusty onward).

Apparently rosdep (run during bloom process) couldn't resolve the dependency and gave an error, but then bloom offered an option to skip it (log1). Combined with a recent announcement, I thought I could somehow move forward making a release into Indio except on Saucy platform. Turned out I was wrong (I then got a bunch of error emails from buildfarm (log2) stating that a release branch for Saucy wasn't found).

log1

==> git-bloom-generate -y rosdebian --prefix release/indigo indigo -i 0
Generating source debs for the packages: ['hironx_calibration', 'hironx_moveit_config', 'hironx_ros_bridge', 'rtmros_hironx']
Debian Incremental Version: 0
Debian Distributions: ['saucy', 'trusty']
Releasing for rosdistro: indigo

Pre-verifying Debian dependency keys...
Running 'rosdep update'...
Key 'python-termcolor' resolved to '['termcolor']' with installer 'pip', which does not match the default installer 'apt'.
Failed to resolve python-termcolor on ubuntu:saucy with: Error running generator: The Debian generator does not support dependencies which are installed with the 'pip' installer.
python-termcolor is depended on by these packages: ['hironx_ros_bridge']
<== Failed
Some of the dependencies for packages in this repository could not be resolved by rosdep.
You can try to address the issues which appear above and try again if you wish.
Would you like to try again? [Y/n]? n
User aborted after rosdep keys were not resolved.
<== The following generator action reported that it is missing one or more
    rosdep keys, but that the key exists in other platforms:
'['/usr/bin/git-bloom-generate', '-y', 'rosdebian', '--prefix', 'release/indigo', 'indigo', '-i', '0']'

If you are absolutely sure that this key is unavailable for the platform in
question, the generator can be skipped and you can proceed with the release.
Skip generator action and continue with release [y/N]? y

Action skipped, continuing with release.

==> git-bloom-generate -y rosrpm --prefix release/indigo indigo -i 0
Generating source RPMs for the packages: ['hironx_calibration', 'hironx_moveit_config', 'hironx_ros_bridge', 'rtmros_hironx']
RPM Incremental Version: 0
RPM Distributions: ['21', 'heisenbug']
Releasing for rosdistro: indigo

Pre-verifying RPM dependency keys...
Running 'rosdep update'...
Key 'python-termcolor' resolved to '['termcolor']' with installer 'pip', which does not match the default installer 'yum'.
Failed to resolve python-termcolor on fedora:21 with: Error running generator: The RPM generator does not support dependencies which are installed with the 'pip' installer.
python-termcolor is depended on by these packages: ['hironx_ros_bridge']
<== Failed
Key 'python-termcolor' resolved to '['termcolor']' with installer 'pip', which does not match the default installer 'yum'.
Failed to resolve python-termcolor on fedora:heisenbug with: Error running generator: The RPM generator does not support dependencies which are installed with ...
(more)
edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2016-02-11 12:29:53 -0500

Dirk Thomas gravatar image

It is not planned to support custom set of distributions. Simply because one ROS distribution aims to provide a certain set and not diverge across various Ubuntu distributions.

That being set your specific problem might be resolved by the fact that EOL Ubuntu distributions will be not be built for in the near future. See http://lists.ros.org/pipermail/ros-us... for more information on that.

edit flag offensive delete link more

Comments

Ok, I think I just misinterpret Tully's announcement. Now I understand that once Saucy's build reaches EOLed for Indigo, 1) all Indigo build jobs for Saucy will be stopped, 2) and maintainers will not have an option for excluding certain platforms (same as we have not had).

130s gravatar image130s ( 2016-02-11 12:40:10 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2016-02-11 12:21:15 -0500

Seen: 138 times

Last updated: Feb 11 '16