# Preparing for Kinetic Sync 2018-06-06

**URL:** <https://discourse.openrobotics.org/t/preparing-for-kinetic-sync-2018-06-06/5034>\
**Category:** Kinetic\
**Created:** [June 6, 2018, 3:51pm UTC](https://discourse.openrobotics.org/t/preparing-for-kinetic-sync-2018-06-06/5034 "2018-06-06T15:51:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![tfoote](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/tfoote/32/3813_2.png) [@tfoote](https://discourse.openrobotics.org/u/tfoote)\
**Post date:** [June 6, 2018, 3:51pm UTC](https://discourse.openrobotics.org/t/preparing-for-kinetic-sync-2018-06-06/5034/1 "2018-06-06T15:51:26Z")

</div>

Thank you to all the maintainers who have been patient while we’ve been debugging ramifications of Meltdown and Spectre on the buildfarm. We have seen performance degredation

[https://github.com/ros-infrastructure/ros\_buildfarm/issues/535](https://github.com/ros-infrastructure/ros_buildfarm/issues/535)

But the fix exposed a worse problem than the performance problems.

[https://github.com/ros-infrastructure/buildfarm\_deployment/issues/204](https://github.com/ros-infrastructure/buildfarm_deployment/issues/204)

We’ve gotten the farm back into a good state with over 200 packages to sync.

However it looks like there’s one remaining regression blocking [8 packages](http://repositories.ros.org/status_page/ros_kinetic_default.html?q=REGRESSION) I’ve ticketed the issue.

[https://github.com/mrpt-ros-pkg/mrpt\_navigation/issues/101](https://github.com/mrpt-ros-pkg/mrpt_navigation/issues/101)

However since the issue appears to be isolated to a specific projects packages I’m not planning to hold the release

I will plan to sync tomorrow, Thursday. If there’s any unknown issue please reply here.

---

<div class="post-metadata">

**Author:** ![tfoote](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/tfoote/32/3813_2.png) [@tfoote](https://discourse.openrobotics.org/u/tfoote)\
**Post date:** [June 6, 2018, 10:16pm UTC](https://discourse.openrobotics.org/t/preparing-for-kinetic-sync-2018-06-06/5034/2 "2018-06-06T22:16:15Z")

</div>

Also note that this will be the last sync which will include Jessie packages.

Debian Jessie is [officially EOL as of today](https://wiki.debian.org/DebianReleases) so we’re going to turn off generating new packages for it.

[https://github.com/ros-infrastructure/ros\_buildfarm\_config/pull/118](https://github.com/ros-infrastructure/ros_buildfarm_config/pull/118)

If there are any issues with that please reply here. We plan to hold that merge until immediately after this sync.

---

<div class="post-metadata">

**Author:** ![tfoote](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/tfoote/32/3813_2.png) [@tfoote](https://discourse.openrobotics.org/u/tfoote)\
**Post date:** [June 7, 2018, 1:17am UTC](https://discourse.openrobotics.org/t/preparing-for-kinetic-sync-2018-06-06/5034/3 "2018-06-07T01:17:16Z")

</div>

In reviewing the current build status I identified one other small regression of a single package on Jessie only. It’s ticketed here:

[https://github.com/ENSTABretagneRobotics/sbg\_ros\_driver/issues/6](https://github.com/ENSTABretagneRobotics/sbg_ros_driver/issues/6)

And there’s a fix in for mrpt1 that will hopefully restore the build once it cycles through.

[https://github.com/ros/rosdistro/pull/18140](https://github.com/ros/rosdistro/pull/18140)

---

<div class="post-metadata">

**Author:** ![tfoote](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/tfoote/32/3813_2.png) [@tfoote](https://discourse.openrobotics.org/u/tfoote)\
**Post date:** [June 7, 2018, 6:40pm UTC](https://discourse.openrobotics.org/t/preparing-for-kinetic-sync-2018-06-06/5034/4 "2018-06-07T18:40:46Z")

</div>

The Kinetic sync is out and was announced here: [New Packages for Kinetic 2018-06-07 - ROS General - Open Robotics Discourse](http://discourse.ros.org/t/new-packages-for-kinetic-2018-06-07/5049)

The mrpt1 fix didn’t resolve the issues so I’ve gone ahead and synced with it still regressing. I hope it will get back into testing shortly and we can restore it in the next sync.