Revision history [back]

I think you ran into ros_comm#703. This was also mentioned by William in his post to ros-users (Re: [ros-users] New packages for Indigo and Jade):

I wanted to let everyone know about an ABI break between roscpp 1.11.13 and 1.11.16 (applies for indigo and jade). Thanks to Jonathan Binney for finding and raising the issue with us: https://github.com/ros/ros_comm/issues/703

That this is not normally something that should happen is also acknowledged by William:

It's generally not our intention to introduce breaking ABI in our core packages, but it does happen from time to time. At this pointing fixing the ABI breakage would cause another ABI breakage for people who have already upgraded, so we're not going to take any action other than to notify people of the problem.

However, there is currently no ABI compatibility guarantee for any of the OSRF distributed packages (no hard guarantee, but it is something that is taken very seriously):

We have long had plans to integrate ABI checking to our build farm in a general way, but there are several technical hurdles that we need to get over before that's possible. Short of a general solution, we could manually add it for a few core packages, and we may do that to avoid issues like this in the future. [..]

See [proposal] Versioning ROS libraries ABI (long) in ros-sig-buildsystem for an earlier discussion about this subject.

I think you ran into ros_comm#703. This was also mentioned by William in his post to ros-users (Re: [ros-users] New packages for Indigo and Jade):, 2015-11-20):

I wanted to let everyone know about an ABI break between roscpp 1.11.13 and 1.11.16 (applies for indigo and jade). Thanks to Jonathan Binney for finding and raising the issue with us: https://github.com/ros/ros_comm/issues/703

That this is not normally something that should happen is also acknowledged by William:

It's generally not our intention to introduce breaking ABI in our core packages, but it does happen from time to time. At this pointing fixing the ABI breakage would cause another ABI breakage for people who have already upgraded, so we're not going to take any action other than to notify people of the problem.

However, there is currently no ABI compatibility guarantee for any of the OSRF distributed packages (no hard guarantee, but it is something that is taken very seriously):

We have long had plans to integrate ABI checking to our build farm in a general way, but there are several technical hurdles that we need to get over before that's possible. Short of a general solution, we could manually add it for a few core packages, and we may do that to avoid issues like this in the future. [..]

See [proposal] Versioning ROS libraries ABI (long) in ros-sig-buildsystem for an earlier discussion about this subject.

I think you ran into ros_comm#703. This was mentioned by William @William in his post to ros-users (Re: [ros-users] New packages for Indigo and Jade, 2015-11-20):

I wanted to let everyone know about an ABI break between roscpp 1.11.13 and 1.11.16 (applies for indigo and jade). Thanks to Jonathan Binney for finding and raising the issue with us: https://github.com/ros/ros_comm/issues/703

That this is not normally something that should happen is also acknowledged by William:@William:

It's generally not our intention to introduce breaking ABI in our core packages, but it does happen from time to time. At this pointing fixing the ABI breakage would cause another ABI breakage for people who have already upgraded, so we're not going to take any action other than to notify people of the problem.

However, afaik there is currently no ABI compatibility guarantee for any of the OSRF distributed packages (no hard guarantee, but it is something that is taken very seriously):

We have long had plans to integrate ABI checking to our build farm in a general way, but there are several technical hurdles that we need to get over before that's possible. Short of a general solution, we could manually add it for a few core packages, and we may do that to avoid issues like this in the future. [..]

See [proposal] Versioning ROS libraries ABI (long) in ros-sig-buildsystem for an earlier discussion about this subject.