It appears that having duplicate entries for the same repo in a kickstart file can crash /some/ versions of Anaconda. This can sometimes happen with cobbler imports, when it includes a part of an installation tree more than once. For instance, RHEL trees are split into many subtrees, so import has to make them each into yum repos so that they can be installed from kickstart. However, if we include each of these subtrees twice, that can be a problem. Naturally, we shouldn't be including them twice, but this is about fixing that for all imports in the past and not asking folks to re-import, as that would be a pain.
(This is when I explain that install trees are more than just repos, they contain data usable as repos once createrepo is run on them, but it's important to remember that "cobbler import" is for install trees and "cobbler repo add" is for regular repos like updates, extra package repos, EPEL, and so forth) Anyway, I've made a fix for this on both branches of Cobbler, but there's no real need to apply this unless you're seeing problems with Anaconda tracebacks. So far I have heard about this in RHEL 5.1, but only just this week -- it's not a new problem, it's just that likely in most cases Anaconda tolerates this and doesn't care. Seeing I felt like being paranoid, I also added a check to make sure the same repo doesn't ever appear in yum twice, for example if yum_post_install_mirror was enabled in settings (to allow packages not yet in updates to be used on installed systems without mirroring the "everything" tree, for instance). So there is now some duplicate supression there too. Yum shouldn't care itself though. Here's the patch: http://git.fedorahosted.org/git/cobbler?p=cobbler;a=commitdiff;h=077ee6fcce87cd66faf682f96f59c19ea354a9fe --Michael _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
