libecpg6.5-debuginfo-9.3.23-alt0.M70P.1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6.2-debuginfo-9.0.23-alt0.M70P.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.3-debuginfo-9.1.24-alt0.M70P.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.10-debuginfo-10.4-alt0.M70P.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.6-debuginfo-9.4.18-alt0.M70P.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.7-debuginfo-9.5.13-alt0.M70P.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.8-1C-debuginfo-9.6.9-alt0.M70P.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.8-debuginfo-9.6.9-alt0.M70P.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.2-debuginfo-9.0.23-alt0.M70P.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.3-debuginfo-9.1.24-alt0.M70P.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.4-alt0.M70P.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.6-debuginfo-9.4.18-alt0.M70P.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.7-debuginfo-9.5.13-alt0.M70P.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.8-1C-debuginfo-9.6.9-alt0.M70P.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.8-debuginfo-9.6.9-alt0.M70P.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.2-debuginfo-9.0.23-alt0.M70P.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.3-debuginfo-9.1.24-alt0.M70P.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.4-alt0.M70P.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.6-debuginfo-9.4.18-alt0.M70P.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.7-debuginfo-9.5.13-alt0.M70P.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.8-1C-debuginfo-9.6.9-alt0.M70P.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.8-debuginfo-9.6.9-alt0.M70P.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.; 
libpq5.6-debuginfo-9.3.23-alt0.M70P.1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libpq.so.5.debug is different from the same symlink in the package libpq5.3-debuginfo-9.0.23-alt0.M70P.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/libpq.so.5.debug is different from the same symlink in the package libpq5.4-debuginfo-9.1.24-alt0.M70P.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/libpq.so.5.debug is different from the same symlink in the package libpq5.10-debuginfo-10.4-alt0.M70P.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/libpq.so.5.debug is different from the same symlink in the package libpq5.7-debuginfo-9.4.18-alt0.M70P.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/libpq.so.5.debug is different from the same symlink in the package libpq5.8-debuginfo-9.5.13-alt0.M70P.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/libpq.so.5.debug is different from the same symlink in the package libpq5.9-1C-debuginfo-9.6.9-alt0.M70P.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/libpq.so.5.debug is different from the same symlink in the package libpq5.9-debuginfo-9.6.9-alt0.M70P.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.; 
postgresql9.3-contrib-9.3.23-alt0.M70P.1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql10-contrib-10.4-alt0.M70P.1.x86_64, for example, /usr/bin/oid2name (36 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql9.0-contrib-9.0.23-alt0.M70P.2.x86_64, for example, /usr/bin/pg_archivecleanup (26 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql9.1-contrib-9.1.24-alt0.M70P.1.x86_64, for example, /usr/bin/pg_archivecleanup (19 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql9.4-contrib-9.4.18-alt0.M70P.1.x86_64, for example, /usr/bin/oid2name (25 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql9.5-contrib-9.5.13-alt0.M70P.1.x86_64, for example, /usr/bin/oid2name (30 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/bin/pg_xlogdump conflicts with the package postgresql9.6-1C-9.6.9-alt0.M70P.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.; There are file conflicts with the package postgresql9.6-1C-contrib-9.6.9-alt0.M70P.1.x86_64, for example, /usr/bin/oid2name (30 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql9.6-contrib-9.6.9-alt0.M70P.1.x86_64, for example, /usr/bin/oid2name (32 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
postgresql9.3-perl-9.3.23-alt0.M70P.1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql10-perl-10.4-alt0.M70P.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.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.0-perl-9.0.23-alt0.M70P.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.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.1-perl-9.1.24-alt0.M70P.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.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.5-perl-9.5.13-alt0.M70P.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.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.6-1C-perl-9.6.9-alt0.M70P.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.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.6-perl-9.6.9-alt0.M70P.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.; 
postgresql9.3-python-9.3.23-alt0.M70P.1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql10-python-10.4-alt0.M70P.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.; File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.0-python-9.0.23-alt0.M70P.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.; File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.1-python-9.1.24-alt0.M70P.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.; File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.4-python-9.4.18-alt0.M70P.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.; File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.5-python-9.5.13-alt0.M70P.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.; File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.6-1C-python-9.6.9-alt0.M70P.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.; File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.6-python-9.6.9-alt0.M70P.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.; 
postgresql9.3-server-9.3.23-alt0.M70P.1.x86_64	arch-dep-package-has-big-usr-share	info	The package has a significant amount of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
postgresql9.3-server-9.3.23-alt0.M70P.1.x86_64	checkbashisms	experimental	checkbashisms utility found possible bashisms in: /usr/bin/postgresql-check-db-dir /etc/rc.d/init.d/postgresql; 
postgresql9.3-tcl-9.3.23-alt0.M70P.1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql10-tcl-10.4-alt0.M70P.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.; Files /usr/bin/pltcl_delmod /usr/bin/pltcl_listmod conflict with the package postgresql9.0-tcl-9.0.23-alt0.M70P.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.; Files /usr/bin/pltcl_listmod /usr/bin/pltcl_loadmod conflict with the package postgresql9.4-tcl-9.4.18-alt0.M70P.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.; Files /usr/bin/pltcl_listmod /usr/bin/pltcl_loadmod conflict with the package postgresql9.5-tcl-9.5.13-alt0.M70P.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.; Files /usr/bin/pltcl_listmod /usr/bin/pltcl_loadmod /usr/lib64/pgsql/pltcl.so conflict with the package postgresql9.6-1C-tcl-9.6.9-alt0.M70P.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.; Files /usr/bin/pltcl_listmod /usr/bin/pltcl_loadmod /usr/lib64/pgsql/pltcl.so conflict with the package postgresql9.6-tcl-9.6.9-alt0.M70P.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.;