FC3 daily yum.cron reports repomd.xml broken, how to repair and prevent?

To: For users of Fedora Core releases <fedora-list@xxxxxxxxxx>
Subject: FC3 daily yum.cron reports repomd.xml broken, how to repair and prevent?
From: Rhesa Rozendaal <perl@xxxxxxxxx>
Date: Sun, 06 Nov 2005 19:49:20 +0100
List-help: <mailto:[email protected]?subject=help>
List-id: For users of Fedora Core releases <fedora-list.redhat.com>
List-post: <mailto:[email protected]>
List-subscribe: <https://www.redhat.com/mailman/listinfo/fedora-list>, <mailto:[email protected]?subject=subscribe>
List-unsubscribe: <https://www.redhat.com/mailman/listinfo/fedora-list>, <mailto:[email protected]?subject=unsubscribe>
Reply-to: For users of Fedora Core releases <fedora-list@xxxxxxxxxx>
User-agent: Debian Thunderbird 1.0.2 (X11/20050602)

Got this report in the mail:

/etc/cron.daily/yum.cron:

//var/cache/yum/base/repomd.xml:1: parser error : Document is empty

^

//var/cache/yum/base/repomd.xml:1: parser error : Start tag expected, '<' notfound


^
Cannot open/read repomd.xml file for repository: base

Error importing repomd.xml from base: Error: could not parse file//var/cache/yum/base/repomd.xml

How the hell did that happen, and what should I do to prevent it fromhappening again, and what should I do to repair it?


TIA,
Rhesa

Follow-Ups:
- Re: FC3 daily yum.cron reports repomd.xml broken, how to repair and prevent?
  - From: Danny Terweij - Net Tuning | Net