Repocop reports by test

  status rpm id message
warn AFLplusplus-debuginfo-4.21c-alt3.x86_64 value of symlink /usr/lib/debug/usr/bin/afl-g++.debug is different from the same symlink in the package afl-debuginfo-2.57b-alt1.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.
.
.
warn TORCS-1.3.7-alt2.x86_64 value of symlink /usr/lib64/libtgfclient.so is different from the same symlink in the package speed-dreams-2.3.0-alt1.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.
warn TORCS-debuginfo-1.3.7-alt2.x86_64 value of symlink /usr/lib/debug/usr/lib64/libtgfclient.so.debug is different from the same symlink in the package speed-dreams-debuginfo-2.3.0-alt1.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.
warn afl-debuginfo-2.57b-alt1.x86_64 value of symlink /usr/lib/debug/usr/bin/afl-g++.debug is different from the same symlink in the package AFLplusplus-debuginfo-4.21c-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.
.
.
warn debug-ide-0.7.3-alt1.noarch value of symlink /usr/bin/rdebug-ide is different from the same symlink in the package ruby-debug-ide-0.7.3.2-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
warn giflib-devel-5.2.2-alt1.x86_64 value of symlink /usr/lib64/libgif.so is different from the same symlink in the package libgif-devel-4.1.6-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.
warn ilmbase-devel-2.5.6-alt2.x86_64 value of symlink /usr/lib64/libImath.so is different from the same symlink in the package imath-devel-3.1.6-alt4.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.
warn imath-devel-3.1.6-alt4.x86_64 value of symlink /usr/lib64/libImath.so is different from the same symlink in the package ilmbase-devel-2.5.6-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.
warn kde5-kimageannotator-devel-0.7.1-alt2.x86_64 value of symlink /usr/lib64/cmake/kImageAnnotator/kImageAnnotatorConfig.cmake is different from the same symlink in the package kde6-kimageannotator-devel-0.7.1-alt1.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.
atives.
.
warn kde6-kimageannotator-devel-0.7.1-alt1.x86_64 value of symlink /usr/lib64/cmake/kImageAnnotator/kImageAnnotatorConfig.cmake is different from the same symlink in the package kde5-kimageannotator-devel-0.7.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.
atives.
.
warn libLLVMSPIRVLib-devel-18.1.4-alt1.x86_64 value of symlink /usr/lib64/libLLVMSPIRVLib.so is different from the same symlink in the package libspirv-llvm14.0-translator-devel-14.0.3-alt1.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.
warn libdb4.8_java-devel-4.8.30-alt7.x86_64 value of symlink /usr/lib64/libdb_java.so is different from the same symlink in the package libdb6.1_java-devel-6.1.19-alt9.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.
warn libdb6.1_java-devel-6.1.19-alt9.x86_64 value of symlink /usr/lib64/libdb_java.so is different from the same symlink in the package libdb4.8_java-devel-4.8.30-alt7.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.
warn libecpg6-12-debuginfo-12.22-alt1.x86_64 value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.2-alt1.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.
s.

s.
warn libecpg6-13-debuginfo-13.18-alt1.x86_64 value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.2-alt1.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.
s.

s.
warn libecpg6-14-debuginfo-14.15-alt1.x86_64 value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.2-alt1.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.
s.

s.
warn libecpg6-15-debuginfo-15.10-alt1.x86_64 value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.2-alt1.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.
s.

s.
warn libecpg6-16-1C-debuginfo-16.4-alt7.x86_64 value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.2-alt1.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.

s.
warn libecpg6-16-debuginfo-16.6-alt1.x86_64 value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.2-alt1.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.

s.
warn libecpg6-17-debuginfo-17.2-alt1.x86_64 value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-16-debuginfo-16.6-alt1.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.
s.

