warn	AFLplusplus-debuginfo-4.20c-alt1.x86_64	value of symlink /usr/lib/debug/usr/bin/afl-clang++.debug is different from the same symlink in the package afl-debuginfo-2.56-alt4.b.git.f10d601.x86_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/afl-clang-fast++.debug is different from the same symlink in the package afl-debuginfo-2.56-alt4.b.git.f10d601.x86_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/afl-clang.debug is different from the same symlink in the package afl-debuginfo-2.56-alt4.b.git.f10d601.x86_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/afl-g++.debug is different from the same symlink in the package afl-debuginfo-2.56-alt4.b.git.f10d601.x86_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	GMT-6.1.1-alt1_1.x86_64	value of symlink /usr/bin/batch is different from the same symlink in the package vixie-cron-4.1.20060426-alt10.3.x86_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	GMT-debuginfo-6.1.1-alt1_1.x86_64	value of symlink /usr/lib/debug/usr/bin/batch.debug is different from the same symlink in the package vixie-cron-debuginfo-4.1.20060426-alt10.3.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	afl-debuginfo-2.56-alt4.b.git.f10d601.x86_64	value of symlink /usr/lib/debug/usr/bin/afl-clang++.debug is different from the same symlink in the package AFLplusplus-debuginfo-4.20c-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/afl-clang-fast++.debug is different from the same symlink in the package AFLplusplus-debuginfo-4.20c-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/afl-clang.debug is different from the same symlink in the package AFLplusplus-debuginfo-4.20c-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/afl-g++.debug is different from the same symlink in the package AFLplusplus-debuginfo-4.20c-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-common-debuginfo-11.0.6-alt4.x86_64	value of symlink /usr/lib/debug/usr/lib64/libbac.so.debug is different from the same symlink in the package bacula13-common-debuginfo-13.0.4-alt2.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbac.so.debug is different from the same symlink in the package bacula15-common-debuginfo-15.0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbaccfg.so.debug is different from the same symlink in the package bacula13-common-debuginfo-13.0.4-alt2.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbaccfg.so.debug is different from the same symlink in the package bacula15-common-debuginfo-15.0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbacfind.so.debug is different from the same symlink in the package bacula13-common-debuginfo-13.0.4-alt2.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbacfind.so.debug is different from the same symlink in the package bacula15-common-debuginfo-15.0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbacsd.so.debug is different from the same symlink in the package bacula13-common-debuginfo-13.0.4-alt2.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbacsd.so.debug is different from the same symlink in the package bacula15-common-debuginfo-15.0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	bacula11-director-common-debuginfo-11.0.6-alt4.x86_64	value of symlink /usr/lib/debug/usr/lib64/libbacsql.so.debug is different from the same symlink in the package bacula13-director-common-debuginfo-13.0.4-alt2.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbacsql.so.debug is different from the same symlink in the package bacula15-director-common-debuginfo-15.0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	bacula11-director-mysql-debuginfo-11.0.6-alt4.x86_64	value of symlink /usr/lib/debug/usr/lib64/libbaccats-mysql.so.debug is different from the same symlink in the package bacula13-director-mysql-debuginfo-13.0.4-alt2.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbaccats-mysql.so.debug is different from the same symlink in the package bacula15-director-mysql-debuginfo-15.0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	bacula11-director-postgresql-debuginfo-11.0.6-alt4.x86_64	value of symlink /usr/lib/debug/usr/lib64/libbaccats-postgresql.so.debug is different from the same symlink in the package bacula13-director-postgresql-debuginfo-13.0.4-alt2.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbaccats-postgresql.so.debug is different from the same symlink in the package bacula15-director-postgresql-debuginfo-15.0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	bacula11-director-sqlite3-debuginfo-11.0.6-alt4.x86_64	value of symlink /usr/lib/debug/usr/lib64/libbaccats-sqlite3.so.debug is different from the same symlink in the package bacula13-director-sqlite3-debuginfo-13.0.4-alt2.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbaccats-sqlite3.so.debug is different from the same symlink in the package bacula15-director-sqlite3-debuginfo-15.0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	bacula13-common-debuginfo-13.0.4-alt2.p10.1.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.6-alt4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbac.so.debug is different from the same symlink in the package bacula15-common-debuginfo-15.0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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.6-alt4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbaccfg.so.debug is different from the same symlink in the package bacula15-common-debuginfo-15.0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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.6-alt4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbacfind.so.debug is different from the same symlink in the package bacula15-common-debuginfo-15.0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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.6-alt4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbacsd.so.debug is different from the same symlink in the package bacula15-common-debuginfo-15.0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	bacula13-director-common-debuginfo-13.0.4-alt2.p10.1.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.6-alt4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbacsql.so.debug is different from the same symlink in the package bacula15-director-common-debuginfo-15.0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	bacula13-director-mysql-debuginfo-13.0.4-alt2.p10.1.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.6-alt4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbaccats-mysql.so.debug is different from the same symlink in the package bacula15-director-mysql-debuginfo-15.0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	bacula13-director-postgresql-debuginfo-13.0.4-alt2.p10.1.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.6-alt4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbaccats-postgresql.so.debug is different from the same symlink in the package bacula15-director-postgresql-debuginfo-15.0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	bacula13-director-sqlite3-debuginfo-13.0.4-alt2.p10.1.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.6-alt4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbaccats-sqlite3.so.debug is different from the same symlink in the package bacula15-director-sqlite3-debuginfo-15.0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	bacula15-common-debuginfo-15.0.2-alt2.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.6-alt4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbac.so.debug is different from the same symlink in the package bacula13-common-debuginfo-13.0.4-alt2.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbaccfg.so.debug is different from the same symlink in the package bacula11-common-debuginfo-11.0.6-alt4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbaccfg.so.debug is different from the same symlink in the package bacula13-common-debuginfo-13.0.4-alt2.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbacfind.so.debug is different from the same symlink in the package bacula11-common-debuginfo-11.0.6-alt4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbacfind.so.debug is different from the same symlink in the package bacula13-common-debuginfo-13.0.4-alt2.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbacsd.so.debug is different from the same symlink in the package bacula11-common-debuginfo-11.0.6-alt4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbacsd.so.debug is different from the same symlink in the package bacula13-common-debuginfo-13.0.4-alt2.p10.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	bacula15-director-common-debuginfo-15.0.2-alt2.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.6-alt4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbacsql.so.debug is different from the same symlink in the package bacula13-director-common-debuginfo-13.0.4-alt2.p10.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	bacula15-director-mysql-debuginfo-15.0.2-alt2.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.6-alt4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbaccats-mysql.so.debug is different from the same symlink in the package bacula13-director-mysql-debuginfo-13.0.4-alt2.p10.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	bacula15-director-postgresql-debuginfo-15.0.2-alt2.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.6-alt4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbaccats-postgresql.so.debug is different from the same symlink in the package bacula13-director-postgresql-debuginfo-13.0.4-alt2.p10.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	bacula15-director-sqlite3-debuginfo-15.0.2-alt2.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.6-alt4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libbaccats-sqlite3.so.debug is different from the same symlink in the package bacula13-director-sqlite3-debuginfo-13.0.4-alt2.p10.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	crtools-debuginfo-3.15-alt2.x86_64	value of symlink /usr/lib/debug/usr/sbin/crtools.debug is different from the same symlink in the package crtools-ovz-debuginfo-3.15.2.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	crtools-ovz-debuginfo-3.15.2.5-alt1.x86_64	value of symlink /usr/lib/debug/usr/sbin/crtools.debug is different from the same symlink in the package crtools-debuginfo-3.15-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	java-17-openjdk-headless-debuginfo-17.0.14.0.7-alt1.x86_64	value of symlink /usr/lib/debug/.build-id/dc/ade80224f9bb8c305627460c3b8e06eaf512e8 is different from the same symlink in the package java-21-openjdk-headless-debuginfo-21.0.6.0.7-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/.build-id/dc/ade80224f9bb8c305627460c3b8e06eaf512e8.debug is different from the same symlink in the package java-21-openjdk-headless-debuginfo-21.0.6.0.7-alt0.p10.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	java-21-openjdk-headless-debuginfo-21.0.6.0.7-alt0.p10.1.x86_64	value of symlink /usr/lib/debug/.build-id/dc/ade80224f9bb8c305627460c3b8e06eaf512e8 is different from the same symlink in the package java-17-openjdk-headless-debuginfo-17.0.14.0.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/.build-id/dc/ade80224f9bb8c305627460c3b8e06eaf512e8.debug is different from the same symlink in the package java-17-openjdk-headless-debuginfo-17.0.14.0.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	kde5-smplayer-debuginfo-23.6.0-alt1.x86_64	value of symlink /usr/lib/debug/.build-id/2b/1d412cfec9fbc1aed0227ee340c3a485b54128 is different from the same symlink in the package smplayer-webserver-debuginfo-23.6.0-alt2.10169.x86_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/2b/1d412cfec9fbc1aed0227ee340c3a485b54128.debug is different from the same symlink in the package smplayer-webserver-debuginfo-23.6.0-alt2.10169.x86_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-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	libblas-devel-3.9.2-alt3.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-alt11.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-alt11.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-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	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-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	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	libecpg6-10-debuginfo-10.23-alt1.p10.4.x86_64	value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-11-debuginfo-11.22-alt0.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-12-debuginfo-12.22-alt0.p10.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/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-13-debuginfo-13.20-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-14-debuginfo-14.17-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-15-1C-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-15-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-16-debuginfo-16.8-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.4-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-11-debuginfo-11.22-alt0.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-12-debuginfo-12.22-alt0.p10.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/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-13-debuginfo-13.20-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-14-debuginfo-14.17-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-15-1C-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-15-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-16-debuginfo-16.8-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.4-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-11-debuginfo-11.22-alt0.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-12-debuginfo-12.22-alt0.p10.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/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-13-debuginfo-13.20-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-14-debuginfo-14.17-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-15-1C-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-15-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-16-debuginfo-16.8-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.4-alt0.p10.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	libecpg6-11-debuginfo-11.22-alt0.p10.4.x86_64	value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-10-debuginfo-10.23-alt1.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-12-debuginfo-12.22-alt0.p10.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/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-13-debuginfo-13.20-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-14-debuginfo-14.17-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-15-1C-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-15-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-16-debuginfo-16.8-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.4-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-10-debuginfo-10.23-alt1.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-12-debuginfo-12.22-alt0.p10.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/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-13-debuginfo-13.20-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-14-debuginfo-14.17-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-15-1C-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-15-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-16-debuginfo-16.8-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.4-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-10-debuginfo-10.23-alt1.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-12-debuginfo-12.22-alt0.p10.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/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-13-debuginfo-13.20-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-14-debuginfo-14.17-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-15-1C-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-15-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-16-debuginfo-16.8-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.4-alt0.p10.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	libecpg6-12-debuginfo-12.22-alt0.p10.2.x86_64	value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-10-debuginfo-10.23-alt1.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-11-debuginfo-11.22-alt0.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-13-debuginfo-13.20-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-14-debuginfo-14.17-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-15-1C-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-15-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-16-debuginfo-16.8-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.4-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-10-debuginfo-10.23-alt1.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-11-debuginfo-11.22-alt0.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-13-debuginfo-13.20-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-14-debuginfo-14.17-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-15-1C-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-15-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-16-debuginfo-16.8-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.4-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-10-debuginfo-10.23-alt1.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-11-debuginfo-11.22-alt0.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-13-debuginfo-13.20-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-14-debuginfo-14.17-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-15-1C-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-15-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-16-debuginfo-16.8-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.4-alt0.p10.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	libecpg6-13-debuginfo-13.20-alt0.p10.1.x86_64	value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-10-debuginfo-10.23-alt1.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-11-debuginfo-11.22-alt0.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-12-debuginfo-12.22-alt0.p10.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/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-14-debuginfo-14.17-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-15-1C-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-15-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-16-debuginfo-16.8-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.4-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-10-debuginfo-10.23-alt1.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-11-debuginfo-11.22-alt0.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-12-debuginfo-12.22-alt0.p10.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/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-14-debuginfo-14.17-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-15-1C-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-15-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-16-debuginfo-16.8-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.4-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-10-debuginfo-10.23-alt1.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-11-debuginfo-11.22-alt0.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-12-debuginfo-12.22-alt0.p10.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/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-14-debuginfo-14.17-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-15-1C-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-15-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-16-debuginfo-16.8-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.4-alt0.p10.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	libecpg6-14-debuginfo-14.17-alt0.p10.1.x86_64	value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-10-debuginfo-10.23-alt1.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-11-debuginfo-11.22-alt0.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-12-debuginfo-12.22-alt0.p10.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/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-13-debuginfo-13.20-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-15-1C-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-15-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-16-debuginfo-16.8-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.4-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-10-debuginfo-10.23-alt1.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-11-debuginfo-11.22-alt0.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-12-debuginfo-12.22-alt0.p10.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/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-13-debuginfo-13.20-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-15-1C-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-15-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-16-debuginfo-16.8-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.4-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-10-debuginfo-10.23-alt1.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-11-debuginfo-11.22-alt0.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-12-debuginfo-12.22-alt0.p10.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/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-13-debuginfo-13.20-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-15-1C-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-15-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-16-debuginfo-16.8-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.4-alt0.p10.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	libecpg6-15-1C-debuginfo-15.12-alt0.p10.1.x86_64	value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-10-debuginfo-10.23-alt1.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-11-debuginfo-11.22-alt0.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-12-debuginfo-12.22-alt0.p10.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/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-13-debuginfo-13.20-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-14-debuginfo-14.17-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-16-debuginfo-16.8-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.4-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-10-debuginfo-10.23-alt1.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-11-debuginfo-11.22-alt0.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-12-debuginfo-12.22-alt0.p10.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/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-13-debuginfo-13.20-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-14-debuginfo-14.17-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-16-debuginfo-16.8-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.4-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-10-debuginfo-10.23-alt1.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-11-debuginfo-11.22-alt0.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-12-debuginfo-12.22-alt0.p10.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/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-13-debuginfo-13.20-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-14-debuginfo-14.17-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-16-debuginfo-16.8-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.4-alt0.p10.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	libecpg6-15-debuginfo-15.12-alt0.p10.1.x86_64	value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-10-debuginfo-10.23-alt1.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-11-debuginfo-11.22-alt0.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-12-debuginfo-12.22-alt0.p10.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/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-13-debuginfo-13.20-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-14-debuginfo-14.17-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-16-debuginfo-16.8-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.4-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-10-debuginfo-10.23-alt1.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-11-debuginfo-11.22-alt0.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-12-debuginfo-12.22-alt0.p10.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/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-13-debuginfo-13.20-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-14-debuginfo-14.17-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-16-debuginfo-16.8-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.4-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-10-debuginfo-10.23-alt1.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-11-debuginfo-11.22-alt0.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-12-debuginfo-12.22-alt0.p10.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/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-13-debuginfo-13.20-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-14-debuginfo-14.17-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-16-debuginfo-16.8-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.4-alt0.p10.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	libecpg6-16-debuginfo-16.8-alt0.p10.1.x86_64	value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-10-debuginfo-10.23-alt1.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-11-debuginfo-11.22-alt0.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-12-debuginfo-12.22-alt0.p10.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/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-13-debuginfo-13.20-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-14-debuginfo-14.17-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-15-1C-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-15-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.4-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-10-debuginfo-10.23-alt1.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-11-debuginfo-11.22-alt0.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-12-debuginfo-12.22-alt0.p10.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/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-13-debuginfo-13.20-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-14-debuginfo-14.17-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-15-1C-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-15-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.4-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-10-debuginfo-10.23-alt1.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-11-debuginfo-11.22-alt0.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-12-debuginfo-12.22-alt0.p10.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/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-13-debuginfo-13.20-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-14-debuginfo-14.17-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-15-1C-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-15-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.4-alt0.p10.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	libecpg6-17-debuginfo-17.4-alt0.p10.1.x86_64	value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-10-debuginfo-10.23-alt1.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-11-debuginfo-11.22-alt0.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-12-debuginfo-12.22-alt0.p10.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/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-13-debuginfo-13.20-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-14-debuginfo-14.17-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-15-1C-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-15-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6-16-debuginfo-16.8-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-10-debuginfo-10.23-alt1.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-11-debuginfo-11.22-alt0.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-12-debuginfo-12.22-alt0.p10.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/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-13-debuginfo-13.20-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-14-debuginfo-14.17-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-15-1C-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-15-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6-16-debuginfo-16.8-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-10-debuginfo-10.23-alt1.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-11-debuginfo-11.22-alt0.p10.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.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-12-debuginfo-12.22-alt0.p10.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/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-13-debuginfo-13.20-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-14-debuginfo-14.17-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-15-1C-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-15-debuginfo-15.12-alt0.p10.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-16-debuginfo-16.8-alt0.p10.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	libgcrypt-devel-1.10.2-alt2.x86_64	value of symlink /usr/lib64/libgcrypt.so is different from the same symlink in the package libgcrypt-gost-devel-1.8.5-alt6.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libgcrypt-gost-devel-1.8.5-alt6.x86_64	value of symlink /usr/lib64/libgcrypt.so is different from the same symlink in the package libgcrypt-devel-1.10.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libglfw-devel-2.7.9-alt1.x86_64	value of symlink /usr/lib64/libglfw.so is different from the same symlink in the package libglfw3-devel-3.3-alt1.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libglfw3-devel-3.3-alt1.1.x86_64	value of symlink /usr/lib64/libglfw.so is different from the same symlink in the package libglfw-devel-2.7.9-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libgs-devel-10.04.0-alt1.x86_64	value of symlink /usr/lib64/libgxps.so is different from the same symlink in the package libgxps-devel-0.3.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libgxps-devel-0.3.2-alt1.x86_64	value of symlink /usr/lib64/libgxps.so is different from the same symlink in the package libgs-devel-10.04.0-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	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	libpjsip-devel-2.11-alt1.x86_64	value of symlink /usr/lib64/libresample.so is different from the same symlink in the package libresample-devel-0.1.3-alt5.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libreadline-devel-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.11-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libsdp-devel-1.1.108-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.3-alt1.x86_64	value of symlink /usr/lib64/libstrophe.so is different from the same symlink in the package netxms-server-2.2.11-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libticables-devel-1.3.4-alt1_1.x86_64	value of symlink /usr/lib64/libticables2.so is different from the same symlink in the package libticables2-devel-1.3.5-alt1_4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libticables2-devel-1.3.5-alt1_4.x86_64	value of symlink /usr/lib64/libticables2.so is different from the same symlink in the package libticables-devel-1.3.4-alt1_1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libucl-devel-1.03-alt4.x86_64	value of symlink /usr/lib64/libucl.so is different from the same symlink in the package libucl5-devel-0.8.1-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libucl5-devel-0.8.1-alt1.x86_64	value of symlink /usr/lib64/libucl.so is different from the same symlink in the package libucl-devel-1.03-alt4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libwxBase3.0-devel-debuginfo-3.0.5.1-alt1.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.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.; value of symlink /usr/lib/debug/usr/bin/wxrc.debug is different from the same symlink in the package libwxGTK-devel-debuginfo-2.8.12-alt1.svn20131012.6.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/bin/wxrc.debug is different from the same symlink in the package libwxBase3.2-devel-debuginfo-3.2.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libwxBase3.1-devel-debuginfo-3.1.5-alt1.x86_64	value of symlink /usr/lib/debug/usr/bin/wxrc.debug is different from the same symlink in the package libwxBase3.0-devel-debuginfo-3.0.5.1-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/wxrc.debug is different from the same symlink in the package libwxGTK-devel-debuginfo-2.8.12-alt1.svn20131012.6.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/usr/bin/wxrc.debug is different from the same symlink in the package libwxBase3.2-devel-debuginfo-3.2.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libwxBase3.2-devel-debuginfo-3.2.2-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.5.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.; 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.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.; value of symlink /usr/lib/debug/usr/bin/wxrc.debug is different from the same symlink in the package libwxGTK-devel-debuginfo-2.8.12-alt1.svn20131012.6.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libwxGTK-devel-debuginfo-2.8.12-alt1.svn20131012.6.x86_64	value of symlink /usr/lib/debug/usr/bin/wxrc.debug is different from the same symlink in the package libwxBase3.0-devel-debuginfo-3.0.5.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.; 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.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.; value of symlink /usr/lib/debug/usr/bin/wxrc.debug is different from the same symlink in the package libwxBase3.2-devel-debuginfo-3.2.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	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-alt8.x86_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-alt8.x86_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-alt8.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.3-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ocaml-gettext-debuginfo-0.4.2-alt3.x86_64	value of symlink /usr/lib/debug/.build-id/ba/6319f9b16927940d4bbeea3ec832ae4020c6dc is different from the same symlink in the package ocaml-num-debuginfo-1.4-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/.build-id/ba/6319f9b16927940d4bbeea3ec832ae4020c6dc.debug is different from the same symlink in the package ocaml-num-debuginfo-1.4-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ocaml-num-debuginfo-1.4-alt1.x86_64	value of symlink /usr/lib/debug/.build-id/ba/6319f9b16927940d4bbeea3ec832ae4020c6dc is different from the same symlink in the package ocaml-gettext-debuginfo-0.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/.build-id/ba/6319f9b16927940d4bbeea3ec832ae4020c6dc.debug is different from the same symlink in the package ocaml-gettext-debuginfo-0.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	ossp-uuid-1.6.2-alt2.x86_64	value of symlink /usr/bin/uuid is different from the same symlink in the package uuid-2.3.9-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	smplayer-webserver-debuginfo-23.6.0-alt2.10169.x86_64	value of symlink /usr/lib/debug/.build-id/2b/1d412cfec9fbc1aed0227ee340c3a485b54128 is different from the same symlink in the package kde5-smplayer-debuginfo-23.6.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/.build-id/2b/1d412cfec9fbc1aed0227ee340c3a485b54128.debug is different from the same symlink in the package kde5-smplayer-debuginfo-23.6.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	tomcat-el-3.0-api-9.0.98-alt0_1jpp17.p10.1.noarch	value of symlink /usr/share/java/tomcat-el-api.jar is different from the same symlink in the package tomcat10-lib-10.1.20-alt1_jvm17.p10.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	tomcat-jsp-2.3-api-9.0.98-alt0_1jpp17.p10.1.noarch	value of symlink /usr/share/java/tomcat-jsp-api.jar is different from the same symlink in the package tomcat10-lib-10.1.20-alt1_jvm17.p10.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	tomcat-servlet-4.0-api-9.0.98-alt0_1jpp17.p10.1.noarch	value of symlink /usr/share/java/tomcat-servlet-api.jar is different from the same symlink in the package tomcat10-lib-10.1.20-alt1_jvm17.p10.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	tomcat10-lib-10.1.20-alt1_jvm17.p10.noarch	value of symlink /usr/share/java/tomcat-el-api.jar is different from the same symlink in the package tomcat-el-3.0-api-9.0.98-alt0_1jpp17.p10.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.; value of symlink /usr/share/java/tomcat-jsp-api.jar is different from the same symlink in the package tomcat-jsp-2.3-api-9.0.98-alt0_1jpp17.p10.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.; value of symlink /usr/share/java/tomcat-servlet-api.jar is different from the same symlink in the package tomcat-servlet-4.0-api-9.0.98-alt0_1jpp17.p10.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	utils-0.34.0-alt1.noarch	value of symlink /usr/bin/edit is different from the same symlink in the package vi-traditional-4.1.3-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	uuid-2.3.9-alt1.noarch	value of symlink /usr/bin/uuid is different from the same symlink in the package ossp-uuid-1.6.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	vi-traditional-4.1.3-alt1.x86_64	value of symlink /usr/bin/edit is different from the same symlink in the package utils-0.34.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/bin/view is different from the same symlink in the package vim-common-9.1.1264-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/man/man1/view.1.xz is different from the same symlink in the package vim-common-9.1.1264-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	vim-common-9.1.1264-alt1.noarch	value of symlink /usr/bin/view is different from the same symlink in the package vi-traditional-4.1.3-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/share/man/man1/view.1.xz is different from the same symlink in the package vi-traditional-4.1.3-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	vixie-cron-4.1.20060426-alt10.3.x86_64	value of symlink /usr/bin/batch is different from the same symlink in the package GMT-6.1.1-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	vixie-cron-debuginfo-4.1.20060426-alt10.3.x86_64	value of symlink /usr/lib/debug/usr/bin/batch.debug is different from the same symlink in the package GMT-debuginfo-6.1.1-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.;