<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">I'd suggest an audit that looks for the
same package being include in multiple repo's lst files, but with
a different version.<br>
<br>
Based on <a class="moz-txt-link-freetext" href="https://storyboard.openstack.org/#!/story/2003462">https://storyboard.openstack.org/#!/story/2003462</a>, we
would also want to compare RPM vs SRPM versions to ensure our
compiled SRPMS are never masked.<br>
<br>
Scott.<br>
<br>
<br>
On 18-08-22 10:47 AM, McKenna, Jason wrote:<br>
</div>
<blockquote type="cite"
cite="mid:EF69F8938994714CB4694DB8872C48E6CE1EA564@ALA-MBD.corp.ad.wrs.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-CA">Hi folks (especially
Erich, Scott, Marcela, or anyone else working on the
download tools),<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">We’d like to support
per-repo .lst files used by download_mirrors.sh. This would
decouple the stx-tools repo from all the code repos.
Changes (for example, to uprev a package) would only affect
a single repo rather than both the code repo and stx-tools.
This would also allow individual entities to integrate their
own repos into products, or to pick-and-choose versions of
the different repos to build into products. My initial work
would just be to support per-repo .lst files as an option,
with actually breaking the existing .lst files up among the
repos as a later task. My initial thoughts would be that
.src.rpms would be in per-repo lst files. Build-time and
run time requirement binary rpms are tougher to nail down,
as they might be used by different repos, and we don’t want
one repo asking for one version, and a second repo asking
for a different version, etc.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">Before I start working
too deep on this, does anyone have any thoughts, or work in
progress along these lines?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">-Jason<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
</div>
<!--'"--><br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Starlingx-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Starlingx-discuss@lists.starlingx.io">Starlingx-discuss@lists.starlingx.io</a>
<a class="moz-txt-link-freetext" href="http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss">http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>