I'm having some trouble recreating the issue (I'm tracking it here ). I've created a 64 bit Quantal VM, set the debian source to shadow-fixed, and installed arm_navigation (sudo apt-get install ros-groovy-arm-navigation). I then check out arm_navigation_experimental from github (the wiki indicates that arm_navigation is still on kforge, not sure how this is still working). move_arm_warehouse builds without any problems. The rebuild was triggered by changes to catkin here . I'm simply using rosmake to build. Is there a way to better mimic what is happening on the build server (something including the changes made to catkin?). Any help/thoughts are appreciated, Shaun On Tue, Aug 26, 2014 at 2:02 PM, William Woodall wrote: > With just a brief glance, it sounds like this might be related: > > https://github.com/ros-visualization/rviz/pull/589 > > Then again maybe not. > > > On Tue, Aug 26, 2014 at 9:12 AM, Shaun Edwards > wrote: > >> All, >> >> It looks like several packages(ROS-I, PR2, and others) are held on >> Quantal due to a failure in arm-navigation-experimental. I'm working on >> tracking down the issue. The build logs complain about a parser issue on >> BOOST:JOIN. I found this helpful link: >> http://stackoverflow.com/questions/15455178/qt4-cgal-parse-error-at-boost-join. >> It appears to be a bug in QT, that has been fixed, but maybe not on >> Quantal? I'm quickly getting out of my element, so I figured I'd see if >> anybody else already tackled this problem. >> >> Shaun >> >> >> On Mon, Aug 25, 2014 at 7:04 PM, Tully Foote >> wrote: >> >>> Hi Everyone, >>> >>> With Indigo Igloo released, and as we prepare to setup the >>> infrastructure for Jade Turtle, Groovy Galapagos has now reached it’s >>> End-of-Life. We are looking at turning the groovy jobs off on the >>> buildfarm in the near future, after which the groovy packages will still be >>> available, however we will no longer be able to build updated packages or >>> documentation. As such I’d like to suggest that groovy maintainers take a >>> few minutes and verify that documentation and packages for groovy are >>> stable and if there’s anything outstanding which should be taken care of, >>> that the groovy maintainers do so now. >>> >>> There are almost 100 updated packages queued for release which we would >>> like to get out. However there are several packages currently regressing >>> on the groovy debbuild status page. [1] >>> >>> We will plan to release groovy a week from Friday, September 3rd, with >>> as many update to packages as possible. After which we will freeze new >>> releases into groovy. As with any releases there is a chance of >>> regression. So we will keep the buildfarm operational for the remainder of >>> September, but only accept regression patch fixes. After which all groovy >>> jobs will be turned off. >>> >>> If you have any feedback, questions, or suggestions please let us know. >>> >>> Tully >>> >>> [1] http://www.ros.org/debbuild/groovy.html?q=regression >>> >>> >>> _______________________________________________ >>> ros-release mailing list >>> ros-release@code.ros.org >>> http://lists.ros.org/mailman/listinfo/ros-release >>> >>> >> >> _______________________________________________ >> ros-release mailing list >> ros-release@code.ros.org >> http://lists.ros.org/mailman/listinfo/ros-release >> >> > > > -- > William Woodall > ROS Development Team > william@osrfoundation.org > http://wjwwood.io/ > > _______________________________________________ > ros-release mailing list > ros-release@code.ros.org > http://lists.ros.org/mailman/listinfo/ros-release > >