The installation fails because ros-humble-negotiated was not available as a prebuilt Debian package in the configured repositories. The message about held broken packages is the final APT dependency error; it does not establish that a held package caused the failure.
Trace the failing dependency chain
| Requested package | Required dependency | Observed result |
|---|---|---|
ros-humble-isaac-ros-visual-slam |
ros-humble-isaac-ros-nitros |
Dependency is not installed |
ros-humble-isaac-ros-nitros |
ros-humble-negotiated |
Dependency is not installable |
ros-humble-negotiated |
Prebuilt package from a configured repository | No installation candidate |
The decisive error is Package 'ros-humble-negotiated' has no installation candidate. Resolve that missing package before troubleshooting the higher-level Isaac ROS packages.
Understand why APT updates do not resolve it
ros-humble-negotiated had not been submitted to the Open Robotics BuildFarm and did not yet exist as a prebuilt Debian package. Consequently, refreshing repository metadata cannot create an installation candidate that the repositories do not publish.
ros-humble-isaac-ros-visual-slam
└── ros-humble-isaac-ros-nitros
└── ros-humble-negotiated [no prebuilt Debian candidate]This explains why both sudo apt update and rosdep update leave the installation blocked.
Select the supported decision path
- Confirm that direct installation of
ros-humble-negotiatedstill reports no installation candidate. - If using the Isaac ROS Dev base image is acceptable, use the package built from source there.
- For a native Jetson OS installation without Docker, build the missing package from source before retrying the dependent packages. The evidence does not provide a repository, branch, or build procedure, so obtain those exact inputs from current NVIDIA Isaac ROS documentation or an official NVIDIA support channel rather than guessing them.
- If a source build is not acceptable, wait until the package is published through the NVIDIA ROS 2 Buildfarm and verify its availability with APT before retrying the installation.
Verify the Jetson installation
The reported platform is a Jetson Orin Nano 8GB devkit running an aarch64 R35 release with revision 4.1. After supplying ros-humble-negotiated by a supported source build or repository package, retry installation in dependency order: negotiated, Isaac ROS NITROS, then Isaac ROS Visual SLAM. Successful dependency resolution verifies package installation only; runtime Visual SLAM validation requires separate launch and sensor checks not supplied in the evidence.
FAQ
Why does ros-humble-negotiated have no installation candidate?
It was not available as a prebuilt Debian package and had not been submitted to the Open Robotics BuildFarm. APT therefore had no repository candidate to install.
Will sudo apt update or rosdep update fix ros-humble-negotiated?
No. Updating metadata does not help while no configured repository publishes ros-humble-negotiated.
How can I install Isaac ROS Visual SLAM on Jetson without Docker?
Build the missing ros-humble-negotiated dependency from source using current official NVIDIA instructions, then install ros-humble-isaac-ros-nitros and ros-humble-isaac-ros-visual-slam. No bare-metal source repository or build commands are provided in the evidence.
