Can we figure out how much traffic updates-testing is actually getting currently to see if it can be unmirrored? In my mind, it would seem that the fact updates live inside updates-testing for a very short time (on the timescale of days) before being moved to normal updates, and the fact it is not enabled by default, would make me think it is probably low traffic in comparison. Alternately, is there an option in DNF to automatically use the mirror that was updated most recently, even if it isn't the fastest/geographically closest? -Ian > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > --00000000000064cb9e05d72f996b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail= _attr">On Thu, Feb 3, 2022 at 7:41 PM Kevin Fenzi <<a href=3D"mailto:kev= in@xxxxxxxxx" target=3D"_blank">kevin@xxxxxxxxx</a>> wrote:<br></div><bl= ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef= t:1px solid rgb(204,204,204);padding-left:1ex">On Thu, Feb 03, 2022 at 06:3= 8:11PM +0000, Ian McInerney via devel wrote:<br> > <br> > I guess it was a mirror caching issue. I tried again just now and it p= icked<br> > up the update just fine. I didn't think the updates-testing repo w= as<br> > mirrored though, but it is very annoying that the mirror sync and the = push<br> > to updates-testing apparently aren't synchronized, leading to a la= rge lag<br> > there.<br> <br> yes, updates-testing is mirrored just like updates. <br> <br> Sadly there's not too much we can do about the sync time, since mirrors= <br> are free to sync as ofter or inoften as they like. ;( <br> <br> It's possible that updates-testing doesn't get that much traffic th= ese<br> days and we could look at un-mirroring it somehow. Everyone seems pretty<br= > used to it by now however and you can get the updates from koji or from<br> bodhi directly too. <br> <br> kevin<br></blockquote><div><br></div><div>From a user experience perspectiv= e, the mirror lag time on it is very annoying. When the update is pushed to= testing, Bodhi posts a comment in the associated Bugzilla saying that you = should "soon" be able to install the update using the relevant DN= F command. In my opinion, having to wait 18 hours before that command works= (and continually having to try that command throughout the day to see when= it will start working) is very annoying from the perspective of someone wh= o wants to test the fix to a bug they are affected by/reported.</div><div><= br></div><div>Can we figure out how much traffic updates-testing is actuall= y getting currently to see if it can be unmirrored? In my mind, it would se= em that the fact updates live inside updates-testing for a very short time = (on the timescale of days) before being moved to normal updates, and the fa= ct it is not enabled by default, would make me think it is probably low tra= ffic in comparison.<br></div><div><br></div><div>Alternately, is there an o= ption in DNF to automatically use the mirror that was updated most recently= , even if it isn't the fastest/geographically closest?</div><div><br></= div><div>-Ian<br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" s= tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad= ding-left:1ex"> _______________________________________________<br> devel mailing list -- <a href=3D"mailto:devel@xxxxxxxxxxxxxxxxxxxxxxx"; targ= et=3D"_blank">devel@xxxxxxxxxxxxxxxxxxxxxxx</a><br> To unsubscribe send an email to <a href=3D"mailto:devel-leave@lists.fedorap= roject.org" target=3D"_blank">devel-leave@xxxxxxxxxxxxxxxxxxxxxxx</a><br> Fedora Code of Conduct: <a href=3D"https://docs.fedoraproject.org/en-US/pro= ject/code-of-conduct/" rel=3D"noreferrer" target=3D"_blank">https://docs.fe= doraproject.org/en-US/project/code-of-conduct/</a><br> List Guidelines: <a href=3D"https://fedoraproject.org/wiki/Mailing_list_gui= delines" rel=3D"noreferrer" target=3D"_blank">https://fedoraproject.org/wik= i/Mailing_list_guidelines</a><br> List Archives: <a href=3D"https://lists.fedoraproject.org/archives/list/dev= el@xxxxxxxxxxxxxxxxxxxxxxx" rel=3D"noreferrer" target=3D"_blank">https://li= sts.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx</a><br> Do not reply to spam on the list, report it: <a href=3D"https://pagure.io/f= edora-infrastructure" rel=3D"noreferrer" target=3D"_blank">https://pagure.i= o/fedora-infrastructure</a><br> </blockquote></div></div> --00000000000064cb9e05d72f996b-- --===============7614411673218358447== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZGV2ZWwgbWFp bGluZyBsaXN0IC0tIGRldmVsQGxpc3RzLmZlZG9yYXByb2plY3Qub3JnClRvIHVuc3Vic2NyaWJl IHNlbmQgYW4gZW1haWwgdG8gZGV2ZWwtbGVhdmVAbGlzdHMuZmVkb3JhcHJvamVjdC5vcmcKRmVk b3JhIENvZGUgb2YgQ29uZHVjdDogaHR0cHM6Ly9kb2NzLmZlZG9yYXByb2plY3Qub3JnL2VuLVVT L3Byb2plY3QvY29kZS1vZi1jb25kdWN0LwpMaXN0IEd1aWRlbGluZXM6IGh0dHBzOi8vZmVkb3Jh cHJvamVjdC5vcmcvd2lraS9NYWlsaW5nX2xpc3RfZ3VpZGVsaW5lcwpMaXN0IEFyY2hpdmVzOiBo dHRwczovL2xpc3RzLmZlZG9yYXByb2plY3Qub3JnL2FyY2hpdmVzL2xpc3QvZGV2ZWxAbGlzdHMu ZmVkb3JhcHJvamVjdC5vcmcKRG8gbm90IHJlcGx5IHRvIHNwYW0gb24gdGhlIGxpc3QsIHJlcG9y dCBpdDogaHR0cHM6Ly9wYWd1cmUuaW8vZmVkb3JhLWluZnJhc3RydWN0dXJlCg== --===============7614411673218358447==--
