No, that is not breaking anything. I am trying to make it run on python 3 that's all. Sorry for publishing not working state packages.
Search Criteria
Package Details: ros-melodic-desktop-full 1.4.1-3
Package Actions
Git Clone URL: | https://aur.archlinux.org/ros-melodic-desktop-full.git (read-only, click to copy) |
---|---|
Package Base: | ros-melodic-desktop-full |
Description: | ROS - A metapackage to aggregate several packages. |
Upstream URL: | https://github.com/ros/metapackages |
Keywords: | melodic morena robot robotics ros |
Licenses: | BSD |
Submitter: | GPereira |
Maintainer: | None |
Last Packager: | bionade24 |
Votes: | 12 |
Popularity: | 0.000000 |
First Submitted: | 2018-05-13 18:47 (UTC) |
Last Updated: | 2021-03-23 03:30 (UTC) |
Dependencies (7)
- ros-melodic-desktopAUR
- ros-melodic-perceptionAUR
- ros-melodic-simulators
- ros-melodic-urdf-sim-tutorialAUR
- cmake (cmake-gitAUR) (make)
- ros-build-toolsAUR (make)
- ros-melodic-catkinAUR (make)
Required by (0)
Sources (1)
GPereira commented on 2018-09-09 18:00 (UTC)
timonegk commented on 2018-09-09 15:22 (UTC)
Why are you using the git upstream instead of the tarball releases for melodic? That breaks package versioning.
tsp commented on 2018-09-09 09:11 (UTC)
A lot of packages have broken PKGBUILD
s since the most recent update. The cmake
call needs to be updated to point to the specific directory in the sources.
So for example the ros-melodic-map-msgs
package:
# Build the project.
cmake ${srcdir}/${_dir} \
-DCMAKE_BUILD_TYPE=Release \
-DCATKIN_BUILD_BINARY_PACKAGE=ON \
-DCMAKE_INSTALL_PREFIX=/opt/ros/melodic \
-DPYTHON_EXECUTABLE=/usr/bin/python3 \
-DPYTHON_INCLUDE_DIR=/usr/include/python3.7m \
-DPYTHON_LIBRARY=/usr/lib/libpython3.7m.so \
-DPYTHON_BASENAME=.cpython-37m \
-DSETUPTOOLS_DEB_LAYOUT=OFF
make
Becomes
# Build the project.
cmake ${srcdir}/${_dir}/map_msgs \
-DCMAKE_BUILD_TYPE=Release \
-DCATKIN_BUILD_BINARY_PACKAGE=ON \
-DCMAKE_INSTALL_PREFIX=/opt/ros/melodic \
-DPYTHON_EXECUTABLE=/usr/bin/python3 \
-DPYTHON_INCLUDE_DIR=/usr/include/python3.7m \
-DPYTHON_LIBRARY=/usr/lib/libpython3.7m.so \
-DPYTHON_BASENAME=.cpython-37m \
-DSETUPTOOLS_DEB_LAYOUT=OFF
make
timonegk commented on 2018-09-08 11:42 (UTC) (edited on 2018-09-08 11:46 (UTC) by timonegk)
I think that it might be time to update the ros-melodic stack to python3.
Python2 end of life is in 2020 and Arch has used python3 as default since several years. For ROS Melodic, all packages should support python3 (see REP3).
I built every ros-melodic-* package in the AUR with python3 and all the packages were built successfully except of ros-melodic-tf2-py which was not yet python3.7 compatible. There is https://github.com/ros/geometry2/pull/320 which fixes the problem but is not yet released. I added a custom patch to the PKGBUILD to resolve the issue until the next release. I will add a comment to the corresponding package later. (EDIT: here)
To update all the PKGBUILD files to python3, you can use the following command (in a folder where every subfolder contains one of the packages):
sed -i -e "/fix-python-scripts.sh/s/-v 2/-v 3/" -e "s/python2.7/python3.7m/" -e "s/ python2/ python/" -e "s/python2/python3/g" */PKGBUILD
Explanation: The first expression fixes the version in the call of the fix-python-scripts editing the shebang line, the second expression fixes the library and include directories now ending with m, the third expression updates the package dependencies like python2-yaml -> python-yaml and the fourth expression updates the python binary from /usr/bin/python2 to /usr/bin/python3.
If you have further questions, feel free to ask or write an email.
LazyLucretia commented on 2018-06-28 11:51 (UTC)
Hello,
In latest version of this package, gazebo
fails to build as I stated here: https://aur.archlinux.org/packages/gazebo/#news One possible workaround is to downgrade ogre
to 1.10.10-3 and boost
/boost-libs
to 1.66.0-3. This lets Gazebo to build, but breaks ros-melodic-diff-drive-controller
's dependencies, along with many other packages that uses boost and ogre.
GPereira commented on 2018-06-22 19:36 (UTC)
before that:
Can you build ros-melodic-qt-gui-cpp? I am having trouble
GPereira commented on 2018-06-22 19:22 (UTC)
maybe a pastebin simplifies things:
GPereira commented on 2018-06-22 19:21 (UTC)
I put that information there (ROS Wiki) to inform that ROS packages are available in Arch Linux, I didn't mean to say it were binaries, it was just a cleaner way to display that info. I know it refers above "binary" but the installation tutorial then explains it. Do you wanna help create binary packages? I just need an automated script to do it :D can you do it for me? :D I have a folder with all ROS melodic packages it is just a matter of iterating through them all and modify automaticaly PKBUILD to install that package (without forgeting to replace the source to the package and not the git repository) and then a makepkg --printsrcinfo > .SRCINFO, then git add then commit and finaly push it :D What I have right now: for dir in $(find "$basedir" -mindepth 1 -maxdepth 1 -type d); do if test -d "$dir"; then cd $dir makepkg --printsrcinfo > .SRCINFO git add .SRCINFO PKGBUILD git commit -m "Update" git push cd .. fi done
Elephantusparvus commented on 2018-06-22 10:20 (UTC)
Hi,
First of all thank you for packaging this. According to the ros wiki (http://wiki.ros.org/melodic) there are binary packages available for Arch. Is this a "mistake" in the Documentation and these AUR packages are meant or are binary packages planned/available for Arch. The latter would be really awesome. If this is the wrong place to ask for this please ignore/delete this post.
Best regards
Pinned Comments