On Sat, Oct 04, 2008 at 05:54:53PM -0400, James Antill wrote: > > Ok, I have "working" metalink code for yum client side: > > http://people.redhat.com/jantill/yum/patches/yum-metalink-full.patch > > ...just apply the above and where you have: > > mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f$releasever.newkey&arch=$basearch > > ...also add: > > metalink=http://mirrors.fedoraproject.org/metalink?repo=updates-released-f$releasever.newkey&arch=$basearch > > ...etc. > > However one big problem atm. is that MM seems to be behind the actual > mirrors for all the data. > > Rawhide has a current repomd.xml of: > > Sat Oct 4 10:15:41 2008 GMT > > ...but all MM has is: > > Fri Oct 3 09:54:56 2008 GMT > Thu Oct 2 09:54:25 2008 GMT > > ...Fedora 9 updates-newkey etc. has the same problem but with different > data. > > So until that's fixed you get a lot of failures, until you find an > "old" mirror.
MM indexes the master mirror file system every 4-6 hours, so it shouldn't be out of date longer than this. I need to implement a better way to know when directories change and index those that change more frequently more often. Regardless, any index updates don't propogate to the mirrorlist cache until the top of the hour, so there will always be that much of a delay... -- Matt Domsch Linux Technology Strategist, Dell Office of the CTO linux.dell.com & www.dell.com/linux _______________________________________________ Yum-devel mailing list Yum-devel@lists.baseurl.org http://lists.baseurl.org/mailman/listinfo/yum-devel
