| |
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 |
libecpg6-12-debuginfo-12.22-alt1.x86_64 |
rpm-filesystem-conflict-symlink-symlink |
warn |
value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.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.
s.
s. |
|
taf |
libecpg6-12-devel-static-12.22-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package libecpg6-17-devel-static-17.2-alt1.x86_64, for example, /usr/lib64/libecpg.a (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.
s. |
|
taf |
libecpg6-13-debuginfo-13.18-alt1.x86_64 |
rpm-filesystem-conflict-symlink-symlink |
warn |
value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.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.
s.
s. |
|
taf |
libecpg6-13-devel-static-13.18-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package libecpg6-17-devel-static-17.2-alt1.x86_64, for example, /usr/lib64/libecpg.a (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.
s. |
|
taf |
libecpg6-14-debuginfo-14.15-alt1.x86_64 |
rpm-filesystem-conflict-symlink-symlink |
warn |
value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.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.
s.
s. |
|
taf |
libecpg6-14-devel-static-14.15-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package libecpg6-17-devel-static-17.2-alt1.x86_64, for example, /usr/lib64/libecpg.a (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.
s. |
|
taf |
libecpg6-15-debuginfo-15.10-alt1.x86_64 |
rpm-filesystem-conflict-symlink-symlink |
warn |
value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.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.
s.
s. |
|
taf |
libecpg6-15-devel-static-15.10-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package libecpg6-17-devel-static-17.2-alt1.x86_64, for example, /usr/lib64/libecpg.a (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.
s. |
|
taf |
libecpg6-16-1C-debuginfo-16.4-alt7.x86_64 |
rpm-filesystem-conflict-symlink-symlink |
warn |
value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.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.
s. |
|
taf |
libecpg6-16-1C-devel-static-16.4-alt7.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package libecpg6-17-devel-static-17.2-alt1.x86_64, for example, /usr/lib64/libecpg.a (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. |
|
taf |
libecpg6-16-debuginfo-16.6-alt1.x86_64 |
rpm-filesystem-conflict-symlink-symlink |
warn |
value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.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.
s. |
|
taf |
libecpg6-16-devel-static-16.6-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package libecpg6-17-devel-static-17.2-alt1.x86_64, for example, /usr/lib64/libecpg.a (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.
s. |
|
taf |
libecpg6-17-debuginfo-17.2-alt1.x86_64 |
rpm-filesystem-conflict-symlink-symlink |
warn |
value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-16-debuginfo-16.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.
s.
s. |
|
taf |
libecpg6-17-devel-static-17.2-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package libecpg6-16-devel-static-16.6-alt1.x86_64, for example, /usr/lib64/libecpg.a (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.
s. |
|
taf |
postgresql12-contrib-12.22-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql17-contrib-17.2-alt1.x86_64, for example, /usr/bin/oid2name (73 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.22-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql17-llvmjit-17.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.
s. |
|
taf |
postgresql12-perl-12.22-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql17-perl-17.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.22-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 postgresql17-python-17.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.22-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.22-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql17-server-17.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.22-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql17-tcl-17.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.
cts are avoidable, consider using alternatives. |
|
taf |
postgresql13-contrib-13.18-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql17-contrib-17.2-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. |
|
taf |
postgresql13-llvmjit-13.18-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql17-llvmjit-17.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (796 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 |
postgresql13-perl-13.18-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql17-perl-17.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.18-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 postgresql17-python-17.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.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 |
postgresql13-server-13.18-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql17-server-17.2-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (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. |
|
taf |
postgresql13-tcl-13.18-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql17-tcl-17.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.
er. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives. |
|
taf |
postgresql14-contrib-14.15-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql17-contrib-17.2-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. |
|
taf |
postgresql14-llvmjit-14.15-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql17-llvmjit-17.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (756 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 |
postgresql14-perl-14.15-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql17-perl-17.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.15-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql17-python-17.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.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. |
|
taf |
postgresql14-server-14.15-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql17-server-17.2-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (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. |
|
taf |
postgresql14-tcl-14.15-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql17-tcl-17.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.
er. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives. |
|
taf |
postgresql15-15.10-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-contrib-15.10-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql17-contrib-17.2-alt1.x86_64, for example, /usr/bin/pg_archivecleanup (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 |
postgresql15-llvmjit-15.10-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql17-llvmjit-17.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (761 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 |
postgresql15-perl-15.10-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql17-perl-17.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.10-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql17-python-17.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.10-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.10-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql17-server-17.2-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (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. |
|
taf |
postgresql15-tcl-15.10-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql14-tcl-14.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.
nflicts are avoidable, consider using alternatives. |
|
taf |
postgresql16-16.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 |
postgresql16-1C-16.4-alt7.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-1C-contrib-16.4-alt7.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/jsonb_plpython3.so conflicts with the package postgresql13-python-13.18-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 |
postgresql16-1C-llvmjit-16.4-alt7.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql17-llvmjit-17.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (598 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.
natives. |
|
taf |
postgresql16-1C-server-16.4-alt7.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.6-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql17-contrib-17.2-alt1.x86_64, for example, /usr/bin/pg_archivecleanup (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. |
|
taf |
postgresql16-llvmjit-16.6-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql17-llvmjit-17.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (590 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.
ternatives. |
|
taf |
postgresql16-perl-16.6-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql15-perl-15.10-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.6-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql15-python-15.10-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.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 |
postgresql16-server-16.6-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql17-server-17.2-alt1.x86_64, for example, /usr/bin/initdb (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.
lternatives. |
|
taf |
postgresql16-tcl-16.6-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql14-tcl-14.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.
nflicts are avoidable, consider using alternatives. |
|
taf |
postgresql17-17.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 |
postgresql17-contrib-17.2-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-contrib-16.6-alt1.x86_64, for example, /usr/bin/pg_archivecleanup (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. |
|
taf |
postgresql17-llvmjit-17.2-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-llvmjit-16.6-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (590 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 |
postgresql17-perl-17.2-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql15-perl-15.10-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 |
postgresql17-python-17.2-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql15-python-15.10-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 |
postgresql17-server-17.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 |
postgresql17-server-17.2-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-server-16.6-alt1.x86_64, for example, /usr/bin/initdb (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.
lternatives. |
|
taf |
postgresql17-tcl-17.2-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql14-tcl-14.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.
nflicts are avoidable, consider using alternatives. |