Bug 240539 - Anaconda fails to work with non-flat repositories
Summary: Anaconda fails to work with non-flat repositories
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-05-18 11:54 UTC by Lubomir Kundrak
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-10-26 15:34:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Lubomir Kundrak 2007-05-18 11:54:09 UTC
Description of problem:

I've created a yum repository and attempted to tell anaconda to use it
during the package selection phase. I got an error like "Unable to fetch
repodata/comps.xml, No more mirrors to try" (or something similar). My
repository was layouted like this:

repository
    packages1
         *.rpm
    packages2
         *.rpm
    repodata
         *

As per tcpdump and webserver logs (the repository was accessible via http),
it seemed that anaconda downloaded the comps.xml correctly. When I changed
the layout to look like this, anaconda finally accepted the repository:

repository
     *.rpm
     repodata
          *

If this is a design issue, it would be at least nice to get a somewhat
better error message.

Comment 1 Jeremy Katz 2007-05-18 21:34:23 UTC
Did the repodata properly reference the packages under packages1/, etc?

Comment 2 Red Hat Bugzilla 2007-06-12 03:54:34 UTC
requested by Jams Antill

Comment 3 Lubomir Kundrak 2007-10-17 09:55:37 UTC
Jeremy: I did not use the fc6 anaconda with such repositories since I reported
this. Yesterday I installed Rawhide (the repodata created in Rawhide as well)
correctly with the repository laid as described above.

Comment 4 Chris Lumens 2007-10-26 15:34:04 UTC
If I understand comment #3 correctly, this is no longer an issue.  Feel free to
reopen this bug if you are continuing to see this problem, though.


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