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 <a href="https://github.com/ros/rosdistro/blob/master/releases/targets.yaml" target="_blank">https://github.com/ros/rosdistro/blob/master/releases/targets.yaml</a><div>
<br></div><div>There's an example of reading targets.yaml here: <a href="https://github.com/willowgarage/catkin-debs/blob/master/scripts/jenkins/create_all.py" target="_blank">https://github.com/willowgarage/catkin-debs/blob/master/scripts/jenkins/create_all.py</a><br>
<br>I've updated the fuerte status to pull from targets.yaml as well. Next run it should list precise as well. <br><br>Tully<br><br><div class="gmail_quote">On Wed, Apr 11, 2012 at 12:45 AM, Vincent Rabaud <span dir="ltr"><<a href="mailto:vrabaud@willowgarage.com" target="_blank">vrabaud@willowgarage.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Awesome, thx !<div>I modified catkin so that catkin-generate-debian also has precise as a default.</div><div><br></div><div>Until the new catkin release, to create the precise tags for a new wet release, you can just use:</div>
<div>git catkin-generate-debian fuerte --distros lucid oneiric precise</div><div><br></div><div>Any other place where that should be changed ?</div><div><br><div class="gmail_quote"><div><div>On Tue, Apr 10, 2012 at 5:56 PM, Tully Foote <span dir="ltr"><<a href="mailto:tfoote@willowgarage.com" target="_blank">tfoote@willowgarage.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>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. <div>
<br></div><div>That will automatically do the rosdep resolution, not have an issue with source deb versions, and create the tags for you. </div><span><font color="#888888">
</font></span><div><span><font color="#888888"><div><br></div></font></span><div><span><font color="#888888">Tully</font></span><div><div><br><br><div class="gmail_quote">On Tue, Apr 10, 2012 at 5:18 PM, Tully Foote <span dir="ltr"><<a href="mailto:tfoote@willowgarage.com" target="_blank">tfoote@willowgarage.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hey all, <div><br></div><div>In good news we have built one precise deb already! <a href="http://hudson.willowgarage.com:8080/job/ros-fuerte-catkin_binarydeb_precise_amd64/1/" target="_blank">http://hudson.willowgarage.com:8080/job/ros-fuerte-catkin_binarydeb_precise_amd64/1/</a></div>
<div><br></div><div>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. </div>
<div><br></div><div>There is still a bunch to do for dry stacks, but wet is more or less going forward. </div><div><br></div><div>To get a wet style precise deb for catkin I did the following:</div><div>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.)</div>
<div>Manually triggered the sourcedeb, (it will fail because it can't reupload the other distros)</div><div>Manually triggered the binarydeb. (It won't autostart due to above failure)</div><div><br></div><div>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. </div>
<span><font color="#888888">
<div><br></div><div>Tully<br clear="all"><div><br></div>-- <br>Tully Foote<br>Systems Engineer<br>Willow Garage, Inc.<br><a href="mailto:tfoote@willowgarage.com" target="_blank">tfoote@willowgarage.com</a><br><a href="tel:%28650%29%20475-2827" value="+16504752827" target="_blank">(650) 475-2827</a><br>
</div>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br>Tully Foote<br>Systems Engineer<br>Willow Garage, Inc.<br><a href="mailto:tfoote@willowgarage.com" target="_blank">tfoote@willowgarage.com</a><br>
<a href="tel:%28650%29%20475-2827" value="+16504752827" target="_blank">(650) 475-2827</a><br>
</div></div></div></div>
<br></div></div>_______________________________________________<br>
Ros-release mailing list<br>
<a href="mailto:Ros-release@code.ros.org" target="_blank">Ros-release@code.ros.org</a><br>
<a href="https://code.ros.org/mailman/listinfo/ros-release" target="_blank">https://code.ros.org/mailman/listinfo/ros-release</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Tully Foote<br>Systems Engineer<br>Willow Garage, Inc.<br><a href="mailto:tfoote@willowgarage.com" target="_blank">tfoote@willowgarage.com</a><br><a href="tel:%28650%29%20475-2827" value="+16504752827" target="_blank">(650) 475-2827</a><br>
</div>