Repocop reports for by-leader slev

	rpm id	test	status	message
	389-ds-base-2.4.5-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no SysV init scripts.
	bumper-0.1.13-alt1.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/bin/bump conflicts with the package mesa-demos-9.0.0-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.
	cockpit-tests-311.1-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no SysV init scripts.
	cockpit-tests-311.1-alt1.x86_64	systemd-check-socket-name	experimental	in cockpit-tests-311.1-alt1.x86_64: there is a socket cockpit-session.socket but no service cockpit-session.service. Ask ildar@ why it is not right.
	cockpit-ws-311.1-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no SysV init scripts.
	cockpit-ws-311.1-alt1.x86_64	systemd-check-socket-name	experimental	in cockpit-ws-311.1-alt1.x86_64: there is a socket cockpit-wsinstance-https-factory.socket but no service cockpit-wsinstance-https-factory.service. Ask ildar@ why it is not right.
	dogtag-pki-acme-11.4.3-alt4.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists 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.
	dogtag-pki-ca-11.4.3-alt4.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists 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.
	dogtag-pki-java-11.4.3-alt4.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists 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.
	dogtag-pki-kra-11.4.3-alt4.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists 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.
	dogtag-pki-server-11.4.3-alt4.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no SysV init scripts.
	dogtag-pki-server-theme-11.4.3-alt4.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists 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.
	dogtag-pki-tps-11.4.3-alt4.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists 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.
	freeipa-client-epn-4.11.1-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no SysV init scripts.
	freeipa-common-4.11.1-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists 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.
	freeipa-healthcheck-0.16-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no SysV init scripts.
	freeipa-server-4.11.1-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no SysV init scripts.
	freeipa-server-4.11.1-alt2.x86_64	systemd-check-socket-name	experimental	in freeipa-server-4.11.1-alt2.x86_64: there is a socket ipa-otpd.socket but no service ipa-otpd.service. Ask ildar@ why it is not right.
	freeipa-server-common-4.11.1-alt2.x86_64	file-in-usr-marked-as-conffile	warn	Files below /usr may not be marked as conffiles, since /usr might be mounted read-only and thus, the local system administrator would not have a chance to modify this configuration file.
	freeipa-server-common-4.11.1-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no SysV init scripts.
	freeipa-server-dns-4.11.1-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no SysV init scripts.
	gssproxy-0.9.1-alt1.1.x86_64	subdir-in-var-run	info	Found a subdir in /var/run or /var/lock. /var/run and /var/lock may be mounted as temporary filesystems, so the init.d scripts must handle this correctly. This will typically amount to creating any required subdirectories dynamically when the init.d script is run, rather than including them in the package and relying on rpm to create them.
	gssproxy-0.9.1-alt1.1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no SysV init scripts.
	python3-module-pyproject-fmt-1.7.0-alt1.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/bin/pyproject-fmt conflicts with the package python3-module-pyproject-parser-0.11.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
	python3-module-rfc3986-1.4.0-alt1.1.noarch	altlinux-policy-description-has-tags	fail	Description contains tags such as Provides/Requires/BuildRequires. Beware of errors with %ifs/%endifs!
	python3-module-system-seed-wheels-0.0.1-alt1.x86_64	missing-url	info	Missing Url: in a package.
	python3-module-system-seed-wheels-wheels-0.0.1-alt1.x86_64	missing-url	info	Missing Url: in a package.
	uid_wrapper-1.3.0-alt3.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libuid_wrapper.so but just /usr/lib64/libuid_wrapper.so.0.2.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libuid_wrapper.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/libuid_wrapper.so to \%files of uid_wrapper-1.3.0-alt3.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.