On Thursday 16 September 2010 10:03:29 Ruben Smits wrote:
> Hi ros-developers,
>
> I'm trying the new release packages to release a first version of our
> orocos_toolchain_ros stack.
...

I'm honoured that the ros developers choose the orocos-dev mailing list for
their daily discussions :-)

Peter

Please ignore this e-mail, it was (obviously) send to the wrong mailinglist :s

Ruben

On Thursday 16 September 2010 10:03:29 Ruben Smits wrote:
> Hi ros-developers,
>
> I'm trying the new release packages to release a first version of our
> orocos_toolchain_ros stack.
>
> Documentation is very well, the release almost succeeded. It failed when
> the process wanted to do:
>
> creating new tarball directory
> svn mkdir --parents -m creating new tarball directory
> https://code.ros.org/svn/release/download/stacks/orocos_toolchain_ros/oroco
> s_toolchain_ros-0.1.0
>
> Which is fairly reasonable since the remaining steps are:
>
> # checkin the tarball
> copy_to_server(name, version, tarball, control)
>
> # cleanup temporary file
> os.remove(tarball)
>
> # update the rosdistro file
> if not repair:
> update_rosdistro_yaml(name, version, distro_file)
> checkin_distro_file(name, version, distro_file)
>
> # trigger source deb system
> trigger_hudson_source_deb(name, version, distro)
>
> Which are all related to changing stuff on code.ros.org? Would it be hard
> to make the tarball directory configurable? And probably you guys do not
> want to have me checkin the adapted distro_file? We have a local hudson
> running, so we could also do the deb building ourselves if this is made
> configurable.
>
> Anyway, it did create the tarball and automatically created the svn-tags,
> so I'll start from that.
>
> Ruben