Repocop reports by srpm

  rpm id test status message
postgresql12-12.3-alt1.src beehive-log-unpackaged-files-found-i586 info warning: Installed (but unpackaged) file(s) found:
/usr/share/pgsql/extension/hstore_plpython3u--1.0.sql
/usr/share/pgsql/extension/hstore_plpython3u.control
/usr/share/pgsql/extension/jsonb_plpython3u--1.0.sql
/usr/share/pgsql/extension/jsonb_plpython3u.control
/usr/share/pgsql/extension/ltree_plpython3u--1.0.sql
/usr/share/pgsql/extension/ltree_plpython3u.control
postgresql12-12.3-alt1.src beehive-log-unpackaged-files-found-x86_64 info warning: Installed (but unpackaged) file(s) found:
/usr/share/pgsql/extension/hstore_plpython3u--1.0.sql
/usr/share/pgsql/extension/hstore_plpython3u.control
/usr/share/pgsql/extension/jsonb_plpython3u--1.0.sql
/usr/share/pgsql/extension/jsonb_plpython3u.control
/usr/share/pgsql/extension/ltree_plpython3u--1.0.sql
/usr/share/pgsql/extension/ltree_plpython3u.control
postgresql12-contrib-12.3-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql10-contrib-10.13-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 postgresql11-contrib-11.8-alt1.x86_64, for example, /usr/bin/oid2name (29 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.22-alt1.x86_64, for example, /usr/bin/oid2name (51 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.18-alt1.x86_64, for example, /usr/bin/oid2name (50 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.
postgresql12-perl-12.3-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql10-perl-10.13-alt1.x86_64, for example, /usr/lib64/pgsql/plperl.so (5 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-perl-11.8-alt1.x86_64, for example, /usr/share/pgsql/extension/plperl--1.0.sql (4 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-perl-9.5.22-alt1.x86_64, for example, /usr/lib64/pgsql/plperl.so (5 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-perl-9.6.18-alt1.x86_64, for example, /usr/lib64/pgsql/plperl.so (5 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.
postgresql12-python-12.3-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql10-python-10.13-alt1.x86_64, for example, /usr/lib64/pgsql/plpython2.so (5 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-python-11.8-alt1.x86_64, for example, /usr/share/pgsql/extension/plpython2u--1.0.sql (4 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-python-9.5.22-alt1.x86_64, for example, /usr/lib64/pgsql/plpython2.so (5 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-python-9.6.18-alt1.x86_64, for example, /usr/lib64/pgsql/plpython2.so (5 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.
postgresql12-server-12.3-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.
postgresql12-server-12.3-alt1.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/postgresql-check-db-dir /etc/rc.d/init.d/postgresql
postgresql12-server-12.3-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql10-server-10.13-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (38 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-server-11.8-alt1.x86_64, for example, /usr/bin/initdb (33 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-server-9.5.22-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (46 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-server-9.6.18-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (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.
postgresql12-tcl-12.3-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql10-tcl-10.13-alt1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (5 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-tcl-11.8-alt1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (5 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-tcl-9.5.22-alt1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (5 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-tcl-9.6.18-alt1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (5 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.

generated by repocop at Mon Jul 13 04:22:35 2020