Red Hat Bugzilla – Bug 439925
system-config-kickstart requires repoid of [main] to locate package info
Last modified: 2009-09-09 16:17:03 EDT
Description of problem: system-config-kickstart requires repoid of [main] to locate package info. I noticed this when using a custom repo config file in which I had edited all of the repo-ids (by appending a suffix indicating the source, e.g. "-localHTTP", "-localDisk", etc) and had also disabled the default repo config file. This is not a big deal, but the software would be a bit more robust if it didn't depend on the repo-id, but just the repo contents. Version-Release number of selected component (if applicable): 2.6.19.1 How reproducible: Always Steps to Reproduce: 1. Edit /etc/yum.repos.d/*Base.repo and alter repoid of [main] to [foomain] 2. Run system-config-kickstart 3. Package information not found Actual results: Package information not found Expected results:Package information found Additional info:
I can confirm the bug, but with different repo-id name: core, base and develoment are working for me, I found the names on a line 252 in /usr/share/system-config-kickstart/packages.py: # If we're on a release, we want to try the base repo first. Otherwise, # try development. If neither of those works, we have a problem. if "base" in map(lambda repo: repo.id, self.repos.listEnabled()): repoorder = ["core", "base", "development"] else: repoorder = ["development", "core", "base"]
We've got to get a "base" repo somehow in order to provide an interface that lets you select packages that'll give you an installable system. Otherwise, you could just be showing a list of a handful of random add-on packages instead of something really useful to provide an installation from. And there's no good way to determine what's a base repo and what's not unless we stick with the names. It's a pretty gross hack, I agree, but I can't see a better way to accomplish it than what I'm already doing.