For prerelease jobs using the devel branch of the selected upstream repos the prerelease jobs tried to install all dependencies from Debian packages.
But it did not exclude the package names which were build in the workspace from source.
Therefore it tried to install Debian packages which are not available (since they are currently not yet released).

I have fixed the bug in the prerelease job: https://github.com/ros-infrastructure/jenkins_scripts/pull/66
The latest prerelease jobs of your package passed without a problem.

Thanks for pointing it out.

Cheers,
- Dirk


On Thu, Mar 13, 2014 at 10:49 AM, Dirk Thomas <dthomas@osrfoundation.org> wrote:
Since these two packages in question are part of the repository you selected for prerelease the state of the Debian packages is not relevant.

I am not yet sure what happened but will get back to you when I was able to take a closer look.

- Dirk


On Thu, Mar 13, 2014 at 10:41 AM, William Woodall <william@osrfoundation.org> wrote:
I'm not sure about this, but I have a theory that you caught the shadow-fixed repository in an inconsistent state? I believe pre-release uses shadow-fixed, and it may be that in the middle of the shadow-fixed sync from building the repo got into an inconsistent state, but I could be wrong about that.

I would recommend trying the pre-release again and see if it still gives you trouble.


On Thu, Mar 13, 2014 at 1:56 AM, Thomas Moulard <thomas.moulard@gmail.com> wrote:
Hello everyone,
I am trying to release vision_visp / hydro with Catkin and Bloom.

Unfortunately the buildfarm fails with this error:
http://jenkins.ros.org/job/prerelease-hydro-vision_visp/ARCH_PARAM=amd64,UBUNTU_PARAM=precise,label=prerelease/6/consoleText

[...]
Built target run_tests
Retrieve the ROS build environment by sourcing
/tmp/test_repositories/build_repository/devel/setup.bash
Get list of wet repositories that build-depend on repo list: vision_visp
repo_name vision_visp
pkg_name vision_visp
depends_on set([])
pkg_name visp_auto_tracker
depends_on set([])
pkg_name visp_bridge
depends_on set(['visp_camera_calibration',
'visp_hand2eye_calibration', 'visp_auto_tracker'])
pkg_name visp_camera_calibration
depends_on set(['visp_camera_calibration',
'visp_hand2eye_calibration', 'visp_auto_tracker'])
pkg_name visp_hand2eye_calibration
depends_on set(['visp_camera_calibration',
'visp_hand2eye_calibration', 'visp_auto_tracker'])
pkg_name visp_tracker
depends_on set(['visp_camera_calibration',
'visp_hand2eye_calibration', 'visp_auto_tracker'])
Build depends_on list of pkg list: visp_camera_calibration,
visp_hand2eye_calibration, visp_auto_tracker
Rosinstall for depends_on:
 - git: {local-name: visp_camera_calibration, uri:
'https://github.com/lagadic/vision_visp-release.git',
    version: release/hydro/visp_camera_calibration/0.7.1-0}
- git: {local-name: visp_hand2eye_calibration, uri:
'https://github.com/lagadic/vision_visp-release.git',
    version: release/hydro/visp_hand2eye_calibration/0.7.1-0}
- git: {local-name: visp_auto_tracker, uri:
'https://github.com/lagadic/vision_visp-release.git',
    version: release/hydro/visp_auto_tracker/0.7.1-0}
[...]
Executing command 'apt-get install --yes
ros-hydro-camera-calibration-parsers ros-hydro-catkin
ros-hydro-geometry-msgs ros-hydro-image-proc ros-hydro-message-filters
ros-hydro-message-generation ros-hydro-resource-retriever
ros-hydro-sensor-msgs ros-hydro-std-msgs ros-hydro-visp-bridge
ros-hydro-visp-tracker'
[...]
E: Unable to locate package ros-hydro-visp-bridge
E: Unable to locate package ros-hydro-visp-tracker

These two packages are part of the stack I am trying to release. There
is no previous
released package so this is expected that these Debian packages are
not available.

Could anyone tell me what is wrong in my current approach?
Thanks,
--
Thomas Moulard
_______________________________________________
ros-release mailing list
ros-release@code.ros.org
http://lists.ros.org/mailman/listinfo/ros-release



--
William Woodall
ROS Development Team

_______________________________________________
ros-release mailing list
ros-release@code.ros.org
http://lists.ros.org/mailman/listinfo/ros-release