Description of problem: Newer yum produces broken comps.xml. First problem: In Fedora 8, language support groups are tagged as <langonly>. In Fedora 9, language support groups are tagged as <lang_only>, but yum itself assumes <langonly> when selecting package group. Second problem: In Fedora 8, conditinal packages are like below: <packagereq type="conditional" requires="xorg-x11-server-Xorg">scim-anthy</packagereq> In Fedora 9, like below: <packagereq type="conditional" requires="scim-anthy">xorg-x11-server-Xorg</packagereq> And, yum itself assumes Fedora 8's format when selecting packages. As it's result, Fedora 9 installer do not install language support groups. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. Boot F9 installer. 2. Select Japanese. 3. Do installation. Actual results: Japanese Support group was not selected by default. Even when manually selected Japanese Support group, it was not installed. Expected results: Japanese Support group was selected by default and installed automatically if language is Japanese. Additional info:
Created attachment 305229 [details] a patch for yum-3.2.14/yum/comps.py
Fixed in upstream commit: 4d786c6d615ff74f47612940861464c8860998f9 Should be in the first yum update for Fed-9
*** Bug 446602 has been marked as a duplicate of this bug. ***
yum-3.2.16-1.fc9 has been submitted as an update for Fedora 9
yum-3.2.16-1.fc9 has been pushed to the Fedora 9 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update yum'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-4076
yum-3.2.16-2.fc9 has been submitted as an update for Fedora 9
*** Bug 447095 has been marked as a duplicate of this bug. ***
*** Bug 447701 has been marked as a duplicate of this bug. ***
yum-3.2.16-2.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 453490 has been marked as a duplicate of this bug. ***