Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 200672 - Cannot open/read repomd.xml file for anaconda
Cannot open/read repomd.xml file for anaconda
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Paul Nasrat
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2006-07-30 09:51 EDT by Stuart Johnson
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-08-14 14:06:33 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Stuart Johnson 2006-07-30 09:51:51 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20060719 Firefox/

Description of problem:
When installing FC6T1 from either the i386 or x86_64 DVD image, I get the following dialog box:
Unable to read package metadata. This may be due to a missing repodata directory. Please ensure that your install tree has been correctly generated.
Can not read/open repomd.xml file for repository:

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Boot from install DVD 
2.proceed with typical installation

Actual Results:

Expected Results:

Additional info:
eMachines m6811 laptop, 3400+ cpu, radeon mobility 9600 graphics. I am try to install on to a dual-boot configuration which previously had XP and FC5 installed.
Comment 1 Paul Nasrat 2006-07-31 11:21:31 EDT
Any logs on tty3 tty4?
Comment 2 Paul Nasrat 2006-08-14 14:06:33 EDT
I can not reproduce here, please ensure you have media checked your dvd and also
try FC6T2.

I'm closing due to lack of additional information - if you have anything to add
to this bug please retest and reopen.

Note You need to log in before you can comment on or make changes to this bug.