Repocop reports by srpm

  rpm id test status message
gcc9-9.2.1-alt3.src beehive-log-unpackaged-files-found-i586 info warning: Installed (but unpackaged) file(s) found:
/usr/lib/gcc/i586-alt-linux/9/include/sanitizer/lsan_interface.h
/usr/lib/gcc/i586-alt-linux/9/include/sanitizer/tsan_interface.h
gcc9-doc-9.2.1-alt3.noarch rpm-obsolete-live-package info The package obsoletes the package gcc4.3-doc-4.3.2-alt22.noarch, but the package gcc4.3-doc-4.3.2-alt22.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.4-doc-4.4.7-alt6.noarch, but the package gcc4.4-doc-4.4.7-alt6.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.5-doc-4.5.4-alt7.noarch, but the package gcc4.5-doc-4.5.4-alt7.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.6-doc-4.6.3-alt14.noarch, but the package gcc4.6-doc-4.6.3-alt14.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.7-doc-4.7.2-alt13.noarch, but the package gcc4.7-doc-4.7.2-alt13.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.8-doc-4.8.2-alt7.noarch, but the package gcc4.8-doc-4.8.2-alt7.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.9-doc-4.9.2-alt7.noarch, but the package gcc4.9-doc-4.9.2-alt7.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 gcc5-doc-5.3.1-alt7.noarch, but the package gcc5-doc-5.3.1-alt7.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 gcc6-doc-6.3.1-alt5.noarch, but the package gcc6-doc-6.3.1-alt5.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 gcc7-doc-7.3.1-alt9.noarch, but the package gcc7-doc-7.3.1-alt9.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 gcc8-doc-8.3.1-alt7.noarch, but the package gcc8-doc-8.3.1-alt7.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.
gcc9-fortran-doc-9.2.1-alt3.x86_64 rpm-filesystem-conflict-file-file warn File /usr/share/info/gfortran.info.xz conflicts with the package gcc4.3-doc-4.3.2-alt22.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/info/gfortran.info.xz conflicts with the package gcc4.4-doc-4.4.7-alt6.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/info/gfortran.info.xz conflicts with the package gcc4.5-doc-4.5.4-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.
File /usr/share/info/gfortran.info.xz conflicts with the package gcc4.6-doc-4.6.3-alt14.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/info/gfortran.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.
File /usr/share/info/gfortran.info.xz conflicts with the package gcc4.8-doc-4.8.2-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.
File /usr/share/info/gfortran.info.xz conflicts with the package gcc4.9-doc-4.9.2-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.
File /usr/share/info/gfortran.info.xz conflicts with the package gcc5-doc-5.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.
File /usr/share/info/gfortran.info.xz conflicts with the package gcc6-doc-6.3.1-alt5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
gcc9-fortran-doc-9.2.1-alt3.x86_64 rpm-obsolete-live-package info The package obsoletes the package gcc7-fortran-doc-7.3.1-alt9.x86_64, but the package gcc7-fortran-doc-7.3.1-alt9.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.
The package obsoletes the package gcc8-fortran-doc-8.3.1-alt7.x86_64, but the package gcc8-fortran-doc-8.3.1-alt7.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.
gcc9-go-doc-9.2.1-alt3.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.
gcc9-go-doc-9.2.1-alt3.x86_64 rpm-obsolete-live-package info The package obsoletes the package gcc7-go-doc-7.3.1-alt9.x86_64, but the package gcc7-go-doc-7.3.1-alt9.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.
The package obsoletes the package gcc8-go-doc-8.3.1-alt7.x86_64, but the package gcc8-go-doc-8.3.1-alt7.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.
libstdc++9-devel-9.2.1-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.

generated by repocop at Wed Feb 26 04:58:12 2020