[ros-users] rosinstall script creating rosinstall local branches for git repositories

[Tully Foote]

William,
rosinstall requires ros to be defined in the rosinstall file.  It does not
look at your environment anymore for that was very fragile and caused
problems when updating if you weren't very careful about cleaning up your
environment.

Based on your environment the following will work if you used rosinstall or
debians to install into /opt/ros


rosinstall automow /opt/ros/cturtle
http://github.com/wjwwood/au-automow/raw/master/automow.rosconfig

If you do not have a .rosinstall file in /opt/ros/cturtle you can add one
with this content
{{{
- other:
    local-name: /opt/ros/cturtle/ros
- other:
    local-name: /opt/ros/cturtle/stacks
}}}
Followed by `rosinstall automow /opt/ros/cturtle

Or you can directly insert the above entries into automow/.rosinstall
 followed by `rosinstall automow` to regenerate your setup file.

Re rosinstall and git: the branches are tracking correctly in rosinstall
version 0.5.5 which is already out and in r10703 I have made the branch name
default to master.  That will go out in 0.5.6  All git clones create local
branches of the remote branches, the naming is just a cosmetic thing as long
as the tracking is setup correctly.

Tully

On Thu, Aug 12, 2010 at 3:44 PM, William Woodall <wjwwood at gmail.com> wrote:

> 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?
>
> Additionally, at the end of rosinstall I now get this error:
>
> ...
> 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 .
> http://www.ros.org/rosinstalls/boxturtle_ros.rosinstall'. 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.
> ...
>
> So then I run export to check and this is what I get:
>
> ~$ export
> ...
> declare -x
> PATH="/opt/ros/cturtle/ros/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
> declare -x PWD="/home/mowbot"
> declare -x PYTHONPATH=":/opt/ros/cturtle/ros/core/roslib/src"
> declare -x ROS_MASTER_URI="http://localhost:11311"
> declare -x ROS_PACKAGE_PATH="/opt/ros/cturtle/stacks"
> declare -x ROS_ROOT="/opt/ros/cturtle/ros"
> ...
>
> 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.
>
> 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.
>
> 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.
>
> I appreciate any insight into how I should be setting up my working
> environment differently or to why I am getting errors from rosinstall.
>
> Thanks,
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>  William Woodall
> Graduate Software Engineering
> Auburn University
> w at auburn.edu
> wjwwood at gmail.com
> 256-345-9938
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
> On Wed, Aug 11, 2010 at 8:21 PM, Tully Foote <tfoote at willowgarage.com>wrote:
>
>> Dejan,
>> 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.
>>
>> Tully
>>
>>
>> On Wed, Aug 4, 2010 at 3:18 PM, Dejan Pangercic <
>> dejan.pangercic at gmail.com> wrote:
>>
>>> Hi there,
>>>
>>> I am using rosinstall script from pypi, version 0.5.2. After updating
>>> my installation today I noticed that all git repositories specified in
>>> my overlay file have been cloned to the local branches named
>>> "rosinstall" as oppose to e.g. branch "master".
>>> In my POV this should be considered as a bug right?
>>>
>>> cheers, D.
>>>
>>> --
>>> MSc. Dejan Pangercic
>>> PhD Student/Researcher
>>> Intelligent Autonomous Systems Group
>>> Technische Universität München
>>> Telephone: +49 (89) 289-26908
>>> E-Mail: dejan.pangercic at cs.tum.edu
>>> WWW: http://ias.cs.tum.edu/people/pangercic
>>> _______________________________________________
>>> 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
>>
>> _______________________________________________
>> 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/20100813/7eec7572/attachment-0004.html>