s.
warn libgcrypt-devel-1.10.2-alt2.x86_64 value of symlink /usr/lib64/libgcrypt.so is different from the same symlink in the package libgcrypt-gost-devel-1.8.5-alt6.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.
warn libgcrypt-gost-devel-1.8.5-alt6.x86_64 value of symlink /usr/lib64/libgcrypt.so is different from the same symlink in the package libgcrypt-devel-1.10.2-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.
warn libgif-devel-4.1.6-alt3.x86_64 value of symlink /usr/lib64/libgif.so is different from the same symlink in the package giflib-devel-5.2.2-alt1.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.
warn libglfw-devel-2.7.9-alt1.x86_64 value of symlink /usr/lib64/libglfw.so is different from the same symlink in the package libglfw3-devel-3.3-alt1.1.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.
warn libglfw3-devel-3.3-alt1.1.x86_64 value of symlink /usr/lib64/libglfw.so is different from the same symlink in the package libglfw-devel-2.7.9-alt1.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.
warn libgs-devel-10.04.0-alt1.x86_64 value of symlink /usr/lib64/libgxps.so is different from the same symlink in the package libgxps-devel-0.3.2-alt1.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.
warn libgxps-devel-0.3.2-alt1.x86_64 value of symlink /usr/lib64/libgxps.so is different from the same symlink in the package libgs-devel-10.04.0-alt1.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.
warn libintel-opencl-clang-devel-18.1.0-alt1.x86_64 value of symlink /usr/lib64/libopencl-clang.so is different from the same symlink in the package libintel-opencl-clang14-devel-14.0.0-alt1.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.
warn libintel-opencl-clang14-devel-14.0.0-alt1.x86_64 value of symlink /usr/lib64/libopencl-clang.so is different from the same symlink in the package libintel-opencl-clang-devel-18.1.0-alt1.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.
warn liblensfun-devel-0.3.95-alt1.x86_64 value of symlink /usr/lib64/liblensfun.so is different from the same symlink in the package liblensfun1-devel-0.3.4-alt1.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.
warn liblensfun1-devel-0.3.4-alt1.x86_64 value of symlink /usr/lib64/liblensfun.so is different from the same symlink in the package liblensfun-devel-0.3.95-alt1.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.
warn libmpeg4ip-devel-1.5.0.1-alt17.x86_64 value of symlink /usr/lib64/libsdp.so is different from the same symlink in the package libsdp-devel-1.1.108-alt2.0.17.ga6958ef.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.
warn libpjsip-devel-2.11-alt1.x86_64 value of symlink /usr/lib64/libresample.so is different from the same symlink in the package libresample-devel-0.1.3-alt5.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.
warn libreadline-devel-8.2.10-alt1.x86_64 value of symlink /usr/lib64/libhistory.so is different from the same symlink in the package libreadline5-devel-5.2.14-alt7.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.
warn libreadline5-devel-5.2.14-alt7.x86_64 value of symlink /usr/lib64/libhistory.so is different from the same symlink in the package libreadline-devel-8.2.10-alt1.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.
warn libresample-devel-0.1.3-alt5.x86_64 value of symlink /usr/lib64/libresample.so is different from the same symlink in the package libpjsip-devel-2.11-alt1.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.
warn libsdp-devel-1.1.108-alt2.0.17.ga6958ef.x86_64 value of symlink /usr/lib64/libsdp.so is different from the same symlink in the package libmpeg4ip-devel-1.5.0.1-alt17.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.
warn libspirv-llvm14.0-translator-devel-14.0.3-alt1.x86_64 value of symlink /usr/lib64/libLLVMSPIRVLib.so is different from the same symlink in the package libLLVMSPIRVLib-devel-18.1.4-alt1.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.
warn libucl-devel-1.03-alt4.x86_64 value of symlink /usr/lib64/libucl.so is different from the same symlink in the package libucl5-devel-0.8.1-alt1.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.
warn libucl5-devel-0.8.1-alt1.x86_64 value of symlink /usr/lib64/libucl.so is different from the same symlink in the package libucl-devel-1.03-alt4.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.
warn libwxBase3.0-devel-debuginfo-3.0.5.1-alt5.20240531.x86_64 value of symlink /usr/lib/debug/usr/bin/wxrc.debug is different from the same symlink in the package libwxBase3.2-devel-debuginfo-3.2.6-alt1.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.
warn libwxBase3.2-devel-debuginfo-3.2.6-alt1.x86_64 value of symlink /usr/lib/debug/usr/bin/wxrc.debug is different from the same symlink in the package libwxBase3.0-devel-debuginfo-3.0.5.1-alt5.20240531.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.
warn mailutils-debuginfo-3.17.90-alt1.x86_64 value of symlink /usr/lib/debug/usr/bin/mailx.debug is different from the same symlink in the package mailx-debuginfo-8.1.2-alt9.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.
warn mailx-debuginfo-8.1.2-alt9.x86_64 value of symlink /usr/lib/debug/usr/bin/mailx.debug is different from the same symlink in the package mailutils-debuginfo-3.17.90-alt1.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.
warn ocaml-gettext-debuginfo-0.4.2-alt5.x86_64 value of symlink /usr/lib/debug/.build-id/e6/f16ea08d598561dc96f26a483c28dec3fb3793.debug is different from the same symlink in the package ocaml-num-debuginfo-1.5-alt1.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.
warn ocaml-num-debuginfo-1.5-alt1.x86_64 value of symlink /usr/lib/debug/.build-id/e6/f16ea08d598561dc96f26a483c28dec3fb3793.debug is different from the same symlink in the package ocaml-gettext-debuginfo-0.4.2-alt5.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.
warn ossp-uuid-1.6.2-alt2.x86_64 value of symlink /usr/bin/uuid is different from the same symlink in the package uuid-2.3.9-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
warn proxifier-1.0.3-alt2.noarch value of symlink /usr/bin/pruby is different from the same symlink in the package proxifier2-1.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
warn proxifier2-1.1.0-alt1.noarch value of symlink /usr/bin/pruby is different from the same symlink in the package proxifier-1.0.3-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
warn ruby-debug-ide-0.7.3.2-alt0.1.noarch value of symlink /usr/bin/rdebug-ide is different from the same symlink in the package debug-ide-0.7.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
warn speed-dreams-2.3.0-alt1.x86_64 value of symlink /usr/lib64/libtgfclient.so is different from the same symlink in the package TORCS-1.3.7-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.
warn speed-dreams-debuginfo-2.3.0-alt1.x86_64 value of symlink /usr/lib/debug/usr/lib64/libtgfclient.so.debug is different from the same symlink in the package TORCS-debuginfo-1.3.7-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.
warn tomcat-el-3.0-api-9.0.83-alt1_1jpp11.noarch value of symlink /usr/share/java/tomcat-el-api.jar is different from the same symlink in the package tomcat10-lib-10.1.20-alt2_jvm17.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
warn tomcat-jsp-2.3-api-9.0.83-alt1_1jpp11.noarch value of symlink /usr/share/java/tomcat-jsp-api.jar is different from the same symlink in the package tomcat10-lib-10.1.20-alt2_jvm17.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
warn tomcat-servlet-4.0-api-9.0.83-alt1_1jpp11.noarch value of symlink /usr/share/java/tomcat-servlet-api.jar is different from the same symlink in the package tomcat10-lib-10.1.20-alt2_jvm17.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
warn tomcat10-lib-10.1.20-alt2_jvm17.noarch value of symlink /usr/share/java/tomcat-servlet-api.jar is different from the same symlink in the package tomcat-servlet-4.0-api-9.0.83-alt1_1jpp11.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
warn utils-0.34.0-alt1.noarch value of symlink /usr/bin/edit is different from the same symlink in the package vi-traditional-4.1.3-alt1.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.
warn uuid-2.3.9-alt1.noarch value of symlink /usr/bin/uuid is different from the same symlink in the package ossp-uuid-1.6.2-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.
warn vi-traditional-4.1.3-alt1.x86_64 value of symlink /usr/share/man/man1/view.1.xz is different from the same symlink in the package vim-common-9.1.0050-alt4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
warn vim-common-9.1.0050-alt4.noarch value of symlink /usr/share/man/man1/view.1.xz is different from the same symlink in the package vi-traditional-4.1.3-alt1.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.

generated by repocop at Thu Nov 21 02:24:37 2024