# Preparing for Indigo Sync 2016-12-21

**URL:** <https://discourse.openrobotics.org/t/preparing-for-indigo-sync-2016-12-21/1004>\
**Category:** Indigo\
**Created:** [December 22, 2016, 2:29am UTC](https://discourse.openrobotics.org/t/preparing-for-indigo-sync-2016-12-21/1004 "2016-12-22T02:29:55Z")\
**Posts on this page:** 3\
**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:** [December 22, 2016, 2:29am UTC](https://discourse.openrobotics.org/t/preparing-for-indigo-sync-2016-12-21/1004/1 "2016-12-22T02:29:55Z")

</div>

We successfully synced Jade and Kinetic last week. We held off on indigo since there was only ~30 packages ready and there was a regression in the jsk packages.

Since there we’ve added several releases and now have over 100 packages to sync. However we also have a few [more regressions](http://repositories.ros.org/status_page/ros_indigo_default.html?q=REGRESSION).

Many of the regressions are due to this issue:  
[https://github.com/ros-planning/moveit/issues/386#issuecomment-268689110](https://github.com/ros-planning/moveit/issues/386#issuecomment-268689110)

It would be great to get a sync out before the end of the year but I know that we’re looking at a lull in development as people will be travelling for the next week or two. So at the latest lets shoot for a new sync in the first week of January.

---

<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:** [December 29, 2016, 2:04am UTC](https://discourse.openrobotics.org/t/preparing-for-indigo-sync-2016-12-21/1004/2 "2016-12-29T02:04:33Z")

</div>

We’re close to no regressoins. We are down to 4 packages that are indicated as regressions. Of which 2 are failing to build and the other two are dependent on the failing packages.

I’ve ticketed the two failing packages:

[https://github.com/ros-industrial/universal\_robot/issues/274](https://github.com/ros-industrial/universal_robot/issues/274)

[https://github.com/auboliuxin/aubo\_robot/issues/5](https://github.com/auboliuxin/aubo_robot/issues/5)

However it appears that they might be a result of a moved or removed moveit header files. @130s I haven’t dug into this but it looks like both these failing builds were triggered by the recent moveit release; [http://build.ros.org/view/Ibin\_uS64/job/Ibin\_uS64\_\_ur\_kinematics\_\_ubuntu\_saucy\_amd64\_\_binary/34/](http://build.ros.org/view/Ibin_uS64/job/Ibin_uS64 __ur_kinematics__ ubuntu_saucy_amd64__binary/34/)  
[http://build.ros.org/view/Ibin\_uS64/job/Ibin\_uS64\_\_aubo\_kinematics\_\_ubuntu\_saucy\_amd64\_\_binary/19/](http://build.ros.org/view/Ibin_uS64/job/Ibin_uS64 __aubo_kinematics__ ubuntu_saucy_amd64__binary/19/)

Unless it sounds like there will be a fix in the next day or two I will likely still sync with the regressions since we have a large batch of packages that have been waiting longer than normal already.

If we do sync with the regressions and the fixes are in soon we can rerun the sync ahead of schedule to fix the regressions.

---

<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:** [January 3, 2017, 4:39am UTC](https://discourse.openrobotics.org/t/preparing-for-indigo-sync-2016-12-21/1004/3 "2017-01-03T04:39:09Z")

</div>

We have the fixed version of ur\_kinematics available now:

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

We had one regression which I’ve reverted so we can get a clean build:

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

Once the rebuild finishes, I expect we can get a sync out.