roslocate returns weird results:

[tkruse]

Sometimes returns no valid url, wrong url, fuerte url or version

$ roslocate info rospack
- svn:
    local-name: ros
    uri: null

http://ros.org/doc/api/rospack/manifest.yaml
(uri should be github)

$ roslocate info xmlrpcpp
- svn:
    local-name: vmi-ros-pkg
    uri: https://svn.vmi.ei.tum.de/vmi-ros-pkg/trunk/ros_comm6/utilities/xmlrpcpp

http://ros.org/doc/api/xmlrpcpp/manifest.yaml
(should be github ros_comm)

$ roslocate info ros_comm
- svn:
    local-name: ros_comm
    uri: https://code.ros.org/svn/ros/stacks/ros_comm/trunk

http://ros.org/doc/api/ros_comm/stack.yaml
(should be github?)

$ roslocate info rqt
- git:
    local-name: rqt
    meta:
      repo-name: rosdistro_fuerte
    uri: https://github.com/ros-visualization/rqt.git
    version: fuerte-devel

http://ros.org/doc/api/rqt/stack.yaml
(should not be fuerte-devel, version should best be empty)

$ ~/work/python/rosinstall/scripts/roslocate info nodelet
- hg:
    local-name: nodelet_core
    meta:
      repo-name: wg-kforge
    uri: https://kforge.ros.org/common/nodeletcore
    version: default

http://ros.org/doc/api/nodelet_core/stack.yaml
(should be github)

Similar problems for
$ roslocate info rosbag
$ roslocate info gencpp
...

I could go on and raise issues on the respective packages, but I might miss some that way, and this should be fixed in a better way also for the future.

roslocate may also need fixing in the process. Curently it goes to http://ros.org/doc/[distroname/]/api/stackagename

and looks for manifest.yaml and stack.yaml (which were generated using some rosdoc job in the past)

Those files either need to be updated, or we need to define a protocol for how roslocate should not operate, or simply deprecate roslocate.

[tkruse]

Meeting notes:

• suggest postponing this after update of rosinstall_generator?
• also to apply pathes from github gbp repo?

[tfoote]

The rosco roslocate infrastructure is now mostly invalid. We should ticket the rosinstall generation to be able to get just one package url, not recursive. Then we should switch rosco and roslocate to use the rosinstall generator as the backend.

[tkruse]

See ros-infrastructure/prerelease_website/issues/7

[pirobot]

Another example:

$ roslocate uri face_recognition

error contacting http://ros.org/doc/api/face_recognition/stack.yaml:
HTTP Error 404: Not Found
error contacting http://ros.org/doc/api/face_recognition/manifest.yaml:
HTTP Error 404: Not Found
cannot locate information about face_recognition

[tfoote]

There is no face_recognition package indexed: http://ros.org/doc/api/ The the unversioned urls are just a symlink to groovy.

[pirobot]

Thanks Tully. However, I get the same 404 messages when I try to roslocate my own packages that I have already submitted using the new rosdistro instructions. For example, try:

$ roslocate info pi_vision

So what I am missing?

[tfoote]

The default is groovy, you have not submitted pi_vision for groovy, it
appears to be in electric and fuerte.

You can see the documentation status on the wiki, by clicking the drop
down: http://www.ros.org/wiki/pi_vision

[pirobot]

Ahhhh. OK, thanks.

[tfoote]

uri will work with --distro option. It does look like info is broken at
the moment though.

On Thu, Feb 14, 2013 at 1:15 PM, pirobot notifications@github.com wrote:

Ahhhh. OK, thanks.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/366#issuecomment-13578978.

Tully Foote
tfoote@willowgarage.com
(650) 475-2827

[tfoote]

Duplicate of above reference.