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 |
libcurlpp-dev is not packaged for buster.
Looking here: https://packages.debian.org/sid/libcurlpp-dev it's only on bullseye bookworm and sid
You can compare that to libcurl-dev which is available on all platforms: https://packages.debian.org/sid/libcurl4-dev
The rosdep key should be updated to state that the resolution is valid for wildcard, but null for stretch, buster to be completely accurate. With this inaccuracy bloom filled in an invalid package. And that is why the build is failing. If the rosdep key was more complete bloom would have failed at an earlier stage and you could have skipped buster generation.
| | 2 | No.2 Revision |
libcurlpp-dev is not packaged for buster.
Looking here: https://packages.debian.org/sid/libcurlpp-dev it's only on bullseye bookworm and sid
You can compare that to libcurl-dev which is available on all platforms: https://packages.debian.org/sid/libcurl4-dev
The rosdep key should be updated to state that the resolution is valid for wildcard, but null for stretch, buster to be completely accurate. With this inaccuracy bloom filled in an invalid package. And that is why the build is failing. If the rosdep key was more complete bloom would have failed at an earlier stage and you could have skipped buster generation. If this is a necessary dependency blacklistingit for buster as suggested by @gvdhoorn is likely the best solution. Also a fix for the rosdep key would be appreciated.
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.
