On Fri, 2005-11-04 at 01:09 +1300, Tom wrote:
Johnny Hughes wrote:
On Thu, 2005-11-03 at 20:45 +0900, Mark Sargent wrote:
its a problem on the remote end, not your side of things. Just shift to using a mirror and the problem will go away, the mirror that was recommended ( mirrorservice.org ) works well for me too.
- K
Hi All,
yep, updated the yum.conf to reflect the mirror suggested. Cheers.
Mark Sargent.
Just for the record, dag has commented on this before.
The main site that hosts his repo is also an apache project test site ... so from time to time there are issues on that box.
funny thing is it only seems to affect centos4, I don't get those errors with any of my 3 boxes.
In this particular case, that is because yum 2.0.x (the one in CentOS 3) uses individual headers and a .info file ... and yum 2.2.x/2.3.x/2.4.x (the one in CentOS 4 is now 2.4.x) uses .xml files and repomd data (all the headers in one file).
The xml file generation produces a zero size .xml file on that mirror (intermittently)... which only effects products using yum 2.2.x/2.3.x/2.4.x (so for CentOS, it only effects CentOS-4). It would also effect FC 3 and 4 and RHEL 4 with yum.