gcc10-doc-10.3.1-alt2.noarch	rpm-obsolete-live-package	info	The package obsoletes the package gcc9-doc-9.3.1-alt3.noarch, but the package gcc9-doc-9.3.1-alt3.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.; .; .; .; 
gcc10-fortran-doc-10.3.1-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/share/info/gfortran.info.xz conflicts with the package gcc6-doc-6.3.1-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; .; ; 
gcc10-fortran-doc-10.3.1-alt2.x86_64	rpm-obsolete-live-package	info	The package obsoletes the package gcc9-fortran-doc-9.3.1-alt3.x86_64, but the package gcc9-fortran-doc-9.3.1-alt3.x86_64 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.; .; 
gcc10-go-doc-10.3.1-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/share/info/gccgo.info.xz conflicts with the package gcc4.7-doc-4.7.2-alt13.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
gcc10-go-doc-10.3.1-alt2.x86_64	rpm-obsolete-live-package	info	The package obsoletes the package gcc9-go-doc-9.3.1-alt3.x86_64, but the package gcc9-go-doc-9.3.1-alt3.x86_64 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.; .; 
libgphobos10-devel-10.3.1-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/libgphobos.spec conflicts with the package libgphobos9-devel-9.3.1-alt3.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
libstdc++10-devel-10.3.1-alt2.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.;