<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">The new upstream repo should be
introduced 24 hours before any lst files that reference content
from that repo. <br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">That should give CENGN to mirror the
new repo. Once cengn has a copy of the version we want, it no
longer matters if upstream changes the version.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Scott</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 2020-01-14 3:22 p.m., Miller, Frank
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:A43F4E51FB41274EA099B52A6EE25DC19DD30AA4@ALA-MBD.corp.ad.wrs.com"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><span
style="mso-list:Ignore">2)<span style="font:7.0pt "Times
New Roman"">
</span></span></span><!--[endif]--><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Identify
how we can prevent a build failure in the future when kata puts
out a new version and deletes the 1.9.3-8.1 version. Is there a
way the StarlingX build or CENGN mirror can cache this version
so we can control when we move to a new version?</span></blockquote>
<p><br>
</p>
</body>
</html>