Repocop reports by srpm

	rpm id	test	status	message
	libecpg6-17-1C-debuginfo-17.6-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-18-debuginfo-18.0-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.
	libpq5-17-1C-devel-17.6-alt2.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libpq.so but just /usr/lib64/libpq.so.5.17. According to SharedLibs Policy Draft, symlink /usr/lib64/libpq.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libpq.so to \%files of libpq5-17-1C-devel-17.6-alt2.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.
	libpq5-17-1C-devel-debuginfo-17.6-alt2.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libpq.so.debug is different from the same symlink in the package libpq5-16-devel-debuginfo-16.10-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.
	libpq5-17-1C-devel-static-17.6-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/libpq.a conflicts with the package libpq5-18-devel-static-18.0-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-17.6-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-1C-contrib-17.6-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/jsonb_plpython3.so /usr/share/pgsql/extension/hstore_plpython3u--1.0.sql /usr/share/pgsql/extension/ltree_plpython3u--1.0.sql conflict with the package postgresql18-python-18.0-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-llvmjit-17.6-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-llvmjit-18.0-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (671 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. atives.
	postgresql17-1C-server-17.6-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.