On Tue, May 15, 2007 at 04:08:40PM +0200, Florian La Roche wrote:

Hello,

If you look at the below data, it seems that some hosts with older repomd.xml data are still in the mirrorlist and not removed. Is the data not checked further to leave out older mirrors until now?

No, I see the problem. Thanks for the report. I knew this was going to bite me sooner or later, and have plans to fix it, but hadn't had time to implement it...

Getting mirrorlist from updates-released-debug-fc5-DE-ppc.txt. cacheLocal: looking at url: updates-released-debug-fc5-DE-ppc.txt Reading yum repository http://ftp.uni-koeln.de/mirrors/fedora/linux/core/updates/5/ppc/debug. cacheLocal: looking at url: http://ftp.uni-koeln.de/mirrors/fedora/linux/core/updates/5/ppc/debug/repoda... 2007/04/24

This host was crawled today, and that the repodata directory isn't up-to-date, but the crawler thinks that the updates/5/ppc/debug directory *is* up-to-date. But it shouldn't.

up2date path lastCrawled date

True updates/5/ppc 2007-05-16 07:43:17 True updates/5/ppc/debug 2007-05-16 07:43:10 False updates/5/ppc/debug/repodata 2007-05-16 07:43:02 False updates/5/ppc/repodata 2007-05-16 07:43:22

The problem is, the database doesn't track every single file in a directory full of RPMs or HTML files. That would have exploded the size of the database. So, I only look at 10 files in such directories (and all files in all other directories). It's supposed to be "the ten most recent files", but that part of the logic is what's broken. It uses the first ten as reported by the dict, which isn't right.

I'll have to fix that to solve this. It's just a matter of adding rsync directory list parsing into the update-master-directory-list program, shouldn't be hard, just needs a little time and a little testing...

Thanks, Matt