PopOS 19.10 Support

asked 2020-01-17 20:57:39 -0600

Root3287
16 ●1 ●3 ●2

Specs

OS: Pop!_OS 19.10 x86_64 Kernel: 5.3.0-7625-generic Shell: bash 5.0.3 DE: GNOME 3.34.1 CPU: Intel i5-7600K (4) @ 4.200GHz GPU: NVIDIA GeForce GTX 1060 6GB Memory: 5881MiB / 15970MiB

When I try to install ros through apt. This is the following message

sudo apt install ros-melodic-desktop-full
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 ros-melodic-desktop-full : Depends: ros-melodic-desktop but it is not going to be installed
                            Depends: ros-melodic-perception but it is not going to be installed
                            Depends: ros-melodic-simulators but it is not going to be installed
                            Depends: ros-melodic-urdf-sim-tutorial but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

When you add the dependencies those packages has more. Those other packages has more dependencies. etc.

I tried compiling from source, but I would get

[connext_cmake_module] Warning: The location at which Connext was found when the workspace was built [[/opt/rti.com/rti_connext_dds-5.3.1]] does not point to a valid directory, and the NDDSHOME environment variable has not been set. Support for Connext will not be available.

Trying to find solutions for both of those lead me nowhere.

The farthest I went on the installation was step 1.5. I was able to do rosdep init and update. When I try to set up the environment there was not /opt/ros/melodic/setup.bash

edit retag flag offensive close merge delete

add a comment

2 Answers

Sort by » oldest newest most voted

answered 2020-01-18 04:21:05 -0600

gvdhoorn
86574 ●283 ●1432 ●1054 http://cor.tudelft.nl/

updated 2020-01-18 08:03:01 -0600

Pop OS 19.10 is based on Ubuntu Eoan Ermine (19.10).

There are no binary ROS 1 builds available for that Ubuntu version. See REP 3: Target Platforms - Platforms by Distribution: Melodic Morenia (May 2018 - May 2023), which states that Melodic is only available for Ubuntu Bionic.

When I try to install ros through apt. This is the following message

please tell us how you've configured apt in this case, as I suspect you've specified an incorrect distribution code name to be able to download any indices. Specifically, what is the contents of /etc/apt/sources.list.d/ros-latest.list?

When you add the dependencies those packages has more. Those other packages has more dependencies. etc.

And this is most likely caused by the fact that you're attempting to install binary packages that were not made for your OS (or the Ubuntu version it is based on).

I tried compiling from source, but I would get

the error mentions Connext, which makes me believe this is output from an attempted source build of ROS 2.

Could you please clarify what exactly you'd like to install, as mixing and matching all of this will not make anything any easier.

Edit:

Yeah, I was mixing and matching, but the binaries should be the same though.

No. The binaries for Ubuntu Bionic are not the same as those for Ubuntu Eoan would be (if there were any provided).

I did went though the installation with just eoan. The same thing happened.

Which isn't surprising, as Ubuntu Eoan is not supported by ROS Melodic. The problem was not Pop OS, but the Eoan underlying it.

I just want the basics, so I could start working on the code for our UAV team.

If you need something now, you'll have to either:

install a supported version of Ubuntu
build ROS (I guess 1) from source (but this may run into dependency issues)
use Docker or similar container technology

Currently the /etc/apt/sources.list.d/ros-latest.list contain deb http://packages.ros.org/ros/ubuntu bionic main, but I did try to use deb http://packages.ros.org/ros/ubuntu eoan main. That would not give me the ros-mellodic-desktop-full.

Neither of these will work for installing ROS Melodic on Ubuntu Eoan. The former would make apt download indices which are not suitable for the OS you are running, while the latter would not work as there are no package built for Eoan.

It did however gave me ros-desktop-full. Same result.

Please be aware that those are the UpstreamPackages. Those are not compatible with the regular ROS distributions as provided by packages.ros.org.

I even went as far to installing the Debian Buster/Strech Repo to get python-lark-parser in apt.

Seeing that package name I'm assuming you did this for your ROS 2 from-source build attempt?

Just trying to install RoS on anything but Windows is just a pain.

I'm not sure this isn't a ... (more)

edit flag offensive delete link

Comments

Yeah, I was mixing and matching, but the binaries should be the same though. I did went though the installation with just eoan. The same thing happened.

I just want the basics, so I could start working on the code for our UAV team.

Currently the /etc/apt/sources.list.d/ros-latest.list contain deb http://packages.ros.org/ros/ubuntu bionic main, but I did try to use deb http://packages.ros.org/ros/ubuntu eoan main. That would not give me the ros-mellodic-desktop-full. It did however gave me ros-desktop-full. Same result. I even went as far to installing the Debian Buster/Strech Repo to get python-lark-parser in apt.

Just trying to install RoS on anything but Windows is just a pain. Yeah we're on different operating systems, and there is some person that will say, "Get used to the work." But there is applications that has Windows ...(more)

Root3287 ( 2020-01-18 06:34:23 -0600 )edit

It kinda sucks when there are people who like to be on top of their updates, but the application is not supporting their system. Ubuntu is about to soon release 20.04 Which would put 18.04, in my eyes, very out of date. It a big screw you to whose ever on 19.04/19.10

Root3287 ( 2020-01-18 06:38:39 -0600 )edit

add a comment

answered 2020-01-19 05:31:18 -0600

marguedas

3621 ●17 ●109 ●57

It kinda sucks when there are people who like to be on top of their updates, but the application is not supporting their system.

As a person that like to be on top of the updates, I do understand there is a trade-off between being at the edge and have good support; and for many project I end up having to build from source.

This is the option you will have to use here as you are using a non supported platform.

I did build both ROS Melodic and ROS 2 Eloquent on Eoan back in October 19 and could use both without issue.

I just followed the official instructions http://wiki.ros.org/melodic/Installat...

IIRC the only thing I had to change was to tell rosdep to pretend I was on bionic when resolving dependencies.

rosdep install --from-paths src --ignore-src --rosdistro melodic -y --os ubuntu:bionic

edit flag offensive delete link

Comments

Building from source is indeed one of the options OP has.

Please be aware though that this means OP would also be responsible for his own update-cycle (ie: he will not get notified of updates being available, and would have to check this himself periodically).

gvdhoorn ( 2020-01-20 02:33:49 -0600 )edit

add a comment

PopOS 19.10 Support

2 Answers

Comments

Comments

Question Tools

Stats

Related questions

PopOS 19.10 Support edit

2 Answers

Comments

Comments

Question Tools

Stats

Related questions

PopOS 19.10 Support