<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Dec 3, 2012 at 10:30 PM, Daniel Stonier <span dir="ltr"><<a href="mailto:d.stonier@gmail.com" target="_blank">d.stonier@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br><br><div class="gmail_quote">On 4 December 2012 12:38, Jack O'Quin <span dir="ltr"><<a href="mailto:jack.oquin@gmail.com" target="_blank">jack.oquin@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I prefer to run pre-release tests before releasing a stack.<div><br></div><div>How can I do that now?</div><div class="gmail_extra"><div><div><br></div></div></div></blockquote><div><br></div><div>I haven't been able to do that - first tried a couple of weeks ago, but not sure about the current status. At the very least, I think to get a dry stack showing up in the drop down you'd need your entry in <a href="https://code.ros.org/svn/release/trunk/distros/fuerte.rosdistro" target="_blank">https://code.ros.org/svn/release/trunk/distros/fuerte.rosdistro</a>, not at <a href="http://github.com/ros/rosdistro" target="_blank">github.com/ros/rosdistro</a>.</div>
<div> </div></div></blockquote><div>That's correct for dry stacks it's still in the release project on <a href="http://code.ros.org">code.ros.org</a>. </div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_extra"><div><div><br><div class="gmail_quote">On Mon, Dec 3, 2012 at 4:34 PM, Daniel Stonier <span dir="ltr"><<a href="mailto:d.stonier@gmail.com" target="_blank">d.stonier@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p>Ive been releasing dry stacks using the olde release svn repo and release-legacy method.</p>
<p>I believe updating your information in rosdistro is only for catkin stacks. You can see the output below is calling rosinstall --catkin.</p>
<p></p><div><div>On Dec 4, 2012 6:38 AM, "Jack O'Quin" <<a href="mailto:jack.oquin@gmail.com" target="_blank">jack.oquin@gmail.com</a>> wrote:<br>
><br>
> I would like to release camera_info_manager_py, a new Python implementation of the camera info manager interface for both Fuerte and Groovy. It remains a dry stack, for now, so I can maintain the same sources for both. <br>
><br>
> But, I am having trouble following the instructions correctly.<br>
><br>
> First, I went to the Fuerte pre-release page:<br>
><br>
> <a href="http://packages.ros.org/web/prerelease/create_job/fuerte" target="_blank">http://packages.ros.org/web/prerelease/create_job/fuerte</a><br>
><br>
> Naturally, the new stack was not listed there. So, I followed the link to:<br>
><br>
> <a href="http://www.ros.org/wiki/regression_tests" target="_blank">http://www.ros.org/wiki/regression_tests</a><br>
><br>
> Based on that, I added stanzas for the new camera_info_manager_py to the rosdistro repository:<br>
><br>
> <a href="https://github.com/jack-oquin/rosdistro/commit/0abfa392044bcb0bc9155c21c5bd6d15ba1132fe" target="_blank">https://github.com/jack-oquin/rosdistro/commit/0abfa392044bcb0bc9155c21c5bd6d15ba1132fe</a><br>
><br>
> Since this component has not yet been released, I copied some other entries, setting the version to null. Maybe that was a bad guess.<br>
><br>
> That update was merged, and now camera_info_manager_py appears as a pre-release test component for Groovy, but not Fuerte (which I had also expected).<br>
><br>
> So, I tried to run a Groovy pre-release test on it, but the checkout failed. Perhaps, I used the wrong "version:" setting.<br>
><br>
> <a href="http://jenkins.willowgarage.com:8080/job/prerelease-groovy-camera_info_manager_py/ARCH_PARAM=amd64,UBUNTU_PARAM=precise,label=prerelease/2/" target="_blank">http://jenkins.willowgarage.com:8080/job/prerelease-groovy-camera_info_manager_py/ARCH_PARAM=amd64,UBUNTU_PARAM=precise,label=prerelease/2/</a><br>
><br>
> The failure appear here, I think:<br>
><br>
> Creating rosinstall file for repo list<br>
> Using latest release distro file to download repositories<br>
> rosinstall file for all repositories: <br>
> - git: {local-name: camera_info_manager_py, uri: 'git://<a href="http://github.com/jack-oquin/camera_info_manager_py.git" target="_blank">github.com/jack-oquin/camera_info_manager_py.git</a>',<br>
> version: release/camera_info_manager_py}<br>
><br>
> Install repo list from source<br>
> Executing command 'rosinstall /tmp/test_repositories/src_repository /home/rosbuild/hudson/workspace/prerelease-groovy-camera_info_manager_py/ARCH_PARAM/amd64/UBUNTU_PARAM/precise/label/prerelease/repo.rosinstall --catkin'<br>
> rosinstall operating on /tmp/test_repositories/src_repository from specifications in rosinstall files /home/rosbuild/hudson/workspace/prerelease-groovy-camera_info_manager_py/ARCH_PARAM/amd64/UBUNTU_PARAM/precise/label/prerelease/repo.rosinstall<br>
> (Over-)Writing /tmp/test_repositories/src_repository/.rosinstall<br>
> [camera_info_manager_py] Installing git://<a href="http://github.com/jack-oquin/camera_info_manager_py.git" target="_blank">github.com/jack-oquin/camera_info_manager_py.git</a> (version release/camera_info_manager_py) to /tmp/test_repositories/src_repository/camera_info_manager_py<br>
> Exception caught during install: Error processing 'camera_info_manager_py' : [camera_info_manager_py] Checkout of git://<a href="http://github.com/jack-oquin/camera_info_manager_py.git" target="_blank">github.com/jack-oquin/camera_info_manager_py.git</a> version release/camera_info_manager_py into /tmp/test_repositories/src_repository/camera_info_manager_py failed.<br>
><br>
><br>
><br>
> I could use some pointers on how to do this job properly with the new tools.<br>
> -- <br>
> joq<br>
><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>
><p></p>
</blockquote></div><br><br clear="all"><span class="HOEnZb"><font color="#888888"><div><br></div></font></span></div></div><span class="HOEnZb"><font color="#888888"><span><font color="#888888">-- <br> joq<br>
</font></span></font></span></div><span class="HOEnZb"><font color="#888888">
</font></span></blockquote></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><div><br></div>-- <br>Phone : +82-10-5400-3296 (010-5400-3296)<br>Home: <a href="http://snorriheim.dnsdojo.com/" target="_blank">http://snorriheim.dnsdojo.com/</a><br>
<div>Yujin R&D: <a href="http://rnd.yujinrobot.com/" target="_blank">http://rnd.yujinrobot.com/<br>
</a><br></div><br>
</font></span><br>_______________________________________________<br>
Ros-release mailing list<br>
<a href="mailto:Ros-release@code.ros.org">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><br clear="all"><div><br></div>-- <br>Tully Foote<br><a href="mailto:tfoote@willowgarage.com" target="_blank">tfoote@willowgarage.com</a><br>(650) 475-2827<br>
</div>