[ros-users] Experimental Results Repository

Fri Oct 8 17:05:28 UTC 2010

Ivan,
What version of git are you using?  Are you on a version of Ubuntu I could
test?  I'm on lucid 64.

Tully

{{{
tfoote at bgt:/tmp$ em t.ri
tfoote at bgt:/tmp$ rosinstall t /opt/ros/cturtle t.ri
rosinstall operating on /tmp/t from specifications in rosinstall files
/opt/ros/cturtle, t.ri
processing config_uri /opt/ros/cturtle
Installing /tmp/t/ccny-ros-pkg to
http://robotics.ccny.cuny.edu/git/ccny-ros-pkg.git ICRA2011
Initialized empty Git repository in /tmp/t/ccny-ros-pkg/.git/
Branch ICRA2011 set up to track remote branch ICRA2011 from origin.
Switched to a new branch 'ICRA2011'
other config element is a ros path /opt/ros/cturtle/ros
other config element is not a ros path /opt/ros/cturtle/stacks
other config element is a ros path /opt/ros/cturtle/ros
other config element is not a ros path /opt/ros/cturtle/stacks
Bootstraping ROS build
[ rosmake ] Packages requested are:
['rostest']

[ rosmake ] Logging to
directory/u/tfoote/.ros/rosmake/rosmake_output-20101008-100255

[ rosmake ] Expanded args ['rostest'] to:
['rostest']

[ rosmake ] Generating Install Script using rosdep then executing. This may
take a minute, you will be prompted for permissions. . .
executing this script:
 set -o errexit
#No Packages to install
[ rosmake ] rosdep successfully installed all system
dependencies

[rosmake-0] Starting >>> roslib [ make
]

[rosmake-0] Finished <<< roslib ROS_NOBUILD in package
roslib

[rosmake-0] Starting >>> rosclean [ make
]

[rosmake-0] Finished <<< rosclean ROS_NOBUILD in package
rosclean

[rosmake-0] Starting >>> rosgraph [ make
]

[rosmake-0] Finished <<< rosgraph ROS_NOBUILD in package
rosgraph

[rosmake-5] Starting >>> roslang [ make
]

[rosmake-5] Finished <<< roslang ROS_NOBUILD in package roslang
 No Makefile in package roslang
[rosmake-6] Starting >>> rosmaster [ make
]

[rosmake-6] Finished <<< rosmaster ROS_NOBUILD in package
rosmaster

[rosmake-6] Starting >>> xmlrpcpp [ make
]

[rosmake-6] Finished <<< xmlrpcpp ROS_NOBUILD in package
xmlrpcpp

[rosmake-2] Starting >>> rosconsole [ make
]

[rosmake-2] Finished <<< rosconsole ROS_NOBUILD in package
rosconsole
[rosmake-7] Starting >>> rospy [ make
]

[rosmake-2] Starting >>> roscpp [ make
]

[rosmake-7] Finished <<< rospy ROS_NOBUILD in package
rospy

[rosmake-2] Finished <<< roscpp ROS_NOBUILD in package
roscpp

[rosmake-2] Starting >>> rosout [ make
]

[rosmake-2] Finished <<< rosout ROS_NOBUILD in package
rosout

[rosmake-2] Starting >>> roslaunch [ make
]

[rosmake-2] Finished <<< roslaunch ROS_NOBUILD in package roslaunch
 No Makefile in package roslaunch
[rosmake-7] Starting >>> rostest [ make
]

[rosmake-7] Finished <<< rostest ROS_NOBUILD in package
rostest

[ rosmake ]
Results:

[ rosmake ] Built 14 packages with 0
failures.

[ rosmake ] Summary output to
directory

[ rosmake ]
/u/tfoote/.ros/rosmake/rosmake_output-20101008-100255

done. Now, type 'source /tmp/t/setup.sh' to set up your environment.
Add that to the bottom of your ~/.bashrc to set it up every time.

tfoote at bgt:/tmp$ rosinstall t
rosinstall operating on /tmp/t from specifications in rosinstall files
/tmp/t/.rosinstall
Installing /tmp/t/ccny-ros-pkg to
http://robotics.ccny.cuny.edu/git/ccny-ros-pkg.git ICRA2011
Already up-to-date.
other config element is a ros path /opt/ros/cturtle/ros
other config element is not a ros path /opt/ros/cturtle/stacks
other config element is a ros path /opt/ros/cturtle/ros
other config element is not a ros path /opt/ros/cturtle/stacks
Bootstraping ROS build
[ rosmake ] Packages requested are:
['rostest']

[ rosmake ] Logging to
directory/u/tfoote/.ros/rosmake/rosmake_output-20101008-100309

[ rosmake ] Expanded args ['rostest'] to:
['rostest']

[ rosmake ] Generating Install Script using rosdep then executing. This may
take a minute, you will be prompted for permissions. . .
executing this script:
 set -o errexit
#No Packages to install
[ rosmake ] rosdep successfully installed all system
dependencies

[rosmake-0] Starting >>> roslib [ make
]

[rosmake-0] Finished <<< roslib ROS_NOBUILD in package
roslib

[rosmake-0] Starting >>> rosclean [ make
]

[rosmake-0] Finished <<< rosclean ROS_NOBUILD in package
rosclean

[rosmake-0] Starting >>> rosgraph [ make
]

[rosmake-0] Finished <<< rosgraph ROS_NOBUILD in package
rosgraph

[rosmake-5] Starting >>> roslang [ make
]

[rosmake-5] Finished <<< roslang ROS_NOBUILD in package roslang
 No Makefile in package roslang
[rosmake-5] Starting >>> rospy [ make
]

[rosmake-5] Finished <<< rospy ROS_NOBUILD in package
rospy

[rosmake-1] Starting >>> rosmaster [ make
]

[rosmake-1] Finished <<< rosmaster ROS_NOBUILD in package
rosmaster

[rosmake-2] Starting >>> xmlrpcpp [ make
]

[rosmake-2] Finished <<< xmlrpcpp ROS_NOBUILD in package
xmlrpcpp

[rosmake-2] Starting >>> rosconsole [ make
]

[rosmake-2] Finished <<< rosconsole ROS_NOBUILD in package
rosconsole
[rosmake-2] Starting >>> roscpp [ make
]

[rosmake-2] Finished <<< roscpp ROS_NOBUILD in package
roscpp

[rosmake-2] Starting >>> rosout [ make
]

[rosmake-2] Finished <<< rosout ROS_NOBUILD in package
rosout

[rosmake-6] Starting >>> roslaunch [ make
]

[rosmake-6] Finished <<< roslaunch ROS_NOBUILD in package roslaunch
 No Makefile in package roslaunch
[rosmake-6] Starting >>> rostest [ make
]

[rosmake-6] Finished <<< rostest ROS_NOBUILD in package
rostest

[ rosmake ]
Results:

[ rosmake ] Built 14 packages with 0
failures.

[ rosmake ] Summary output to
directory

[ rosmake ]
/u/tfoote/.ros/rosmake/rosmake_output-20101008-100309

done. Now, type 'source /tmp/t/setup.sh' to set up your environment.
Add that to the bottom of your ~/.bashrc to set it up every time.

tfoote at bgt:/tmp$ git --version
git version 1.7.0.4
}}}

