V4r

[bajo]

@ipa-nhg buildbot is not happy as it still uses the old repository. On our machines it is compiling though. I think it is ok to merge it.

[ipa-nhg]

@bajo I think that it is working on your machine because you didn't remove the old mirror configuration, /etc/apt/source... and /etc/rosdep... if you clean these files and setup again, you will not be able to compile the repo.

For sure this https://github.com/squirrel-project/squirrel_perception/blob/indigo_dev/squirrel_perception/setup.sh#L3 was wrong because you need still the old server to find the ros-indigo-classifier-srv-definitions package , for v4r I am not sure where is the error, I updated buildbot to use the new repo..

[bajo]

@ipa-nhg
@jibweb is trying to fix this issue. However, it seems that it still installs ros-indigo-v4r from lincoln's mirror. Not sure why this is happening as the private.yaml clearly links v4r to v4r and not to ros-indigo-v4r anymore.

I will try this on my machine after cleaning /etc/apt/source... and /etc/rosdep... to check if the current commit should work on another machine.

[ipa-nhg]

Hi @bajo @jibweb ,

dont worry, I think that the problem is buildbot, but I dont find the error. I am currently modifying the source code of buildbot to debug the problem, if I call during the test execution "rosdep where-defined v4r" ( http://402e2b47.ngrok.io/builders/squirrel_perception_indigo_testbuild/builds/18/steps/squirrel_perception-build/logs/stdio ) it is not working , and on my machine I haven't got the problem... at some point rosdep is not reading the yaml file.

please ignore the current errors from buildbot, my buildbot code is causing the errors and not squirrel_perception...