<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 28 July 2016 at 15:04, Maxin B. John <span dir="ltr"><<a href="mailto:maxin.john@intel.com" target="_blank">maxin.john@intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":2f5" class="a3s aXjCH m15631d6668b51e0f">Recipes that use DEBIAN_MIRROR in SRC_URI are setting themselves up for failure<br>
as the Debian mirror network only stores active releases, so once a version we<br>
use isn't in oldstable/stable/testing/unstable then it will be removed.<br>
<br>
The solution here is to use the <a href="http://snapshot.debian.org" rel="noreferrer" target="_blank">snapshot.debian.org</a> service for the SRC_URI,<br>
and set UPSTREAM_CHECK_URI to the relevant pool directory on DEBIAN_MIRRORS.<br>
This way we get a stable SRC_URI but still have new upstream release checking.<br></div></blockquote></div><br>Will these all apply to master too?</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>