Package Details: ros-melodic-desktop-full 1.4.1-2

Git Clone URL: (read-only, click to copy)
Package Base: ros-melodic-desktop-full
Description: ROS - A metapackage to aggregate several packages.
Upstream URL:
Keywords: melodic morena robot robotics ros
Licenses: BSD
Submitter: GPereira
Maintainer: bionade24 (jwhendy)
Last Packager: bionade24
Votes: 12
Popularity: 0.015279
First Submitted: 2018-05-13 18:47
Last Updated: 2020-09-21 17:26

Pinned Comments

bionade24 commented on 2019-04-09 19:13

We moved our Development to Github: Please open issues there instead of commenting.

ROS binary Repo (Thirdparty):
pacman-key --recv-keys CB222E7EBC11D682AAC8B317A4A0D73114FDE6FC
pacman-key --edit-key CB222E7EBC11D682AAC8B317A4A0D73114FDE6FC
Add this to your pacman.conf:

Server =

Please vote for getting these packages into community repo.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

bionade24 commented on 2018-09-26 14:56

ros-melodic-rosout requires liboost packages version 1.67, but Arch has version 1.68. Any solution for that?

bionade24 commented on 2018-09-26 14:04

I now always get this:

-- Using Python nosetests: /usr/bin/nosetests-3.7 ImportError: "from catkin_pkg.package import parse_package" failed: No module named 'catkin_pkg' Make sure that you have installed "catkin_pkg", it is up to date and on the PYTHONPATH.

Seems like python2-catkin_pkg changed to python-catkin_pkg. This have to be added as dependency.

GPereira commented on 2018-09-26 12:11

It should be good now, please check

stones commented on 2018-09-26 11:49

Thank you, However I have crossed the package aur-ros-melodic-rostime/src/ros-melodic-rostime" does not appear to contain CMakeLists.txt.

Is there any possibility to do fast check??

GPereira commented on 2018-09-26 11:23

I am uploading the fixes now! :)

stones commented on 2018-09-26 09:43

@GPereira, please it is only one sentence to add (even one word), in the CMake files,

So at the end, we should continue our life without ROS !!!!

krukai commented on 2018-09-25 13:29

@GPereira, we really need a rollback.

While I am endlessly grateful for the work you have done to make ROS available on Arch, I'll have to switch to Ubuntu for my ROS work for the time being, simply because I do not have the time, experience, or let alone efficient workflow to manually patch dozens of packages, just because some patches were applied too hastily.

Before this upgrade to Python 3, I already had to compile RViz with OGRE 9 again because OGRE 11 RViz still has issues with RobotModels and Maps, see

I understand that making ROS available on the AUR is a daunting task, and that perhaps deeming Arch a reliable workstation distro is much more of a gamble than I would like to admit, but going from something that worked really well for half a year with just some rebuilds and minor patching to an experimental playground of this scale is frustrating.

At this point, I would rather be at the mercy of prebuilt ROS binaries on Arch than dreading every single -Suy. If that would also be an option for others, I would happily join an effort to make this a reality.

lsr commented on 2018-09-24 19:48

I ended up replacing the prepare() section of almost all files with:

prepare() {
    cd ${srcdir}/${_dir}
    _pkgname=$(echo ${pkgname} | sed 's/ros-melodic-//' | sed 's/-/_/g')
    git checkout release/melodic/${_pkgname}

Some packages are fixed by only fixing the sed 's/ros-lunar-//' segment, but many are not (and these seem to have nothing to restrict them to melodic).

stones commented on 2018-09-24 12:17

@GPereira, You can easily try to build ros-melodic-roscpp. it has a dependency with ros-melodic-cpp-common that does not contain the CMakeLists

At the end, there is no possibility to build the package.

DarioP commented on 2018-09-23 17:21

I also tried to build this few days ago, encountering the same impingements. After reading the experience of miramur, for sure I am not going to follow that path. My opinion is that the rollback to python2 is necessary untill a working python3 packaging is found, otherwise several people (included me) will just give up using ROS on Arch.