Hi,
well, this was bound to happen.
I'm not sure how the wiki operates. We've managed to leave references to
ros_comm in stack.yaml (Catkin-ProjectName) and setup.py (PKG). Maybe
this is causing trouble for the indexer.
We've sent patches for IPv6 support to WG last week, so maybe this will
be resolved that way.
Thanks,
Tobias
On Do, 2012-08-23 at 22:35 -0700, Tully Foote wrote:
> Hi Daniel,
>
>
> Thanks for catching that. The ros_comm6 is effectively a fork of
> ros_comm and consequently the package names collide in the single
> indexer. I've deindexed it for now until that can be resolved. The
> wiki content should update after the next indexer run.
>
>
> Tully
>
> On Thu, Aug 23, 2012 at 8:37 PM, Daniel Stonier <d.stonier@gmail.com>
> wrote:
>
>
> Hi all,
>
> I just noticed the wiki is having trouble handling the
> ros_comm and ros_comm6 stacks simultaneously. Currently if you
> go to any of ros_comm's packages, it directs to documentation
> listed under ros_comm6. This is not a different wiki page, but
> all of the autogenerated content reflects ros_comm6's stacks.
>
>
> This makes it impossible to find autogenerated content like
> repository URL for the original roscpp/topic_tools etc.
>
>
> Just thought I'd post this in case the owners of ros_comm6
> weren't aware of the problem.
>
>
> Cheers,
> Daniel.
>
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
>
>
>
>
> --
> Tully Foote
> tfoote@willowgarage.com
> (650) 475-2827
>
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
(text/plain)