Repocop reports by srpm

  rpm id test status message
clang10.0-10.0.0-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package clang7.0-7.0.1-alt7.rel.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.
There are file conflicts with the package clang9.0-9.0.1-alt3.x86_64, for example, /usr/bin/c-index-test (11 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.
clang10.0-10.0.0-alt2.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-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.
value of symlink /usr/bin/clang is different from the same symlink in the package clang7.0-7.0.1-alt7.rel.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.
clang10.0-analyzer-10.0.0-alt2.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package clang7.0-analyzer-7.0.1-alt7.rel.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.
Files /usr/bin/scan-build /usr/libexec/ccc-analyzer conflict with the package clang9.0-analyzer-9.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
clang10.0-debuginfo-10.0.0-alt2.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-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.
value of symlink /usr/lib/debug/usr/bin/clang++.debug is different from the same symlink in the package clang7.0-debuginfo-7.0.1-alt7.rel.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-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.
value of symlink /usr/lib/debug/usr/bin/clang-cl.debug is different from the same symlink in the package clang7.0-debuginfo-7.0.1-alt7.rel.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-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.
value of symlink /usr/lib/debug/usr/bin/clang-cpp.debug is different from the same symlink in the package clang7.0-debuginfo-7.0.1-alt7.rel.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-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.
value of symlink /usr/lib/debug/usr/bin/clang.debug is different from the same symlink in the package clang7.0-debuginfo-7.0.1-alt7.rel.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.
clang10.0-devel-10.0.0-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package clang7.0-devel-7.0.1-alt7.rel.x86_64, for example, /usr/include/clang-c/BuildSystem.h (508 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.
There are file conflicts with the package clang9.0-devel-9.0.1-alt3.x86_64, for example, /usr/include/clang-c/BuildSystem.h (235 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.
clang10.0-devel-10.0.0-alt2.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib64/libclang-cpp.so is different from the same symlink in the package clang9.0-devel-9.0.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.
value of symlink /usr/lib64/libclang.so is different from the same symlink in the package clang9.0-devel-9.0.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.
value of symlink /usr/lib64/libclang.so is different from the same symlink in the package clang7.0-devel-7.0.1-alt7.rel.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.
clang10.0-devel-static-10.0.0-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package clang7.0-devel-static-7.0.1-alt7.rel.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.
There are file conflicts with the package clang9.0-devel-static-9.0.1-alt3.x86_64, for example, /usr/lib64/libclangARCMigrate.a (33 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.
clang10.0-doc-10.0.0-alt2.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package clang7.0-doc-7.0.1-alt7.rel.noarch, for example, /usr/share/doc/clang/html/AddressSanitizer.html (113 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.
There are file conflicts with the package clang9.0-doc-9.0.1-alt3.noarch, for example, /usr/share/doc/clang/html/AddressSanitizer.html (99 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.
clang10.0-libs-10.0.0-alt2.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
lld10.0-10.0.0-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/bin/lld conflicts with the package lld7.0-7.0.1-alt7.rel.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.
File /usr/bin/lld conflicts with the package lld9.0-9.0.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.
lld10.0-devel-10.0.0-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package lld7.0-devel-7.0.1-alt7.rel.x86_64, for example, /usr/include/lld/Common/Args.h (33 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.
There are file conflicts with the package lld9.0-devel-9.0.1-alt3.x86_64, for example, /usr/include/lld/Common/Driver.h (12 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.
llvm10.0-10.0.0-alt2.src beehive-log-unpackaged-files-found-i586 info warning: Installed (but unpackaged) file(s) found:
/usr/share/clang/bash-autocomplete.sh
/usr/share/clang/clang-format-bbedit.applescript
/usr/share/clang/clang-format-diff.py
/usr/share/clang/clang-format-sublime.py
/usr/share/clang/clang-format.el
/usr/share/clang/clang-format.py
/usr/share/clang/clang-rename.el
/usr/share/clang/clang-rename.py
/usr/share/opt-viewer/opt-diff.py
/usr/share/opt-viewer/opt-stats.py
/usr/share/opt-viewer/opt-viewer.py
/usr/share/opt-viewer/optpmap.py
/usr/share/opt-viewer/optrecord.py
/usr/share/opt-viewer/style.css
llvm10.0-10.0.0-alt2.src beehive-log-unpackaged-files-found-x86_64 info warning: Installed (but unpackaged) file(s) found:
/usr/share/clang/bash-autocomplete.sh
/usr/share/clang/clang-format-bbedit.applescript
/usr/share/clang/clang-format-diff.py
/usr/share/clang/clang-format-sublime.py
/usr/share/clang/clang-format.el
/usr/share/clang/clang-format.py
/usr/share/clang/clang-rename.el
/usr/share/clang/clang-rename.py
/usr/share/opt-viewer/opt-diff.py
/usr/share/opt-viewer/opt-stats.py
/usr/share/opt-viewer/opt-viewer.py
/usr/share/opt-viewer/optpmap.py
/usr/share/opt-viewer/optrecord.py
/usr/share/opt-viewer/style.css
llvm10.0-10.0.0-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package llvm7.0-7.0.1-alt7.rel.x86_64, for example, /usr/bin/bugpoint (78 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.
There are file conflicts with the package llvm9.0-9.0.1-alt3.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.
llvm10.0-devel-10.0.0-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package llvm7.0-devel-7.0.1-alt7.rel.x86_64, for example, /usr/bin/llvm-config (1202 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.
There are file conflicts with the package llvm9.0-devel-9.0.1-alt3.x86_64, for example, /usr/bin/llvm-config (595 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.
llvm10.0-devel-10.0.0-alt2.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-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.
value of symlink /usr/lib64/libLLVM.so is different from the same symlink in the package llvm7.0-devel-7.0.1-alt7.rel.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-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.
value of symlink /usr/lib64/libLTO.so is different from the same symlink in the package llvm7.0-devel-7.0.1-alt7.rel.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/libRemarks.so is different from the same symlink in the package llvm9.0-devel-9.0.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.
llvm10.0-devel-static-10.0.0-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package llvm7.0-devel-static-7.0.1-alt7.rel.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.
There are file conflicts with the package llvm9.0-devel-static-9.0.1-alt3.x86_64, for example, /usr/lib64/libLLVMAMDGPUAsmParser.a (94 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.
llvm10.0-doc-10.0.0-alt2.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package llvm7.0-doc-7.0.1-alt7.rel.noarch, for example, /usr/share/doc/llvm/html/AMDGPUOperandSyntax.html (277 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.
There are file conflicts with the package llvm9.0-doc-9.0.1-alt3.noarch, for example, /usr/share/doc/llvm/html/AMDGPU/AMDGPUAsmGFX10.html (721 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.
llvm10.0-libs-10.0.0-alt2.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 Mon Jul 13 04:22:35 2020