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.; 
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.; 
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.; 
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.; 
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.; .; 
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.; 
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.; 
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.; 
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.; 
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.;