Repocop reports by srpm

	rpm id	test	status	message
	libecpg6-17-debuginfo-17.2-alt2.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-devel-static-17.2-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package libecpg6-17-1C-devel-static-17.2-alt1.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-17.2-alt2.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-contrib-17.2-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql16-contrib-16.6-alt2.x86_64, for example, /usr/bin/pg_archivecleanup (22 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-llvmjit-17.2-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql17-1C-llvmjit-17.2-alt1.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-perl-17.2-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql15-perl-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. nflicts are avoidable, consider using alternatives.
	postgresql17-python-17.2-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql15-python-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. dable, consider using alternatives. ernatives.
	postgresql17-server-17.2-alt2.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-server-17.2-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql16-server-16.6-alt2.x86_64, for example, /usr/bin/initdb (26 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. lternatives.
	postgresql17-tcl-17.2-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql14-tcl-14.15-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. nflicts are avoidable, consider using alternatives.