wstool init fails on ros_comm/rosbag_storage when building Melodic [closed]
When I attempt to follow the instructions to build Melodic from source, the wstool init
command fails every time with this error:
Exception caught during install: Error processing 'ros_comm/rosbag_storage' : [ros_comm/rosbag_storage] Checkout of https://github.com/ros-gbp/ros_comm-release/archive/release/melodic/rosbag_storage/1.14.3-0.tar.gz version ros_comm-release-release-melodic-rosbag_storage-1.14.3-0 into /home/chrisl8/ros_catkin_ws/src/ros_comm/rosbag_storage failed.
Error processing 'ros_comm/rosgraph' : [ros_comm/rosgraph] Checkout of https://github.com/ros-gbp/ros_comm-release/archive/release/melodic/rosgraph/1.14.3-0.tar.gz version ros_comm-release-release-melodic-rosgraph-1.14.3-0 into /home/chrisl8/ros_catkin_ws/src/ros_comm/rosgraph failed.
ERROR in config: Error processing 'ros_comm/rosbag_storage' : [ros_comm/rosbag_storage] Checkout of https://github.com/ros-gbp/ros_comm-release/archive/release/melodic/rosbag_storage/1.14.3-0.tar.gz version ros_comm-release-release-melodic-rosbag_storage-1.14.3-0 into /home/chrisl8/ros_catkin_ws/src/ros_comm/rosbag_storage failed.
Error processing 'ros_comm/rosgraph' : [ros_comm/rosgraph] Checkout of https://github.com/ros-gbp/ros_comm-release/archive/release/melodic/rosgraph/1.14.3-0.tar.gz version ros_comm-release-release-melodic-rosgraph-1.14.3-0 into /home/chrisl8/ros_catkin_ws/src/ros_comm/rosgraph failed.
Update:
As pointed out in the comments, this seems to be the same issue as http://answers.ros.org/question/314827/
Running these lines AFTER rosinstall_generator
but BEFORE wstool
allowed me to finish the process:
sed -i 's/version: \(ros_comm-release-release-melodic-ros_comm\)-[0-9\.\-]\+/version: \1/g' melodic-desktop-full.rosinstall
sed -i 's/version: \(ros_comm-release-release-melodic-rosbag_storage\)-[0-9\.\-]\+/version: \1/g' melodic-desktop-full.rosinstall
sed -i 's/version: \(ros_comm-release-release-melodic-rosgraph\)-[0-9\.\-]\+/version: \1/g' melodic-desktop-full.rosinstall
That doesn't really solve the root cause, but at least I can build the source now.
UPDATE:
A github issue has been opened against wstools:
Errors extracting tarballs from github (recent change?) #130
I believe you could be running into the same problem as the OP of #q314827.
Yes @gvdhoorn That does seem to be the issue, and that gave me a clue about how to at least get past the issue, if not solve it.
For new people to this topic, I have proposed this fix.
@KenYN could you please point to how to use your fix? Should I clone your fork and run setup.py?
@RickOMello The quickest way is
sudo pip install --upgrade https://github.com/KenYN/vcstools/archive/v0.1.40-tar-fix.zip
for a global install or this for a local install.@KenYN thank you!
Please note: using
sudo pip install ..
installs the replacementvcstools
into/usr/local
and IIRC that location will always be searched first when looking forvcstools
scripts. This, combined with the fact that the/usr/local
install will not be automatically upgraded can lead .... to some interesting situations in the future, when the official
vcstools
sees new releases, but those are never actually used on machines that have/usr/local
installs.