On Wed, Oct 6, 2010 at 6:22 PM, Ivan Dryanovski
<ivan.dryanovski at gmail.com>wrote:

> I'm sorry to go back to this thread, but I am still having issues with
> the rosinstall tool.
>
> I have the following lines in my rosconfig file that I am passing to
> ROS Install:
>
> - git:
>    uri: http://robotics.ccny.cuny.edu/git/ccny-ros-exp.git
>    version: master
>    local-name: ccny-ros-exp
> - git:
>    uri: http://robotics.ccny.cuny.edu/git/ccny-ros-pkg.git
>    version: ICRA2011
>    local-name: ccny-ros-pkg
>
> The first on works fine. When the installer attempts to check out the
> he second one, it produces this error:
>
> fatal: git checkout: updating paths is incompatible with switching
> branches/forcing
> Did you intend to checkout 'ICRA2011' which can not be resolved as commit?
> ERROR: Failed to install tree '/home/idryanov/icra2011_ccny/ccny-ros-pkg'
>  vcs not setup correctly.
>
> A quick search on the issue gives me this:
>
>
> http://www.skrinakcreative.com/wp/2008/11/fatal-git-checkout-problem-resolved/
>
> The comments suggest pulling first, and then checking out the desired
> branch. How does rosinstall handle it?
> Any help would be appreciated
>
> Ivan
>
> On Wed, Sep 29, 2010 at 7:54 PM, Brian Gerkey <gerkey at willowgarage.com>
> wrote:
> > On Wed, Sep 29, 2010 at 2:57 PM, Ivan Dryanovski
> > <ivan.dryanovski at gmail.com> wrote:
> >> I ran into an svn versioning issue.
> >>
> >> I am using the following command to get the svn revisions:
> >>
> >> ./unwrap_externals.py
> >> https://code.ros.org/svn/ros-pkg/externals/latest/ >
> >> icra2011_dryanovski.rosconfig
> >
> > You probably want to unwrap the cturtle external instead, e.g.:
> >
> > ./unwrap_externals.py
> > https://code.ros.org/svn/ros-pkg/externals/distro/cturtle/all >
> > icra2011_dryanovski.rosconfig
> >
> > In general, you'd want to unwrap the external from which you'd checked
> > out the code.
> >
> > Now that I think about it, there's a potential mismatch between the
> > version currently pointed to by the external and the version that was
> > used.    A while back, I wrote a script to rummage over your
> > ROS_PACKAGE_PATH, and produce a rosinstall file that would check out
> > the same stuff that you currently have checked out (assuming that it
> > all came from SVN).  I can't find that script now, but it would be
> > easy to reproduce.
> >
> > But still we're talking about doing work from a source-based install,
> > which is (hopefully) becoming less common as the binary packages are
> > gaining traction (at least for people running Ubuntu).
> >
> > It seems like, to record the software that makes up your experimental
> > environment, you need to know:
> >  * the versions of all released stacks in use
> >  * the svn/git/bzr/hg URI and revision/branch/hash info for everything
> else.
> > (To be complete, you could record the version of the Linux kernel and
> > so on, but we have to bottom out somewhere.)  So perhaps we need a
> > tool that gathers that information....
> >
> >        brian.
> > _______________________________________________
> > ros-users mailing list
> > ros-users at code.ros.org
> > https://code.ros.org/mailman/listinfo/ros-users
> >
> _______________________________________________
> ros-users mailing list
> ros-users at code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>

-- 
Tully Foote
Systems Engineer
Willow Garage, Inc.
tfoote at willowgarage.com
(650) 475-2827
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-users/attachments/20101008/96e98f28/attachment-0003.html>