Repocop reports by test

  status rpm id message
warn chromium-debuginfo-86.0.4240.111-alt1.x86_64 value of symlink /usr/lib/debug/.build-id/4e/54b14b6e52af66557efdb4e89cc3db558fd5c9 is different from the same symlink in the package chromium-gost-debuginfo-86.0.4240.111-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.
value of symlink /usr/lib/debug/.build-id/4e/54b14b6e52af66557efdb4e89cc3db558fd5c9.debug is different from the same symlink in the package chromium-gost-debuginfo-86.0.4240.111-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 chromium-gost-debuginfo-86.0.4240.111-alt1.x86_64 value of symlink /usr/lib/debug/.build-id/4e/54b14b6e52af66557efdb4e89cc3db558fd5c9 is different from the same symlink in the package chromium-debuginfo-86.0.4240.111-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.
value of symlink /usr/lib/debug/.build-id/4e/54b14b6e52af66557efdb4e89cc3db558fd5c9.debug is different from the same symlink in the package chromium-debuginfo-86.0.4240.111-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 clang10.0-10.0.1-alt2.x86_64 value of symlink /usr/bin/clang is different from the same symlink in the package clang11.0-11.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 clang10.0-debuginfo-10.0.1-alt2.x86_64 value of symlink /usr/lib/debug/usr/bin/clang++.debug is different from the same symlink in the package clang11.0-debuginfo-11.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.
value of symlink /usr/lib/debug/usr/bin/clang-cl.debug is different from the same symlink in the package clang11.0-debuginfo-11.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.
value of symlink /usr/lib/debug/usr/bin/clang-cpp.debug is different from the same symlink in the package clang11.0-debuginfo-11.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.
value of symlink /usr/lib/debug/usr/bin/clang.debug is different from the same symlink in the package clang11.0-debuginfo-11.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 clang10.0-devel-10.0.1-alt2.x86_64 value of symlink /usr/lib64/libclang-cpp.so is different from the same symlink in the package clang11.0-devel-11.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.
value of symlink /usr/lib64/libclang.so is different from the same symlink in the package clang11.0-devel-11.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 clang11.0-11.0.0-alt1.x86_64 value of symlink /usr/bin/clang is different from the same symlink in the package clang10.0-10.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.
warn clang11.0-debuginfo-11.0.0-alt1.x86_64 value of symlink /usr/lib/debug/usr/bin/clang++.debug is different from the same symlink in the package clang10.0-debuginfo-10.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 clang10.0-debuginfo-10.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 clang10.0-debuginfo-10.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 clang10.0-debuginfo-10.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.
warn clang11.0-devel-11.0.0-alt1.x86_64 value of symlink /usr/lib64/libclang-cpp.so is different from the same symlink in the package clang10.0-devel-10.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/libclang.so is different from the same symlink in the package clang10.0-devel-10.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.
warn crtools-debuginfo-3.14-alt2.x86_64 value of symlink /usr/lib/debug/usr/sbin/crtools.debug is different from the same symlink in the package crtools-ovz-debuginfo-3.12.5.50-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 crtools-ovz-debuginfo-3.12.5.50-alt1.x86_64 value of symlink /usr/lib/debug/usr/sbin/crtools.debug is different from the same symlink in the package crtools-debuginfo-3.14-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 libatlas-devel-3.9.35-alt1.qa1.x86_64 value of symlink /usr/lib64/libblas.so is different from the same symlink in the package libblas-devel-3.9.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 libblas-devel-3.9.2-alt2.x86_64 value of symlink /usr/lib64/libblas.so is different from the same symlink in the package libatlas-devel-3.9.35-alt1.qa1.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.7-devel-static-4.7.25-alt9.x86_64 value of symlink /usr/lib64/libdb.a is different from the same symlink in the package libdb4.8-devel-static-4.8.30-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 libdb4.7_cxx-devel-static-4.7.25-alt9.x86_64 value of symlink /usr/lib64/libdb_cxx.a is different from the same symlink in the package libdb4.8_cxx-devel-static-4.8.30-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 libdb4.8-devel-static-4.8.30-alt4.x86_64 value of symlink /usr/lib64/libdb.a is different from the same symlink in the package libdb4.7-devel-static-4.7.25-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 libdb4.8_cxx-devel-static-4.8.30-alt4.x86_64 value of symlink /usr/lib64/libdb_cxx.a is different from the same symlink in the package libdb4.7_cxx-devel-static-4.7.25-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 libdb4.8_java-devel-4.8.30-alt4.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-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 libdb6.1_java-devel-6.1.19-alt6.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-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 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.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.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-9.53.3-alt1.x86_64 value of symlink /usr/lib64/libgxps.so is different from the same symlink in the package libgxps-devel-0.3.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 libgxps-devel-0.3.1-alt1.x86_64 value of symlink /usr/lib64/libgxps.so is different from the same symlink in the package libgs-devel-9.53.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 libhdf5-8-mpi-debuginfo-1.8.13-alt4.x86_64 value of symlink /usr/lib/debug/usr/lib64/libhdf5.so.8.0.2.debug is different from the same symlink in the package libhdf5-8-seq-debuginfo-1.8.13-alt1.qa4.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/lib64/libhdf5.so.8.debug is different from the same symlink in the package libhdf5-8-seq-debuginfo-1.8.13-alt1.qa4.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/lib64/libhdf5_hl.so.8.0.2.debug is different from the same symlink in the package libhdf5-8-seq-debuginfo-1.8.13-alt1.qa4.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/lib64/libhdf5_hl.so.8.debug is different from the same symlink in the package libhdf5-8-seq-debuginfo-1.8.13-alt1.qa4.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 libhdf5-8-seq-debuginfo-1.8.13-alt1.qa4.x86_64 value of symlink /usr/lib/debug/usr/lib64/libhdf5.so.8.0.2.debug is different from the same symlink in the package libhdf5-8-mpi-debuginfo-1.8.13-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.
value of symlink /usr/lib/debug/usr/lib64/libhdf5.so.8.debug is different from the same symlink in the package libhdf5-8-mpi-debuginfo-1.8.13-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.
value of symlink /usr/lib/debug/usr/lib64/libhdf5_hl.so.8.0.2.debug is different from the same symlink in the package libhdf5-8-mpi-debuginfo-1.8.13-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.
value of symlink /usr/lib/debug/usr/lib64/libhdf5_hl.so.8.debug is different from the same symlink in the package libhdf5-8-mpi-debuginfo-1.8.13-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 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.103-alt1.qa1.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 libnetcdf11-mpi-debuginfo-4.4.1.1-alt2.x86_64 value of symlink /usr/lib/debug/usr/lib64/libnetcdf.so.11.0.4.debug is different from the same symlink in the package libnetcdf11-seq-debuginfo-4.4.1.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/lib64/libnetcdf.so.11.debug is different from the same symlink in the package libnetcdf11-seq-debuginfo-4.4.1.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.
warn libnetcdf11-seq-debuginfo-4.4.1.1-alt3.x86_64 value of symlink /usr/lib/debug/usr/lib64/libnetcdf.so.11.0.4.debug is different from the same symlink in the package libnetcdf11-mpi-debuginfo-4.4.1.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/lib64/libnetcdf.so.11.debug is different from the same symlink in the package libnetcdf11-mpi-debuginfo-4.4.1.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.
warn libnetcdf_c++-4-mpi-debuginfo-4.2-alt5.x86_64 value of symlink /usr/lib/debug/usr/lib64/libnetcdf_c++.so.4.2.0.debug is different from the same symlink in the package libnetcdf_c++-4-seq-debuginfo-4.2-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/lib64/libnetcdf_c++.so.4.debug is different from the same symlink in the package libnetcdf_c++-4-seq-debuginfo-4.2-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 libnetcdf_c++-4-seq-debuginfo-4.2-alt3.x86_64 value of symlink /usr/lib/debug/usr/lib64/libnetcdf_c++.so.4.2.0.debug is different from the same symlink in the package libnetcdf_c++-4-mpi-debuginfo-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.
value of symlink /usr/lib/debug/usr/lib64/libnetcdf_c++.so.4.debug is different from the same symlink in the package libnetcdf_c++-4-mpi-debuginfo-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 libnetcdf_c++4-1-mpi-debuginfo-4.3.0-alt2.x86_64 value of symlink /usr/lib/debug/usr/lib64/libnetcdf_c++4.so.1.0.3.debug is different from the same symlink in the package libnetcdf_c++4-1-seq-debuginfo-4.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.
value of symlink /usr/lib/debug/usr/lib64/libnetcdf_c++4.so.1.debug is different from the same symlink in the package libnetcdf_c++4-1-seq-debuginfo-4.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 libnetcdf_c++4-1-seq-debuginfo-4.3.0-alt1.x86_64 value of symlink /usr/lib/debug/usr/lib64/libnetcdf_c++4.so.1.0.3.debug is different from the same symlink in the package libnetcdf_c++4-1-mpi-debuginfo-4.3.0-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/lib64/libnetcdf_c++4.so.1.debug is different from the same symlink in the package libnetcdf_c++4-1-mpi-debuginfo-4.3.0-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 libnetcdff6-mpi-debuginfo-4.4.4-alt2.x86_64 value of symlink /usr/lib/debug/usr/lib64/libnetcdff.so.6.1.1.debug is different from the same symlink in the package libnetcdff6-seq-debuginfo-4.4.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.
value of symlink /usr/lib/debug/usr/lib64/libnetcdff.so.6.debug is different from the same symlink in the package libnetcdff6-seq-debuginfo-4.4.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 libnetcdff6-seq-debuginfo-4.4.4-alt1.x86_64 value of symlink /usr/lib/debug/usr/lib64/libnetcdff.so.6.1.1.debug is different from the same symlink in the package libnetcdff6-mpi-debuginfo-4.4.4-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/lib64/libnetcdff.so.6.debug is different from the same symlink in the package libnetcdff6-mpi-debuginfo-4.4.4-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 libopusfile-0.9-alt1.x86_64 value of symlink /usr/lib64/libopusfile.so.0 is different from the same symlink in the package libopusfile0-0.11-alt0.5.gd2577d7.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/libopusurl.so.0 is different from the same symlink in the package libopusurl0-0.11-alt0.5.gd2577d7.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 libopusfile-debuginfo-0.9-alt1.x86_64 value of symlink /usr/lib/debug/usr/lib64/libopusfile.so.0.debug is different from the same symlink in the package libopusfile0-debuginfo-0.11-alt0.5.gd2577d7.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/lib64/libopusurl.so.0.debug is different from the same symlink in the package libopusurl0-debuginfo-0.11-alt0.5.gd2577d7.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 libopusfile-devel-0.9-alt1.x86_64 value of symlink /usr/lib64/libopusfile.so is different from the same symlink in the package opusfile-devel-0.11-alt0.5.gd2577d7.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/libopusurl.so is different from the same symlink in the package opusurl-devel-0.11-alt0.5.gd2577d7.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 libopusfile0-0.11-alt0.5.gd2577d7.x86_64 value of symlink /usr/lib64/libopusfile.so.0 is different from the same symlink in the package libopusfile-0.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 libopusfile0-debuginfo-0.11-alt0.5.gd2577d7.x86_64 value of symlink /usr/lib/debug/usr/lib64/libopusfile.so.0.debug is different from the same symlink in the package libopusfile-debuginfo-0.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 libopusurl0-0.11-alt0.5.gd2577d7.x86_64 value of symlink /usr/lib64/libopusurl.so.0 is different from the same symlink in the package libopusfile-0.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 libopusurl0-debuginfo-0.11-alt0.5.gd2577d7.x86_64 value of symlink /usr/lib/debug/usr/lib64/libopusurl.so.0.debug is different from the same symlink in the package libopusfile-debuginfo-0.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 libpjsip-devel-2.8-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-7.0.3-alt3.x86_64 value of symlink /usr/lib64/libhistory.so is different from the same symlink in the package libreadline5-devel-5.2.14-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 libreadline5-devel-5.2.14-alt6.x86_64 value of symlink /usr/lib64/libhistory.so is different from the same symlink in the package libreadline-devel-7.0.3-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 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.8-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.103-alt1.qa1.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 libstrophe-devel-0.9.3-alt1.x86_64 value of symlink /usr/lib64/libstrophe.so is different from the same symlink in the package netxms-server-2.2.11-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 libticables-devel-1.3.4-alt1_1.x86_64 value of symlink /usr/lib64/libticables2.so is different from the same symlink in the package libticables2-devel-1.3.5-alt1_4.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 libticables2-devel-1.3.5-alt1_4.x86_64 value of symlink /usr/lib64/libticables2.so is different from the same symlink in the package libticables-devel-1.3.4-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 libwxBase3.0-devel-debuginfo-3.0.4-alt6.x86_64 value of symlink /usr/lib/debug/usr/bin/wxrc.debug is different from the same symlink in the package libwxGTK-devel-debuginfo-2.8.12-alt1.svn20131012.6.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/wxrc.debug is different from the same symlink in the package libwxBase3.1-devel-debuginfo-3.1.3-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 libwxBase3.1-devel-debuginfo-3.1.3-alt2.x86_64 value of symlink /usr/lib/debug/usr/bin/wxrc.debug is different from the same symlink in the package libwxGTK-devel-debuginfo-2.8.12-alt1.svn20131012.6.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/wxrc.debug is different from the same symlink in the package libwxBase3.0-devel-debuginfo-3.0.4-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 libwxGTK-devel-debuginfo-2.8.12-alt1.svn20131012.6.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.4-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.
value of symlink /usr/lib/debug/usr/bin/wxrc.debug is different from the same symlink in the package libwxBase3.1-devel-debuginfo-3.1.3-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 llvm10.0-devel-10.0.1-alt2.x86_64 value of symlink /usr/lib64/libLLVM.so is different from the same symlink in the package llvm11.0-devel-11.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.
value of symlink /usr/lib64/libLTO.so is different from the same symlink in the package llvm11.0-devel-11.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.
value of symlink /usr/lib64/libRemarks.so is different from the same symlink in the package llvm11.0-devel-11.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 llvm11.0-devel-11.0.0-alt1.x86_64 value of symlink /usr/lib64/libLLVM.so is different from the same symlink in the package llvm10.0-devel-10.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 llvm10.0-devel-10.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/libRemarks.so is different from the same symlink in the package llvm10.0-devel-10.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.
warn mailutils-debuginfo-3.10-alt0.20200913.1.x86_64 value of symlink /usr/lib/debug/usr/bin/Mail.debug is different from the same symlink in the package mailx-debuginfo-8.1.2-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.
value of symlink /usr/lib/debug/usr/bin/mailx.debug is different from the same symlink in the package mailx-debuginfo-8.1.2-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 mailx-debuginfo-8.1.2-alt7.x86_64 value of symlink /usr/lib/debug/usr/bin/Mail.debug is different from the same symlink in the package mailutils-debuginfo-3.10-alt0.20200913.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.
value of symlink /usr/lib/debug/usr/bin/mailx.debug is different from the same symlink in the package mailutils-debuginfo-3.10-alt0.20200913.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 netxms-server-2.2.11-alt2.x86_64 value of symlink /usr/lib64/libstrophe.so is different from the same symlink in the package libstrophe-devel-0.9.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 opusfile-devel-0.11-alt0.5.gd2577d7.x86_64 value of symlink /usr/lib64/libopusfile.so is different from the same symlink in the package libopusfile-devel-0.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 opusurl-devel-0.11-alt0.5.gd2577d7.x86_64 value of symlink /usr/lib64/libopusurl.so is different from the same symlink in the package libopusfile-devel-0.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 vi-traditional-4.1.3-alt1.x86_64 value of symlink /usr/bin/view is different from the same symlink in the package vim-common-8.2.0011-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.
value of symlink /usr/share/man/man1/view.1.xz is different from the same symlink in the package vim-common-8.2.0011-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 vim-common-8.2.0011-alt2.noarch value of symlink /usr/bin/view 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.
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 Sun Nov 1 04:32:24 2020