Ivan, <br>What version of git are you using? Are you on a version of Ubuntu I could test? I'm on lucid 64.<br><br>Tully<br><br>{{{<br>tfoote@bgt:/tmp$ em t.ri<br>tfoote@bgt:/tmp$ rosinstall t /opt/ros/cturtle t.ri <br>
rosinstall operating on /tmp/t from specifications in rosinstall files /opt/ros/cturtle, t.ri<br>processing config_uri /opt/ros/cturtle<br>Installing /tmp/t/ccny-ros-pkg to <a href="http://robotics.ccny.cuny.edu/git/ccny-ros-pkg.git">http://robotics.ccny.cuny.edu/git/ccny-ros-pkg.git</a> ICRA2011<br>
Initialized empty Git repository in /tmp/t/ccny-ros-pkg/.git/<br>Branch ICRA2011 set up to track remote branch ICRA2011 from origin.<br>Switched to a new branch 'ICRA2011'<br>other config element is a ros path /opt/ros/cturtle/ros<br>
other config element is not a ros path /opt/ros/cturtle/stacks<br>other config element is a ros path /opt/ros/cturtle/ros<br>other config element is not a ros path /opt/ros/cturtle/stacks<br>Bootstraping ROS build<br>[ rosmake ] Packages requested are: ['rostest'] <br>
[ rosmake ] Logging to directory/u/tfoote/.ros/rosmake/rosmake_output-20101008-100255 <br>[ rosmake ] Expanded args ['rostest'] to:<br>['rostest'] <br>
[ rosmake ] Generating Install Script using rosdep then executing. This may take a minute, you will be prompted for permissions. . . <br>executing this script:<br> set -o errexit<br>#No Packages to install<br>[ rosmake ] rosdep successfully installed all system dependencies <br>
[rosmake-0] Starting >>> roslib [ make ] <br>[rosmake-0] Finished <<< roslib ROS_NOBUILD in package roslib <br>
[rosmake-0] Starting >>> rosclean [ make ] <br>[rosmake-0] Finished <<< rosclean ROS_NOBUILD in package rosclean <br>
[rosmake-0] Starting >>> rosgraph [ make ] <br>[rosmake-0] Finished <<< rosgraph ROS_NOBUILD in package rosgraph <br>
[rosmake-5] Starting >>> roslang [ make ] <br>[rosmake-5] Finished <<< roslang ROS_NOBUILD in package roslang<br>
No Makefile in package roslang <br>[rosmake-6] Starting >>> rosmaster [ make ] <br>
[rosmake-6] Finished <<< rosmaster ROS_NOBUILD in package rosmaster <br>[rosmake-6] Starting >>> xmlrpcpp [ make ] <br>
[rosmake-6] Finished <<< xmlrpcpp ROS_NOBUILD in package xmlrpcpp <br>[rosmake-2] Starting >>> rosconsole [ make ] <br>
[rosmake-2] Finished <<< rosconsole ROS_NOBUILD in package rosconsole <br>[rosmake-7] Starting >>> rospy [ make ] <br>
[rosmake-2] Starting >>> roscpp [ make ] <br>[rosmake-7] Finished <<< rospy ROS_NOBUILD in package rospy <br>
[rosmake-2] Finished <<< roscpp ROS_NOBUILD in package roscpp <br>[rosmake-2] Starting >>> rosout [ make ] <br>
[rosmake-2] Finished <<< rosout ROS_NOBUILD in package rosout <br>[rosmake-2] Starting >>> roslaunch [ make ] <br>
[rosmake-2] Finished <<< roslaunch ROS_NOBUILD in package roslaunch<br> No Makefile in package roslaunch <br>[rosmake-7] Starting >>> rostest [ make ] <br>
[rosmake-7] Finished <<< rostest ROS_NOBUILD in package rostest <br>[ rosmake ] Results: <br>
[ rosmake ] Built 14 packages with 0 failures. <br>[ rosmake ] Summary output to directory <br>
[ rosmake ] /u/tfoote/.ros/rosmake/rosmake_output-20101008-100255 <br><br>done. Now, type 'source /tmp/t/setup.sh' to set up your environment.<br>
Add that to the bottom of your ~/.bashrc to set it up every time.<br><br><br>tfoote@bgt:/tmp$ rosinstall t<br>rosinstall operating on /tmp/t from specifications in rosinstall files /tmp/t/.rosinstall<br>Installing /tmp/t/ccny-ros-pkg to <a href="http://robotics.ccny.cuny.edu/git/ccny-ros-pkg.git">http://robotics.ccny.cuny.edu/git/ccny-ros-pkg.git</a> ICRA2011<br>
Already up-to-date.<br>other config element is a ros path /opt/ros/cturtle/ros<br>other config element is not a ros path /opt/ros/cturtle/stacks<br>other config element is a ros path /opt/ros/cturtle/ros<br>other config element is not a ros path /opt/ros/cturtle/stacks<br>
Bootstraping ROS build<br>[ rosmake ] Packages requested are: ['rostest'] <br>[ rosmake ] Logging to directory/u/tfoote/.ros/rosmake/rosmake_output-20101008-100309 <br>
[ rosmake ] Expanded args ['rostest'] to:<br>['rostest'] <br>[ rosmake ] Generating Install Script using rosdep then executing. This may take a minute, you will be prompted for permissions. . . <br>
executing this script:<br> set -o errexit<br>#No Packages to install<br>[ rosmake ] rosdep successfully installed all system dependencies <br>[rosmake-0] Starting >>> roslib [ make ] <br>
[rosmake-0] Finished <<< roslib ROS_NOBUILD in package roslib <br>[rosmake-0] Starting >>> rosclean [ make ] <br>
[rosmake-0] Finished <<< rosclean ROS_NOBUILD in package rosclean <br>[rosmake-0] Starting >>> rosgraph [ make ] <br>
[rosmake-0] Finished <<< rosgraph ROS_NOBUILD in package rosgraph <br>[rosmake-5] Starting >>> roslang [ make ] <br>
[rosmake-5] Finished <<< roslang ROS_NOBUILD in package roslang<br> No Makefile in package roslang <br>[rosmake-5] Starting >>> rospy [ make ] <br>
[rosmake-5] Finished <<< rospy ROS_NOBUILD in package rospy <br>[rosmake-1] Starting >>> rosmaster [ make ] <br>
[rosmake-1] Finished <<< rosmaster ROS_NOBUILD in package rosmaster <br>[rosmake-2] Starting >>> xmlrpcpp [ make ] <br>
[rosmake-2] Finished <<< xmlrpcpp ROS_NOBUILD in package xmlrpcpp <br>[rosmake-2] Starting >>> rosconsole [ make ] <br>
[rosmake-2] Finished <<< rosconsole ROS_NOBUILD in package rosconsole <br>[rosmake-2] Starting >>> roscpp [ make ] <br>
[rosmake-2] Finished <<< roscpp ROS_NOBUILD in package roscpp <br>[rosmake-2] Starting >>> rosout [ make ] <br>
[rosmake-2] Finished <<< rosout ROS_NOBUILD in package rosout <br>[rosmake-6] Starting >>> roslaunch [ make ] <br>
[rosmake-6] Finished <<< roslaunch ROS_NOBUILD in package roslaunch<br> No Makefile in package roslaunch <br>[rosmake-6] Starting >>> rostest [ make ] <br>
[rosmake-6] Finished <<< rostest ROS_NOBUILD in package rostest <br>[ rosmake ] Results: <br>
[ rosmake ] Built 14 packages with 0 failures. <br>[ rosmake ] Summary output to directory <br>
[ rosmake ] /u/tfoote/.ros/rosmake/rosmake_output-20101008-100309 <br><br>done. Now, type 'source /tmp/t/setup.sh' to set up your environment.<br>
Add that to the bottom of your ~/.bashrc to set it up every time.<br><br><br>tfoote@bgt:/tmp$ git --version<br>git version 1.7.0.4<br>}}}<br><br><div class="gmail_quote">On Wed, Oct 6, 2010 at 6:22 PM, Ivan Dryanovski <span dir="ltr"><<a href="mailto:ivan.dryanovski@gmail.com">ivan.dryanovski@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">I'm sorry to go back to this thread, but I am still having issues with<br>
the rosinstall tool.<br>
<br>
I have the following lines in my rosconfig file that I am passing to<br>
ROS Install:<br>
<br>
- git:<br>
uri: <a href="http://robotics.ccny.cuny.edu/git/ccny-ros-exp.git" target="_blank">http://robotics.ccny.cuny.edu/git/ccny-ros-exp.git</a><br>
version: master<br>
local-name: ccny-ros-exp<br>
- git:<br>
uri: <a href="http://robotics.ccny.cuny.edu/git/ccny-ros-pkg.git" target="_blank">http://robotics.ccny.cuny.edu/git/ccny-ros-pkg.git</a><br>
version: ICRA2011<br>
local-name: ccny-ros-pkg<br>
<br>
The first on works fine. When the installer attempts to check out the<br>
he second one, it produces this error:<br>
<br>
fatal: git checkout: updating paths is incompatible with switching<br>
branches/forcing<br>
Did you intend to checkout 'ICRA2011' which can not be resolved as commit?<br>
ERROR: Failed to install tree '/home/idryanov/icra2011_ccny/ccny-ros-pkg'<br>
vcs not setup correctly.<br>
<br>
A quick search on the issue gives me this:<br>
<br>
<a href="http://www.skrinakcreative.com/wp/2008/11/fatal-git-checkout-problem-resolved/" target="_blank">http://www.skrinakcreative.com/wp/2008/11/fatal-git-checkout-problem-resolved/</a><br>
<br>
The comments suggest pulling first, and then checking out the desired<br>
branch. How does rosinstall handle it?<br>
Any help would be appreciated<br>
<font color="#888888"><br>
Ivan<br>
</font><div><div></div><div class="h5"><br>
On Wed, Sep 29, 2010 at 7:54 PM, Brian Gerkey <<a href="mailto:gerkey@willowgarage.com">gerkey@willowgarage.com</a>> wrote:<br>
> On Wed, Sep 29, 2010 at 2:57 PM, Ivan Dryanovski<br>
> <<a href="mailto:ivan.dryanovski@gmail.com">ivan.dryanovski@gmail.com</a>> wrote:<br>
>> I ran into an svn versioning issue.<br>
>><br>
>> I am using the following command to get the svn revisions:<br>
>><br>
>> ./unwrap_externals.py<br>
>> <a href="https://code.ros.org/svn/ros-pkg/externals/latest/" target="_blank">https://code.ros.org/svn/ros-pkg/externals/latest/</a> ><br>
>> icra2011_dryanovski.rosconfig<br>
><br>
> You probably want to unwrap the cturtle external instead, e.g.:<br>
><br>
> ./unwrap_externals.py<br>
> <a href="https://code.ros.org/svn/ros-pkg/externals/distro/cturtle/all" target="_blank">https://code.ros.org/svn/ros-pkg/externals/distro/cturtle/all</a> ><br>
> icra2011_dryanovski.rosconfig<br>
><br>
> In general, you'd want to unwrap the external from which you'd checked<br>
> out the code.<br>
><br>
> Now that I think about it, there's a potential mismatch between the<br>
> version currently pointed to by the external and the version that was<br>
> used. A while back, I wrote a script to rummage over your<br>
> ROS_PACKAGE_PATH, and produce a rosinstall file that would check out<br>
> the same stuff that you currently have checked out (assuming that it<br>
> all came from SVN). I can't find that script now, but it would be<br>
> easy to reproduce.<br>
><br>
> But still we're talking about doing work from a source-based install,<br>
> which is (hopefully) becoming less common as the binary packages are<br>
> gaining traction (at least for people running Ubuntu).<br>
><br>
> It seems like, to record the software that makes up your experimental<br>
> environment, you need to know:<br>
> * the versions of all released stacks in use<br>
> * the svn/git/bzr/hg URI and revision/branch/hash info for everything else.<br>
> (To be complete, you could record the version of the Linux kernel and<br>
> so on, but we have to bottom out somewhere.) So perhaps we need a<br>
> tool that gathers that information....<br>
><br>
> brian.<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>
_______________________________________________<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>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Tully Foote<br>Systems Engineer<br>Willow Garage, Inc.<br><a href="mailto:tfoote@willowgarage.com">tfoote@willowgarage.com</a><br>(650) 475-2827<br>