ROS2 Eloquent dependency clashes Ubuntu 18.04.3

asked 2019-12-30 06:40:54 -0500

Apothus gravatar image

updated 2019-12-31 09:55:37 -0500

allenh1 gravatar image

I've run into challenges trying to install ROS2 from binaries on an Odroid H2 (Intel Celeron J4105). Following the guide I installed Ubuntu18.04.03-LTS. The followed the guides. However 'Aptitude' was showing clashes on over 200 packages. Attempting to build from sauce was also causing similar grief.

Many of the packages installed by Ubuntu were newer versions than the dependencies required by ROS2. Notably many of the installed packages appeared to be Ubuntu specific e.g. '3.06-ubuntu1' with a ROS dependency of '3.06' causing a conflict.

Ultimately rolling back to Ubuntu 18.04.2 has fixed the problems and I was able to isntall ROS2 very easily following the steps and compiled binaries.

My concern is that I missed something? or a newer version of Ubuntu means the newbie instructions are out of date. Ideally I'd love to know where I went wrong because I'm sure I missed something in the installation of Ubuntu 18.04.3 and I'd like to avoid anyone else loosing a day to this

edit retag flag offensive close merge delete


There is a good chance the packages you've been trying to install were built against 18.04.2 specifically.

Could you show the contents of /etc/apt/sources.list.d/ros2-latest.list and the output of uname -rvmp and lsb_release -a?

gvdhoorn gravatar image gvdhoorn  ( 2019-12-30 08:16:29 -0500 )edit

If possible please also show the exact errors for more clarity.

tfoote gravatar image tfoote  ( 2019-12-30 11:38:18 -0500 )edit

That was interesting, I blew away my Ubuntu 18.04.02 install with the 18.04.03 to get a list of the errors I had seen. Yet this time it installed correctly. The configuration structure of my install is the same and I did not skip any steps previously yet today it worked. I assume I must have overlooked something, where could I check the build history of the release binaries?

Apothus gravatar image Apothus  ( 2020-01-01 08:14:20 -0500 )edit

The binary packages haven't changed for over two weeks which I think covers you testing period. I suspect that you had something else on your system that had trouble installing and was causing the conflicts for versions.

tfoote gravatar image tfoote  ( 2020-01-01 13:01:45 -0500 )edit