| |
packager |
rpm id |
test |
status |
message |
 |
oddity |
pgadmin3-1.23.0b-alt3.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. |
 |
taf |
postgresql12-contrib-12.18-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-contrib-16.2-alt1.x86_64, for example, /usr/bin/oid2name (70 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. |
|
taf |
postgresql12-llvmjit-12.18-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-llvmjit-16.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (799 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.
s. |
|
taf |
postgresql12-perl-12.18-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-perl-16.2-alt1.x86_64, for example, /usr/lib64/pgsql/plperl.so (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.
licts are avoidable, consider using alternatives. |
|
taf |
postgresql12-python-12.18-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql16-python-16.2-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. |
|
taf |
postgresql12-server-12.18-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. |
|
taf |
postgresql12-server-12.18-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-server-16.2-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (633 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. |
|
taf |
postgresql12-tcl-12.18-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-tcl-16.2-alt1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (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.
icts are avoidable, consider using alternatives. |
|
taf |
postgresql13-contrib-13.14-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-contrib-16.2-alt1.x86_64, for example, /usr/bin/pgbench (39 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.
|
|
taf |
postgresql13-llvmjit-13.14-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-llvmjit-16.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (804 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.
es.
s. |
|
taf |
postgresql13-perl-13.14-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql16-perl-16.2-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.
ther. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives. |
|
taf |
postgresql13-python-13.14-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
Files /usr/lib64/pgsql/jsonb_plpython3.so /usr/lib64/pgsql/plpython3.so conflict with the package postgresql16-python-16.2-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.
ernatives. |
|
taf |
postgresql13-server-13.14-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. |
|
taf |
postgresql13-server-13.14-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-server-16.2-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (34 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. |
|
taf |
postgresql13-tcl-13.14-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql16-tcl-16.2-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.
her. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives. |
|
taf |
postgresql14-contrib-14.11-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-contrib-16.2-alt1.x86_64, for example, /usr/bin/pgbench (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.
|
|
taf |
postgresql14-llvmjit-14.11-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-llvmjit-16.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (783 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.
es.
s. |
|
taf |
postgresql14-perl-14.11-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql16-perl-16.2-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.
nflicts are avoidable, consider using alternatives. |
|
taf |
postgresql14-python-14.11-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql16-python-16.2-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.
idable, consider using alternatives.
ernatives. |
|
taf |
postgresql14-server-14.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. |
|
taf |
postgresql14-server-14.11-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-server-16.2-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (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. |
|
taf |
postgresql14-tcl-14.11-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql16-tcl-16.2-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.
her. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives. |
|
taf |
postgresql15-15.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. |
|
taf |
postgresql15-1C-15.5-alt4.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. |
|
taf |
postgresql15-1C-contrib-15.5-alt4.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/jsonb_plpython3.so conflicts with the package postgresql13-python-13.14-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. |
|
taf |
postgresql15-1C-llvmjit-15.5-alt4.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-llvmjit-16.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (784 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.
es. |
|
taf |
postgresql15-1C-server-15.5-alt4.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. |
|
taf |
postgresql15-contrib-15.6-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-contrib-16.2-alt1.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.
|
|
taf |
postgresql15-llvmjit-15.6-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-llvmjit-16.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (787 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.
tives. |
|
taf |
postgresql15-perl-15.6-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql16-perl-16.2-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.
nflicts are avoidable, consider using alternatives. |
|
taf |
postgresql15-python-15.6-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql16-python-16.2-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.
idable, consider using alternatives.
ernatives. |
|
taf |
postgresql15-server-15.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. |
|
taf |
postgresql15-server-15.6-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-server-16.2-alt1.x86_64, for example, /usr/bin/initdb (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.
lternatives. |
|
taf |
postgresql15-tcl-15.6-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql14-tcl-14.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.
nflicts are avoidable, consider using alternatives. |
|
taf |
postgresql16-16.2-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. |
|
taf |
postgresql16-contrib-16.2-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql15-contrib-15.6-alt1.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.
|
|
taf |
postgresql16-llvmjit-16.2-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql15-llvmjit-15.6-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (787 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.
s. |
|
taf |
postgresql16-perl-16.2-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql15-perl-15.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.
nflicts are avoidable, consider using alternatives. |
|
taf |
postgresql16-python-16.2-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql15-python-15.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.
dable, consider using alternatives.
ernatives. |
|
taf |
postgresql16-server-16.2-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. |
|
taf |
postgresql16-server-16.2-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql15-server-15.6-alt1.x86_64, for example, /usr/bin/initdb (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.
lternatives. |
|
taf |
postgresql16-tcl-16.2-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql14-tcl-14.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.
nflicts are avoidable, consider using alternatives. |