@core	bind-9.18.42-alt1.src	specfile-useradd-n	warn	 -n in useradd is compat option and can be removed any time. Use -N instead.; 
@core	bind-9.18.42-alt1.x86_64	init-lsb	fail	/etc/rc.d/init.d/bind: not systemd compatible: lsb init header missing and bind.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
@core	bind-9.18.42-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/bind-9.18.42-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/bind.conf sisyphus_check: check-fhs ERROR: FHS violation; 
azol	asciidoc-10.2.1-alt2.src	altlinux-policy-tex-rpm-build-texmf	warn	According to TeX policy (http://www.altlinux.org/TeXPolicy) packages that install files to /usr/share/texmf should BuildRequires(pre): rpm-build-texmf for the dependency magic to work.; 
imz	tests-for-installed-python3-pkgs-0.1.29-alt1.noarch	missing-url	info	Missing Url: in a package.; 
lav	displaycal-3.9.16-alt1.noarch	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/displaycal-3dlut-maker.desktop. Please add it or report a bug against this test if you already have registered one (not including menu unrelated ones as Core or Qt).; ).; .; Qt).; 
lav	displaycal-3.9.16-alt1.noarch	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/displaycal-vrml-to-x3d-converter.desktop: warning: value "model/vrml;x-world/x-vrml;" for key "MimeType" in group "Desktop Entry" contains value "x-world/x-vrml" which is a MIME type that should probably not be used: the use of "x-world" as media type is strongly discouraged in favor of a subtype of the "application" media type; 
savoptik	udiskie-2.5.8-alt2.noarch	altlinux-find-lang-mo	warn	Language specific files in /usr/share/locale should be marked, for example, using %find_lang. See http://www.altlinux.org/FindLangPolicy for details.; 
sin	libsss_autofs-2.9.7-alt4.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
sin	libsss_sudo-2.9.7-alt4.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
sin	sssd-2.9.7-alt4.src	specfile-useradd-n	warn	 -n in useradd is compat option and can be removed any time. Use -N instead.; 
sin	sssd-2.9.7-alt4.x86_64	systemd-check-socket-name	experimental	in sssd-2.9.7-alt4.x86_64: there is a socket sssd-pam-priv.socket but no service sssd-pam-priv.service. Ask ildar@ why it is not right.; 
sin	sssd-kcm-2.9.7-alt4.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
sin	sssd-pac-2.9.7-alt4.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
slev	389-ds-base-3.1.3-alt3.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
slev	certmonger-0.79.21-alt1.x86_64	file-in-usr-marked-as-conffile	warn	Files below <tt>/usr</tt> may not be marked as conffiles, since;  <tt>/usr</tt> might be mounted read-only and thus, the local system;  administrator would not have a chance to modify this configuration;  file.; ; 
slev	certmonger-0.79.21-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/certmonger-0.79.21-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/certmonger.conf sisyphus_check: check-fhs ERROR: FHS violation; 
slev	cockpit-ws-336.2-alt3.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/cockpit-ws-336.2-alt3.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/cockpit-ws.conf sisyphus_check: check-fhs ERROR: FHS violation; 
slev	cockpit-ws-336.2-alt3.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
slev	cockpit-ws-336.2-alt3.x86_64	systemd-check-socket-name	experimental	in cockpit-ws-336.2-alt3.x86_64: there is a socket cockpit-session.socket but no service cockpit-session.service. Ask ildar@ why it is not right.; in cockpit-ws-336.2-alt3.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.; 
slev	dogtag-pki-ca-11.6.1-alt1.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.; 
slev	dogtag-pki-java-11.6.1-alt1.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.; 
slev	dogtag-pki-kra-11.6.1-alt1.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.; 
slev	dogtag-pki-server-11.6.1-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
slev	dogtag-pki-server-theme-11.6.1-alt1.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.; 
slev	dogtag-pki-tps-11.6.1-alt1.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.; 
slev	freeipa-client-epn-4.12.5-alt3.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
slev	freeipa-common-4.12.5-alt3.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.; 
slev	freeipa-healthcheck-0.19-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
slev	freeipa-server-4.12.5-alt3.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/freeipa-server-4.12.5-alt3.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/ipa.conf sisyphus_check: check-fhs ERROR: FHS violation; 
slev	freeipa-server-4.12.5-alt3.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
slev	freeipa-server-4.12.5-alt3.x86_64	systemd-check-socket-name	experimental	in freeipa-server-4.12.5-alt3.x86_64: there is a socket ipa-otpd.socket but no service ipa-otpd.service. Ask ildar@ why it is not right.; 
slev	freeipa-server-common-4.12.5-alt3.x86_64	file-in-usr-marked-as-conffile	warn	Files below <tt>/usr</tt> may not be marked as conffiles, since;  <tt>/usr</tt> might be mounted read-only and thus, the local system;  administrator would not have a chance to modify this configuration;  file.; ; 
slev	freeipa-server-dns-4.12.5-alt3.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
slev	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.; 
slev	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.
slev	opendnssec-2.1.14-alt2.x86_64	file-in-usr-marked-as-conffile	warn	Files below <tt>/usr</tt> may not be marked as conffiles, since;  <tt>/usr</tt> might be mounted read-only and thus, the local system;  administrator would not have a chance to modify this configuration;  file.; ; 
slev	opendnssec-2.1.14-alt2.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/opendnssec-2.1.14-alt2.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/opendnssec.conf sisyphus_check: check-fhs ERROR: FHS violation; 
slev	python3-module-proxy-py-2.4.10-alt1.1.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/bin/proxy conflicts with the package libproxy-tools-0.5.11-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.; 
slev	python3-module-pyproject-fmt-2.6.0-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/bin/pyproject-fmt conflicts with the package python3-module-pyproject-parser-0.13.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.; 
slev	python3-module-snmpclitools-0.7.2-alt1.noarch	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package net-snmp-clients-5.9.4-alt1.3.x86_64, for example, /usr/bin/snmpbulkwalk (6 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.; 
slev	python3-module-system-seed-wheels-0.0.2-alt1.x86_64	missing-url	info	Missing Url: in a package.; 
slev	python3-module-system-seed-wheels-wheels-0.0.2-alt1.x86_64	missing-url	info	Missing Url: in a package.; 
slev	uid_wrapper-1.3.2-alt1.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.2. According to SharedLibs Policy Draft, symlink /usr/lib64/libuid_wrapper.so should be placed in a special subpackage named lib<name>-devel. If you have already packaged this symlink in lib<name>-devel, just append \%exclude /usr/lib64/libuid_wrapper.so to \%files of uid_wrapper-1.3.2-alt1.x86_64. Otherwise, move the symlink into the subpackage lib<name>-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.; 
viy	dogtag-ldapjdk-5.6.0-alt1.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.; 
viy	tomcat-el-3.0-api-9.0.109-alt1.noarch	altlinux-java-duplicate-jars	info	file /usr/share/java/tomcat-el-api.jar confilicts with package: tomcat10-lib-10.1.20-alt3_jvm17.noarch: if the jar do provide the same standard interface, it should be alternative. Otherwise it is recommended to rename the jar; 
viy	tomcat-el-3.0-api-9.0.109-alt1.noarch	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/share/java/tomcat-el-api.jar is different from the same symlink in the package tomcat10-lib-10.1.20-alt3_jvm17.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
viy	tomcat-jsp-2.3-api-9.0.109-alt1.noarch	altlinux-java-duplicate-jars	info	file /usr/share/java/tomcat-jsp-api.jar confilicts with package: tomcat10-lib-10.1.20-alt3_jvm17.noarch: if the jar do provide the same standard interface, it should be alternative. Otherwise it is recommended to rename the jar; 
viy	tomcat-jsp-2.3-api-9.0.109-alt1.noarch	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/share/java/tomcat-jsp-api.jar is different from the same symlink in the package tomcat10-lib-10.1.20-alt3_jvm17.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
viy	tomcat-servlet-4.0-api-9.0.109-alt1.noarch	altlinux-java-duplicate-jars	info	file /usr/share/java/tomcat-servlet-api.jar confilicts with package: tomcat10-lib-10.1.20-alt3_jvm17.noarch: if the jar do provide the same standard interface, it should be alternative. Otherwise it is recommended to rename the jar; 
viy	tomcat-servlet-4.0-api-9.0.109-alt1.noarch	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/share/java/tomcat-servlet-api.jar is different from the same symlink in the package tomcat10-lib-10.1.20-alt3_jvm17.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
