New packages for Foxy Fitzroy 2020-09-25

We’re happy to announce new packages and updates for Foxy Fitzroy!

Package Updates for foxy

Added Packages [25]:

Updated Packages [54]:

Removed Packages [2]:

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:

  • AutonomouStuff Software Development Team
  • AutonomouStuff Software Team
  • Christophe Bedard
  • Cyberbotics
  • Daniel Stonier
  • Detullah Atas
  • Dirk Thomas
  • Dorian Scholz
  • Felix Ruess
  • Hunter L. Allen
  • Jeffrey Kane Johnson
  • Olivier Stasse
  • ROS Security Working Group
2 Likes

Why are all the links for chiconybot dead? Should those packages be removed if the git-repo/docs/wiki for it have all been taken down? This isn’t very transparent.

So we did actually remove the package from the index in foxy: drop ros_cb by shr-project · Pull Request #26663 · ros/rosdistro · GitHub . However, it still somehow got into the sync. I’m not entirely sure how that happened; we’ll have to look at it on the ROS buildfarm scripts.

1 Like

Even in a recent sync to testing, the chiconybot packages are still there: http://build.ros2.org/job/Frel_sync-packages-to-testing_focal_amd64/300

I would have expected them to be removed.

Removing a package is a rare event in our rosdistro maintenance and it will be eventually consistent but does not currently actively clean up packages.

As a quick summary of the state. The apt repository (building) does not have an active cleaning process. The packages will persist until a dependency is released invalidates them. Because this was released and rolled back and nothing in depends on has been released since then, the package is still considered valid in the repository as released and synced to testing and then main each cycle.

The packages will go away the next time one of their dependencies is released. Otherwise they can be manually removed from the building repository and then they will be removed by the next syncs to testing and main successively.