<div dir="ltr">I ran the docker image b4e7907c1ad7 (which is the state directly after the `apt-get update`) and `apt-cache showpkg apt-src` can't locate the package. Since `apt-get` neither returned an error code nor printed any warning I don't think the build farm can catch this.<div><br></div><div>Cheers,</div><div>- Dirk</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 20, 2016 at 9:45 AM, Tully Foote via ros-release <span dir="ltr"><<a href="mailto:ros-release@lists.ros.org" target="_blank">ros-release@lists.ros.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Indeed please do open a ticket on ros_buildfarm. This looks like the apt-get update somehow failed or the loading of the apt-cache in the python process failed for this instance such that 'apt-src' was not in the package database. (Giving the KeyError). It's a dependency that we inject [1] that helps us build the sourcedebs [2] <div><br></div><div>Tully<br><div><div><br></div><div>[1] <a href="https://github.com/ros-infrastructure/ros_buildfarm/blob/master/scripts/release/create_binarydeb_task_generator.py#L60" target="_blank">https://github.com/ros-infrastructure/ros_buildfarm/blob/master/scripts/release/create_binarydeb_task_generator.py#L60</a></div><div>[2] <a href="https://github.com/ros-infrastructure/ros_buildfarm/blob/master/ros_buildfarm/binarydeb_job.py#L117" target="_blank">https://github.com/ros-infrastructure/ros_buildfarm/blob/master/ros_buildfarm/binarydeb_job.py#L117</a><br><div><div><br></div></div></div></div></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 20, 2016 at 5:57 AM, Vincent Rabaud via ros-release <span dir="ltr"><<a href="mailto:ros-release@lists.ros.org" target="_blank">ros-release@lists.ros.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>And it magically got fixed: <a href="http://build.ros.org/job/Ibin_uT32__roslisp__ubuntu_trusty_i386__binary/" target="_blank">http://build.ros.org/job/Ibin_uT32__roslisp__ubuntu_trusty_i386__binary/</a></div><div>When getting that kind of weird system error, the rule of thumb is to wait for the re-trigger to see if it happens twice :)</div><div>You should probably still open up an issue so that it does not happen again: <a href="https://github.com/ros-infrastructure/ros_buildfarm/issues" target="_blank">https://github.com/ros-infrastructure/ros_buildfarm/issues</a> Thx !</div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 20, 2016 at 9:31 AM, Georg Bartels via ros-release <span dir="ltr"><<a href="mailto:ros-release@lists.ros.org" target="_blank">ros-release@lists.ros.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear fellow ROS maintainers,<br>
<br>
I have a failing Indigo build of roslisp which puzzles me. Here is the link to the failing build:<br>
<br>
<<a href="http://build.ros.org/job/Ibin_uT32__roslisp__ubuntu_trusty_i386__binary/4/" rel="noreferrer" target="_blank">http://build.ros.org/job/Ibin_uT32__roslisp__ubuntu_trusty_i386__binary/4/</a>><br>
<br>
<br>
It seems that some script cannot find the package 'apt-src'. This surprises me because that package is not part of my dependencies, and seems like a basic ubuntu package to me. Also, a build of the very same release succeeded on Friday. Other builds of the same roslisp release work fine on Indigo, Jade, and Kinetic...<br>
<br>
Can anybody help me figure out how to fix this? I'd be happy for any help! Thanks in advance. :)<br>
<br>
Cheers,<br>
Georg.<br>
_______________________________________________<br>
ros-release mailing list<br>
<a href="mailto:ros-release@lists.ros.org" target="_blank">ros-release@lists.ros.org</a><br>
<a href="http://lists.ros.org/mailman/listinfo/ros-release" rel="noreferrer" target="_blank">http://lists.ros.org/mailman/listinfo/ros-release</a><br>
</blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
ros-release mailing list<br>
<a href="mailto:ros-release@lists.ros.org" target="_blank">ros-release@lists.ros.org</a><br>
<a href="http://lists.ros.org/mailman/listinfo/ros-release" rel="noreferrer" target="_blank">http://lists.ros.org/mailman/listinfo/ros-release</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
ros-release mailing list<br>
<a href="mailto:ros-release@lists.ros.org">ros-release@lists.ros.org</a><br>
<a href="http://lists.ros.org/mailman/listinfo/ros-release" rel="noreferrer" target="_blank">http://lists.ros.org/mailman/listinfo/ros-release</a><br>
<br></blockquote></div><br></div>