ros-infrastructure/bloom — pull request #141 by wjwwood (2013-04-22 19:58:20+00:00)
Title: When pushing upstream into release-branch symbolic links are changed into the refered files/directories.

When bloom pushes the upstream-branch into it's release branch it automatically changes symbolic links into the files/directories which the symbolic links referred to.

This is an urgent bug as it leads to roslisp no longer compiling on the build-farms for Fuerte. As a result several packages that rely on roslisp are also no longer available as debians for Fuerte.

The behaviour can be seen in the last commit (March, 5th) in the release-branch of ros_comm for fuerte:
https://github.com/ros-gbp/ros_comm-release/tree/debian/fuerte/precise/ros_comm

The commits that contains the wrong changes has the commit-message "Rebase from 'upstream'". The development branch for fuerte can be found here:
https://github.com/ros-gbp/ros_comm-release/tree/debian/fuerte/precise/ros_comm

Background: The buildsystem of roslisp (asdf) relies on a directory ASDF to be in every lisp-package in ROS (also roslisp itself). Each oft these ASDF directories has to hold symbolic links to *.asd-files which describe the dependencies of the lisp-systems. The lisp-compiler expects these asd-files to always reside in the same directory as the lisp-source files. When these symbolic links are changed into the real *.asd-files in the ASDF-directory compilation of breaks. For roslisp, this directory can be found in the sub-folder clients/roslisp of the development repo.