New packages for ROS 2 Rolling Ridley 2020-06-30

Packaging and Release Management Rolling
,
1

Package Updates for rolling

dbgsym packages are filtered from output but are still reflected in counts.

Added Packages [1]:

  • ros-rolling-rcl-logging-interface: 2.0.0-1

Updated Packages [89]:

  • ros-rolling-action-msgs: 1.0.0-2 -> 1.0.1-1
  • ros-rolling-ament-cmake: 0.9.5-3 -> 0.9.6-1
  • ros-rolling-ament-cmake-auto: 0.9.5-3 -> 0.9.6-1
  • ros-rolling-ament-cmake-core: 0.9.5-3 -> 0.9.6-1
  • ros-rolling-ament-cmake-export-definitions: 0.9.5-3 -> 0.9.6-1
  • ros-rolling-ament-cmake-export-dependencies: 0.9.5-3 -> 0.9.6-1
  • ros-rolling-ament-cmake-export-include-directories: 0.9.5-3 -> 0.9.6-1
  • ros-rolling-ament-cmake-export-interfaces: 0.9.5-3 -> 0.9.6-1
  • ros-rolling-ament-cmake-export-libraries: 0.9.5-3 -> 0.9.6-1
  • ros-rolling-ament-cmake-export-link-flags: 0.9.5-3 -> 0.9.6-1
  • ros-rolling-ament-cmake-export-targets: 0.9.5-3 -> 0.9.6-1
  • ros-rolling-ament-cmake-gmock: 0.9.5-3 -> 0.9.6-1
  • ros-rolling-ament-cmake-gtest: 0.9.5-3 -> 0.9.6-1
  • ros-rolling-ament-cmake-include-directories: 0.9.5-3 -> 0.9.6-1
  • ros-rolling-ament-cmake-libraries: 0.9.5-3 -> 0.9.6-1
  • ros-rolling-ament-cmake-nose: 0.9.5-3 -> 0.9.6-1
  • ros-rolling-ament-cmake-pytest: 0.9.5-3 -> 0.9.6-1
  • ros-rolling-ament-cmake-python: 0.9.5-3 -> 0.9.6-1
  • ros-rolling-ament-cmake-target-dependencies: 0.9.5-3 -> 0.9.6-1
  • ros-rolling-ament-cmake-test: 0.9.5-3 -> 0.9.6-1
  • ros-rolling-ament-cmake-version: 0.9.5-3 -> 0.9.6-1
  • ros-rolling-builtin-interfaces: 1.0.0-2 -> 1.0.1-1
  • ros-rolling-composition-interfaces: 1.0.0-2 -> 1.0.1-1
  • ros-rolling-interactive-markers: 2.1.1-2 -> 2.1.2-1
  • ros-rolling-lifecycle-msgs: 1.0.0-2 -> 1.0.1-1
  • ros-rolling-rcl: 1.1.5-2 -> 1.2.0-1
  • ros-rolling-rcl-action: 1.1.5-2 -> 1.2.0-1
  • ros-rolling-rcl-interfaces: 1.0.0-2 -> 1.0.1-1
  • ros-rolling-rcl-lifecycle: 1.1.5-2 -> 1.2.0-1
  • ros-rolling-rcl-logging-log4cxx: 1.0.0-2 -> 2.0.0-1
  • ros-rolling-rcl-logging-noop: 1.0.0-2 -> 2.0.0-1
  • ros-rolling-rcl-logging-spdlog: 1.0.0-2 -> 2.0.0-1
  • ros-rolling-rcl-yaml-param-parser: 1.1.5-2 -> 1.2.0-1
  • ros-rolling-rclcpp: 2.0.0-2 -> 3.0.0-1
  • ros-rolling-rclcpp-action: 2.0.0-2 -> 3.0.0-1
  • ros-rolling-rclcpp-components: 2.0.0-2 -> 3.0.0-1
  • ros-rolling-rclcpp-lifecycle: 2.0.0-2 -> 3.0.0-1
  • ros-rolling-rclpy: 1.0.2-2 -> 1.1.0-1
  • ros-rolling-rcpputils: 1.0.1-2 -> 1.2.0-1
  • ros-rolling-rcutils: 1.0.1-2 -> 1.1.0-1
  • ros-rolling-rmw: 1.0.1-2 -> 1.1.0-2
  • ros-rolling-rmw-connext-cpp: 1.0.0-2 -> 1.1.0-1
  • ros-rolling-rmw-connext-shared-cpp: 1.0.0-2 -> 1.1.0-1
  • ros-rolling-rmw-cyclonedds-cpp: 0.7.1-2 -> 0.8.1-1
  • ros-rolling-rmw-implementation-cmake: 1.0.1-2 -> 1.1.0-2
  • ros-rolling-ros-environment: 2.5.0-2 -> 3.0.0-1
  • ros-rolling-rosgraph-msgs: 1.0.0-2 -> 1.0.1-1
  • ros-rolling-rviz-assimp-vendor: 8.1.1-2 -> 8.2.0-1
  • ros-rolling-rviz-common: 8.1.1-2 -> 8.2.0-1
  • ros-rolling-rviz-default-plugins: 8.1.1-2 -> 8.2.0-1
  • ros-rolling-rviz-ogre-vendor: 8.1.1-2 -> 8.2.0-1
  • ros-rolling-rviz-rendering: 8.1.1-2 -> 8.2.0-1
  • ros-rolling-rviz-rendering-tests: 8.1.1-2 -> 8.2.0-1
  • ros-rolling-rviz-visual-testing-framework: 8.1.1-2 -> 8.2.0-1
  • ros-rolling-rviz2: 8.1.1-2 -> 8.2.0-1
  • ros-rolling-statistics-msgs: 1.0.0-2 -> 1.0.1-1
  • ros-rolling-test-msgs: 1.0.0-2 -> 1.0.1-1

Removed Packages [0]:

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:

  • Amazon B9
  • Anup Pemmaiah
  • Chris Lalancette
  • Dirk Thomas
  • Emerson Knapp
  • Erik Boasson
  • Jacob Perron
  • Karsten Knese
  • Michael Carroll
  • ROS Tooling Working Group
  • Scott K Logan
  • Shane Loretz
  • Tully Foote
  • William Woodall
1 Like
2

@nuclearsandwich it looks like these packages didn’t get uploaded to packages.ros.org.
The issue seems to come from the fact that the http://build.ros2.org/job/Rrel_sync-packages-to-main/ job is missing a downstream job configuration to trigger upload_main (a similar tweak would be needed for the sync-packages-to-testing to trigger upload_testing).

@ruffsl FYI

1 Like
3

Wow you’re right. I was away from my computer with a token for redeploying the upload job and ran an upload manually… apparently on the wrong build farm cluster. upload_main #90 [Jenkins] has now run and when I get online proper today I’ll fix the job triggers.

4

Awesome, thanks for the quick update