Issues with sourcing and ROS_PACKAGE_PATH when using camera_pose [closed]

edit

I've been running into issues trying to run camera_pose_calibration in Hydro. Long story short, I decided to source Groovy on a whim and it seems like it actually is making progress. In my .bashrc file I have

source /opt/ros/groovy/setup.bash

export ROS_PACKAGE_PATH="/opt/ros/groovy/share:/opt/ros/groovy/stacks:/opt/ros/fuerte/share:/opt/ros/fuerte/stacks"

When I launch my kinects I use

roslaunch openni_launch openni.launch camera:=kinect_1 device_id:=1@0

and adjust to numbers 2 and 3 for the second and third respectively. The Kinects launch without error or issue and I try to use camera_pose_calibration package with this code:

roslaunch camera_pose_calibration calibrate_3_camera.launch camera1_ns:=kinect_1 camera2_ns:=kinect_2 camera3_ns:=kinect_3 checker_rows:=6 checker_cols:=8 checker_size:=0.027

This puts out an aggregated_image window with three "tv static" squares and one black one which is an improvement over nothing when I was using Hydro. However, I still get two errors:

ERROR: cannot launch node of type [image_cb_detector/image_cb_detector_action_old]: can't locate node [image_cb_detector_action_old] in package [image_cb_detector]

This error above appears for all 3 Kinects.

This other appears as well:

File "/usr/lib/pymodules/python2.7/rospkg/rospack.py", line 190, in get_path
    raise ResourceNotFound(name, ros_paths=self._ros_paths)
rospkg.common.ResourceNotFound: pr2_calibration_executive
ROS path [0]=/opt/ros/groovy/share/ros
ROS path [1]=/opt/ros/groovy/share
ROS path [2]=/opt/ros/groovy/stacks
ROS path [3]=/opt/ros/fuerte/share
ROS path [4]=/opt/ros/fuerte/stacks
Waiting for Server

[capture_exec-19] process has died [pid 31368, exit code 1, cmd /opt/ros/fuerte/stacks/camera_pose/camera_pose_calibration/src/camera_pose_calibration/multicam_capture_exec.py kinect_1 kinect_2 kinect_3 request_interval:=interval_filtered __name:=capture_exec __log:=/home/robot2/.ros/log/672c23ce-7e26-11e3-b35b-b8ca3a789964/capture_exec-19.log].
log file: /home/robot2/.ros/log/672c23ce-7e26-11e3-b35b-b8ca3a789964/capture_exec-19*.log

Now, this is without overlaying a fork that seems to have fixed other people's problem. If I overlay it, I get a whole other mess of errors that seem to indicate it can't access the other necessary components.