[ros-users] [Discourse.ros.org] [Packaging and Release Management/Kinetic] Preparing for Kinetic Sync 2017-11-29

[Tully Foote]

With our extended sync this cycle we have [over 300 packages queued to sync](http://repositories.ros.org/status_page/ros_kinetic_default.html?q=SYNC). However we have a [couple of regressions](http://repositories.ros.org/status_page/ros_kinetic_default.html?q=REGRESSION) at the moment.

I'd like to target the sync for the end of this week. 

## General regressions

The two regressions are below. Both appear to possibly be side effects of changes to upstream packages.

https://github.com/stonier/cost_map/issues/45

@stonier  @pfankhauser This looks like it might be an API change in [grid_map](https://github.com/ethz-asl/grid_map). 

https://github.com/srv/srv_tools/issues/17

@miquelmassot @Vincent_Rabaud This might be related to the opencv3 update.  

These are causing regressions in 8 packages within the same repos as the tickets.  It would be great to resolve these before we sync however I don't currently plan to hold the sync beyond the end of this week since we have such a large update for these. 

## Jessie specific

In this cycle we have recently resolved that rosjava will not be supported on Debian Jessie as it's OpenJDK does not have newenough SSL certificates. 

Tracking issue:

https://github.com/rosjava/rosjava_bootstrap/issues/61

This brings up the consideration that this is one of many things that Jessie is now falling behind on and is making things harder for maintainers to support. As Jessie is not one of our mainline targets we can consider making it EOL since it's not one of our LTS targets. How do others feel about this?

Otherwise we'll plan to sync before the end of the week. If there are any other issues you'd like to see reviewed please reply here.





---
[Visit Topic](https://discourse.ros.org/t/preparing-for-kinetic-sync-2017-11-29/3275/1) or reply to this email to respond.