Repocop reports by test

  status rpm id message
warn branding-altlinux-centaurus-alterator-7.0.5-alt1.noarch value of symlink /usr/share/alterator/design/images/steps/install2-basesystem.png is different from the same symlink in the package branding-xalt-kworkstation-alterator-8.3.0-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.
value of symlink /usr/share/alterator/design/images/steps/install2-preinstall.png is different from the same symlink in the package branding-xalt-kworkstation-alterator-8.3.0-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.
value of symlink /usr/share/alterator/design/images/steps/notes-release-notes.png is different from the same symlink in the package branding-xalt-kworkstation-alterator-8.3.0-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.
value of symlink /usr/share/alterator/design/images/steps/pkg-groups.png is different from the same symlink in the package branding-xalt-kworkstation-alterator-8.3.0-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.
value of symlink /usr/share/alterator/design/images/steps/root.png is different from the same symlink in the package branding-xalt-kworkstation-alterator-8.3.0-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.
value of symlink /usr/share/alterator/design/images/steps/timezone.png is different from the same symlink in the package branding-xalt-kworkstation-alterator-8.3.0-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.
warn branding-altlinux-spt-alterator-7.0.0-alt1.noarch value of symlink /usr/share/alterator/design/images/steps/install2-basesystem.png is different from the same symlink in the package branding-xalt-kworkstation-alterator-8.3.0-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.
value of symlink /usr/share/alterator/design/images/steps/install2-preinstall.png is different from the same symlink in the package branding-xalt-kworkstation-alterator-8.3.0-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.
value of symlink /usr/share/alterator/design/images/steps/notes-release-notes.png is different from the same symlink in the package branding-xalt-kworkstation-alterator-8.3.0-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.
value of symlink /usr/share/alterator/design/images/steps/pkg-groups.png is different from the same symlink in the package branding-xalt-kworkstation-alterator-8.3.0-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.
value of symlink /usr/share/alterator/design/images/steps/root.png is different from the same symlink in the package branding-xalt-kworkstation-alterator-8.3.0-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.
value of symlink /usr/share/alterator/design/images/steps/timezone.png is different from the same symlink in the package branding-xalt-kworkstation-alterator-8.3.0-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.
warn branding-xalt-kworkstation-alterator-8.3.0-alt3.noarch value of symlink /usr/share/alterator/design/images/steps/install2-basesystem.png is different from the same symlink in the package branding-altlinux-spt-alterator-7.0.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.
value of symlink /usr/share/alterator/design/images/steps/install2-basesystem.png is different from the same symlink in the package branding-altlinux-centaurus-alterator-7.0.5-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.
value of symlink /usr/share/alterator/design/images/steps/install2-preinstall.png is different from the same symlink in the package branding-altlinux-spt-alterator-7.0.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.
value of symlink /usr/share/alterator/design/images/steps/install2-preinstall.png is different from the same symlink in the package branding-altlinux-centaurus-alterator-7.0.5-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.
value of symlink /usr/share/alterator/design/images/steps/notes-release-notes.png is different from the same symlink in the package branding-altlinux-spt-alterator-7.0.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.
value of symlink /usr/share/alterator/design/images/steps/notes-release-notes.png is different from the same symlink in the package branding-altlinux-centaurus-alterator-7.0.5-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.
value of symlink /usr/share/alterator/design/images/steps/pkg-groups.png is different from the same symlink in the package branding-altlinux-spt-alterator-7.0.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.
value of symlink /usr/share/alterator/design/images/steps/pkg-groups.png is different from the same symlink in the package branding-altlinux-centaurus-alterator-7.0.5-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.
value of symlink /usr/share/alterator/design/images/steps/root.png is different from the same symlink in the package branding-altlinux-spt-alterator-7.0.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.
value of symlink /usr/share/alterator/design/images/steps/root.png is different from the same symlink in the package branding-altlinux-centaurus-alterator-7.0.5-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.
value of symlink /usr/share/alterator/design/images/steps/timezone.png is different from the same symlink in the package branding-altlinux-spt-alterator-7.0.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.
value of symlink /usr/share/alterator/design/images/steps/timezone.png is different from the same symlink in the package branding-altlinux-centaurus-alterator-7.0.5-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 exim-common-4.90.1-alt2.1.x86_64 value of symlink /etc/aliases is different from the same symlink in the package postfix-2.11.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.
value of symlink /usr/sbin/sendmail is different from the same symlink in the package msmtp-sendmail-1.6.6-alt1.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 kde5-smplayer-debuginfo-18.9.0.9113-alt1.S1.x86_64 value of symlink /usr/lib/debug/.build-id/da/845fc5e54cf96237e400eea500b045e3e938cb is different from the same symlink in the package smplayer-debuginfo-18.9.0-alt1.9113.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/da/845fc5e54cf96237e400eea500b045e3e938cb.debug is different from the same symlink in the package smplayer-debuginfo-18.9.0-alt1.9113.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 kubernetes-client-1.13.2-alt1.noarch value of symlink /usr/bin/kubectl is different from the same symlink in the package origin-clients-3.11.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 libarpack-devel-96-alt11.x86_64 value of symlink /usr/lib64/libarpack.so is different from the same symlink in the package libarpack-ng-devel-3.7.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 libarpack-ng-devel-3.7.0-alt1.x86_64 value of symlink /usr/lib64/libarpack.so is different from the same symlink in the package libarpack-devel-96-alt11.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-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 libblas-devel-3.9.2-alt1.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.2.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 libglfw3-devel-3.2.1-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 libgnustep-gdl2-devel-0.12.0-alt5.svn20130819.1.x86_64 value of symlink /usr/lib64/libEOControl.so is different from the same symlink in the package libsope-devel-4.0.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 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 libmysqlclient20-devel-5.7.24-alt2.x86_64 value of symlink /usr/lib64/libmysqlclient.so is different from the same symlink in the package libmysqlclient21-devel-8.0.15-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 libmysqlclient21-devel-8.0.15-alt1.x86_64 value of symlink /usr/lib64/libmysqlclient.so is different from the same symlink in the package libmysqlclient20-devel-5.7.24-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 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-alt4.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-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/libnetcdf_c++.so.4.debug is different from the same symlink in the package libnetcdf_c++-4-mpi-debuginfo-4.2-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 libnetcdf_c++4-1-mpi-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-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-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-mpi-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 libnetcdff6-mpi-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-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-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-mpi-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 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 libqca-devel-1.0-alt4.1.x86_64 value of symlink /usr/lib64/libqca.so is different from the same symlink in the package libqca2-devel-2.2.0-alt0.1.S1.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 libqca2-devel-2.2.0-alt0.1.S1.x86_64 value of symlink /usr/lib64/libqca.so is different from the same symlink in the package libqca-devel-1.0-alt4.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 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-alt5.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 libreadline5-devel-5.2.14-alt5.1.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 libsope-devel-4.0.5-alt1.x86_64 value of symlink /usr/lib64/libEOControl.so is different from the same symlink in the package libgnustep-gdl2-devel-0.12.0-alt5.svn20130819.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/lib64/libXmlRpc.so is different from the same symlink in the package libxmlrpcxx-devel-0.7-alt2.git20100306.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.2-alt1.1.x86_64 value of symlink /usr/lib64/libstrophe.so is different from the same symlink in the package netxms-server-2.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 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 libwbclient-DC-debuginfo-4.9.4-alt2.x86_64 value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.14.debug is different from the same symlink in the package libwbclient-debuginfo-4.9.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/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-sssd-debuginfo-2.0.0-alt3.gitf0603645f.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/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-debuginfo-4.9.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 libwbclient-debuginfo-4.9.4-alt2.x86_64 value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.14.debug is different from the same symlink in the package libwbclient-DC-debuginfo-4.9.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/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-sssd-debuginfo-2.0.0-alt3.gitf0603645f.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/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-DC-debuginfo-4.9.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 libwbclient-sssd-debuginfo-2.0.0-alt3.gitf0603645f.x86_64 value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-DC-debuginfo-4.9.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/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-debuginfo-4.9.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 libwxBase3.0-devel-debuginfo-3.0.4-alt3.2.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.5.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.1-alt2.2.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.1-alt2.2.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.5.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-alt3.2.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.5.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-alt3.2.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.1-alt2.2.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 libxmlrpcxx-devel-0.7-alt2.git20100306.x86_64 value of symlink /usr/lib64/libXmlRpc.so is different from the same symlink in the package libsope-devel-4.0.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 mailutils-debuginfo-3.5.90-alt1.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.5.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.
value of symlink /usr/lib/debug/usr/bin/mailx.debug is different from the same symlink in the package mailutils-debuginfo-3.5.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 monetdb-common-11.27.11-alt1.2.qa1.x86_64 value of symlink /usr/lib64/libmapi.so is different from the same symlink in the package openchange-devel-2.4-alt33.zentyal23.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 moodle-base-1.9.19.20130513-alt1.noarch value of symlink /var/www/webapps/moodle/lib/default.ttf is different from the same symlink in the package moodle3.3-base-3.3.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 moodle3.3-base-3.3.3-alt2.noarch value of symlink /var/www/webapps/moodle/lib/default.ttf is different from the same symlink in the package moodle-base-1.9.19.20130513-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 msmtp-sendmail-1.6.6-alt1.1.noarch value of symlink /usr/sbin/sendmail is different from the same symlink in the package exim-common-4.90.1-alt2.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-alt1.x86_64 value of symlink /usr/lib64/libstrophe.so is different from the same symlink in the package libstrophe-devel-0.9.2-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 openchange-devel-2.4-alt33.zentyal23.x86_64 value of symlink /usr/lib64/libmapi.so is different from the same symlink in the package monetdb-common-11.27.11-alt1.2.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 origin-clients-3.11.0-alt1.x86_64 value of symlink /usr/bin/kubectl is different from the same symlink in the package kubernetes-client-1.13.2-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 postfix-2.11.11-alt1.x86_64 value of symlink /etc/aliases is different from the same symlink in the package exim-common-4.90.1-alt2.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 samba-DC-winbind-clients-4.9.4-alt2.x86_64 value of symlink /lib64/libnss_winbind.so.2 is different from the same symlink in the package samba-winbind-clients-4.9.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 /lib64/libnss_wins.so.2 is different from the same symlink in the package samba-winbind-clients-4.9.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 samba-winbind-clients-4.9.4-alt2.x86_64 value of symlink /lib64/libnss_winbind.so.2 is different from the same symlink in the package samba-DC-winbind-clients-4.9.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 /lib64/libnss_wins.so.2 is different from the same symlink in the package samba-DC-winbind-clients-4.9.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 smplayer-debuginfo-18.9.0-alt1.9113.x86_64 value of symlink /usr/lib/debug/.build-id/da/845fc5e54cf96237e400eea500b045e3e938cb is different from the same symlink in the package kde5-smplayer-debuginfo-18.9.0.9113-alt1.S1.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/da/845fc5e54cf96237e400eea500b045e3e938cb.debug is different from the same symlink in the package kde5-smplayer-debuginfo-18.9.0.9113-alt1.S1.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 Mon Feb 18 04:40:13 2019