<div dir="ltr">I have improved the cycle detection to spit out an even smaller set of package names: <a href="http://jenkins.ros.org/job/_hydro-reconfigure-release-jobs/486/console">http://jenkins.ros.org/job/_hydro-reconfigure-release-jobs/486/console</a><div>
Based on that I have filled a ticket against cram_core: <a href="https://github.com/cram-code/cram_core/issues/23">https://github.com/cram-code/cram_core/issues/23</a></div><div>I assume it will be fixed soon - otherwise we could still disable these packages temporarily.</div>
<div><br></div><div>- Dirk</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Apr 14, 2014 at 9:15 AM, Austin Hendrix <span dir="ltr"><<a href="mailto:legotown@aol.com" target="_blank">legotown@aol.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">It looks like the _hydro-reconfigure-release-jobs job has been failing for the past three days, due to a dependency loop in the CRAM packages: <a href="http://jenkins.ros.org/job/_hydro-reconfigure-release-jobs/485/console" target="_blank">http://jenkins.ros.org/job/_hydro-reconfigure-release-jobs/485/console</a><div>
<br></div><div>Can someone on the CRAM team or at OSRF take a look at this please? It’s blocking releases of new packages.</div><div><br></div><div>Thanks,</div><div>-Austin</div></div><br>_______________________________________________<br>

ros-release mailing list<br>
<a href="mailto:ros-release@code.ros.org">ros-release@code.ros.org</a><br>
<a href="http://lists.ros.org/mailman/listinfo/ros-release" target="_blank">http://lists.ros.org/mailman/listinfo/ros-release</a><br>
<br></blockquote></div><br></div>