I have run into this as well, and maybe I am unfamiliar with how you guys are using git, but I think the way the rosinstall did its git checkout before was fine. I don't understand why it has to make a new branch when it git clones the repository?<div>
<br></div><div>Additionally, at the end of rosinstall I now get this error:</div><div><br></div><div><div>...</div><div>ERROR: No ROS_ROOT defined. The 'ros' stack is required in all rosinstall directories. Please add a definition of the 'ros' stack either manually in .rosinstall and then call 'rosinstall .' in the directory. Or add one on the command line 'rosinstall . <a href="http://www.ros.org/rosinstalls/boxturtle_ros.rosinstall">http://www.ros.org/rosinstalls/boxturtle_ros.rosinstall</a>'. Or reference an existing install like in /opt/ros/boxturtle with 'rosinstall . /opt/ros/boxturtle'. Note: the above suggestions assume you are using boxturtle, if you are using latest or another distro please change the urls.</div>
<div>...</div><div><br></div><div>So then I run export to check and this is what I get:</div><div><br></div><div>~$ export</div><div>...</div><div>declare -x PATH="/opt/ros/cturtle/ros/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"</div>
<div>declare -x PWD="/home/mowbot"</div><div>declare -x PYTHONPATH=":/opt/ros/cturtle/ros/core/roslib/src"</div><div>declare -x ROS_MASTER_URI="<a href="http://localhost:11311">http://localhost:11311</a>"</div>
<div>declare -x ROS_PACKAGE_PATH="/opt/ros/cturtle/stacks"</div><div>declare -x ROS_ROOT="/opt/ros/cturtle/ros"</div><div>...</div></div><div><br></div><div>This means that it also does not generate a setup.sh file for me to source. I have attached the whole transcript of the problem.</div>
<div><br></div><div>I tried what the message told me and tried doing 'rosinstall . /opt/ros/cturtle' before trying the ros install of my repository and that did not change anything.</div><div><br></div><div>Also, I was looking for how rosinstall is supposed to work now and I think that if the ros_tutorials are included in the deb packages now then the tutorials are not going to work. Specifically the second tutorial instructs users to roscreate-pkg without telling them to change directories or anything. Now if they started tutorial two directly from tutorial one they should still be in turtlesim's pkg directory, which by default will not be writable to most users and roscreate-pkg will fail with permission denied.</div>
<div><br></div><div>I appreciate any insight into how I should be setting up my working environment differently or to why I am getting errors from rosinstall.</div><div><br></div><div>Thanks,</div><div><br clear="all">~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
William Woodall<br>Graduate Software Engineering<br>Auburn University<br><a href="mailto:w@auburn.edu">w@auburn.edu</a><br><a href="mailto:wjwwood@gmail.com">wjwwood@gmail.com</a><br>256-345-9938<br>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
<br><br><div class="gmail_quote">On Wed, Aug 11, 2010 at 8:21 PM, Tully Foote <span dir="ltr"><<a href="mailto:tfoote@willowgarage.com">tfoote@willowgarage.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Dejan, <div>rosinstall creates a named branch to avoid to avoid conflicts when checking in locally. As of version 0.5.5 the git checkouts have been upgraded to properly call --track when branching off of a branch such that push and pull should work. </div>
<div><br></div><div><font color="#888888">Tully</font><div><div></div><div class="h5"><br><br><div class="gmail_quote">On Wed, Aug 4, 2010 at 3:18 PM, Dejan Pangercic <span dir="ltr"><<a href="mailto:dejan.pangercic@gmail.com" target="_blank">dejan.pangercic@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi there,<br>
<br>
I am using rosinstall script from pypi, version 0.5.2. After updating<br>
my installation today I noticed that all git repositories specified in<br>
my overlay file have been cloned to the local branches named<br>
"rosinstall" as oppose to e.g. branch "master".<br>
In my POV this should be considered as a bug right?<br>
<br>
cheers, D.<br>
<br>
--<br>
MSc. Dejan Pangercic<br>
PhD Student/Researcher<br>
Intelligent Autonomous Systems Group<br>
Technische Universität München<br>
Telephone: +49 (89) 289-26908<br>
E-Mail: <a href="mailto:dejan.pangercic@cs.tum.edu" target="_blank">dejan.pangercic@cs.tum.edu</a><br>
WWW: <a href="http://ias.cs.tum.edu/people/pangercic" target="_blank">http://ias.cs.tum.edu/people/pangercic</a><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>
</blockquote></div><br><br clear="all"><br></div></div><div class="im">-- <br>Tully Foote<br>Systems Engineer<br>Willow Garage, Inc.<br><a href="mailto:tfoote@willowgarage.com" target="_blank">tfoote@willowgarage.com</a><br>
(650) 475-2827<br>
</div></div>
<br>_______________________________________________<br>
ros-users mailing list<br>
<a href="mailto:ros-users@code.ros.org">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></div>