Repocop reports by srpm

	rpm id	test	status	message
	libecpg6-17-1C-debuginfo-17.2-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-15-debuginfo-15.10-alt3.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.
	libecpg6-17-1C-devel-static-17.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package libecpg6-17-devel-static-17.2-alt2.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.
	postgresql17-1C-17.2-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.
	postgresql17-1C-contrib-17.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/jsonb_plpython3.so conflicts with the package postgresql13-python-13.18-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. dable, consider using alternatives.
	postgresql17-1C-llvmjit-17.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql17-llvmjit-17.2-alt2.x86_64, for example, /usr/lib64/pgsql/bitcode/auto_explain/auto_explain.bc (204 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.
	postgresql17-1C-perl-17.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql12-perl-12.22-alt1.x86_64, for example, /usr/lib64/pgsql/plperl.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.
	postgresql17-1C-python-17.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql12-python-12.22-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.
	postgresql17-1C-server-17.2-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.
	postgresql17-1C-server-17.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql12-server-12.22-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (633 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.
	postgresql17-1C-tcl-17.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql12-tcl-12.22-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.