<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I did not query Sandro about why he did the update the way he did. He<br>
knows far more then I do about the various build processes of the<br>
various packages and oVirt, an I tend to trust his judgement.<br></blockquote><div><br></div><div>But we should (CCing Sandro). I do not see any mistrust here. Even if we can make our infra behave abnormal way there is no warranty that such RPM will not get wild (or be prevented from going out). We cannot clear caches of all of our users. I even not sure how repoman will behave when oVirt releases are composed in this case, it does not compare RPM content and assumes that they are immutable as designed. </div><div><br></div><div>So makes sense to check this.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This can take time, every maintainer has his own (bad) habits, and not<br>
everyone will agree to do what we want (Some downright regard oVirt as<br>
a "downstream" consumer and refuse to do anything that they regard as<br>
oVirt-specific!).<br></blockquote><div><br></div><div>This is correct. So sounds like we need to send an announcement that RPM versions are supposed to change when content change and see who have issues with this and try to analyse why and help if needed.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
In the meantime we need to be resilient to such issues if we can. We<br>
can`t just let everything fail while we try to "fix the world".<br></blockquote><div><br></div><div>Meantime if we need to support this we have to disable caching for everything minus repos we know follow the rules. But I would insist that this is not normal situation and we need to have an idea of how we notify people to fix it and how we can help.</div><div><br></div><div>And we are not fixing the world. yum is there for a long time and world is ok. It is just we have problem in our stuff we need to fix so we can use all the systems the world designed for us.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Also, next time around, we could be seeing similar caching issues with<br>
a non-yum/rpm file, so its good to have a deep understanding of the<br>
data paths into our system.<br></blockquote><div><br></div><div>Afaik we have a configuration on proxy server that caches only immutable content for yum repos? So this is indeed an interesting discovery!</div></div><br>Anton.<br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><span><font color="#888888"><div>Anton Marchukov<br>Senior Software Engineer - <span><span><font color="#888888"><span><span><font color="#888888"><span><span><font color="#888888">RHEV CI - </font></span></span></font></span></span>Red Hat</font></span></span><br><br></div></font></span></div></div></div></div>
</div></div>