Dear Wim,
The command to branch is just:
> bzr branch lp:sr-ros-interface/stable
I thought the process was branch the tip of dev-branch, tag it with tag_name and push it to uri+tag_name. (sorry I can't remember the names of those variables in the _rules as I'm at home and don't have access to my code).
To branch the code, it should work (it will produce a warning stating that you won't be able to push to the parent branch).
Cheers,
Ugo
On Wed, Mar 30, 2011 at 7:33 PM, Wim Meeussen
<meeussen@willowgarage.com> wrote:
> This is the first bzr stack our pre-release system has attempted, so there
> may be an issue there. We'll look into it.
Okay, I think the bazaar pipeline is up now. I resolved the following issues:
* bzr support was not fully implemented in our rosdistro parser
* the shadow robot entry in the rosdistro file used an invalid tag
"dev", and was missing "deb-branch" and "disto-branch" tags.
* bzr was not installed in the chroot
However, I think your bzr url/branch is not set up correcty. When I run:
bzr branch -r lp:sr-ros-interface/stable
bzr+ssh://bazaar.launchpad.net/~shadowrobot/sr-ros-interface
I get:
Launchpad user 'wim' doesn't have a registered SSH key
Permission denied (publickey).
bzr: ERROR: Connection closed: Unexpected end of message. Please check
connectivity and permissions, and report a bug if problems persist.
You might have to specify a separate uri for anonymous access (see the
git examples in the rosdisto file).
We still need to resolve an issue with the host certificate of your bzr host.
Wim
--
--
Wim Meeussen
Willow Garage Inc.
<http://www.willowgarage.com)
--
Ugo Cupcic | Shadow Robot Company |
ugo@shadowrobot.com Software Engineer | 251 Liverpool Road |
need a Hand? | London N1 1LX | +44 20 7700 2487
http://www.shadowrobot.com/hand/ @shadowrobot