Error cloning repository during create_firmware_ws.sh

Dieses Issue hat noch niemand übernommen.

- Hardware description: esp32 or olimex-stm32-e407
- RTOS: FreeRTOS
- Installation type: -
- Version or commit hash: humble
- Im working on Ubuntu 22.04 with ROS2 Humble.

#### Steps to reproduce the issue

I followed the "First micro-ROS Application on FreeRTOS" tutorial until $ ros2 run micro_ros_setup create_firmware_ws.sh freertos olimex-stm32-e407

where i face this error:
$ ros2 run micro_ros_setup create_firmware_ws.sh freertos olimex-stm32-e407
Creating firmware for freertos platform olimex-stm32-e407
/usr/bin/vcs:6: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
from pkg_resources import load_entry_point
.......
=== ./ament/ament_cmake (git) ===
Cloning in '.'...
=== ./ament/ament_index (git) ===
Cloning in '.'...
=== ./ament/ament_lint (git) ===
Cloning in '.'...
=== ./ament/ament_package (git) ===
Cloning in '.'...
=== ./ament/googletest (git) ===
Cloning in '.'...
=== ./ament/uncrustify_vendor (git) ===
Cloning in '.'...
=== ./ros2/ament_cmake_ros (git) ===
Cloning in '.'...
/usr/bin/vcs:6: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
from pkg_resources import load_entry_point
List of repositories is empty
#All required rosdeps installed successfully
/usr/bin/vcs:6: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
from pkg_resources import load_entry_point
..............
=== ./ros2/common_interfaces (git) ===
Cloning in '.'...
=== ./ros2/example_interfaces (git) ===
Cloning in '.'...
=== ./ros2/libyaml_vendor (git) ===
Cloning in '.'...
=== ./ros2/rcl (git) ===
Cloning in '.'...
=== ./ros2/rcl_interfaces (git) ===
Cloning in '.'...
=== ./ros2/rcl_logging (git) ===
Cloning in '.'...
=== ./ros2/rcpputils (git) ===
Cloning in '.'...
=== ./ros2/rmw (git) ===
Cloning in '.'...
=== ./ros2/rmw_implementation (git) ===
Cloning in '.'...
=== ./ros2/rosidl (git) ===
Cloning in '.'...
=== ./ros2/rosidl_dds (git) ===
Cloning in '.'...
=== ./ros2/rosidl_defaults (git) ===
Cloning in '.'...
=== ./ros2/test_interface_files (git) ===
Cloning in '.'...
=== ./ros2/unique_identifier_msgs (git) ===
Cloning in '.'...
/usr/bin/vcs:6: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
from pkg_resources import load_entry_point
.........E.
=== ./eProsima/Micro-CDR (git) ===
Cloning in '.'...
=== ./eProsima/Micro-XRCE-DDS-Client (git) ===
Cloning in '.'...
=== ./uros/micro_ros_msgs (git) ===
Cloning in '.'...
=== ./uros/micro_ros_utilities (git) ===
Cloning in '.'...
=== ./uros/rcl (git) ===
Cloning in '.'...
=== ./uros/rclc (git) ===
Cloning in '.'...
=== ./uros/rcutils (git) ===
Cloning in '.'...
=== ./uros/rmw_microxrcedds (git) ===
Cloning in '.'...
=== ./uros/rosidl_typesupport (git) ===
Cloning in '.'...
=== ./uros/rosidl_typesupport_microxrcedds (git) ===
Cloning in '.'...
=== ./uros/tracetools (git) ===
Could not determine ref type of version: remote:
remote: ========================================================================
remote:
remote: ERROR: The namespace you were looking for could not be found.

remote:
remote: ========================================================================
remote:
fatal: Could not read from remote repository.

Please make sure you have the correct access permissions
and that the repository exists.
[ros2run]: Process exited with failure 1
[ros2run]: Process exited with failure 1

#### Additional information

Same error doing: $ ros2 run micro_ros_setup create_firmware_ws.sh freertos esp32

Seems could not find tracetools package, dont know why...

Thanks in advance!

Beginnen Sie mit create_firmware_ws.sh und reproduzieren Sie den Befehl sowohl für olimex-stm32-e407 als auch für esp32. Untersuchen Sie, wie der Firmware-Workspace das uros/tracetools-Repository und seine Version auswählt, und überprüfen Sie anschließend, dass der konfigurierte Remote vorhanden ist und das Klonen ohne den angezeigten Ref- oder Berechtigungsfehler abgeschlossen wird.

Vom Indexierungsmodell aus dem Issue-Text verfasst.