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@willowgarage.com> wrote:
> On Wed, Sep 29, 2010 at 2:57 PM, Ivan Dryanovski
> <ivan.dryanovski@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@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>