<br><div class="gmail_quote">2012/9/25 Michael Janssen (CS Grad) <span dir="ltr"><<a href="mailto:mjanssen@cs.umn.edu" target="_blank">mjanssen@cs.umn.edu</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
So, the installation instructions for installing Fuerte on Debian have<br>
been out of date for a little while now; They don't work<br>
out-of-the-box for sure, and I've been trying to figure out how to<br>
make them a bit better.<br></blockquote><div><br>Hi,<br><br>I was one of the Debian users that tried to keep ROS working
on Debian, but I'm now with electric and not willing to change before a
quite long time. I'm not surprised that the information are a bit outdated. <br>I'm unfortunately not capable to help to improve this. The only this I have done was to update the documentation between cturtle, diamondback and electric and sending trac tickets to have rosdeps.yaml files updated.<br>
<br> I will stay with electric for quite a long time now, so I'm sorry to say that I will not be available for testing purpose :(<br><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
PIP is suggested as part of the first thing to get the rosinstall,<br>
rospkg, and rosdep tools. This has been [disrecommended on this<br>
list][1] for about a month. The recommended way is to use apt now,<br>
but there aren't any instructions on the [Debian Fuerte install<br>
page][2] for that. I would like to remedy this.<br>
<br>
The packages installed via pip are rosinstall, rospkg, rosdep, and<br>
vcstools. They are available in the ubuntu repository at<br>
<a href="http://packages.ros.org/ros/ubuntu/" target="_blank">http://packages.ros.org/ros/ubuntu/</a><br>
<br>
Lucky for us, python is nice and cross plaform, and Ubuntu packages<br>
are compatible with Debian, and none of these packages have<br>
dependencies outside this set, so they install fine with dpkg if you<br>
download them all and put them on one line. python-vcstools and<br>
python-rosinstall depend on bzr, which isn't included in the<br>
"bootstrap dependencies" earlier in the wiki document, but 'apt-get<br>
install bzr' remedies that situation.<br>
<br>
>From here on out, the install instructions work fine, installing from<br>
source. However, I would prefer to have a completely Debian-package<br>
based install, similar to the Ubuntu install. Most of the packages<br>
and all of the package tools are shared between Ubuntu and Debian.<br>
Using the fuerte.yaml from [the rosdistro page][3] and the fact that<br>
we've already installed python-yaml from the earlier steps, we can<br>
build Debian packages automatically for the entire underlay. Using<br>
the "precise" tags that are the most recent work fine on both Debian<br>
squeeze and sid. I haven't been able to test on wheezy yet, but I<br>
suspect it works fine there as well.<br>
<br>
The attached script should take a Debian system from nothing to a<br>
working ros-underlay install (ready to start at step 1.3.2 on the<br>
[installation page][2]), with all Debian packages instead of source.<br>
I've tested it on current (2012-09-24) squeeze and sid.<br>
<br>
My next step is to contribute some rosdep rules, I think. Right now I<br>
have a branch at <a href="http://github.com/jamuraa/rosdep" target="_blank">http://github.com/jamuraa/rosdep</a> (in accordance with<br>
the [instructions pointed at by Tully][4]) and have been updating it.<br>
Right now I am stuck at packages in two states: packages like pcl and<br>
ros which have their own packages built for Ubuntu (and therefore<br>
should not be handled through rosdep?) or sets of missing resources<br>
like this:<br>
<br>
runtime_monitor: Missing resource rxbag<br>
turtle_actionlib: Missing resource turtlesim<br>
smach_viewer: Missing resource xdot<br>
<br>
There are a [couple][5] of [questions][6] on <a href="http://answers.ros.org" target="_blank">answers.ros.org</a>, but they<br>
aren't getting much attention / answers. If someone else has tried<br>
this and has some advise / tips, or wants to point me in the right<br>
direction for setting up a build server, I'd be grateful.<br>
<br>
[1]: <a href="http://code.ros.org/lurker/attach/3@20120806.010403.409c5c22.attach" target="_blank">http://code.ros.org/lurker/attach/3@20120806.010403.409c5c22.attach</a><br>
[2]: <a href="http://www.ros.org/wiki/fuerte/Installation/Debian" target="_blank">http://www.ros.org/wiki/fuerte/Installation/Debian</a><br>
[3]: <a href="https://github.com/ros/rosdistro/raw/master/releases/fuerte.yaml" target="_blank">https://github.com/ros/rosdistro/raw/master/releases/fuerte.yaml</a><br>
[4]: <a href="http://ros.org/doc/api/rosdep2/html/contributing_rules.html" target="_blank">http://ros.org/doc/api/rosdep2/html/contributing_rules.html</a><br>
[5]: <a href="http://answers.ros.org/question/44070/contributing-rosdep-rules-for-debian/" target="_blank">http://answers.ros.org/question/44070/contributing-rosdep-rules-for-debian/</a><br>
[6]: <a href="http://answers.ros.org/question/33002/rosdep-install-a-fails-on-debian-sqeeze/" target="_blank">http://answers.ros.org/question/33002/rosdep-install-a-fails-on-debian-sqeeze/</a><br>
<br>
Michael Janssen --- <a href="mailto:mjanssen@cs.umn.edu" target="_blank">mjanssen@cs.umn.edu</a><br>
Center for Distributed Robotics --- University of Minnesota<br>
<br>_______________________________________________<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/listinfo/ros-users</a><br>
<br></blockquote></div><br>