I’m preparing to do another Melodic sync soon since there are a large number of packages to be released, and Autoware.ai has requested a release to make carla_msgs available.
Currently Melodic has two known regressions and 141 packages ready to sync. I plan on holding packages starting tomorrow, March 13, with a sync next week. The only exception will be fixes for the regression.
Please comment here if there are any outstanding issues I should know about before performing the sync.
Hi @clalancette – my ifm3d_core package was synced into Kinetic for the first time last week. Unfortunately I discovered that my dependency on OpenCV via the libopencv-dev package has some problems on Kinetic (due to OpenCV2 on xenial vs OpenCV3 in kinetic) and that the correct way to depend on OpenCV is via the cv_bridge package.
FWIW, the last sync of this package failed to compile due to user error, so nobody has it yet. Might be a good time to pull this fix in to avoid issues later?
It looks like the last binary build succeeded on Melodic: http://build.ros.org/job/Mbin_uB64__ifm3d_core__ubuntu_bionic_amd64__binary/ . However, you are right that it hasn’t been included in any official sync yet. So I’ll merge your PR, but just be aware that if it fails, I won’t hold up the sync for another fix.
I’m not sure if the sync is the actual cause, but after I apt-get upgrade, build of some packages fails in my environment.
The problem occurs when a package with parameter files for dynamic_reconfigure (e.g. compressed_image_transport) is already installed via apt-get and also is located on catkin workspace and there is difference between parameter files of the packages.
It looks like g++ looks at header files generated from dynamic reconfigure params on /opt/ros/melodic instead of the current catkin workspace.
I further looked into build logs and found that devel directory is passed to compiler using -isystem instead of -I.
@furushchev Thanks for the detailed analysis. There were updates to catkin, ros, ros_comm, and some other low-level packages for this sync, so I suspect that is the issue. I’d suggest opening an issue against catkin to follow-up with this; we can always move the issue around if it turns out to be in another component.
FYI, looks like this is one of two issues with the version of dynamic_reconfigure that got released (1.6.1-1bionic.20200306.144628). See also #150. Until another sync is possible, I suppose the workaround is to build dynamic_reconfigure from source?
Thank you very much for the quick response and releasing the fix!
I confirmed the issue was resolved after upgrading to the latest release version in my environment.