gcc4.4-doc-4.4.7-alt3.noarch	rpm-obsolete-live-package	info	The package obsoletes the package gcc3.4-doc-3.4.5-alt16.noarch, but the package gcc3.4-doc-3.4.5-alt16.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.; The package obsoletes the package gcc4.1-doc-4.1.2-alt11.noarch, but the package gcc4.1-doc-4.1.2-alt11.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.; The package obsoletes the package gcc4.3-doc-4.3.2-alt18.noarch, but the package gcc4.3-doc-4.3.2-alt18.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.; 
gcc4.4-doc-4.4.7-alt3.noarch	rpm-package-is-obsoleted	warn	The package is  obsoleted by the package gcc4.5-doc-4.5.4-alt2.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.5-doc-4.5.4-alt2.noarch to remove Obsoletes: tag.; The package is  obsoleted by the package gcc4.6-doc-4.6.3-alt9.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.6-doc-4.6.3-alt9.noarch to remove Obsoletes: tag.; The package is  obsoleted by the package gcc4.7-doc-4.7.2-alt7.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.7-doc-4.7.2-alt7.noarch to remove Obsoletes: tag.; 
libstdc++4.4-devel-4.4.7-alt3.x86_64	arch-dep-package-has-big-usr-share	info	The package has a significant amount of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.;