Description of problem: Acroread lists itself as a provider of libstdc++, in a kickstart install where Supplementary is made available as a repo, this means that anaconda will select acroread as the provider. When the system boots, there will be no usable libstdc++, which happens to be a dependency of RPM, etc. IOW, you cannot kickstart a box and use the supplementary repo (so much for pre-installed Java) and end up with a usable system afterwords. Version-Release number of selected component (if applicable): According to bug # 434762, which this is a likely duplicate of (in a new product), this has been ongoing since RHEL4. How reproducible: Every time. Steps to Reproduce: 1. Create a minimal (i.e. @base) kickstart with the supplementary repository listed 2. Kickstart a box using #1 3. Anything depending on libstdc++ (RPM being the largest) is severely borked. Actual results: acroread is selected as the provider for libstdc++. Expected results: libstdc++ is the provider of libstdc++. Additional info: How did this make it into the wild?
This was fixed in acroread-8.1.2.SU1: https://rhn.redhat.com/errata/RHSA-2008-0641.html