gen_versioned_debs.py crashes

[tfoote]

I saw this error today in groovy. It's possibly a new upstream release which went out today. But it doesn't look like an error which should come from an upstream error.

The last successful build was 0.2.2

hector_slam-0.2.3/hector_imu_attitude_to_tf/mainpage.dox
hector_slam-0.2.3/hector_imu_attitude_to_tf/CMakeLists.txt
hector_slam-0.2.3/hector_imu_attitude_to_tf/manifest.xml
./update_version.py debian/changelog.tmp > debian/changelog
bash -c ". setup_deb.sh && ./gen_versioned_debs.py groovy hector_slam" >> /tmp/buildd/ros-groovy-hector-slam-0.2.3/debian/ros-groovy-hector-slam.substvars
Package `ros-groovy-hector-common' is not installed and no info is available.
Use dpkg --info (= dpkg-deb --info) to examine archive files,
and dpkg --contents (= dpkg-deb --contents) to list their contents.
Traceback (most recent call last):
  File "./gen_versioned_debs.py", line 54, in <module>
    main(sys.argv, sys.stdout, os.environ)
  File "./gen_versioned_debs.py", line 41, in main
    raise Exception("Could not find dependency version number")
Exception: Could not find dependency version number
make[1]: *** [install] Error 1
make[1]: Leaving directory `/tmp/buildd/ros-groovy-hector-slam-0.2.3'
make: *** [install] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit status 2
E: Failed autobuilding of package
W: no hooks of type C found -- ignoring
I: unmounting /var/cache/pbuilder/ccache filesystem

[tfoote]

Link to the failing job http://jenkins.willowgarage.com:8080/view/GbinP32/job/ros-groovy-hector-slam_binarydeb_precise_i386/64/ I've reverted it for now. FYI @meyerj

[meyerj]

Sorry for having interrupted the groovy sync process. I released the new versions of the hector_slam and hector_worldmodel stacks for fuerte and groovy yesterday before your mail to the ros-release mailing list.

Could you give me a hint what is wrong with the hector_slam 0.2.3 release from the error messages? The same version with the same source tarball was built successfully for fuerte. There have been no changes in the stack dependencies or whatever between 0.2.2 and 0.2.3. The prerelease tests run without problems (with the exception of lucid builds which seem to be constantly failing).

[tfoote]

No problem. I looked into it briefly and wasn't able to see what the problem was. After we sync we can turn it back on and try to dig a little deeper. It's a very odd error to see. At first I expected it to be a transient error, but it failed twice in a row.

[meyerj]

I re-released the two stacks hector_slam and hector_worldmodel by simply reverting your commit r31475 in the release repository (https://code.ros.org/gf/project/release/scmsvn/?action=browse&path=%2F&view=rev&revision=31476). Is there a way to trigger the buildfarm manually or do I have to wait for a trigger due to changes in upstream packages?

However, the hector_slam stack version 0.2.3 has been built successfully in the meantime: http://jenkins.willowgarage.com:8080/view/GbinP32/job/ros-groovy-hector-slam_binarydeb_precise_i386/66/.

[tfoote]

That's really weird. I'm going to close this as we can't reproduce it anymore and nothing known has changed.