Repocop reports by srpm

  rpm id test status message
clang7.0-7.0.1-alt4.rel.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package clang9.0-9.0.1-alt2.x86_64, for example, /usr/bin/c-index-test (9 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
clang7.0-7.0.1-alt4.rel.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/bin/clang is different from the same symlink in the package clang9.0-9.0.1-alt2.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.
clang7.0-7.0.1-alt4.rel.x86_64 sisyphus_check fail sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/clang7.0-7.0.1-alt4.rel.x86_64.rpm: forbidden requires: python-base sisyphus_check: check-deps ERROR: package dependencies violation
clang7.0-analyzer-7.0.1-alt4.rel.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package clang9.0-analyzer-9.0.1-alt2.noarch, for example, /usr/bin/scan-build (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
clang7.0-debuginfo-7.0.1-alt4.rel.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/usr/bin/clang++.debug is different from the same symlink in the package clang9.0-debuginfo-9.0.1-alt2.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.
value of symlink /usr/lib/debug/usr/bin/clang-cl.debug is different from the same symlink in the package clang9.0-debuginfo-9.0.1-alt2.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.
value of symlink /usr/lib/debug/usr/bin/clang-cpp.debug is different from the same symlink in the package clang9.0-debuginfo-9.0.1-alt2.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.
value of symlink /usr/lib/debug/usr/bin/clang.debug is different from the same symlink in the package clang9.0-debuginfo-9.0.1-alt2.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.
clang7.0-devel-7.0.1-alt4.rel.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package clang9.0-devel-9.0.1-alt2.x86_64, for example, /usr/include/clang-c/Index.h (504 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
clang7.0-devel-7.0.1-alt4.rel.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib64/libclang.so is different from the same symlink in the package clang9.0-devel-9.0.1-alt2.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.
clang7.0-devel-static-7.0.1-alt4.rel.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package clang9.0-devel-static-9.0.1-alt2.x86_64, for example, /usr/lib64/libclangARCMigrate.a (29 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
clang7.0-doc-7.0.1-alt4.rel.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package clang9.0-doc-9.0.1-alt2.noarch, for example, /usr/share/doc/clang/html/AddressSanitizer.html (110 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
clang7.0-libs-7.0.1-alt4.rel.x86_64 library-pkgnames info package contains public library which is used in external packages: name should be lib* according to http://altlinux.org/Drafts/SharedLibs
lld-7.0.1-alt4.rel.x86_64 rpm-package-is-obsoleted warn The package is obsoleted by the package lld9.0-9.0.1-alt2.x86_64, 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 lld9.0-9.0.1-alt2.x86_64 to remove Obsoletes: tag.
lld-devel-7.0.1-alt4.rel.x86_64 rpm-package-is-obsoleted warn The package is obsoleted by the package lld9.0-devel-9.0.1-alt2.x86_64, 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 lld9.0-devel-9.0.1-alt2.x86_64 to remove Obsoletes: tag.
lld-doc-7.0.1-alt4.rel.noarch rpm-package-is-obsoleted warn The package is obsoleted by the package lld9.0-doc-9.0.1-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 lld9.0-doc-9.0.1-alt2.noarch to remove Obsoletes: tag.
llvm7.0-7.0.1-alt4.rel.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package llvm9.0-9.0.1-alt2.x86_64, for example, /usr/bin/bugpoint (75 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
llvm7.0-7.0.1-alt4.rel.x86_64 sisyphus_check fail sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/llvm7.0-7.0.1-alt4.rel.x86_64.rpm: forbidden requires: python-base sisyphus_check: check-deps ERROR: package dependencies violation
llvm7.0-devel-7.0.1-alt4.rel.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package llvm9.0-devel-9.0.1-alt2.x86_64, for example, /usr/bin/llvm-config (1187 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
llvm7.0-devel-7.0.1-alt4.rel.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib64/libLLVM.so is different from the same symlink in the package llvm9.0-devel-9.0.1-alt2.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.
value of symlink /usr/lib64/libLTO.so is different from the same symlink in the package llvm9.0-devel-9.0.1-alt2.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.
llvm7.0-devel-static-7.0.1-alt4.rel.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package llvm9.0-devel-static-9.0.1-alt2.x86_64, for example, /usr/lib64/libLLVMAMDGPUAsmParser.a (88 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
llvm7.0-doc-7.0.1-alt4.rel.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package llvm9.0-doc-9.0.1-alt2.noarch, for example, /usr/share/doc/llvm/html/AMDGPUOperandSyntax.html (261 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
llvm7.0-libs-7.0.1-alt4.rel.x86_64 library-pkgnames info package contains public library which is used in external packages: name should be lib* according to http://altlinux.org/Drafts/SharedLibs

generated by repocop at Sun Feb 23 04:27:10 2020