<div dir="ltr">There's some bug related to metalinks specifically (which is what yum is using). I likely introduced it with the MM 1.4.3 upgrade this week. This is the second report of failure, and I can clearly see that metalinks only are returning a single mirror for some users, while mirrorlist returns the whole list as expected. It looks to be only for hosts that fall within a netblock of a private mirror.<div>
<br></div><div>I am travelling with my family today, so offline mostly. I'll look at it and resolve ASAP.</div><div><br></div><div>Thanks,<br></div><div>Matt</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Fri, Dec 20, 2013 at 7:09 PM, Albert Wang <span dir="ltr"><<a href="mailto:wang@polymathanalytics.com" target="_blank">wang@polymathanalytics.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi everyone,<br>
<br>
Sorry if I'm sending the question to the wrong mailing list, but I'm hoping someone can help me with my problem:<br>
<br>
I have a for-home private repository that I set up, which contains most, but not all the rpm packages, for quicker updates.<br>
It has been working fine until a week or so ago, where, essentially, the call:<br>
curl -s "<a href="https://mirrors.fedoraproject.org/metalink?repo=updates-released-f19&arch=x86_64&ip=98.113.159.63" target="_blank">https://mirrors.fedoraproject.org/metalink?repo=updates-released-f19&arch=x86_64&ip=98.113.159.63</a>"<br>
<br>
now only returns one private repo site (without the full list of other alternatives). This causes problems, since I filtered out certain devel packages.<br>
Is there a policy/implementation change that I am not aware of?<br>
<br>
Thank you very much for your time. Happy holidays!<br>
Albert<br>
<br>
<br>
<br>
--<br>
<br>
</blockquote></div><br></div>