<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Nov 16, 2012 at 12:56 AM, Christian Dornhege <span dir="ltr"><<a href="mailto:dornhege@informatik.uni-freiburg.de" target="_blank">dornhege@informatik.uni-freiburg.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
Am 15.11.2012 19:27, schrieb Eitan Marder-Eppstein:<div class="im"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hey all,<br>
</blockquote>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
So, it's been a bit, but I've finally gotten around to switching<br>
Electric over to the new documentation indexer. So, as some of you have<br>
already noticed, you can now submit your repo to be indexed on Electric<br>
the same way you would for Fuerte and Groovy.<br>
</blockquote>
<br></div>
I've just reviewed the entries in the rosdistro repository and it seems<br>
that there are some rosinstall files for individual stacks (like<br>
freiburg_tools.rosinstall), but none for the whole repository (as was<br>
originally indexed for electric). I'm not sure where they originate<br>
from, my guess would be they are based on released stacks.<br>
<br>
Is it safe to go ahead and remove all those individual files and<br>
replace that by a repository rosinstall?<br>
What would be the behaviour of the indexer when there are two<br>
rosinstall files that contain the same stack/packages?<br></blockquote><div><br></div><div>We have pulled in the full previous index, however it has not successfully turned over. This is due to many stale entries, mostly things which were added to the index. <br>
</div><div><br></div><div>It would be great if your or anyone else with packages indexed wanted to seperate them out into logical semantic groups such as your "repository" or organization. </div><div><br></div>
<div>If there's multiple definitions I think that the last one indexed will override previous ones. It's not deterministic which order they will run in. </div><div><br></div><div>Tully</div><div><br></div><div><br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Best,<br>
Christian<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
A few notes:<br>
<br>
* If your documentation build status is "unstable," this means that<br>
message generation failed for your repository which can lead to improper<br>
Python documentation. This occurs because both Sphinx and Epydoc import<br>
your python module to generate documentation and if python message code<br>
generation fails, your import will also fail, leading to stripped down<br>
docs. Clicking on the details link on the wiki page should take you to<br>
an error report that, I hope, helps maintainers track down and fix<br>
problems fairly easily. With "unstable" builds, we do our best attempt<br>
at providing documentation, but some of the python docs may be a bit wonky.<br>
<br>
* If your documentation build status is "failure," this means that<br>
something more serious is occurring that prevents any documentation from<br>
being generated. Clicking on the details link will take you directly to<br>
the console on Jenkins where you can debug the issue.<br>
<br>
* Maintainers should make sure that when they submit rosinstall files<br>
for a given distro, they use the right branch. For example, using trunk<br>
of your repository in the electric, fuerte, and groovy indexer is<br>
probably not what you intend. Instead, you'd want to make sure to submit<br>
electric-dev, fuerte-dev, groovy-dev, etc.<br>
<br>
Hope all is well and thanks to all who have tested and reported<br>
issues... keep 'em coming,<br>
<br>
Eitan<br>
<br>
On Thu, Nov 8, 2012 at 6:10 AM, Patrick Goebel <<a href="mailto:patrick@pirobot.org" target="_blank">patrick@pirobot.org</a><br></div><div><div class="h5">
<mailto:<a href="mailto:patrick@pirobot.org" target="_blank">patrick@pirobot.org</a>>> wrote:<br>
<br>
Thanks Eitan,<br>
<br>
I will try the instructions for Fuerte/Groovy.<br>
<br>
--patrick<br>
<br>
<br>
<br>
On 11/06/2012 07:23 AM, Eitan Marder-Eppstein wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
Hey all,<br>
<br>
Sorry that's it's taken me a bit to chime in on things. It's been<br>
a hectic start to the week<br>
<br>
Patrick, for your packages, if you submit a repository to the<br>
Fuerte indexer, you'll get headers auto-generated for<br>
that distribution. The same can be said for Groovy. So, you<br>
shouldn't have to manually add headers. With electric, it's a bit<br>
trickier because that's still running the old documentation<br>
indexer and running off the distro file of released stacks. If<br>
there's a ton of demand to have headers generated for electric,<br>
there might be a way for me to create a hybrid system of the old<br>
and new indexers, but it's an item that hasn't been high on my<br>
priority list. As Christain mentioned/quoted, documentation for<br>
electric was actually never very complete, it's just that no one<br>
noticed because distro-level browsing wasn't something that you<br>
could really do on the wiki.<br>
<br>
As for the unstable builds that Mani mentions, there are still<br>
some issues that I'm having with getting message generation to run<br>
properly during documentation. I'm going to try to solve this<br>
problem this week. So, for now, ignoring the fact that a build is<br>
unstable is OK. Perhaps I should remove those messages from the<br>
wiki until I fix the problem that is causing the majority of<br>
this instability Once this issue is fixed, however, the idea is<br>
that stack maintainers can see why their builds are failing or<br>
unstable and make fixes to their repositories as needed. This<br>
should all work properly soon, sorry for the state of limbo that<br>
exists in the near-term.<br>
<br>
Hope this helps and that all is well,<br>
<br>
Eitan<br>
<br>
On Mon, Nov 5, 2012 at 7:36 PM, Patrick Goebel<br></div></div><div><div class="h5">
<<a href="mailto:patrick@pirobot.org" target="_blank">patrick@pirobot.org</a> <mailto:<a href="mailto:patrick@pirobot.org" target="_blank">patrick@pirobot.org</a>>> wrote:<br>
<br>
Thanks Christian,<br>
<br>
So I guess I need to go back and add the header manually to<br>
each wiki page for now.<br>
<br>
--patrick<br>
<br>
<br>
On 11/05/2012 01:59 AM, Christian Dornhege wrote:<br>
<br>
On 03.11.2012 14:02, Patrick Goebel wrote:<br>
<br>
Sorry to be so dense everyone, but can someone tell me<br>
if packages that<br>
have long existed in the indexer for ROS Electric<br>
(e.g. pi_face_tracker)<br>
need to be resubmitted to ros-users to have the<br>
correct header created<br>
on the Wiki page? At the moment, all my old Wiki<br>
pages have the<br>
following message at the top even for Electric:<br>
<br>
Cannot load information on*name: pi_face_tracker,<br>
distro: electric*,<br>
which means that it is not yet in our index. Please<br>
seethis page<br>
<<a href="http://www.ros.org/wiki/Get%20Involved#Indexing_Your_.2A-ros-pkg_Repository_for_Documentation_Generation" target="_blank">http://www.ros.org/wiki/Get%<u></u>20Involved#Indexing_Your_.2A-<u></u>ros-pkg_Repository_for_<u></u>Documentation_Generation</a>>for<br>
<br>
information on how to submit your repository to our index.<br>
<br>
And it appears that it is not just my packages but<br>
others (e.g.<br>
face_recognition). Or is the new requirement that the<br>
package has to<br>
exist as a Debian package?<br>
<br>
<br>
It is the same for our packages. Let me quote Eitan's<br>
reply to my question:<br>
<br>
On Wed, Oct 31, 2012 at 5:57 AM, Christian Dornhege<br>
<<a href="mailto:dornhege@informatik.uni-freiburg.de" target="_blank">dornhege@informatik.uni-<u></u>freiburg.de</a><br></div></div><div class="im">
<mailto:<a href="mailto:dornhege@informatik.uni-freiburg.de" target="_blank">dornhege@informatik.<u></u>uni-freiburg.de</a>>> wrote:<br>
> Was this behavior maybe changed at some time? I remember<br>
it indexing our trunk/ URL. Now it seems that only the<br>
packages are indexed that have been released as debs.<br>
<br>
The behavior for electric documentation always worked this<br>
way. However, there was a separate indexer that ran off of<br>
rosinstall files documenting whatever was in them, but<br>
that is no longer run in favor of the new system. It's<br>
possible that this old indexer produced your headers and<br>
documentation, but the docs for electric specifically were<br>
never generated. With the old wiki, no one would have<br>
noticed this as per-distro browsing wasn't something that<br>
was really possible to do. The old indexer job was kind of<br>
weird to begin with since it could allow for documentation<br>
to be mixed between distros... leading to some weird effects.<br>
<br>
<br>
Best,<br>
Christian<br>
<br>
<br>
Thanks!<br>
patrick<br>
<br>
<br>
<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
ros-users mailing list<br></div>
<a href="mailto:ros-users@code.ros.org" target="_blank">ros-users@code.ros.org</a> <mailto:<a href="mailto:ros-users@code.ros.org" target="_blank">ros-users@code.ros.org</a><u></u>><div class="im"><br>
<a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/<u></u>listinfo/ros-users</a><br>
<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
ros-users mailing list<br></div>
<a href="mailto:ros-users@code.ros.org" target="_blank">ros-users@code.ros.org</a> <mailto:<a href="mailto:ros-users@code.ros.org" target="_blank">ros-users@code.ros.org</a><u></u>><div class="im"><br>
<a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/<u></u>listinfo/ros-users</a><br>
<br>
<br>
<br>
<br>
--<br>
Eitan Marder-Eppstein<br>
President, hiDOF Inc.<br>
<a href="http://www.hidof.com" target="_blank">http://www.hidof.com</a><br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
ros-users mailing list<br></div>
<a href="mailto:ros-users@code.ros.org" target="_blank">ros-users@code.ros.org</a> <mailto:<a href="mailto:ros-users@code.ros.org" target="_blank">ros-users@code.ros.org</a><u></u>><br>
<a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/<u></u>listinfo/ros-users</a><br>
</blockquote>
<br>
<br>
______________________________<u></u>_________________<br>
ros-users mailing list<br>
<a href="mailto:ros-users@code.ros.org" target="_blank">ros-users@code.ros.org</a> <mailto:<a href="mailto:ros-users@code.ros.org" target="_blank">ros-users@code.ros.org</a><u></u>><div class="im"><br>
<a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/<u></u>listinfo/ros-users</a><br>
<br>
<br>
<br>
<br>
--<br>
Eitan Marder-Eppstein<br>
President, hiDOF Inc.<br>
<a href="http://www.hidof.com" target="_blank">http://www.hidof.com</a><br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
ros-users mailing list<br>
<a href="mailto:ros-users@code.ros.org" target="_blank">ros-users@code.ros.org</a><br>
<a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/<u></u>listinfo/ros-users</a><br>
<br>
</div></blockquote><div class="HOEnZb"><div class="h5">
<br>
______________________________<u></u>_________________<br>
ros-users mailing list<br>
<a href="mailto:ros-users@code.ros.org" target="_blank">ros-users@code.ros.org</a><br>
<a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/<u></u>listinfo/ros-users</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Tully Foote<br><a href="mailto:tfoote@willowgarage.com" target="_blank">tfoote@willowgarage.com</a><br>(650) 475-2827<br>
</div>