postgre-etersoft9.6-9.6.1.2-alt1.M80P.2.src	specfile-macros-post_ldconfig-is-deprecated	warn	macros %post_ldconfig/%postun_ldconfig are deprecated and will be removed.; 
postgre-etersoft9.6-9.6.1.2-alt1.M80P.2.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql10-10.17-alt0.M80P.1.x86_64, for example, /usr/bin/clusterdb (13 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 postgresql11-11.12-alt0.M80P.1.x86_64, for example, /usr/bin/clusterdb (13 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 postgresql11-1C-11.12-alt0.M80P.1.x86_64, for example, /usr/bin/clusterdb (13 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 postgresql12-12.7-alt0.M80P.1.x86_64, for example, /usr/bin/clusterdb (13 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-9.1.24-alt0.M80P.3.x86_64, for example, /usr/bin/clusterdb (15 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.3-9.3.25-alt0.M80P.2.x86_64, for example, /usr/bin/clusterdb (15 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-9.4.26-alt0.M80P.1.x86_64, for example, /usr/bin/clusterdb (14 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-9.5.25-alt0.M80P.1.x86_64, for example, /usr/bin/clusterdb (14 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-9.6.22-alt0.M80P.1.x86_64, for example, /usr/bin/clusterdb (14 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.; 
postgre-etersoft9.6-contrib-9.6.1.2-alt1.M80P.2.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.; 
postgre-etersoft9.6-contrib-9.6.1.2-alt1.M80P.2.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/bin/oid2name /usr/bin/pgbench /usr/bin/vacuumlo conflict with the package postgresql10-contrib-10.17-alt0.M80P.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/oid2name /usr/bin/pgbench /usr/bin/vacuumlo conflict with the package postgresql11-1C-contrib-11.12-alt0.M80P.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/oid2name /usr/bin/pgbench /usr/bin/vacuumlo conflict with the package postgresql11-contrib-11.12-alt0.M80P.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/oid2name /usr/bin/pgbench /usr/bin/vacuumlo conflict with the package postgresql12-contrib-12.7-alt0.M80P.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/oid2name /usr/bin/pgbench /usr/bin/vacuumlo conflict with the package postgresql9.1-contrib-9.1.24-alt0.M80P.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.; Files /usr/bin/oid2name /usr/bin/pgbench /usr/bin/vacuumlo conflict with the package postgresql9.3-contrib-9.3.25-alt0.M80P.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/oid2name /usr/bin/pgbench /usr/bin/vacuumlo conflict with the package postgresql9.4-contrib-9.4.26-alt0.M80P.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/oid2name /usr/bin/pgbench /usr/bin/vacuumlo conflict with the package postgresql9.5-contrib-9.5.25-alt0.M80P.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/oid2name /usr/bin/vacuumlo conflict with the package postgresql9.6-contrib-9.6.22-alt0.M80P.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.; 
postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.2.x86_64	checkbashisms	experimental	checkbashisms utility found possible bashisms in: /usr/bin/postgresql-check-db-dir; 
postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.2.x86_64	init-lsb	warn	/etc/rc.d/init.d/postgresql: lsb init header missing.  See http://www.altlinux.org/Services_Policy for details.; 
postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.2.x86_64	rpm-filesystem-conflict-file-file	warn	File /etc/sysconfig/postgresql conflicts with the package postgresql-common-1.0-alt8.noarch. 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/pg_isready /usr/bin/pg_recvlogical /usr/bin/pg_test_timing conflict with the package postgresql10-10.17-alt0.M80P.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/pg_archivecleanup /usr/bin/pg_standby conflict with the package postgresql10-contrib-10.17-alt0.M80P.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 postgresql10-server-10.17-alt0.M80P.1.x86_64, for example, /etc/rc.d/init.d/postgresql (8 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.; Files /usr/bin/pg_isready /usr/bin/pg_recvlogical /usr/bin/pg_test_timing conflict with the package postgresql11-11.12-alt0.M80P.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/pg_isready /usr/bin/pg_recvlogical /usr/bin/pg_test_timing conflict with the package postgresql11-1C-11.12-alt0.M80P.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/pg_archivecleanup /usr/bin/pg_standby conflict with the package postgresql11-1C-contrib-11.12-alt0.M80P.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 postgresql11-1C-server-11.12-alt0.M80P.1.x86_64, for example, /etc/rc.d/init.d/postgresql (9 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.; Files /usr/bin/pg_archivecleanup /usr/bin/pg_standby conflict with the package postgresql11-contrib-11.12-alt0.M80P.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 postgresql11-server-11.12-alt0.M80P.1.x86_64, for example, /etc/rc.d/init.d/postgresql (9 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.; Files /usr/bin/pg_isready /usr/bin/pg_recvlogical /usr/bin/pg_test_timing conflict with the package postgresql12-12.7-alt0.M80P.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/pg_archivecleanup /usr/bin/pg_standby conflict with the package postgresql12-contrib-12.7-alt0.M80P.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 postgresql12-server-12.7-alt0.M80P.1.x86_64, for example, /etc/rc.d/init.d/postgresql (9 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.; Files /usr/bin/pg_archivecleanup /usr/bin/pg_standby conflict with the package postgresql9.1-contrib-9.1.24-alt0.M80P.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.; There are file conflicts with the package postgresql9.1-server-9.1.24-alt0.M80P.3.x86_64, for example, /etc/rc.d/init.d/postgresql (7 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.; Files /usr/bin/pg_isready /usr/bin/pg_test_timing conflict with the package postgresql9.3-9.3.25-alt0.M80P.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/pg_archivecleanup /usr/bin/pg_standby /usr/bin/pg_xlogdump conflict with the package postgresql9.3-contrib-9.3.25-alt0.M80P.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.; There are file conflicts with the package postgresql9.3-server-9.3.25-alt0.M80P.2.x86_64, for example, /etc/rc.d/init.d/postgresql (10 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.; Files /usr/bin/pg_isready /usr/bin/pg_recvlogical conflict with the package postgresql9.4-9.4.26-alt0.M80P.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/pg_archivecleanup /usr/bin/pg_standby /usr/bin/pg_xlogdump conflict with the package postgresql9.4-contrib-9.4.26-alt0.M80P.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.4-server-9.4.26-alt0.M80P.1.x86_64, for example, /etc/rc.d/init.d/postgresql (10 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.; Files /usr/bin/pg_isready /usr/bin/pg_recvlogical conflict with the package postgresql9.5-9.5.25-alt0.M80P.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/pg_standby /usr/bin/pg_xlogdump conflict with the package postgresql9.5-contrib-9.5.25-alt0.M80P.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.5-server-9.5.25-alt0.M80P.1.x86_64, for example, /etc/rc.d/init.d/postgresql (10 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.; Files /usr/bin/pg_isready /usr/bin/pg_recvlogical conflict with the package postgresql9.6-9.6.22-alt0.M80P.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/bin/pg_standby conflicts with the package postgresql9.6-contrib-9.6.22-alt0.M80P.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-server-9.6.22-alt0.M80P.1.x86_64, for example, /etc/rc.d/init.d/postgresql (10 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.;