kdebase4 (or one of its subpacakges) has multiarch conflicts when installed for both i386 and x86_64 in the Fedora development tree. For help in resolving them, see http://fedoraproject.org/wiki/PackagingDrafts/MultilibTricks. file /usr/share/doc/HTML/en/dolphin/index.cache.bz2 from install of kdebase4-3.93.0-6.fc8 conflicts with file from package kdebase4-3.93.0-6.fc8 file /usr/share/doc/HTML/en/faq/index.cache.bz2 from install of kdebase4-3.93.0-6.fc8 conflicts with file from package kdebase4-3.93.0-6.fc8 file /usr/share/doc/HTML/en/quickstart/index.cache.bz2 from install of kdebase4-3.93.0-6.fc8 conflicts with file from package kdebase4-3.93.0-6.fc8 file /usr/share/doc/HTML/en/userguide/index.cache.bz2 from install of kdebase4-3.93.0-6.fc8 conflicts with file from package kdebase4-3.93.0-6.fc8 file /usr/share/doc/HTML/en/visualdict/index.cache.bz2 from install of kdebase4-3.93.0-6.fc8 conflicts with file from package kdebase4-3.93.0-6.fc8 (Note that this is an automated bug filing.) It would be nice to have these bugs fixed by the beta of Fedora 9.
is this more doxygen-induced borkage?
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Was this corrected or is still an issue in F9?
Still an issue in 4.1 or can we close this?
The information we've requested above is required in order to review this problem report further and diagnose or fix the issue if it is still present. Since it has been thirty days or more since we first requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. Setting status to "CLOSED INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report. Thank you in advance.
I don't think this is fixed yet, really. It's the infamous index.cache.bz2 mess. Splitting off a kdebase4-libs so kdebase4 doesn't get multilibbed could help, but then we'd be left with an old kdebase4.i386 with no updates. I wonder if we should just WONTFIX this for F8, it's fixed in F9 by the -libs split. But on the other hand, we should really fix this index.cache.bz2 problem in the first place, kdelibs 4 currently has a hack for the same issue with the Sonnet documentation.
Since F8 is EOL and its not an issue in F9+ closing as WONTFIX