The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
This likely seems to be caused by only partially following the instructions of REP 136. Will come back with the outcome after carefully following that REP.
| | 2 | No.2 Revision |
This likely seems to be caused by only partially following the instructions of REP 136. Will come back with the outcome after carefully following that REP.
Update 10th May'18: It turned out complying with REP 136 is not enough to avoid the shlibdeps errors.
| | 3 | No.3 Revision |
This likely seems to be caused by only partially following the instructions of REP 136. Will come back with the outcome after carefully following that REP.
Update 10th May'18: It turned out complying with REP 136 is not enough to avoid the shlibdeps errors.errors. Here is the log of the newer build in the farm: log
| | 4 | No.4 Revision |
This likely seems (likely seems)-->seemed to be caused by only partially following the instructions of REP 136. Will come back with the outcome after carefully following that REP.
Update 10th May'18: It turned out complying with REP 136 is not enough to avoid the shlibdeps errors. Here is the log of the newer build in the farm: log
| | 5 | No.5 Revision |
This (likely seems)-->seemed to be caused by only partially following the instructions of REP 136. Will come back with the outcome after carefully following that REP.
Update 10th May'18: It turned out complying with REP 136 is not enough to avoid the shlibdeps errors. Here is the log of the newer build in the farm: log
Update 12th May'18: Manually following these instructions to manually build the .deb packages just work as expected without any error (!!).
| | 6 | No.6 Revision |
This (likely seems)-->seemed to be caused by only partially following the instructions of REP 136. Will come back with the outcome after carefully following that REP.
Update 10th May'18: It turned out complying with REP 136 is not enough to avoid the shlibdeps errors. Here is the log of the newer build in the farm: log
Update 12th May'18: Manually following Following these instructions to manually build the .deb packages just work works as expected without any error (!!).
| | 7 | No.7 Revision |
This (likely seems)-->seemed to be caused by only partially following the instructions of REP 136. Will come back with the outcome after carefully following that REP.
Update 10th May'18: It turned out complying with REP 136 is not enough to avoid the shlibdeps errors. Here is the log of the newer build in the farm: log
Update 12th May'18: Following these instructions to manually build the .deb packages just works as expected without any error (!!).
Furthermore, downloading the .dsc and building from sources also works:
dget http://repositories.ros.org/ubuntu/building/pool/main/r/ros-kinetic-mrpt1/ros-kinetic-mrpt1_1.5.7-0xenial.dsc
dpkg-source -x ros-kinetic-mrpt1_1.5.7-0xenial.dsc
cd ros-kinetic-mrpt1-1.5.7
dpkg-buildpackage
...
dpkg-deb: building package 'ros-kinetic-mrpt1' in '../ros-kinetic-mrpt1_1.5.7-0xenial_amd64.deb'.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.