rpm id | test | Status | message | |
---|---|---|---|---|
libecpg6.10-10.7-alt0.M80P.1.x86_64 | distribution-tag | warn | Bad Distribution: tag in a package. | |
libecpg6.10-debuginfo-10.7-alt0.M80P.1.x86_64 | distribution-tag | warn | Bad Distribution: tag in a package. | |
libecpg6.10-debuginfo-10.7-alt0.M80P.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.3-debuginfo-9.1.24-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. value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6.5-debuginfo-9.3.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. 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.2-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. 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.21-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. 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.16-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. 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.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. 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.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. value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6.5-debuginfo-9.3.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. 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.2-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. 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.21-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. 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.16-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. 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.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. 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.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. value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6.5-debuginfo-9.3.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. 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.2-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. 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.21-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. 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.16-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. 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.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. |
|
libpq5.10-10.7-alt0.M80P.1.x86_64 | distribution-tag | warn | Bad Distribution: tag in a package. | |
libpq5.10-debuginfo-10.7-alt0.M80P.1.x86_64 | distribution-tag | warn | Bad Distribution: tag in a package. | |
libpq5.10-debuginfo-10.7-alt0.M80P.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.4-debuginfo-9.1.24-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. value of symlink /usr/lib/debug/usr/lib64/libpq.so.5.debug is different from the same symlink in the package libpq5.6-debuginfo-9.3.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. value of symlink /usr/lib/debug/usr/lib64/libpq.so.5.debug is different from the same symlink in the package libpq5.11-debuginfo-11.2-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. 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.21-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. 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.16-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. 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.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. |
|
postgresql10-10.7-alt0.M80P.1.x86_64 | distribution-tag | warn | Bad Distribution: tag in a package. | |
postgresql10-10.7-alt0.M80P.1.x86_64 | rpm-filesystem-conflict-file-file | warn | There are file conflicts with the package postgre-etersoft9.6-9.6.1.2-alt1.M80P.2.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. Files /usr/bin/pg_isready /usr/bin/pg_recvlogical /usr/bin/pg_test_timing conflict with the package postgre-etersoft9.6-server-9.6.1.2-alt1.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. |
|
postgresql10-contrib-10.7-alt0.M80P.1.x86_64 | distribution-tag | warn | Bad Distribution: tag in a package. | |
postgresql10-contrib-10.7-alt0.M80P.1.x86_64 | rpm-filesystem-conflict-file-file | warn | Files /usr/bin/pgbench /usr/bin/vacuumlo conflict with the package postgre-etersoft9.6-contrib-9.6.1.2-alt1.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 conflict with the package postgre-etersoft9.6-server-9.6.1.2-alt1.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 postgresql11-contrib-11.2-alt0.M80P.1.x86_64, for example, /usr/bin/pgbench (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.1-contrib-9.1.24-alt0.M80P.2.x86_64, for example, /usr/bin/oid2name (31 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-alt0.M80P.1.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.21-alt0.M80P.1.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.16-alt0.M80P.1.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.12-alt0.M80P.1.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-contrib-debuginfo-10.7-alt0.M80P.1.x86_64 | distribution-tag | warn | Bad Distribution: tag in a package. | |
postgresql10-debuginfo-10.7-alt0.M80P.1.x86_64 | distribution-tag | warn | Bad Distribution: tag in a package. | |
postgresql10-docs-10.7-alt0.M80P.1.noarch | distribution-tag | warn | Bad Distribution: tag in a package. | |
postgresql10-perl-10.7-alt0.M80P.1.x86_64 | distribution-tag | warn | Bad Distribution: tag in a package. | |
postgresql10-perl-10.7-alt0.M80P.1.x86_64 | rpm-filesystem-conflict-file-file | warn | File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql11-perl-11.2-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/lib64/pgsql/plperl.so conflicts with the package postgresql9.1-perl-9.1.24-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. File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.3-perl-9.3.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. File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.4-perl-9.4.21-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/lib64/pgsql/plperl.so conflicts with the package postgresql9.5-perl-9.5.16-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/lib64/pgsql/plperl.so conflicts with the package postgresql9.6-perl-9.6.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. |
|
postgresql10-perl-debuginfo-10.7-alt0.M80P.1.x86_64 | distribution-tag | warn | Bad Distribution: tag in a package. | |
postgresql10-python-10.7-alt0.M80P.1.x86_64 | distribution-tag | warn | Bad Distribution: tag in a package. | |
postgresql10-python-10.7-alt0.M80P.1.x86_64 | rpm-filesystem-conflict-file-file | warn | File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql11-python-11.2-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/lib64/pgsql/plpython2.so conflicts with the package postgresql9.1-python-9.1.24-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. File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.3-python-9.3.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. File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.4-python-9.4.21-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/lib64/pgsql/plpython2.so conflicts with the package postgresql9.5-python-9.5.16-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/lib64/pgsql/plpython2.so conflicts with the package postgresql9.6-python-9.6.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. |
|
postgresql10-python-debuginfo-10.7-alt0.M80P.1.x86_64 | distribution-tag | warn | Bad Distribution: tag in a package. | |
postgresql10-server-10.7-alt0.M80P.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. | |
postgresql10-server-10.7-alt0.M80P.1.x86_64 | checkbashisms | experimental | checkbashisms utility found possible bashisms in: /usr/bin/postgresql-check-db-dir /etc/rc.d/init.d/postgresql | |
postgresql10-server-10.7-alt0.M80P.1.x86_64 | distribution-tag | warn | Bad Distribution: tag in a package. | |
postgresql10-server-10.7-alt0.M80P.1.x86_64 | rpm-filesystem-conflict-file-file | warn | There are file conflicts with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.2.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. | |
postgresql10-server-debuginfo-10.7-alt0.M80P.1.x86_64 | distribution-tag | warn | Bad Distribution: tag in a package. | |
postgresql10-tcl-10.7-alt0.M80P.1.x86_64 | distribution-tag | warn | Bad Distribution: tag in a package. | |
postgresql10-tcl-10.7-alt0.M80P.1.x86_64 | rpm-filesystem-conflict-file-file | warn | File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql11-tcl-11.2-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/lib64/pgsql/pltcl.so conflicts with the package postgresql9.1-tcl-9.1.24-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. File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.3-tcl-9.3.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. File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.4-tcl-9.4.21-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/lib64/pgsql/pltcl.so conflicts with the package postgresql9.5-tcl-9.5.16-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/lib64/pgsql/pltcl.so conflicts with the package postgresql9.6-tcl-9.6.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. |
|
postgresql10-tcl-debuginfo-10.7-alt0.M80P.1.x86_64 | distribution-tag | warn | Bad Distribution: tag in a package. |