postgresql13-contrib-13.12-alt0.p10.1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql15-contrib-15.4-alt0.p10.1.x86_64, for example, /usr/bin/oid2name (31 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.; ; 
postgresql13-llvmjit-13.12-alt0.p10.1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql15-llvmjit-15.4-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int/_int_bool.bc (792 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.; 
postgresql13-perl-13.12-alt0.p10.1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql15-perl-15.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.; other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
postgresql13-python-13.12-alt0.p10.1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/jsonb_plpython3.so conflicts with the package postgresql15-python-15.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.; es.; , consider using alternatives.; tives.; 
postgresql13-server-13.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.; 
postgresql13-server-13.12-alt0.p10.1.x86_64	checkbashisms	experimental	checkbashisms utility found possible bashisms in: /usr/bin/postgresql-check-db-dir /etc/rc.d/init.d/postgresql; 
postgresql13-server-13.12-alt0.p10.1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql15-server-15.4-alt0.p10.1.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.; tives.; 
postgresql13-tcl-13.12-alt0.p10.1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/share/pgsql/extension/pltcl--1.0.sql /usr/share/pgsql/extension/pltcl.control /usr/share/pgsql/extension/pltclu--1.0.sql conflict with the package postgresql12-tcl-12.16-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.;