taf libecpg6-13-debuginfo-13.22-alt2.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-18-debuginfo-18.0-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-debuginfo-14.19-alt2.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-18-debuginfo-18.0-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-debuginfo-15.14-alt2.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-18-debuginfo-18.0-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-16-debuginfo-16.10-alt2.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-18-debuginfo-18.0-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-1C-debuginfo-17.6-alt2.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-18-debuginfo-18.0-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-17-debuginfo-17.6-alt2.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-18-debuginfo-18.0-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-18-debuginfo-18.0-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.6-alt2.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 libpq5-13-devel-13.22-alt2.x86_64 altlinux-policy-shared-lib-contains-devel-so info SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libpq.so but just /usr/lib64/libpq.so.5.13. According to SharedLibs Policy Draft, symlink /usr/lib64/libpq.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libpq.so to \%files of libpq5-13-devel-13.22-alt2.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; taf libpq5-13-devel-debuginfo-13.22-alt2.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/usr/lib64/libpq.so.debug is different from the same symlink in the package libpq5-17-devel-debuginfo-17.6-alt2.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 libpq5-13-devel-static-13.22-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/libpq.a conflicts with the package libpq5-18-devel-static-18.0-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 libpq5-14-devel-14.19-alt2.x86_64 altlinux-policy-shared-lib-contains-devel-so info SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libpq.so but just /usr/lib64/libpq.so.5.14. According to SharedLibs Policy Draft, symlink /usr/lib64/libpq.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libpq.so to \%files of libpq5-14-devel-14.19-alt2.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; taf libpq5-14-devel-debuginfo-14.19-alt2.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/usr/lib64/libpq.so.debug is different from the same symlink in the package libpq5-17-devel-debuginfo-17.6-alt2.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 libpq5-14-devel-static-14.19-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/libpq.a conflicts with the package libpq5-18-devel-static-18.0-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 libpq5-15-devel-15.14-alt2.x86_64 altlinux-policy-shared-lib-contains-devel-so info SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libpq.so but just /usr/lib64/libpq.so.5.15. According to SharedLibs Policy Draft, symlink /usr/lib64/libpq.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libpq.so to \%files of libpq5-15-devel-15.14-alt2.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; taf libpq5-15-devel-debuginfo-15.14-alt2.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/usr/lib64/libpq.so.debug is different from the same symlink in the package libpq5-17-devel-debuginfo-17.6-alt2.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 libpq5-15-devel-static-15.14-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/libpq.a conflicts with the package libpq5-18-devel-static-18.0-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 libpq5-16-devel-16.10-alt2.x86_64 altlinux-policy-shared-lib-contains-devel-so info SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libpq.so but just /usr/lib64/libpq.so.5.16. According to SharedLibs Policy Draft, symlink /usr/lib64/libpq.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libpq.so to \%files of libpq5-16-devel-16.10-alt2.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; taf libpq5-16-devel-debuginfo-16.10-alt2.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/usr/lib64/libpq.so.debug is different from the same symlink in the package libpq5-17-devel-debuginfo-17.6-alt2.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 libpq5-16-devel-static-16.10-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/libpq.a conflicts with the package libpq5-18-devel-static-18.0-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 libpq5-17-1C-devel-17.6-alt2.x86_64 altlinux-policy-shared-lib-contains-devel-so info SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libpq.so but just /usr/lib64/libpq.so.5.17. According to SharedLibs Policy Draft, symlink /usr/lib64/libpq.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libpq.so to \%files of libpq5-17-1C-devel-17.6-alt2.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; taf libpq5-17-1C-devel-debuginfo-17.6-alt2.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/usr/lib64/libpq.so.debug is different from the same symlink in the package libpq5-16-devel-debuginfo-16.10-alt2.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 libpq5-17-1C-devel-static-17.6-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/libpq.a conflicts with the package libpq5-18-devel-static-18.0-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 libpq5-17-devel-17.6-alt2.x86_64 altlinux-policy-shared-lib-contains-devel-so info SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libpq.so but just /usr/lib64/libpq.so.5.17. According to SharedLibs Policy Draft, symlink /usr/lib64/libpq.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libpq.so to \%files of libpq5-17-devel-17.6-alt2.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; taf libpq5-17-devel-debuginfo-17.6-alt2.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/usr/lib64/libpq.so.debug is different from the same symlink in the package libpq5-16-devel-debuginfo-16.10-alt2.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 libpq5-17-devel-static-17.6-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/libpq.a conflicts with the package libpq5-18-devel-static-18.0-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 libpq5-18-devel-static-18.0-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/libpq.a conflicts with the package libpq5-17-devel-static-17.6-alt2.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 postgresql13-contrib-13.22-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql18-contrib-18.0-alt1.x86_64, for example, /usr/bin/oid2name (49 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.22-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql18-llvmjit-18.0-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (820 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.22-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql18-perl-18.0-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 postgresql13-python-13.22-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql18-python-18.0-alt1.x86_64, for example, /usr/lib64/pgsql/jsonb_plpython3.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.; taf postgresql13-server-13.22-alt2.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.22-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql18-server-18.0-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (36 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.22-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql18-tcl-18.0-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 postgresql14-contrib-14.19-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql18-contrib-18.0-alt1.x86_64, for example, /usr/bin/oid2name (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.; ; taf postgresql14-llvmjit-14.19-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql18-llvmjit-18.0-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (801 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.19-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql18-perl-18.0-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 postgresql14-python-14.19-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql18-python-18.0-alt1.x86_64, for example, /usr/lib64/pgsql/jsonb_plpython3.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.; taf postgresql14-server-14.19-alt2.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.19-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql18-server-18.0-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (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.; ; taf postgresql14-tcl-14.19-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql18-tcl-18.0-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-15.14-alt2.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.14-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql18-contrib-18.0-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.; natives.; ; taf postgresql15-llvmjit-15.14-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql18-llvmjit-18.0-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (823 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.14-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql18-perl-18.0-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-python-15.14-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql18-python-18.0-alt1.x86_64, for example, /usr/lib64/pgsql/jsonb_plpython3.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.; taf postgresql15-server-15.14-alt2.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.14-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql18-server-18.0-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.; ; taf postgresql15-tcl-15.14-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql18-tcl-18.0-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-16.10-alt2.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.10-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql18-contrib-18.0-alt1.x86_64, for example, /usr/bin/oid2name (36 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-llvmjit-16.10-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql18-llvmjit-18.0-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (753 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.10-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql15-perl-15.14-alt2.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-python-16.10-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql18-python-18.0-alt1.x86_64, for example, /usr/lib64/pgsql/jsonb_plpython3.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.; taf postgresql16-server-16.10-alt2.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.10-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql18-server-18.0-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (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.; ; taf postgresql16-tcl-16.10-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql18-tcl-18.0-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 postgresql17-17.6-alt2.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-1C-17.6-alt2.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-1C-contrib-17.6-alt2.x86_64 rpm-filesystem-conflict-file-file warn Files /usr/lib64/pgsql/jsonb_plpython3.so /usr/share/pgsql/extension/hstore_plpython3u--1.0.sql /usr/share/pgsql/extension/ltree_plpython3u--1.0.sql conflict with the package postgresql18-python-18.0-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 postgresql17-1C-llvmjit-17.6-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql18-llvmjit-18.0-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (671 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.; atives.; taf postgresql17-1C-server-17.6-alt2.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.6-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql18-contrib-18.0-alt1.x86_64, for example, /usr/bin/oid2name (25 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.; rnatives.; taf postgresql17-llvmjit-17.6-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql18-llvmjit-18.0-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (662 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.; ernatives.; taf postgresql17-perl-17.6-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql15-perl-15.14-alt2.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 postgresql17-python-17.6-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql18-python-18.0-alt1.x86_64, for example, /usr/lib64/pgsql/jsonb_plpython3.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.; taf postgresql17-server-17.6-alt2.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.6-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql18-server-18.0-alt1.x86_64, for example, /usr/bin/initdb (24 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.6-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql18-tcl-18.0-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 postgresql18-18.0-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 postgresql18-contrib-18.0-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql17-contrib-17.6-alt2.x86_64, for example, /usr/bin/oid2name (25 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 postgresql18-llvmjit-18.0-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql17-llvmjit-17.6-alt2.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (662 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 postgresql18-perl-18.0-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql15-perl-15.14-alt2.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 postgresql18-python-18.0-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql17-python-17.6-alt2.x86_64, for example, /usr/lib64/pgsql/jsonb_plpython3.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.; , if conflicts are avoidable, consider using alternatives.; taf postgresql18-server-18.0-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 postgresql18-server-18.0-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql17-server-17.6-alt2.x86_64, for example, /usr/bin/initdb (24 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 postgresql18-tcl-18.0-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql17-tcl-17.6-alt2.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.; ;