postgresql15-1C-15.4-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.4-alt0.p10.1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql14-1C-contrib-14.7-alt2.x86_64, for example, /usr/bin/pg_archivecleanup (23 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-llvmjit-15.4-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/amcheck/verify_heapam.bc (253 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-perl-15.4-alt0.p10.1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql14-1C-perl-14.7-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.; licts are avoidable, consider using alternatives.; 
postgresql15-1C-python-15.4-alt0.p10.1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql14-1C-python-14.7-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.;  are avoidable, consider using alternatives.; 
postgresql15-1C-server-15.4-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-server-15.4-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; 
postgresql15-1C-server-15.4-alt0.p10.1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql14-1C-server-14.7-alt2.x86_64, for example, /usr/bin/initdb (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.; ernatives.; 
postgresql15-1C-server-devel-15.4-alt0.p10.1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql14-1C-server-devel-14.7-alt2.x86_64, for example, /usr/bin/pg_server_config (389 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-tcl-15.4-alt0.p10.1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql10-tcl-10.23-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.;