I fixed catkin according to your suggestion (the logic was actually there but buggy) and we now have all of wet, thx ! Let's get dry stuff now :)

On Wed, Apr 11, 2012 at 2:01 AM, Tully Foote <tfoote@willowgarage.com> wrote:
Thanks Vincent.  We should probably patch it pull from the online targets.yaml file to avoid needing to patch for each release.  With the option to override on the command line of course.  The file to read is https://github.com/ros/rosdistro/blob/master/releases/targets.yaml

There's an example of reading targets.yaml here: https://github.com/willowgarage/catkin-debs/blob/master/scripts/jenkins/create_all.py

I've updated the fuerte status to pull from targets.yaml as well.  Next run it should list precise as well.  

Tully


On Wed, Apr 11, 2012 at 12:45 AM, Vincent Rabaud <vrabaud@willowgarage.com> wrote:
Awesome, thx !
I modified catkin so that catkin-generate-debian also has precise as a default.

Until the new catkin release, to create the precise tags for a new wet release, you can just use:
git catkin-generate-debian fuerte --distros lucid oneiric precise

Any other place where that should be changed ?

On Tue, Apr 10, 2012 at 5:56 PM, Tully Foote <tfoote@willowgarage.com> wrote:
A much easier solution is to simply rerelease using the debian inc number.  Or if a new release is on it's way out just release as usual.  

That will automatically do the rosdep resolution, not have an issue with source deb versions, and create the tags for you.  

Tully


On Tue, Apr 10, 2012 at 5:18 PM, Tully Foote <tfoote@willowgarage.com> wrote:
Hey all, 


At Vincent's prompting I have added precise as a target because we are now coming up on it's release date and everything we depend on should be frozen.   I have updated our repos to support precise debs.  

There is still a bunch to do for dry stacks, but wet is more or less going forward.  

To get a wet style precise deb for catkin I did the following:
Manually updated the changelog to reflect precise, committed it and tagged it, and pushed it.  (If you have rosdeps which change between the releases they will be required to be updated in the control file.)
Manually triggered the sourcedeb, (it will fail because it can't reupload the other distros)
Manually triggered the binarydeb. (It won't autostart due to above failure)

I will hold off on adding precise to the dry builds.  And precise support will not gate the Fuerte release, but we can start to make progress on it. 

Tully

--
Tully Foote
Systems Engineer
Willow Garage, Inc.
tfoote@willowgarage.com
(650) 475-2827



--
Tully Foote
Systems Engineer
Willow Garage, Inc.
tfoote@willowgarage.com
(650) 475-2827

_______________________________________________
Ros-release mailing list
Ros-release@code.ros.org
https://code.ros.org/mailman/listinfo/ros-release





--
Tully Foote
Systems Engineer
Willow Garage, Inc.
tfoote@willowgarage.com
(650) 475-2827