Repocop reports for by-leader taf

  rpm id test status message
accel-ppp-1.11.2-alt11.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.
accel-ppp-1.11.2-alt11.x86_64 subdir-in-var-run info Found a subdir in /var/run or /var/lock. /var/run and /var/lock may be mounted as temporary filesystems, so the init.d scripts must handle this correctly. This will typically amount to creating any required subdirectories dynamically when the init.d script is run, rather than including them in the package and relying on rpm to create them.
aspell-ispell-0.60.6.1-alt3.noarch alt-alternatives-master-slave-conflict fail slave alternative /usr/bin/spell is already registered as a master in package: ispell-3.2.06-alt14.x86_64
slave alternative /usr/bin/spell is already registered as a master in package: enchant-1.6.0-alt3.qa1.x86_64
aspell-ispell-0.60.6.1-alt3.noarch aspell-package-not-arch-all fail aspell/ispell packages are endian-sensitive; should be arch
bcunit-3.0.2-alt1.x86_64 library-pkgnames info package contains public library which is used in external packages: name should be lib* according to http://altlinux.org/Drafts/SharedLibs
bitstream-headers-1.4-alt2.noarch buildroot fail found paths to buildroot: /usr/share/pkgconfig/bitstream.pc: prefix=/usr/src/tmp/bitstream-headers-buildroot/usr
includedir=/usr/src/tmp/bitstream-headers-buildroot/usr/include
lighttpd-1.4.52-alt1.x86_64 init-lsb warn /etc/rc.d/init.d/lighttpd: lsb init header missing. See http://www.altlinux.org/Services_Policy for details.
linphone-gui-3.12.0-alt5.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.
linphone-tester-3.12.0-alt5.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.
nftables-0.9.0-alt2.x86_64 systemd-but-no-native-init warn The package have native systemd file(s) but no SysV init scripts.
openfire-4.2.3-alt1.noarch init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.
postgresql10-1C-contrib-10.6-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql11-contrib-11.1-alt1.x86_64, for example, /usr/bin/pgbench (27 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-contrib-9.3.25-alt1.x86_64, for example, /usr/bin/oid2name (35 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.20-alt1.x86_64, for example, /usr/bin/oid2name (37 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.15-alt1.x86_64, for example, /usr/bin/pg_archivecleanup (35 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.11-alt1.x86_64, for example, /usr/bin/pg_archivecleanup (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.
postgresql10-1C-perl-10.6-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql11-perl-11.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.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.3-perl-9.3.25-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.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.4-perl-9.4.20-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.
File /usr/lib64/pgsql/hstore_plperl.so conflicts with the package postgresql9.5-contrib-9.5.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.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.5-perl-9.5.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.
File /usr/lib64/pgsql/hstore_plperl.so conflicts with the package postgresql9.6-contrib-9.6.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.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.6-perl-9.6.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.
postgresql10-1C-python-10.6-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/ltree_plpython2.so conflicts with the package postgresql11-contrib-11.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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql11-python-11.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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.3-python-9.3.25-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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.4-python-9.4.20-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.
File /usr/lib64/pgsql/hstore_plpython2.so conflicts with the package postgresql9.5-contrib-9.5.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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.5-python-9.5.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.
File /usr/lib64/pgsql/hstore_plpython2.so conflicts with the package postgresql9.6-contrib-9.6.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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.6-python-9.6.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.
postgresql10-1C-server-10.6-alt1.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.
postgresql10-1C-server-10.6-alt1.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/postgresql-check-db-dir /etc/rc.d/init.d/postgresql
postgresql10-1C-tcl-10.6-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql11-tcl-11.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.
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.3-tcl-9.3.25-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.
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.4-tcl-9.4.20-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.
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.5-tcl-9.5.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.
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.6-tcl-9.6.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.
postgresql10-contrib-10.6-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql11-contrib-11.1-alt1.x86_64, for example, /usr/bin/pgbench (28 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-contrib-9.3.25-alt1.x86_64, for example, /usr/bin/oid2name (35 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.20-alt1.x86_64, for example, /usr/bin/oid2name (37 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.15-alt1.x86_64, for example, /usr/bin/pg_archivecleanup (37 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.11-alt1.x86_64, for example, /usr/bin/pg_archivecleanup (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.
postgresql10-perl-10.6-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql11-perl-11.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.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.3-perl-9.3.25-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.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.4-perl-9.4.20-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.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.5-perl-9.5.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.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.6-perl-9.6.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.
postgresql10-python-10.6-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql11-python-11.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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.3-python-9.3.25-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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.4-python-9.4.20-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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.5-python-9.5.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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.6-python-9.6.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.
postgresql10-server-10.6-alt1.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.
postgresql10-server-10.6-alt1.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/postgresql-check-db-dir /etc/rc.d/init.d/postgresql
postgresql10-tcl-10.6-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql11-tcl-11.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.
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.3-tcl-9.3.25-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.
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.4-tcl-9.4.20-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.
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.5-tcl-9.5.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.
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.6-tcl-9.6.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.
postgresql11-contrib-11.1-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql10-1C-contrib-10.6-alt1.x86_64, for example, /usr/bin/pgbench (27 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/lib64/pgsql/ltree_plpython2.so conflicts with the package postgresql10-1C-python-10.6-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.
There are file conflicts with the package postgresql10-contrib-10.6-alt1.x86_64, for example, /usr/bin/pgbench (28 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-contrib-9.3.25-alt1.x86_64, for example, /usr/bin/oid2name (41 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.20-alt1.x86_64, for example, /usr/bin/oid2name (43 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.15-alt1.x86_64, for example, /usr/bin/pg_archivecleanup (47 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.11-alt1.x86_64, for example, /usr/bin/pg_archivecleanup (47 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.
postgresql11-perl-11.1-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql10-1C-perl-10.6-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.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql10-perl-10.6-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.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.3-perl-9.3.25-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.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.4-perl-9.4.20-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.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.5-perl-9.5.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.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.6-perl-9.6.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.
postgresql11-python-11.1-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql10-1C-python-10.6-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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql10-python-10.6-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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.3-python-9.3.25-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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.4-python-9.4.20-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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.5-python-9.5.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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.6-python-9.6.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.
postgresql11-server-11.1-alt1.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.
postgresql11-server-11.1-alt1.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/postgresql-check-db-dir /etc/rc.d/init.d/postgresql
postgresql11-tcl-11.1-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql10-1C-tcl-10.6-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.
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql10-tcl-10.6-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.
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.3-tcl-9.3.25-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.
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.4-tcl-9.4.20-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.
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.5-tcl-9.5.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.
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.6-tcl-9.6.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.
postgresql9.4-contrib-9.4.20-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql10-1C-contrib-10.6-alt1.x86_64, for example, /usr/bin/oid2name (37 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 postgresql10-contrib-10.6-alt1.x86_64, for example, /usr/bin/oid2name (37 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-contrib-11.1-alt1.x86_64, for example, /usr/bin/oid2name (43 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-contrib-9.3.25-alt1.x86_64, for example, /usr/bin/oid2name (21 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.15-alt1.x86_64, for example, /usr/bin/oid2name (22 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.11-alt1.x86_64, for example, /usr/bin/oid2name (28 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.4-perl-9.4.20-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql10-1C-perl-10.6-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.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql10-perl-10.6-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.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql11-perl-11.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.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.5-perl-9.5.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.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.6-perl-9.6.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.
postgresql9.4-python-9.4.20-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql10-1C-python-10.6-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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql10-python-10.6-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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql11-python-11.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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.5-python-9.5.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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.6-python-9.6.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.
postgresql9.4-server-9.4.20-alt1.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.4-server-9.4.20-alt1.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/postgresql-check-db-dir /etc/rc.d/init.d/postgresql
postgresql9.4-tcl-9.4.20-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql10-1C-tcl-10.6-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.
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql10-tcl-10.6-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.
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql11-tcl-11.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.
Files /usr/bin/pltcl_listmod /usr/bin/pltcl_loadmod conflict with the package postgresql9.3-tcl-9.3.25-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.
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.6-tcl-9.6.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.
postgresql9.5-contrib-9.5.15-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql10-1C-contrib-10.6-alt1.x86_64, for example, /usr/bin/pg_archivecleanup (35 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/lib64/pgsql/hstore_plperl.so conflicts with the package postgresql10-1C-perl-10.6-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.
File /usr/lib64/pgsql/hstore_plpython2.so conflicts with the package postgresql10-1C-python-10.6-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.
There are file conflicts with the package postgresql10-contrib-10.6-alt1.x86_64, for example, /usr/bin/pg_archivecleanup (37 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-contrib-11.1-alt1.x86_64, for example, /usr/bin/pg_archivecleanup (47 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-contrib-9.3.25-alt1.x86_64, for example, /usr/bin/oid2name (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.4-contrib-9.4.20-alt1.x86_64, for example, /usr/bin/oid2name (22 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.11-alt1.x86_64, for example, /usr/bin/pg_xlogdump (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.
postgresql9.5-perl-9.5.15-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql10-1C-perl-10.6-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.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql10-perl-10.6-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.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql11-perl-11.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.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.3-perl-9.3.25-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.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.4-perl-9.4.20-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.
postgresql9.5-python-9.5.15-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql10-1C-python-10.6-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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql10-python-10.6-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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql11-python-11.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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.3-python-9.3.25-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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.4-python-9.4.20-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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.6-python-9.6.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.
postgresql9.5-server-9.5.15-alt1.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.5-server-9.5.15-alt1.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/postgresql-check-db-dir /etc/rc.d/init.d/postgresql
postgresql9.5-tcl-9.5.15-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql10-1C-tcl-10.6-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.
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql10-tcl-10.6-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.
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql11-tcl-11.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.
Files /usr/bin/pltcl_listmod /usr/bin/pltcl_loadmod conflict with the package postgresql9.3-tcl-9.3.25-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.
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.6-tcl-9.6.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.
postgresql9.6-contrib-9.6.11-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql10-1C-contrib-10.6-alt1.x86_64, for example, /usr/bin/pg_archivecleanup (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/lib64/pgsql/hstore_plperl.so conflicts with the package postgresql10-1C-perl-10.6-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.
File /usr/lib64/pgsql/hstore_plpython2.so conflicts with the package postgresql10-1C-python-10.6-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.
There are file conflicts with the package postgresql10-contrib-10.6-alt1.x86_64, for example, /usr/bin/pg_archivecleanup (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.
There are file conflicts with the package postgresql11-contrib-11.1-alt1.x86_64, for example, /usr/bin/pg_archivecleanup (47 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-contrib-9.3.25-alt1.x86_64, for example, /usr/bin/oid2name (28 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.20-alt1.x86_64, for example, /usr/bin/oid2name (28 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.15-alt1.x86_64, for example, /usr/bin/pg_xlogdump (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.
postgresql9.6-perl-9.6.11-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql10-1C-perl-10.6-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.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql10-perl-10.6-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.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql11-perl-11.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.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.3-perl-9.3.25-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.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.4-perl-9.4.20-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.
postgresql9.6-python-9.6.11-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql10-1C-python-10.6-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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql10-python-10.6-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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql11-python-11.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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.3-python-9.3.25-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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.4-python-9.4.20-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.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.5-python-9.5.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.
postgresql9.6-server-9.6.11-alt1.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.6-server-9.6.11-alt1.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/postgresql-check-db-dir /etc/rc.d/init.d/postgresql
postgresql9.6-tcl-9.6.11-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql10-1C-tcl-10.6-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.
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql10-tcl-10.6-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.
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql11-tcl-11.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.
Files /usr/bin/pltcl_listmod /usr/bin/pltcl_loadmod /usr/lib64/pgsql/pltcl.so conflict with the package postgresql9.3-tcl-9.3.25-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.
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.4-tcl-9.4.20-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.
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.5-tcl-9.5.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.
zabbix-java-gateway-4.0.3-alt1.noarch init-condrestart fail /etc/rc.d/init.d/zabbix_java_gateway: missing condstop target. ERROR: alt-specific script %_sbindir/preun_service (used in your %preun_service macro) depends on condstop. Please, fix.

generated by repocop at Wed Jan 16 04:48:39 2019