Re: Mysql 5.0.41 Source downloads - md5 doesn't match -
I agree we messed up in that respect. Even if many downloaders
would not read it, and might fetch packages directly from the
FTP mirrors, that is no reason to exclude a warning.
I can just ensure you we have been working on this, but as
we don't run the mirrors ourselves the communication is a
problem. We also initially assumed as it was the main European
mirror that had a faulty disk and that spread corrupted packages,
that US mirrors should not be affected. But many of them are.
Finding out exactly what mirror has any corrupted files still,
would require us to download all files from all mirrors, something
we don't have the bandwidth to do. And to tell a mirror is ok again,
we would need to download them repeatably.
I did however download all files from the corrupted main mirror,
compared the files with our originals, and changed the time stamp
on the originals for the files that were corrupted. This will
retrigger the rsync transfer to the mirrors, hopefully replacing
the faulty ones with the correct ones. In the default setting
most mirrors use, rsync will check file size and modification
time to find out if it should compare content at all, i.e. the
only way to trigger replacement of the faulty ones is to change
time stamp.
Problem with this was that I had to wait until the single main
mirror in Europe was up and running again.
We have also contacted some sites to find additional European
main mirrors, reducing the future dependency on only one mirror
in Europe. We have found some and will work with mirror
maintainers to get them up and running.
But we should have resolved this faster and communicated
with the community better. Sorry about the problems, and
thanks for your input about how to handle this better if
it happens a next time.
Just as a note, I hope the above doesn't sound as I in any
way put blame on the mirror maintainers. MySQL AB highly
appreciate their work and that they offer disk space and
bandwidth for spearding MySQL to the users,
kent
Kent Boortz, Release Staff Engineer
Oracle, the MySQL team, www.mysql.com