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 |
According to packages.debian.org, python-pycryptodome is available starting in stretch-backports, and fully in buster. In Ubuntu it's available starting with bionic (here).
Debian 9.12 would be Stretch. So it should at least be available in the backports repository.
If you don't want to use that, you could append --skip-keys="python-pycryptodome" to the rosdep invocation.
| | 2 | No.2 Revision |
According to packages.debian.org, python-pycryptodome is available starting in stretch-backports, and fully in buster. In Ubuntu it's available starting with bionic (here).
Debian 9.12 would be Stretch. So it should at least be available in the backports repository.
If you don't want to use that, you could append --skip-keys="python-pycryptodome" to the rosdep invocation.
Edit: I just checked, and it seems ros/rosdistro#22011 added pycryptodome to the rosdep DB. @Dirk Thomas comments there:
On Debian Stretch the package is only available when using
stretch-backports: [..]
and:
We imported the package for Debian Stretch from the backports repo into the ROS repos: ros-infrastructure/reprepro-updater#69.
This seems to imply that if:
packages.ros.org configured as an apt repository on your system, andyou should be able to resolve the python-pycryptodome dependency using apt.
Do you have the ROS repositories configured? What is the output of apt-cache policy python-pycryptodome?
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.