warn	bacula11-common-debuginfo-11.0.5-alt2.x86_64	value of symlink /usr/lib/debug/usr/lib64/libbac.so.debug is different from the same symlink in the package bacula9-common-debuginfo-9.6.7-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/libbaccfg.so.debug is different from the same symlink in the package bacula9-common-debuginfo-9.6.7-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/libbacfind.so.debug is different from the same symlink in the package bacula9-common-debuginfo-9.6.7-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/libbacsd.so.debug is different from the same symlink in the package bacula9-common-debuginfo-9.6.7-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	bacula11-director-common-debuginfo-11.0.5-alt2.x86_64	value of symlink /usr/lib/debug/usr/lib64/libbacsql.so.debug is different from the same symlink in the package bacula9-director-common-debuginfo-9.6.7-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	bacula11-director-mysql-debuginfo-11.0.5-alt2.x86_64	value of symlink /usr/lib/debug/usr/lib64/libbaccats-mysql.so.debug is different from the same symlink in the package bacula9-director-mysql-debuginfo-9.6.7-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	bacula11-director-postgresql-debuginfo-11.0.5-alt2.x86_64	value of symlink /usr/lib/debug/usr/lib64/libbaccats-postgresql.so.debug is different from the same symlink in the package bacula9-director-postgresql-debuginfo-9.6.7-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	bacula11-director-sqlite3-debuginfo-11.0.5-alt2.x86_64	value of symlink /usr/lib/debug/usr/lib64/libbaccats-sqlite3.so.debug is different from the same symlink in the package bacula9-director-sqlite3-debuginfo-9.6.7-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	bacula9-common-debuginfo-9.6.7-alt1.x86_64	value of symlink /usr/lib/debug/usr/lib64/libbac.so.debug is different from the same symlink in the package bacula11-common-debuginfo-11.0.5-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/libbaccfg.so.debug is different from the same symlink in the package bacula11-common-debuginfo-11.0.5-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/libbacfind.so.debug is different from the same symlink in the package bacula11-common-debuginfo-11.0.5-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/libbacsd.so.debug is different from the same symlink in the package bacula11-common-debuginfo-11.0.5-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	bacula9-director-common-debuginfo-9.6.7-alt1.x86_64	value of symlink /usr/lib/debug/usr/lib64/libbacsql.so.debug is different from the same symlink in the package bacula11-director-common-debuginfo-11.0.5-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	bacula9-director-mysql-debuginfo-9.6.7-alt1.x86_64	value of symlink /usr/lib/debug/usr/lib64/libbaccats-mysql.so.debug is different from the same symlink in the package bacula11-director-mysql-debuginfo-11.0.5-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	bacula9-director-postgresql-debuginfo-9.6.7-alt1.x86_64	value of symlink /usr/lib/debug/usr/lib64/libbaccats-postgresql.so.debug is different from the same symlink in the package bacula11-director-postgresql-debuginfo-11.0.5-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	bacula9-director-sqlite3-debuginfo-9.6.7-alt1.x86_64	value of symlink /usr/lib/debug/usr/lib64/libbaccats-sqlite3.so.debug is different from the same symlink in the package bacula11-director-sqlite3-debuginfo-11.0.5-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	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-9.2.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-9.2.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-9.2.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-9.2.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-9.2.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-9.2.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-9.2.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-9.2.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-9.2.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-9.2.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-9.2.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-9.2.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-9.2.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-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-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-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/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/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/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/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/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/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/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/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.; 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.; 
warn	clang10.0-10.0.0-alt0.2.p9.x86_64	value of symlink /usr/bin/clang is different from the same symlink in the package llvm-common-clang-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/clang++ is different from the same symlink in the package llvm-common-clang-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/clang-cl is different from the same symlink in the package llvm-common-clang-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/clang-cpp is different from the same symlink in the package llvm-common-clang-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	clang10.0-debuginfo-10.0.0-alt0.2.p9.x86_64	value of symlink /usr/lib/debug/usr/bin/clang++.debug is different from the same symlink in the package clang7.0-debuginfo-7.0.1-alt4.rel.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/bin/clang-cl.debug is different from the same symlink in the package clang7.0-debuginfo-7.0.1-alt4.rel.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/bin/clang-cpp.debug is different from the same symlink in the package clang7.0-debuginfo-7.0.1-alt4.rel.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/bin/clang.debug is different from the same symlink in the package clang7.0-debuginfo-7.0.1-alt4.rel.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	clang7.0-7.0.1-alt4.rel.x86_64	value of symlink /usr/bin/clang is different from the same symlink in the package llvm-common-clang-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/clang++ is different from the same symlink in the package llvm-common-clang-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/clang-cl is different from the same symlink in the package llvm-common-clang-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/clang-cpp is different from the same symlink in the package llvm-common-clang-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	clang7.0-debuginfo-7.0.1-alt4.rel.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.0-alt0.2.p9.x86_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.0-alt0.2.p9.x86_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.0-alt0.2.p9.x86_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.0-alt0.2.p9.x86_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	libgs-devel-9.27-alt1.M90P.1.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.27-alt1.M90P.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	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.108-alt1.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	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	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.108-alt1.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	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-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-alt5.x86_64	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.; 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.; 
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 libwxBase3.0-devel-debuginfo-3.0.4-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/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.; 
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-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/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	lld-7.0.1-alt4.rel.x86_64	value of symlink /usr/bin/ld.lld is different from the same symlink in the package llvm-common-lld-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/ld64.lld is different from the same symlink in the package llvm-common-lld-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/lld-link is different from the same symlink in the package llvm-common-lld-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/wasm-ld is different from the same symlink in the package llvm-common-lld-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	lld10.0-10.0.0-alt0.2.p9.x86_64	value of symlink /usr/bin/ld.lld is different from the same symlink in the package llvm-common-lld-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/ld64.lld is different from the same symlink in the package llvm-common-lld-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/lld-link is different from the same symlink in the package llvm-common-lld-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/wasm-ld is different from the same symlink in the package llvm-common-lld-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	llvm-common-clang-11.0.1-alt3.noarch	value of symlink /usr/bin/clang is different from the same symlink in the package clang10.0-10.0.0-alt0.2.p9.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/clang is different from the same symlink in the package clang7.0-7.0.1-alt4.rel.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/clang++ is different from the same symlink in the package clang10.0-10.0.0-alt0.2.p9.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/clang++ is different from the same symlink in the package clang7.0-7.0.1-alt4.rel.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/clang-cl is different from the same symlink in the package clang10.0-10.0.0-alt0.2.p9.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/clang-cl is different from the same symlink in the package clang7.0-7.0.1-alt4.rel.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/clang-cpp is different from the same symlink in the package clang10.0-10.0.0-alt0.2.p9.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/clang-cpp is different from the same symlink in the package clang7.0-7.0.1-alt4.rel.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	llvm-common-lld-11.0.1-alt3.noarch	value of symlink /usr/bin/ld.lld is different from the same symlink in the package lld-7.0.1-alt4.rel.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/ld.lld is different from the same symlink in the package lld10.0-10.0.0-alt0.2.p9.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/ld64.lld is different from the same symlink in the package lld-7.0.1-alt4.rel.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/ld64.lld is different from the same symlink in the package lld10.0-10.0.0-alt0.2.p9.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/lld-link is different from the same symlink in the package lld-7.0.1-alt4.rel.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/lld-link is different from the same symlink in the package lld10.0-10.0.0-alt0.2.p9.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/wasm-ld is different from the same symlink in the package lld-7.0.1-alt4.rel.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/wasm-ld is different from the same symlink in the package lld10.0-10.0.0-alt0.2.p9.x86_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	llvm-common-util-11.0.1-alt3.noarch	value of symlink /usr/bin/llvm-addr2line is different from the same symlink in the package llvm10.0-10.0.0-alt0.2.p9.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/llvm-dlltool is different from the same symlink in the package llvm10.0-10.0.0-alt0.2.p9.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/llvm-dlltool is different from the same symlink in the package llvm7.0-7.0.1-alt4.rel.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/llvm-install-name-tool is different from the same symlink in the package llvm10.0-10.0.0-alt0.2.p9.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/llvm-lib is different from the same symlink in the package llvm10.0-10.0.0-alt0.2.p9.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/llvm-lib is different from the same symlink in the package llvm7.0-7.0.1-alt4.rel.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/llvm-ranlib is different from the same symlink in the package llvm10.0-10.0.0-alt0.2.p9.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/llvm-ranlib is different from the same symlink in the package llvm7.0-7.0.1-alt4.rel.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/llvm-readelf is different from the same symlink in the package llvm10.0-10.0.0-alt0.2.p9.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/llvm-readelf is different from the same symlink in the package llvm7.0-7.0.1-alt4.rel.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/llvm-strip is different from the same symlink in the package llvm10.0-10.0.0-alt0.2.p9.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/llvm-strip is different from the same symlink in the package llvm7.0-7.0.1-alt4.rel.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	llvm10.0-10.0.0-alt0.2.p9.x86_64	value of symlink /usr/bin/llvm-addr2line is different from the same symlink in the package llvm-common-util-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/llvm-dlltool is different from the same symlink in the package llvm-common-util-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/llvm-install-name-tool is different from the same symlink in the package llvm-common-util-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/llvm-lib is different from the same symlink in the package llvm-common-util-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/llvm-ranlib is different from the same symlink in the package llvm-common-util-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/llvm-readelf is different from the same symlink in the package llvm-common-util-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/llvm-strip is different from the same symlink in the package llvm-common-util-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	llvm7.0-7.0.1-alt4.rel.x86_64	value of symlink /usr/bin/llvm-dlltool is different from the same symlink in the package llvm-common-util-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/llvm-lib is different from the same symlink in the package llvm-common-util-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/llvm-ranlib is different from the same symlink in the package llvm-common-util-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/llvm-readelf is different from the same symlink in the package llvm-common-util-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/llvm-strip is different from the same symlink in the package llvm-common-util-11.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	mailutils-debuginfo-3.15-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.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.; value of symlink /usr/lib/debug/usr/bin/mailx.debug is different from the same symlink in the package mailutils-debuginfo-3.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	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.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	qgis-devel-2.18.28-alt4.1.p9.x86_64	value of symlink /usr/lib64/libqgis_analysis.so is different from the same symlink in the package qgis3-devel-3.18.3-alt0.p9.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/libqgis_app.so is different from the same symlink in the package qgis3-devel-3.18.3-alt0.p9.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/libqgis_core.so is different from the same symlink in the package qgis3-devel-3.18.3-alt0.p9.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/libqgis_gui.so is different from the same symlink in the package qgis3-devel-3.18.3-alt0.p9.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/libqgis_server.so is different from the same symlink in the package qgis3-devel-3.18.3-alt0.p9.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/libqgisgrass7.so is different from the same symlink in the package qgis3-devel-3.18.3-alt0.p9.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/libqgispython.so is different from the same symlink in the package qgis3-devel-3.18.3-alt0.p9.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	qgis3-devel-3.18.3-alt0.p9.1.x86_64	value of symlink /usr/lib64/libqgis_analysis.so is different from the same symlink in the package qgis-devel-2.18.28-alt4.1.p9.x86_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/libqgis_app.so is different from the same symlink in the package qgis-devel-2.18.28-alt4.1.p9.x86_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/libqgis_core.so is different from the same symlink in the package qgis-devel-2.18.28-alt4.1.p9.x86_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/libqgis_gui.so is different from the same symlink in the package qgis-devel-2.18.28-alt4.1.p9.x86_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/libqgis_server.so is different from the same symlink in the package qgis-devel-2.18.28-alt4.1.p9.x86_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/libqgisgrass7.so is different from the same symlink in the package qgis-devel-2.18.28-alt4.1.p9.x86_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/libqgispython.so is different from the same symlink in the package qgis-devel-2.18.28-alt4.1.p9.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.;