libecpg6-15-1C-debuginfo-15.12-alt0.p10.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-10-debuginfo-10.23-alt1.p10.4.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.22-alt0.p10.4.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-12-debuginfo-12.22-alt0.p10.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-13-debuginfo-13.20-alt0.p10.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-14-debuginfo-14.17-alt0.p10.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-16-debuginfo-16.8-alt0.p10.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-17-debuginfo-17.4-alt0.p10.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-10-debuginfo-10.23-alt1.p10.4.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.22-alt0.p10.4.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-12-debuginfo-12.22-alt0.p10.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-13-debuginfo-13.20-alt0.p10.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-14-debuginfo-14.17-alt0.p10.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-16-debuginfo-16.8-alt0.p10.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-17-debuginfo-17.4-alt0.p10.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-10-debuginfo-10.23-alt1.p10.4.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.22-alt0.p10.4.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-12-debuginfo-12.22-alt0.p10.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-13-debuginfo-13.20-alt0.p10.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-14-debuginfo-14.17-alt0.p10.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-16-debuginfo-16.8-alt0.p10.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-17-debuginfo-17.4-alt0.p10.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.; 
libecpg6-15-1C-devel-static-15.12-alt0.p10.1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package libecpg6-10-devel-static-10.23-alt1.p10.4.x86_64, for example, /usr/lib64/libecpg.a (6 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 libecpg6-11-devel-static-11.22-alt0.p10.4.x86_64, for example, /usr/lib64/libecpg.a (6 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 libecpg6-12-devel-static-12.22-alt0.p10.2.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.; There are file conflicts with the package libecpg6-13-devel-static-13.20-alt0.p10.1.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.; There are file conflicts with the package libecpg6-14-devel-static-14.17-alt0.p10.1.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.; There are file conflicts with the package libecpg6-15-devel-static-15.12-alt0.p10.1.x86_64, for example, /usr/lib64/libecpg.a (7 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 libecpg6-16-devel-static-16.8-alt0.p10.1.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.; There are file conflicts with the package libecpg6-17-devel-static-17.4-alt0.p10.1.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.; File /usr/lib64/libpq.a conflicts with the package libpq5-devel-static-17.4-alt0.p10.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.; 
postgresql15-1C-15.12-alt0.p10.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.; 
postgresql15-1C-contrib-15.12-alt0.p10.1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/jsonb_plpython3.so conflicts with the package postgresql13-python-13.20-alt0.p10.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.; 
postgresql15-1C-llvmjit-15.12-alt0.p10.1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql11-llvmjit-11.22-alt0.p10.4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (780 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 postgresql12-llvmjit-12.22-alt0.p10.2.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (794 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 postgresql13-llvmjit-13.20-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int/_int_bool.bc (790 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 postgresql14-llvmjit-14.17-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int/_int_bool.bc (658 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 postgresql15-llvmjit-15.12-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/adminpack/adminpack.bc (265 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 postgresql16-llvmjit-16.8-alt0.p10.1.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.; There are file conflicts with the package postgresql17-llvmjit-17.4-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (808 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.; 
postgresql15-1C-server-15.12-alt0.p10.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.;