andy	ifupdown2-3.3.0.10-alt1.noarch	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
aris	ostree-2025.6-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/ostree-2025.6-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/ostree-tmpfiles.conf sisyphus_check: check-fhs ERROR: FHS violation; 
aris	ostree-2025.6-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
crux	bird-3.1.4-alt1.src	specfile-useradd-n	warn	 -n in useradd is compat option and can be removed any time. Use -N instead.; 
crux	bird-3.1.4-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/bird-3.1.4-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/bird.conf sisyphus_check: check-fhs ERROR: FHS violation; 
dans	lxcfs-6.0.5-alt1.x86_64	init-lsb	fail	/etc/rc.d/init.d/lxcfs: not systemd compatible: lsb init header missing and lxcfs.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
dans	lxd-5.21.1-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
iv	krb5-kdc-1.22.1-alt1.x86_64	init-lsb	fail	/etc/rc.d/init.d/kadmin: not systemd compatible: lsb init header missing and kadmin.service is not present. /etc/rc.d/init.d/kprop: not systemd compatible: lsb init header missing and kprop.service is not present. /etc/rc.d/init.d/krb5kdc: not systemd compatible: lsb init header missing and krb5kdc.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
iv	krb5-kdc-1.22.1-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/krb5-kdc-1.22.1-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/krb5-krb5kdc.conf sisyphus_check: check-fhs ERROR: FHS violation; 
lakostis	nvme-2.15-alt2.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/nvme-2.15-alt2.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/65-persistent-net-nbft.rules /usr/lib/udev/rules.d/70-nvmf-autoconnect.rules /usr/lib/udev/rules.d/70-nvmf-keys.rules /usr/lib/udev/rules.d/71-nvme-hpe.rules /usr/lib/udev/rules.d/71-nvmf-netapp.rules /usr/lib/udev/rules.d/71-nvmf-vastdata.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
lakostis	nvme-2.15-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
lepata	docs-alt-virtualization-pve-11.0-alt2.noarch	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/share/doc/documentation is different from the same symlink in the package docs-alt-virtualization-one-11.0-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
naf	cryptsetup-2.8.1-alt1.x86_64	init-but-no-native-systemd	info	The package have SysV init script(s) but no native systemd files.; 
naf	cryptsetup-2.8.1-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/cryptsetup-2.8.1-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/cryptsetup.conf sisyphus_check: check-fhs ERROR: FHS violation; 
obirvalger	gitea-1.24.5-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
rider	MySQL-8.0.43-alt1.src	specfile-useradd-n	warn	 -n in useradd is compat option and can be removed any time. Use -N instead.; 
rider	MySQL-client-8.0.43-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package mariadb-server-11.8.3-alt2.x86_64, for example, /usr/share/man/man1/myisam_ftdump.1.xz (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.; 
rider	MySQL-server-8.0.43-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.; 
rider	MySQL-server-8.0.43-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/MySQL-server-8.0.43-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/mysql.conf sisyphus_check: check-fhs ERROR: FHS violation; 
rider	collectd-5.12.0-alt7.x86_64	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
rider	gnote-49.0-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.; 
rider	gnote-49.0-alt1.x86_64	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/org.gnome.Gnote.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).; 
rider	keepalived-2.3.4-alt1.x86_64	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
rider	keepalived-2.3.4-alt1.x86_64	dbus-xml-not-in-devel	info	file /usr/share/dbus-1/interfaces/org.keepalived.Vrrp1.Vrrp.xml is not used in run time. Move it to the <name>-devel subpackage.; ge.; 
rider	ocaml-5.3.0-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.; ; 
rider	ocaml-compiler-libs-5.3.0-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/ocaml/compiler-libs/META conflicts with the package ocaml-findlib-1.9.6-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.; 
rider	ocaml-ocamldoc-5.3.0-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/ocaml/ocamldoc/META conflicts with the package ocaml-findlib-1.9.6-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.; 
rider	ocaml-runtime-5.3.0-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package ocaml-findlib-1.9.6-alt2.x86_64, for example, /usr/lib64/ocaml/dynlink/META (5 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.; 
rider	openvswitch-3.3.5-alt1.src	specfile-useradd-n	warn	 -n in useradd is compat option and can be removed any time. Use -N instead.; 
rider	openvswitch-3.3.5-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/openvswitch-3.3.5-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/openvswitch.conf sisyphus_check: check-fhs ERROR: FHS violation; 
rider	openvswitch-ipsec-3.3.5-alt1.noarch	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
sem	etcnet-0.9.35-alt1.noarch	init-condrestart	warn	/etc/rc.d/init.d/network: missing condrestart target. Note: alt-specific script %_sbindir/post_service (used in %post_service macro) depends on condrestart. It is wise to add condrestart anyway./etc/rc.d/init.d/network: missing condstop target. Note: alt-specific script %_sbindir/preun_service (used in %preun_service macro) depends on condstop. It is wise to add condstop anyway.; 
shaba	NetworkManager-openconnect-1.2.10-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.; ; 
shaba	NetworkManager-sstp-1.3.2-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.; ; 
shaba	acmed-0.25.0-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	agola-0.5.0-alt3.src	specfile-useradd-n	warn	 -n in useradd is compat option and can be removed any time. Use -N instead.; 
shaba	agola-0.5.0-alt3.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	anubis-1.23.0-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	arrow-glib-doc-12.0.0-alt2.6.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.; 
shaba	branding-alt-container-11-alt1.src	requires-ImageMagick	info	Dependency on ImageMagick (compat package) found. It probably should be replaced with more specific dependency like /usr/bin/convert or ImageMagick-tools, or it can be already autodetected by findreq-shell.; 
shaba	branding-alt-container-notes-11-alt1.noarch	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.; ; 
shaba	branding-alt-server-11.1-alt4.src	requires-ImageMagick	info	Dependency on ImageMagick (compat package) found. It probably should be replaced with more specific dependency like /usr/bin/convert or ImageMagick-tools, or it can be already autodetected by findreq-shell.; 
shaba	branding-alt-virtualization-pve-11.0-alt0.7.src	requires-ImageMagick	info	Dependency on ImageMagick (compat package) found. It probably should be replaced with more specific dependency like /usr/bin/convert or ImageMagick-tools, or it can be already autodetected by findreq-shell.; 
shaba	branding-alt-virtualization-pve-notes-11.0-alt0.7.noarch	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.; ; 
shaba	branding-alt-virtualization-pve-release-11.0-alt0.7.noarch	rpm-filesystem-conflict-file-file	warn	File /etc/altlinux-release conflicts with the package altlinux-release-sisyphus-20201124-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.; 
shaba	caddy-2.10.2-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	ceph-base-19.2.3-alt1.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libosd_tp.so but just /usr/lib64/libosd_tp.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libosd_tp.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/libosd_tp.so to \%files of ceph-base-19.2.3-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.; pocop test.; 
shaba	ceph-base-19.2.3-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	ceph-common-19.2.3-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.; 
shaba	ceph-common-19.2.3-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/ceph-common-19.2.3-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/ceph-common.conf sisyphus_check: check-fhs ERROR: FHS violation /ALT/Sisyphus/files/x86_64/RPMS/ceph-common-19.2.3-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/50-rbd.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
shaba	ceph-common-19.2.3-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	ceph-exporter-19.2.3-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	ceph-fuse-19.2.3-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	ceph-immutable-object-cache-19.2.3-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	ceph-mds-19.2.3-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	ceph-mgr-19.2.3-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	ceph-mgr-cephadm-19.2.3-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.; 
shaba	ceph-mgr-dashboard-19.2.3-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.; 
shaba	ceph-mgr-diskprediction-local-19.2.3-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.; 
shaba	ceph-mgr-modules-core-19.2.3-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.; 
shaba	ceph-mgr-rook-19.2.3-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.; 
shaba	ceph-mon-19.2.3-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	ceph-osd-19.2.3-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	ceph-radosgw-19.2.3-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	ceph-volume-19.2.3-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	cephfs-mirror-19.2.3-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	cert-manager-1.15.3-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/bin/webhook conflicts with the package webhook-2.8.2-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.; es.; 
shaba	cloud-init-25.1.4-alt1.noarch	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
shaba	cloud-init-25.1.4-alt1.noarch	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.; ; 
shaba	cloud-init-25.1.4-alt1.noarch	init-condrestart	warn	/etc/rc.d/init.d/cloud-config: missing condstop target. Note: alt-specific script %_sbindir/preun_service (used in %preun_service macro) depends on condstop. It is wise to add condstop anyway./etc/rc.d/init.d/cloud-final: missing condstop target. Note: alt-specific script %_sbindir/preun_service (used in %preun_service macro) depends on condstop. It is wise to add condstop anyway./etc/rc.d/init.d/cloud-init: missing condstop target. Note: alt-specific script %_sbindir/preun_service (used in %preun_service macro) depends on condstop. It is wise to add condstop anyway./etc/rc.d/init.d/cloud-init-local: missing condstop target. Note: alt-specific script %_sbindir/preun_service (used in %preun_service macro) depends on condstop. It is wise to add condstop anyway.; 
shaba	cloud-init-25.1.4-alt1.noarch	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/noarch/RPMS/cloud-init-25.1.4-alt1.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/cloud-init.conf sisyphus_check: check-fhs ERROR: FHS violation /ALT/Sisyphus/files/noarch/RPMS/cloud-init-25.1.4-alt1.noarch.rpm: invalid udev rules path: /usr/lib/udev/rules.d/66-azure-ephemeral.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
shaba	cni-plugins-1.7.1-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/cni-plugins-1.7.1-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/cni-plugins.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	cni-plugins-1.7.1-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	connman-1.45-alt1.x86_64	init-lsb	fail	/etc/rc.d/init.d/connmand: not systemd compatible: lsb init header missing and connmand.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
shaba	connman-1.45-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/connman-1.45-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/connman_resolvconf.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	cri-o1.23-1.23.5-alt4.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	cri-o1.24-1.24.6-alt4.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	cri-o1.25-1.25.5-alt3.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	cri-o1.26-1.26.4-alt5.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	cri-o1.27-1.27.8-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	cri-o1.28-1.28.11-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	dmeventd-1.02.210-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	dmsetup-1.02.210-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/dmsetup-1.02.210-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/10-dm.rules /usr/lib/udev/rules.d/11-dm-lvm.rules /usr/lib/udev/rules.d/13-dm-disk.rules /usr/lib/udev/rules.d/95-dm-notify.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
shaba	dracut-108-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	dracut-108-alt1.x86_64	unsafe-tmp-usage-in-scripts	fail	0755
shaba	dracut-live-108-alt1.noarch	unsafe-tmp-usage-in-scripts	fail	The test discovered scripts with errors which may be used by a user for damaging important system files. For example if a script uses in its work a temp file which is created in /tmp directory, then every user can create symlinks with the same name (pattern) in this directory in order to destroy or rewrite some system or another user's files. Scripts _must_ _use_ mktemp/tempfile or must use $TMPDIR. mktemp/tempfile is safest. $TMPDIR is safer than /tmp/ because libpam-tmpdir creates a subdirectory of /tmp that is only accessible by that user, and then sets TMPDIR and other variables to that. Hence, it doesn't matter nearly as much if you create a non-random filename, because nobody but you can access it. Found error in /usr/lib/dracut/modules.d/70livenet/parse-livenet.sh: $ grep /tmp/ /usr/lib/dracut/modules.d/70livenet/parse-livenet.sh # live updates updates=$(getarg live.updates=) if [ "$updates" ]; then # make sure network comes up even if we're doing a local live device if [ "$netroot" ]; then echo > /tmp/net.ifaces fi echo "$updates" > /tmp/liveupdates.info echo '[ /tmp/liveupdates.done ]' > "$hookdir"/initqueue/finished/liveupdates.sh fi str_starts "$root" "live:" && liveurl="$root" str_starts "$liveurl" "live:" || return liveurl="${liveurl#live:}" Found error in /usr/lib/dracut/modules.d/70livenet/livenetroot.sh: $ grep /tmp/ /usr/lib/dracut/modules.d/70livenet/livenetroot.sh PATH=/usr/sbin:/usr/bin:/sbin:/bin RETRIES=${RETRIES:-100} SLEEP=${SLEEP:-5} [ /tmp/livenet.downloaded ] && exit 0 # args get passed from 40network/netroot netroot="$2" liveurl="${netroot#livenet:}" info "fetching $liveurl" sleep "$SLEEP" fi i=$((i + 1)) done > /tmp/livenet.downloaded # TODO: couldn't dmsquash-live-root handle this? if [ "${imgfile##*.}" = "iso" ]; then root=$(losetup -f) losetup "$root" "$imgfile" Found error in /usr/lib/dracut/modules.d/70dmsquash-live-autooverlay/create-overlay.sh: $ grep -A5 -B5 /tmp/ /usr/lib/dracut/modules.d/70dmsquash-live-autooverlay/create-overlay.sh #!/bin/sh command -v getarg > /dev/null || . /lib/dracut-lib.sh if getargbool 0 rd.live.debug; then exec > /tmp/create-overlay.$$.out exec 2>> /tmp/create-overlay.$$.out set -x fi gatherData() { overlay=$(getarg rd.live.overlay) Found error in /usr/lib/dracut/modules.d/70dmsquash-live/iso-scan.sh: $ grep -A5 -B5 /tmp/ /usr/lib/dracut/modules.d/70dmsquash-live/iso-scan.sh do_iso_scan() { local _name local dev for dev in /dev/disk/by-uuid/*; do _name=$(dev_unit_name "$dev") [ -e /tmp/isoscan-"${_name}" ] && continue : > /tmp/isoscan-"${_name}" mount -t auto -o ro "$dev" "/run/initramfs/isoscan" || continue if [ -f "/run/initramfs/isoscan/$isofile" ]; then losetup -f "/run/initramfs/isoscan/$isofile" udevadm trigger --action=add > /dev/null 2>&1 ln -s "$dev" /run/initramfs/isoscandev Found error in /usr/lib/dracut/modules.d/70dmsquash-live/dmsquash-live-root.sh: $ grep -A5 -B5 /tmp/ /usr/lib/dracut/modules.d/70dmsquash-live/dmsquash-live-root.sh command -v unpack_archive > /dev/null || . /lib/img-lib.sh PATH=/usr/sbin:/usr/bin:/sbin:/bin if getargbool 0 rd.live.debug; then exec > /tmp/liveroot.$$.out exec 2>> /tmp/liveroot.$$.out set -x fi [ -z "$1" ] && exit 1 livedev="$1"; 
shaba	dracut-network-manager-108-alt1.noarch	unsafe-tmp-usage-in-scripts	fail	The test discovered scripts with errors which may be used by a user for damaging important system files. For example if a script uses in its work a temp file which is created in /tmp directory, then every user can create symlinks with the same name (pattern) in this directory in order to destroy or rewrite some system or another user's files. Scripts _must_ _use_ mktemp/tempfile or must use $TMPDIR. mktemp/tempfile is safest. $TMPDIR is safer than /tmp/ because libpam-tmpdir creates a subdirectory of /tmp that is only accessible by that user, and then sets TMPDIR and other variables to that. Hence, it doesn't matter nearly as much if you create a non-random filename, because nobody but you can access it. Found error in /usr/lib/dracut/modules.d/35network-manager/nm-run.sh: $ grep /tmp/ /usr/lib/dracut/modules.d/35network-manager/nm-run.sh for _i in /sys/class/net/*; do [ "$_i" ] || continue state="/run/NetworkManager/devices/$(cat "$_i"/ifindex)" grep '^connection-uuid=' "$state" 2> /dev/null || continue ifname="${_i##*/}" dhcpopts_create "$state" > /tmp/dhclient."$ifname".dhcpopts source_hook initqueue/online "$ifname" /sbin/netroot "$ifname" done : > /tmp/nm.done; 
shaba	driverctl-0.111-alt1.noarch	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	fapolicyd-1.3.3-alt2.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/fapolicyd-1.3.3-alt2.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/fapolicyd.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	fapolicyd-1.3.3-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	fcoe-utils-1.0.34-alt3.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	fcoe-utils-1.0.34-alt3.x86_64	systemd-check-socket-name	experimental	in fcoe-utils-1.0.34-alt3.x86_64: there is a socket fcoemon.socket but no service fcoemon.service. Ask ildar@ why it is not right.; 
shaba	fence-sanlock-4.1.0-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/fence-sanlock-4.1.0-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/fence_sanlockd.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	fish-4.0.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.; 
shaba	fish-4.0.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/share/fish/completions/yadm.fish conflicts with the package yadm-3.5.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.; 
shaba	flannel-0.27.3-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/flannel-0.27.3-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/flannel.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	flannel-0.27.3-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	foomuuri-0.29-alt2.noarch	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/noarch/RPMS/foomuuri-0.29-alt2.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/foomuuri.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	foomuuri-0.29-alt2.noarch	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	forgejo-11.0.7-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	freeradius-3.2.8-alt1.src	specfile-useradd-n	warn	 -n in useradd is compat option and can be removed any time. Use -N instead.; 
shaba	freeradius-3.2.8-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.; 
shaba	freeradius-3.2.8-alt1.x86_64	init-lsb	fail	/etc/rc.d/init.d/radiusd: not systemd compatible: lsb init header missing and radiusd.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
shaba	freeradius-3.2.8-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/freeradius-3.2.8-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/radiusd.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	frr-10.3.1-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.; 
shaba	frr-10.3.1-alt1.x86_64	init-condrestart	fail	/etc/rc.d/init.d/frr: missing condstop target. ERROR: alt-specific script %_sbindir/preun_service (used in your %preun_service macro) depends on condstop. Please, fix.; 
shaba	frr-10.3.1-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/frr-10.3.1-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/frr.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	fwbuilder-6.0.0-alt2.beta.106.a5e1.x86_64	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
shaba	fwbuilder-6.0.0-alt2.beta.106.a5e1.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/fwbuilder.desktop: hint: value "System;Settings;Security;Qt;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; 
shaba	galera-garbd-26.4.24-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/galera-garbd-26.4.24-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/garbd.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	gdm-data-49.1-alt1.noarch	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.; ; 
shaba	gdm-libs-49.1-alt1.x86_64	library-pkgnames	info	package contains public library which is used in external packages: name should be lib* according to http://altlinux.org/Drafts/SharedLibs; 
shaba	gerbera-2.6.1-alt1.src	specfile-useradd-n	warn	 -n in useradd is compat option and can be removed any time. Use -N instead.; 
shaba	gerbera-2.6.1-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	gitea-act-0.2.13-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	gitea-tea-0.10.1-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/bin/tea conflicts with the package tea-63.1.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.; 
shaba	gnome-boxes-49.0-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.; 
shaba	gnome-boxes-49.0-alt1.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/org.gnome.Boxes.desktop: hint: value "GNOME;GTK;System;Development;Emulator;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; 
shaba	grafana-12.1.0-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.; 
shaba	grafana-12.1.0-alt2.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/grafana-12.1.0-alt2.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/grafana.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	guacd-1.6.0-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	guestfs-data-0.6-alt3.x86_64	missing-url	info	Missing Url: in a package.; 
shaba	hivex-1.3.24-alt1.x86_64	library-pkgnames	info	package contains public library which is used in external packages: name should be lib* according to http://altlinux.org/Drafts/SharedLibs; 
shaba	ignition-2.19.0-alt3.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	influxdb-1.12.0-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/influxdb-1.12.0-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/influxdb.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	influxdb-1.12.0-alt1.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.; 
shaba	installer-distro-alt-server-v-stage2-10.1.0-alt2.noarch	rpm-filesystem-conflict-file-file	warn	Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-virtualization-pve-stage2-11.0.0-alt0.4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
shaba	installer-distro-virtualization-pve-stage2-11.0.0-alt0.4.noarch	rpm-filesystem-conflict-file-file	warn	Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-virtualization-one-stage2-11.0.0-alt0.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
shaba	iwpmd-59.0-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/iwpmd-59.0-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/90-iwpmd.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
shaba	kapacitor-1.5.9-alt1.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.; 
shaba	kea-common-3.0.1-alt2.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/kea-common-3.0.1-alt2.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/kea.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	kea-ctrl-agent-3.0.1-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	kea-dhcp-ddns-3.0.1-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	kea-dhcp4-3.0.1-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	kea-dhcp6-3.0.1-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	kea-doc-3.0.1-alt2.noarch	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
shaba	kmscon-9.1.0-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	knot-3.4.8-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	knot-resolver-6.0.15-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/knot-resolver-6.0.15-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/knot-resolver.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	knot-resolver-6.0.15-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	kpartx-0.11.1-alt3.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/kpartx-0.11.1-alt3.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/66-kpartx.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
shaba	kubernetes1.23-common-1.23.17-alt4.noarch	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/noarch/RPMS/kubernetes1.23-common-1.23.17-alt4.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/kubernetes.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	kubernetes1.23-kubelet-1.23.17-alt4.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	kubernetes1.23-master-1.23.17-alt4.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	kubernetes1.23-node-1.23.17-alt4.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	kubernetes1.24-common-1.24.17-alt3.noarch	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/noarch/RPMS/kubernetes1.24-common-1.24.17-alt3.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/kubernetes.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	kubernetes1.24-kubelet-1.24.17-alt3.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	kubernetes1.24-master-1.24.17-alt3.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	kubernetes1.24-node-1.24.17-alt3.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	kubernetes1.25-common-1.25.16-alt3.noarch	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/noarch/RPMS/kubernetes1.25-common-1.25.16-alt3.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/kubernetes.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	kubernetes1.25-kubelet-1.25.16-alt3.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	kubernetes1.25-master-1.25.16-alt3.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	kubernetes1.25-node-1.25.16-alt3.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	kubernetes1.26-common-1.26.15-alt3.noarch	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/noarch/RPMS/kubernetes1.26-common-1.26.15-alt3.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/kubernetes.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	kubernetes1.26-kubelet-1.26.15-alt3.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	kubernetes1.26-master-1.26.15-alt3.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	kubernetes1.26-node-1.26.15-alt3.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	kubernetes1.27-common-1.27.16-alt3.noarch	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/noarch/RPMS/kubernetes1.27-common-1.27.16-alt3.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/kubernetes.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	kubernetes1.27-kubelet-1.27.16-alt3.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	kubernetes1.27-master-1.27.16-alt3.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	kubernetes1.27-node-1.27.16-alt3.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	kubernetes1.28-common-1.28.15-alt3.noarch	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/noarch/RPMS/kubernetes1.28-common-1.28.15-alt3.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/kubernetes.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	kubernetes1.28-kubelet-1.28.15-alt3.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	kubernetes1.28-master-1.28.15-alt3.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	kubernetes1.28-node-1.28.15-alt3.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	libdevmapper-event-1.02.210-alt1.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libdevmapper-event-lvm2.so but just /usr/lib64/libdevmapper-event-lvm2.so.2.03. According to SharedLibs Policy Draft, symlink /usr/lib64/libdevmapper-event-lvm2.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/libdevmapper-event-lvm2.so to \%files of libdevmapper-event-1.02.210-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.; 
shaba	liberasurecode-doc-1.6.5-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.; 
shaba	libgadu-devel-1.12.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.; 
shaba	libguac-client-kubernetes-1.6.0-alt2.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libguac-client-kubernetes.so but just /usr/lib64/libguac-client-kubernetes.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libguac-client-kubernetes.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/libguac-client-kubernetes.so to \%files of libguac-client-kubernetes-1.6.0-alt2.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.; 
shaba	libguac-client-rdp-1.6.0-alt2.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libguac-client-rdp.so but just /usr/lib64/libguac-client-rdp.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libguac-client-rdp.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/libguac-client-rdp.so to \%files of libguac-client-rdp-1.6.0-alt2.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.; 
shaba	libguac-client-ssh-1.6.0-alt2.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libguac-client-ssh.so but just /usr/lib64/libguac-client-ssh.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libguac-client-ssh.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/libguac-client-ssh.so to \%files of libguac-client-ssh-1.6.0-alt2.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.; 
shaba	libguac-client-telnet-1.6.0-alt2.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libguac-client-telnet.so but just /usr/lib64/libguac-client-telnet.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libguac-client-telnet.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/libguac-client-telnet.so to \%files of libguac-client-telnet-1.6.0-alt2.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.; 
shaba	libguac-client-vnc-1.6.0-alt2.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libguac-client-vnc.so but just /usr/lib64/libguac-client-vnc.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libguac-client-vnc.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/libguac-client-vnc.so to \%files of libguac-client-vnc-1.6.0-alt2.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.; 
shaba	libguac-devel-1.6.0-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.; 
shaba	libpcsclite-2.4.0-alt1.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libpcsclite_real.so but just /usr/lib64/libpcsclite_real.so.1. According to SharedLibs Policy Draft, symlink /usr/lib64/libpcsclite_real.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/libpcsclite_real.so to \%files of libpcsclite-2.4.0-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.; 
shaba	libpcsclite-devel-2.4.0-alt1.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libpcscspy.so but just /usr/lib64/libpcscspy.so.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libpcscspy.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/libpcscspy.so to \%files of libpcsclite-devel-2.4.0-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.; 
shaba	libproxy-tools-0.5.11-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/bin/proxy conflicts with the package python3-module-proxy-py-2.4.10-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; ernatives.; 
shaba	libsmi-0.5.0-alt3.x86_64	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
shaba	libvirt-daemon-11.5.0-alt1.x86_64	systemd-check-socket-name	experimental	in libvirt-daemon-11.5.0-alt1.x86_64: there is a socket libvirtd-admin.socket but no service libvirtd-admin.service. Ask ildar@ why it is not right.; in libvirt-daemon-11.5.0-alt1.x86_64: there is a socket libvirtd-ro.socket but no service libvirtd-ro.service. Ask ildar@ why it is not right.; in libvirt-daemon-11.5.0-alt1.x86_64: there is a socket libvirtd-tcp.socket but no service libvirtd-tcp.service. Ask ildar@ why it is not right.; in libvirt-daemon-11.5.0-alt1.x86_64: there is a socket libvirtd-tls.socket but no service libvirtd-tls.service. Ask ildar@ why it is not right.; 
shaba	libvirt-daemon-common-11.5.0-alt1.x86_64	init-condrestart	fail	/etc/rc.d/init.d/libvirt-guests: missing condrestart target. Note: alt-specific script %_sbindir/post_service (used in %post_service macro) depends on condrestart. It is wise to add condrestart anyway./etc/rc.d/init.d/libvirt-guests: missing condstop target. ERROR: alt-specific script %_sbindir/preun_service (used in your %preun_service macro) depends on condstop. Please, fix.; 
shaba	libvirt-daemon-driver-interface-11.5.0-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	libvirt-daemon-driver-interface-11.5.0-alt1.x86_64	systemd-check-socket-name	experimental	in libvirt-daemon-driver-interface-11.5.0-alt1.x86_64: there is a socket virtinterfaced-admin.socket but no service virtinterfaced-admin.service. Ask ildar@ why it is not right.; in libvirt-daemon-driver-interface-11.5.0-alt1.x86_64: there is a socket virtinterfaced-ro.socket but no service virtinterfaced-ro.service. Ask ildar@ why it is not right.; 
shaba	libvirt-daemon-driver-lxc-11.5.0-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	libvirt-daemon-driver-lxc-11.5.0-alt1.x86_64	systemd-check-socket-name	experimental	in libvirt-daemon-driver-lxc-11.5.0-alt1.x86_64: there is a socket virtlxcd-admin.socket but no service virtlxcd-admin.service. Ask ildar@ why it is not right.; in libvirt-daemon-driver-lxc-11.5.0-alt1.x86_64: there is a socket virtlxcd-ro.socket but no service virtlxcd-ro.service. Ask ildar@ why it is not right.; 
shaba	libvirt-daemon-driver-network-11.5.0-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	libvirt-daemon-driver-network-11.5.0-alt1.x86_64	systemd-check-socket-name	experimental	in libvirt-daemon-driver-network-11.5.0-alt1.x86_64: there is a socket virtnetworkd-admin.socket but no service virtnetworkd-admin.service. Ask ildar@ why it is not right.; in libvirt-daemon-driver-network-11.5.0-alt1.x86_64: there is a socket virtnetworkd-ro.socket but no service virtnetworkd-ro.service. Ask ildar@ why it is not right.; 
shaba	libvirt-daemon-driver-nodedev-11.5.0-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	libvirt-daemon-driver-nodedev-11.5.0-alt1.x86_64	systemd-check-socket-name	experimental	in libvirt-daemon-driver-nodedev-11.5.0-alt1.x86_64: there is a socket virtnodedevd-admin.socket but no service virtnodedevd-admin.service. Ask ildar@ why it is not right.; in libvirt-daemon-driver-nodedev-11.5.0-alt1.x86_64: there is a socket virtnodedevd-ro.socket but no service virtnodedevd-ro.service. Ask ildar@ why it is not right.; 
shaba	libvirt-daemon-driver-nwfilter-11.5.0-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	libvirt-daemon-driver-nwfilter-11.5.0-alt1.x86_64	systemd-check-socket-name	experimental	in libvirt-daemon-driver-nwfilter-11.5.0-alt1.x86_64: there is a socket virtnwfilterd-admin.socket but no service virtnwfilterd-admin.service. Ask ildar@ why it is not right.; in libvirt-daemon-driver-nwfilter-11.5.0-alt1.x86_64: there is a socket virtnwfilterd-ro.socket but no service virtnwfilterd-ro.service. Ask ildar@ why it is not right.; 
shaba	libvirt-daemon-driver-qemu-11.5.0-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	libvirt-daemon-driver-qemu-11.5.0-alt1.x86_64	systemd-check-socket-name	experimental	in libvirt-daemon-driver-qemu-11.5.0-alt1.x86_64: there is a socket virtqemud-admin.socket but no service virtqemud-admin.service. Ask ildar@ why it is not right.; in libvirt-daemon-driver-qemu-11.5.0-alt1.x86_64: there is a socket virtqemud-ro.socket but no service virtqemud-ro.service. Ask ildar@ why it is not right.; 
shaba	libvirt-daemon-driver-secret-11.5.0-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	libvirt-daemon-driver-secret-11.5.0-alt1.x86_64	systemd-check-socket-name	experimental	in libvirt-daemon-driver-secret-11.5.0-alt1.x86_64: there is a socket virtsecretd-admin.socket but no service virtsecretd-admin.service. Ask ildar@ why it is not right.; in libvirt-daemon-driver-secret-11.5.0-alt1.x86_64: there is a socket virtsecretd-ro.socket but no service virtsecretd-ro.service. Ask ildar@ why it is not right.; 
shaba	libvirt-daemon-driver-storage-core-11.5.0-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	libvirt-daemon-driver-storage-core-11.5.0-alt1.x86_64	systemd-check-socket-name	experimental	in libvirt-daemon-driver-storage-core-11.5.0-alt1.x86_64: there is a socket virtstoraged-admin.socket but no service virtstoraged-admin.service. Ask ildar@ why it is not right.; in libvirt-daemon-driver-storage-core-11.5.0-alt1.x86_64: there is a socket virtstoraged-ro.socket but no service virtstoraged-ro.service. Ask ildar@ why it is not right.; 
shaba	libvirt-daemon-driver-vbox-11.5.0-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	libvirt-daemon-driver-vbox-11.5.0-alt1.x86_64	systemd-check-socket-name	experimental	in libvirt-daemon-driver-vbox-11.5.0-alt1.x86_64: there is a socket virtvboxd-admin.socket but no service virtvboxd-admin.service. Ask ildar@ why it is not right.; in libvirt-daemon-driver-vbox-11.5.0-alt1.x86_64: there is a socket virtvboxd-ro.socket but no service virtvboxd-ro.service. Ask ildar@ why it is not right.; 
shaba	libvirt-daemon-lock-11.5.0-alt1.x86_64	systemd-check-socket-name	experimental	in libvirt-daemon-lock-11.5.0-alt1.x86_64: there is a socket virtlockd-admin.socket but no service virtlockd-admin.service. Ask ildar@ why it is not right.; 
shaba	libvirt-daemon-log-11.5.0-alt1.x86_64	systemd-check-socket-name	experimental	in libvirt-daemon-log-11.5.0-alt1.x86_64: there is a socket virtlogd-admin.socket but no service virtlogd-admin.service. Ask ildar@ why it is not right.; 
shaba	libvirt-daemon-proxy-11.5.0-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	libvirt-daemon-proxy-11.5.0-alt1.x86_64	systemd-check-socket-name	experimental	in libvirt-daemon-proxy-11.5.0-alt1.x86_64: there is a socket virtproxyd-admin.socket but no service virtproxyd-admin.service. Ask ildar@ why it is not right.; in libvirt-daemon-proxy-11.5.0-alt1.x86_64: there is a socket virtproxyd-ro.socket but no service virtproxyd-ro.service. Ask ildar@ why it is not right.; in libvirt-daemon-proxy-11.5.0-alt1.x86_64: there is a socket virtproxyd-tcp.socket but no service virtproxyd-tcp.service. Ask ildar@ why it is not right.; in libvirt-daemon-proxy-11.5.0-alt1.x86_64: there is a socket virtproxyd-tls.socket but no service virtproxyd-tls.service. Ask ildar@ why it is not right.; 
shaba	libvirt-libs-11.5.0-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.; 
shaba	linstor-common-1.32.2-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.; 
shaba	linstor-controller-1.32.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.; 
shaba	linstor-controller-1.32.2-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	linstor-satellite-1.32.2-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	lldpad-1.1.1-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	loki-3.5.3-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	lvm2-2.03.36-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/lvm2-2.03.36-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/lvm2.conf sisyphus_check: check-fhs ERROR: FHS violation /ALT/Sisyphus/files/x86_64/RPMS/lvm2-2.03.36-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/69-dm-lvm.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
shaba	lvm2-cmirrord-2.03.36-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	lvm2-lockd-2.03.36-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	mariadb-11.8.3-alt2.src	specfile-useradd-n	warn	 -n in useradd is compat option and can be removed any time. Use -N instead.; 
shaba	mariadb-client-debuginfo-11.8.3-alt2.x86_64	rpm-filesystem-conflict-symlink-file	warn	symlink /usr/lib/debug/usr/bin/mysqltest.debug is a file in the package MySQL-client-debuginfo-8.0.43-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.; .; ives.; 
shaba	mariadb-server-11.8.3-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package MySQL-client-8.0.43-alt1.x86_64, for example, /usr/share/man/man1/myisam_ftdump.1.xz (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.; 
shaba	mariadb-server-11.8.3-alt2.x86_64	rpm-filesystem-conflict-symlink-file	warn	symlink /usr/share/man/man1/mysql_upgrade.1.xz is a file in the package MySQL-client-8.0.43-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.; ives.; ives.; 
shaba	mariadb-server-11.8.3-alt2.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/mariadb-server-11.8.3-alt2.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/mariadb.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	mariadb-server-debuginfo-11.8.3-alt2.x86_64	rpm-filesystem-conflict-symlink-file	warn	symlink /usr/lib/debug/usr/sbin/mysqld.debug is a file in the package MySQL-server-debuginfo-8.0.43-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.; ives.; ives.; 
shaba	mariadb-server-galera-11.8.3-alt2.x86_64	bin-permissions	info	not executable file /usr/bin/wsrep_sst_common; 
shaba	mariadb-server-galera-11.8.3-alt2.x86_64	systemd-check-socket-name	experimental	in mariadb-server-galera-11.8.3-alt2.x86_64: there is a socket mariadbcheck.socket but no service mariadbcheck.service. Ask ildar@ why it is not right.; 
shaba	mariadb-server-perl-11.8.3-alt2.noarch	rpm-filesystem-conflict-symlink-file	warn	symlink /usr/share/man/man1/mysqldumpslow.1.xz is a file in the package MySQL-client-8.0.43-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.; 
shaba	matchbox-0.11.0-alt1.x86_64	rpm-filesystem-conflict-dir-dir	fail	directory /etc/matchbox is a directory in package matchbox-window-manager-1.2-alt5.1.x86_64 with different user,group or permissions. You should add explicit conflicts.; 
shaba	matchbox-0.11.0-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	mdadm-4.4-alt3.x86_64	init-lsb	fail	/etc/rc.d/init.d/mdadm: not systemd compatible: lsb init header missing and mdadm.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
shaba	mdadm-4.4-alt3.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/mdadm-4.4-alt3.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/01-md-raid-creating.rules /usr/lib/udev/rules.d/63-md-raid-arrays.rules /usr/lib/udev/rules.d/64-md-raid-assembly.rules /usr/lib/udev/rules.d/69-md-clustered-confirm-device.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
shaba	mdevctl-1.4.0-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/mdevctl-1.4.0-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/60-mdevctl.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
shaba	memcached-1.6.38-alt1.src	specfile-useradd-n	warn	 -n in useradd is compat option and can be removed any time. Use -N instead.; 
shaba	minio-2025.10.15-alt1.src	specfile-useradd-n	warn	 -n in useradd is compat option and can be removed any time. Use -N instead.; 
shaba	minio-2025.10.15-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	moosefs-chunkserver-4.58.1-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/moosefs-chunkserver-4.58.1-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/80-moosefs-chunkserver.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
shaba	mstflint-4.32.0.1-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.; 
shaba	multipath-tools-0.11.1-alt3.x86_64	init-lsb	fail	/etc/rc.d/init.d/multipathd: not systemd compatible: lsb init header missing and multipathd.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
shaba	multipath-tools-0.11.1-alt3.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/multipath-tools-0.11.1-alt3.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/multipath.conf sisyphus_check: check-fhs ERROR: FHS violation /ALT/Sisyphus/files/x86_64/RPMS/multipath-tools-0.11.1-alt3.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/11-dm-mpath.rules /usr/lib/udev/rules.d/11-dm-parts.rules /usr/lib/udev/rules.d/56-multipath.rules /usr/lib/udev/rules.d/68-del-part-nodes.rules /usr/lib/udev/rules.d/99-z-dm-mpath-late.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
shaba	net-snmp-clients-5.9.4-alt1.3.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package python3-module-snmpclitools-0.7.2-alt1.noarch, 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.; 
shaba	net-snmp-common-5.9.4-alt1.3.noarch	unsafe-tmp-usage-in-scripts	fail	The test discovered scripts with errors which may be used by a user for damaging important system files. For example if a script uses in its work a temp file which is created in /tmp directory, then every user can create symlinks with the same name (pattern) in this directory in order to destroy or rewrite some system or another user's files. Scripts _must_ _use_ mktemp/tempfile or must use $TMPDIR. mktemp/tempfile is safest. $TMPDIR is safer than /tmp/ because libpam-tmpdir creates a subdirectory of /tmp that is only accessible by that user, and then sets TMPDIR and other variables to that. Hence, it doesn't matter nearly as much if you create a non-random filename, because nobody but you can access it. Found error in /usr/share/doc/net-snmp-common-5.9.4/passtest: $ grep /tmp/ /usr/share/doc/net-snmp-common-5.9.4/passtest # Process SET requests by simply logging the assigned value # Note that such "assignments" are not persistent, # nor is the syntax or requested value validated # if [ "$1" = "-s" ]; then echo $* >> /tmp/passtest.log exit 0 fi # # GETNEXT requests - determine next valid instance; 
shaba	net-snmp-snmpd-5.9.4-alt1.3.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/net-snmp-snmpd-5.9.4-alt1.3.x86_64.rpm: license not found in '/usr/share/license' directory: BSD-like /ALT/Sisyphus/files/x86_64/RPMS/net-snmp-snmpd-5.9.4-alt1.3.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/net-snmp.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	netavark-1.16.1-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	nfs-ganesha-7.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/libganesha_nfsd.so but just /usr/lib64/libganesha_nfsd.so.7.2. According to SharedLibs Policy Draft, symlink /usr/lib64/libganesha_nfsd.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/libganesha_nfsd.so to \%files of nfs-ganesha-7.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.; 
shaba	nfs-ganesha-7.2-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	nmstate-2.1.4-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	open-iscsi-2.1.11-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/open-iscsi-2.1.11-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/iscsi.conf sisyphus_check: check-fhs ERROR: FHS violation /ALT/Sisyphus/files/x86_64/RPMS/open-iscsi-2.1.11-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/50-iscsi-firmware-login.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
shaba	open-iscsi-iscsiuio-2.1.11-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	open-vm-tools-13.0.5-alt1.x86_64	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
shaba	open-vm-tools-13.0.5-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/open-vm-tools-13.0.5-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/open-vm-tools-vgauthd.conf sisyphus_check: check-fhs ERROR: FHS violation /ALT/Sisyphus/files/x86_64/RPMS/open-vm-tools-13.0.5-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/90-vmware-guest-tools.rules /usr/lib/udev/rules.d/98-open-vm-tools.rules /usr/lib/udev/rules.d/99-vmware-scsi-udev.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
shaba	open-vm-tools-13.0.5-alt1.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.; 
shaba	open-vm-tools-desktop-13.0.5-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/open-vm-tools-desktop-13.0.5-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/open-vm-tools-desktop.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	opennebula-context-6.6.1-alt1.noarch	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	openuds-actor-4.0.0-alt1.noarch	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/UDS_Actor_Configuration.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).; 
shaba	openuds-actor-4.0.0-alt1.noarch	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/UDS_Actor_Configuration.desktop: hint: value "Settings;System;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; 
shaba	openuds-client-4.0.0-alt2.noarch	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/UDSClient.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).; 
shaba	openuds-server-4.0.0-alt3.noarch	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	openuds-server-nginx-4.0.0-alt3.noarch	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/noarch/RPMS/openuds-server-nginx-4.0.0-alt3.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/openuds.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	openuds-server-nginx-4.0.0-alt3.noarch	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	openuds-tunnel-4.0.0-alt1.noarch	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	ovirt-imageio-daemon-2.4.7-alt1.1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	ovirt-vmconsole-host-1.0.9-alt1.noarch	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	ovirt-vmconsole-proxy-1.0.9-alt1.noarch	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	ovn-24.03.5-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/ovn-24.03.5-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/ovn.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	ovn-central-24.03.5-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	ovn-host-24.03.5-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	ovn-vtep-24.03.5-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	pcsc-lite-2.4.0-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/pcsc-lite-2.4.0-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/pcsc-lite.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	pdns-4.9.1-alt1.1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	pdns-ixfrdist-4.9.1-alt1.1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	pgbouncer-1.24.1-alt1.x86_64	init-lsb	fail	/etc/rc.d/init.d/pgbouncer: not systemd compatible: lsb init header missing and pgbouncer.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
shaba	pgbouncer-1.24.1-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/pgbouncer-1.24.1-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/pgbouncer.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	podman-5.6.1-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/podman-5.6.1-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/podman.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	podman-5.6.1-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	podman-docker-5.6.1-alt1.noarch	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/noarch/RPMS/podman-docker-5.6.1-alt1.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/podman-docker.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	postgresql13-repmgr-5.5.0-alt4.x86_64	init-lsb	fail	/etc/rc.d/init.d/repmgr: not systemd compatible: lsb init header missing and repmgr.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
shaba	postgresql13-repmgr-5.5.0-alt4.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-repmgr-5.5.0-alt4.x86_64, for example, /usr/bin/repmgr (5 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.; s.; 
shaba	postgresql13-repmgr-5.5.0-alt4.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/postgresql13-repmgr-5.5.0-alt4.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/repmgr.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	postgresql14-repmgr-5.5.0-alt4.x86_64	init-lsb	fail	/etc/rc.d/init.d/repmgr: not systemd compatible: lsb init header missing and repmgr.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
shaba	postgresql14-repmgr-5.5.0-alt4.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-repmgr-5.5.0-alt4.x86_64, for example, /usr/bin/repmgr (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.; s.; consider using alternatives.; 
shaba	postgresql14-repmgr-5.5.0-alt4.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/postgresql14-repmgr-5.5.0-alt4.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/repmgr.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	postgresql15-repmgr-5.5.0-alt4.x86_64	init-lsb	fail	/etc/rc.d/init.d/repmgr: not systemd compatible: lsb init header missing and repmgr.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
shaba	postgresql15-repmgr-5.5.0-alt4.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/bin/repmgr /usr/bin/repmgrd /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc conflict with the package postgresql18-repmgr-5.5.0-alt4.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.; r using alternatives.; 
shaba	postgresql15-repmgr-5.5.0-alt4.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/postgresql15-repmgr-5.5.0-alt4.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/repmgr.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	pptpd-1.5.0-alt1.x86_64	init-lsb	fail	/etc/rc.d/init.d/pptpd: not systemd compatible: lsb init header missing and pptpd.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
shaba	prometheus-common-3.5.0-alt1.noarch	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/noarch/RPMS/prometheus-common-3.5.0-alt1.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/prometheus.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	promtail-3.5.3-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	proxmox-acme-1.7.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.; 
shaba	proxmox-backup-server-4.0.14.1-alt2.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/proxmox-backup-server-4.0.14.1-alt2.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/60-proxmox-backup-server.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
shaba	proxmox-backup-server-4.0.14.1-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	proxmox-widget-toolkit-5.0.4-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.; 
shaba	pve-backup-restore-image-0.5-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.; ; 
shaba	pve-backup-restore-image-0.5-alt1.x86_64	missing-url	info	Missing Url: in a package.; 
shaba	pve-backup-restore-image-0.5-alt1.x86_64	rpm-package-is-obsoleted	warn	The package is  obsoleted by the package proxmox-backup-restore-image-4.0.14.1-alt1.x86_64, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of proxmox-backup-restore-image-4.0.14.1-alt1.x86_64 to remove Obsoletes: tag.; 
shaba	pve-cluster-9.0.6-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	pve-container-6.0.9-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	pve-firewall-6.0.3-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/pve-firewall-6.0.3-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/pve-firewall.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	pve-firewall-6.0.3-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	pve-ha-manager-5.0.4-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	pve-lxc-6.0.5-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	pve-manager-9.0.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.; 
shaba	pve-manager-9.0.6-alt2.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/pve-manager-9.0.6-alt2.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/pve-manager.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	pve-manager-9.0.6-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	pve-qemu-common-10.0.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.; 
shaba	pve-qemu-common-10.0.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/share/qemu/trace-events-all conflicts with the package qemu-tools-10.0.3-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.; cts are avoidable, consider using alternatives.; 
shaba	pve-qemu-server-9.0.18-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	pve-qemu-system-10.0.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/bin/qemu-vmsr-helper conflicts with the package qemu-vmsr-helper-10.0.3-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.; using alternatives.; ernatives.; 
shaba	pve-storage-9.0.13-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/pve-storage-9.0.13-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/50-rbd-pve.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
shaba	qemu-common-10.0.3-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/libexec/qemu-bridge-helper /usr/share/man/man1/qemu.1.xz conflict with the package pve-qemu-system-10.0.2-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.; 
shaba	qemu-device-display-vhost-user-gpu-10.0.3-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/libexec/vhost-user-gpu conflicts with the package pve-qemu-system-10.0.2-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.; 
shaba	qemu-guest-agent-10.0.3-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/qemu-guest-agent-10.0.3-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/90-qemu-guest-agent.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
shaba	qemu-pr-helper-10.0.3-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	qemu-system-hppa-core-10.0.3-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/share/qemu/hppa-firmware.img /usr/share/qemu/hppa-firmware64.img conflict with the package pve-qemu-common-10.0.2-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.; 
shaba	qemu-system-ppc-core-10.0.3-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.; 
shaba	qemu-tools-10.0.3-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/share/qemu/trace-events-all conflicts with the package pve-qemu-common-10.0.2-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.; 
shaba	qemu-vmsr-helper-10.0.3-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/bin/qemu-vmsr-helper conflicts with the package pve-qemu-system-10.0.2-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.; 
shaba	qemu-vmsr-helper-10.0.3-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	rbd-mirror-19.2.3-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	rdma-core-59.0-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/rdma-core-59.0-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/60-rdma-ndd.rules /usr/lib/udev/rules.d/60-rdma-persistent-naming.rules /usr/lib/udev/rules.d/75-rdma-description.rules /usr/lib/udev/rules.d/90-rdma-hw-modules.rules /usr/lib/udev/rules.d/90-rdma-ulp-modules.rules /usr/lib/udev/rules.d/90-rdma-umad.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
shaba	resource-agents-4.16.0-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/resource-agents-4.16.0-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/resource-agents.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	resource-agents-4.16.0-alt1.x86_64	unsafe-tmp-usage-in-scripts	fail	The test discovered scripts with errors which may be used by a user for damaging important system files. For example if a script uses in its work a temp file which is created in /tmp directory, then every user can create symlinks with the same name (pattern) in this directory in order to destroy or rewrite some system or another user's files. Scripts _must_ _use_ mktemp/tempfile or must use $TMPDIR. mktemp/tempfile is safest. $TMPDIR is safer than /tmp/ because libpam-tmpdir creates a subdirectory of /tmp that is only accessible by that user, and then sets TMPDIR and other variables to that. Hence, it doesn't matter nearly as much if you create a non-random filename, because nobody but you can access it. Found error in /usr/lib/ocf/resource.d/heartbeat/rabbitmq-server-ha: $ grep /tmp/ /usr/lib/ocf/resource.d/heartbeat/rabbitmq-server-ha </parameter> <parameter name="debug" unique="0" required="0"> <longdesc lang="en"> The debug flag for agent (${OCF_RESKEY_binary}) instance. In the /tmp/ directory will be created rmq-* files for log some operations and ENV values inside OCF-script. </longdesc> <shortdesc lang="en">AMQP server (${OCF_RESKEY_binary}) debug flag</shortdesc> <content type="boolean" default="${OCF_RESKEY_debug_default}" /> </parameter> local rc=$OCF_ERR_GENERIC local LH="${LL} monitor:" ocf_log debug "${LH} action start." if ocf_is_true "${OCF_RESKEY_debug}"; then d=`date '+%Y%m%d %H:%M:%S'` echo $d >> /tmp/rmq-monitor.log env >> /tmp/rmq-monitor.log echo "$d [monitor] start='${OCF_RESKEY_CRM_meta_notify_start_uname}' stop='${OCF_RESKEY_CRM_meta_notify_stop_uname}' active='${OCF_RESKEY_CRM_meta_notify_active_uname}' inactive='${OCF_RESKEY_CRM_meta_notify_inactive_uname}'" >> /tmp/rmq-ocf.log fi get_monitor rc=$? ocf_log debug "${LH} role: ${OCF_RESKEY_CRM_meta_role}" ocf_log debug "${LH} result: $rc" -- local LH="${LL} start:" local nowtime if ocf_is_true "${OCF_RESKEY_debug}"; then d=`date '+%Y%m%d %H:%M:%S'` echo $d >> /tmp/rmq-start.log env >> /tmp/rmq-start.log echo "$d [start] start='${OCF_RESKEY_CRM_meta_notify_start_uname}' stop='${OCF_RESKEY_CRM_meta_notify_stop_uname}' active='${OCF_RESKEY_CRM_meta_notify_active_uname}' inactive='${OCF_RESKEY_CRM_meta_notify_inactive_uname}'" >> /tmp/rmq-ocf.log fi ocf_log info "${LH} action begin." get_status -- local rc=$OCF_ERR_GENERIC local LH="${LL} stop:" if ocf_is_true "${OCF_RESKEY_debug}"; then d=$(date '+%Y%m%d %H:%M:%S') echo $d >> /tmp/rmq-stop.log env >> /tmp/rmq-stop.log echo "$d [stop] start='${OCF_RESKEY_CRM_meta_notify_start_uname}' stop='${OCF_RESKEY_CRM_meta_notify_stop_uname}' active='${OCF_RESKEY_CRM_meta_notify_active_uname}' inactive='${OCF_RESKEY_CRM_meta_notify_inactive_uname}'" >> /tmp/rmq-ocf.log fi ocf_log info "${LH} action begin." ocf_log info "${LH} Deleting master attribute" -- local LH="${LL} notify:" local nodelist if ocf_is_true "${OCF_RESKEY_debug}"; then d=`date '+%Y%m%d %H:%M:%S'` echo $d >> /tmp/rmq-notify.log env >> /tmp/rmq-notify.log echo "$d [notify] ${OCF_RESKEY_CRM_meta_notify_type}-${OCF_RESKEY_CRM_meta_notify_operation} promote='${OCF_RESKEY_CRM_meta_notify_promote_uname}' demote='${OCF_RESKEY_CRM_meta_notify_demote_uname}' master='${OCF_RESKEY_CRM_meta_notify_master_uname}' slave='${OCF_RESKEY_CRM_meta_notify_slave_uname}' start='${OCF_RESKEY_CRM_meta_notify_start_uname}' stop='${OCF_RESKEY_CRM_meta_notify_stop_uname}' active='${OCF_RESKEY_CRM_meta_notify_active_uname}' inactive='${OCF_RESKEY_CRM_meta_notify_inactive_uname}'" >> /tmp/rmq-ocf.log fi if [ "${OCF_RESKEY_CRM_meta_notify_type}" = 'post' ] ; then # POST- anything notify section case "$OCF_RESKEY_CRM_meta_notify_operation" in -- local rc=$OCF_ERR_GENERIC local LH="${LL} promote:" if ocf_is_true "${OCF_RESKEY_debug}"; then d=$(date '+%Y%m%d %H:%M:%S') echo $d >> /tmp/rmq-promote.log env >> /tmp/rmq-promote.log echo "$d [promote] start='${OCF_RESKEY_CRM_meta_notify_start_uname}' stop='${OCF_RESKEY_CRM_meta_notify_stop_uname}' active='${OCF_RESKEY_CRM_meta_notify_active_uname}' inactive='${OCF_RESKEY_CRM_meta_notify_inactive_uname}'" >> /tmp/rmq-ocf.log fi ocf_log info "${LH} action begin." get_monitor; 
shaba	rsyslog-8.2502.0-alt4.1.x86_64	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
shaba	rygel-45.0-alt1.x86_64	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/rygel-preferences.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).; 
shaba	sanlock-4.1.0-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/sanlock-4.1.0-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/sanlock.conf /usr/lib/tmpfiles.d/wdmd.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	shorewall6-5.2.8-alt2.noarch	uncompressed-manpages	info	Package contains uncompressed manual pages.; 
shaba	snapd-2.66.1-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/snapd-2.66.1-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/snapd.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	snapd-2.66.1-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	spice-vdagent-0.23.0-alt2.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/spice-vdagent-0.23.0-alt2.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/spice-vdagentd.conf sisyphus_check: check-fhs ERROR: FHS violation /ALT/Sisyphus/files/x86_64/RPMS/spice-vdagent-0.23.0-alt2.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/70-spice-vdagentd.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
shaba	spice-vdagent-0.23.0-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	squid-7.1-alt1.x86_64	init-lsb	fail	/etc/rc.d/init.d/squid: not systemd compatible: lsb init header missing and squid.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
shaba	squid-7.1-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/squid-7.1-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/squid.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	squid-7.1-alt1.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.; 
shaba	squid-doc-7.1-alt1.noarch	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
shaba	srp_daemon-59.0-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/srp_daemon-59.0-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/60-srp_daemon.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
shaba	systemd-258.1-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/systemd-258.1-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/20-systemd-osc-context.conf /usr/lib/tmpfiles.d/20-systemd-shell-extra.conf /usr/lib/tmpfiles.d/20-systemd-ssh-generator.conf /usr/lib/tmpfiles.d/20-systemd-stub.conf /usr/lib/tmpfiles.d/20-systemd-userdb.conf /usr/lib/tmpfiles.d/README /usr/lib/tmpfiles.d/credstore.conf /usr/lib/tmpfiles.d/journal-nocow.conf /usr/lib/tmpfiles.d/provision.conf /usr/lib/tmpfiles.d/systemd-nologin.conf /usr/lib/tmpfiles.d/systemd-pstore.conf /usr/lib/tmpfiles.d/systemd-tmp.conf /usr/lib/tmpfiles.d/systemd.conf sisyphus_check: check-fhs ERROR: FHS violation /ALT/Sisyphus/files/x86_64/RPMS/systemd-258.1-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/70-uaccess.rules /usr/lib/udev/rules.d/71-seat.rules /usr/lib/udev/rules.d/73-seat-late.rules /usr/lib/udev/rules.d/90-vconsole.rules /usr/lib/udev/rules.d/99-systemd.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
shaba	systemd-container-258.1-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/systemd-container-258.1-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/systemd-nspawn.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	systemd-networkd-258.1-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/systemd-networkd-258.1-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/systemd-network.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	systemd-portable-258.1-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/systemd-portable-258.1-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/portables.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	systemd-stateless-258.1-alt1.noarch	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/noarch/RPMS/systemd-stateless-258.1-alt1.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/etc.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	systemd-tmpfiles-common-258.1-alt1.noarch	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/noarch/RPMS/systemd-tmpfiles-common-258.1-alt1.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/home.conf /usr/lib/tmpfiles.d/legacy.conf /usr/lib/tmpfiles.d/tmp.conf /usr/lib/tmpfiles.d/var.conf /usr/lib/tmpfiles.d/x11.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	talos-devel-1.10.7-alt2.noarch	macos-ds-store-file-in-package	warn	There is a file in the package named <tt>.DS_Store</tt> or <tt>.DS_Store.gz</tt>, the file name used by Mac OS X to store folder attributes.  Such files are generally useless in packages and were usually accidentally included by copying complete directories from the source tarball.; ; 
shaba	talos-devel-1.10.7-alt2.noarch	unsafe-tmp-usage-in-scripts	fail	The test discovered scripts with errors which may be used by a user for damaging important system files. For example if a script uses in its work a temp file which is created in /tmp directory, then every user can create symlinks with the same name (pattern) in this directory in order to destroy or rewrite some system or another user's files. Scripts _must_ _use_ mktemp/tempfile or must use $TMPDIR. mktemp/tempfile is safest. $TMPDIR is safer than /tmp/ because libpam-tmpdir creates a subdirectory of /tmp that is only accessible by that user, and then sets TMPDIR and other variables to that. Hence, it doesn't matter nearly as much if you create a non-random filename, because nobody but you can access it. Found error in /usr/share/gocode/src/github.com/siderolabs/talos/hack/test/e2e-qemu.sh: $ grep /tmp/ /usr/share/gocode/src/github.com/siderolabs/talos/hack/test/e2e-qemu.sh case "${WITH_AIRGAPPED:-false}" in false) ;; *) "${TALOSCTL}" debug air-gapped 172.20.1.1 >/tmp/airgapped.log 2>&1 & sleep 5 # wait for the air-gapped server to start mv air-gapped-patch.yaml /tmp/air-gapped-patch.yaml QEMU_FLAGS+=("--config-patch=@/tmp/air-gapped-patch.yaml") ;; esac function create_cluster { build_registry_mirrors function destroy_cluster() { "${TALOSCTL}" cluster destroy \ --name "${CLUSTER_NAME}" \ --provisioner "${PROVISIONER}" \ --save-cluster-logs-archive-path="/tmp/logs-${LOG_ARCHIVE_SUFFIX}.tar.gz" \ --save-support-archive-path="/tmp/support-${LOG_ARCHIVE_SUFFIX}.zip" } trap destroy_cluster SIGINT EXIT create_cluster; 
shaba	targetcli-3.0.1-alt1.noarch	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	telegraf-1.35.3-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/telegraf-1.35.3-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/telegraf.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	telegraf-1.35.3-alt1.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.; 
shaba	traefik-3.5.3-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	trivy-0.66.0-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.; 
shaba	trivy-server-0.66.0-alt1.noarch	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	udev-258.1-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/udev-258.1-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/static-nodes-permissions.conf sisyphus_check: check-fhs ERROR: FHS violation /ALT/Sisyphus/files/x86_64/RPMS/udev-258.1-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/50-udev-default.rules /usr/lib/udev/rules.d/60-autosuspend.rules /usr/lib/udev/rules.d/60-block.rules /usr/lib/udev/rules.d/60-cdrom_id.rules /usr/lib/udev/rules.d/60-dmi-id.rules /usr/lib/udev/rules.d/60-drm.rules /usr/lib/udev/rules.d/60-evdev.rules /usr/lib/udev/rules.d/60-fido-id.rules /usr/lib/udev/rules.d/60-infiniband.rules /usr/lib/udev/rules.d/60-input-id.rules /usr/lib/udev/rules.d/60-persistent-alsa.rules /usr/lib/udev/rules.d/60-persistent-hidraw.rules /usr/lib/udev/rules.d/60-persistent-input.rules /usr/lib/udev/rules.d/60-persistent-storage-mtd.rules /usr/lib/udev/rules.d/60-persistent-storage-tape.rules /usr/lib/udev/rules.d/60-persistent-storage.rules /usr/lib/udev/rules.d/60-persistent-v4l.rules /usr/lib/udev/rules.d/60-sensor.rules /usr/lib/udev/rules.d/60-serial.rules /usr/lib/udev/rules.d/64-btrfs.rules /usr/lib/udev/rules.d/70-camera.rules /usr/lib/udev/rules.d/70-joystick.rules /usr/lib/udev/rules.d/70-memory.rules /usr/lib/udev/rules.d/70-mouse.rules /usr/lib/udev/rules.d/70-power-switch.rules /usr/lib/udev/rules.d/70-touchpad.rules /usr/lib/udev/rules.d/75-net-description.rules /usr/lib/udev/rules.d/75-probe_mtd.rules /usr/lib/udev/rules.d/78-sound-card.rules /usr/lib/udev/rules.d/80-drivers.rules /usr/lib/udev/rules.d/80-net-setup-link.rules /usr/lib/udev/rules.d/81-net-bridge.rules /usr/lib/udev/rules.d/81-net-dhcp.rules /usr/lib/udev/rules.d/90-image-dissect.rules /usr/lib/udev/rules.d/90-iocost.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
shaba	udev-258.1-alt1.x86_64	sisyphus_check-check-dirlist	warn	sisyphus_check --check-dirlist failed: package contains a directory /etc/udev/rules.d that exclusively belongs to package udev-rules; 
shaba	udev-rules-sgutils-1.48-alt2.noarch	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/noarch/RPMS/udev-rules-sgutils-1.48-alt2.noarch.rpm: invalid udev rules path: /usr/lib/udev/rules.d/00-scsi-sg3_config.rules /usr/lib/udev/rules.d/40-usb-blacklist.rules /usr/lib/udev/rules.d/54-before-scsi-sg3_id.rules /usr/lib/udev/rules.d/55-scsi-sg3_id.rules /usr/lib/udev/rules.d/58-scsi-sg3_symlink.rules /usr/lib/udev/rules.d/59-fc-wwpn-id.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
shaba	uki-direct-25.7.3-alt1.noarch	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	urbackup-client-2.5.25-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	urbackup-server-2.5.33-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.; 
shaba	urbackup-server-2.5.33-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	valkey-8.1.3-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	vdsm-4.50.6-alt3.noarch	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/noarch/RPMS/vdsm-4.50.6-alt3.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/vdsm.conf sisyphus_check: check-fhs ERROR: FHS violation /ALT/Sisyphus/files/noarch/RPMS/vdsm-4.50.6-alt3.noarch.rpm: invalid udev rules path: /usr/lib/udev/rules.d/12-vdsm-lvm.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
shaba	vdsm-4.50.6-alt3.noarch	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	vdsm-hook-checkips-4.50.6-alt3.noarch	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	vdsm-hook-localdisk-4.50.6-alt3.noarch	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/noarch/RPMS/vdsm-hook-localdisk-4.50.6-alt3.noarch.rpm: invalid udev rules path: /usr/lib/udev/rules.d/12-vdsm-localdisk.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
shaba	vhostmd-1.1-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	victorialogs-1.27.0-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	victorialogs-vlagent-1.27.0-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	victoriametrics-1.122.1-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	victoriametrics-cluster-vminsert-1.122.0-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	victoriametrics-cluster-vmselect-1.122.0-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	victoriametrics-cluster-vmstorage-1.122.0-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	victoriametrics-vmagent-1.122.1-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	victoriametrics-vmalert-1.122.1-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	victoriametrics-vmauth-1.122.1-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	vitastor-mon-2.4.1-alt1.noarch	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	vitastor-osd-2.4.1-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/vitastor-osd-2.4.1-alt1.x86_64.rpm: license not found in '/usr/share/license' directory: VNPL-1.1 /ALT/Sisyphus/files/x86_64/RPMS/vitastor-osd-2.4.1-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/90-vitastor.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
shaba	vitastor-osd-2.4.1-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	vmango-0.12.1-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	vpnc-0.5.3-alt7.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.; 
shaba	vsftpd-3.0.5-alt1.src	specfile-useradd-n	warn	 -n in useradd is compat option and can be removed any time. Use -N instead.; 
shrek	polkit-126-alt2.src	specfile-useradd-n	warn	 -n in useradd is compat option and can be removed any time. Use -N instead.; 
shrek	polkit-126-alt2.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/polkit-126-alt2.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/polkit-tmpfiles.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shrek	polkit-126-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shrek	pve-lxc-syscalld-2.0.2-alt2.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/pve-lxc-syscalld-2.0.2-alt2.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/pve-lxc-syscalld.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shrek	pve-lxc-syscalld-2.0.2-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shrek	rtkit-0.13-alt1.x86_64	dbus-xml-not-in-devel	info	file /usr/share/dbus-1/interfaces/org.freedesktop.RealtimeKit1.xml is not used in run time. Move it to the <name>-devel subpackage.; 
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.
