CroMagRally-3.0.0-alt2.x86_64	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/cromagrally.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).; 
CroMagRally-3.0.0-alt2.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/cromagrally.desktop: warning: value "Cro-Mag Rally" for key "Comment" in group "Desktop Entry" looks the same as that of key "Name"; 
GameHub-0.16.3.2-alt1.x86_64	altlinux-find-lang-mo	warn	Language specific files in /usr/share/locale should be marked, for example, using %find_lang. See http://www.altlinux.org/FindLangPolicy for details.; 
Nanosaur-1.4.4-alt2.x86_64	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/io.jor.nanosaur.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).; 
Nanosaur2-2.1.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/io.jor.nanosaur2.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).; 
OttoMatic-4.0.1-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/io.jor.ottomatic.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).; 
PC6001VX-4.2.13-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.; 
PC6001VX-4.2.13-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/PC6001VX.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).; 
RMG-0.6.5-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.; 
Vanilla-Conquer-06032023-alt1.1.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/Vanilla-Conquer-ra.desktop: warning: value "Vanilla Conquer - Red Alert" for key "Comment" in group "Desktop Entry" looks the same as that of key "Name"; 
alt-tweaks-0.2.2-alt3.noarch	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/org.alt.Tweaks.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).; 
altemu-mount-0.1-alt2.x86_64	missing-url	info	Missing Url: in a package.; 
altemu-mount-0.1-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
altemu-overlayfs-0.2-alt7.x86_64	missing-url	info	Missing Url: in a package.; 
altemu-overlayfs-0.2-alt7.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
b-em-2.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.; 
b-em-2.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/bin/jstest conflicts with the package joyutils-1.8.1-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.; 
blastem-0.6.2-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/blastem.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).; 
blastem-0.6.2-alt1.x86_64	iconsdir	experimental	Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.; 
blockattack-2.8.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.; 
chafa-libs-1.14.2-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; 
chafa-static-1.14.2-alt1.x86_64	library-pkgnames-static	warn	package contains static library which has the same name as a shared library in the repository, but neither package name ends with -devel-static according to http://altlinux.org/Drafts/SharedLibs nor the package explicitly conflicts with the package with .so library; 
denise-2.6-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.; 
dhewm3-1.5.4-alt2.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.dhewm3.Dhewm3.d3xp.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).; 
doomsday-2.3.1-alt1.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libdeng_shell.so but just /usr/lib64/libdeng_shell.so.2.3.1. According to SharedLibs Policy Draft, symlink /usr/lib64/libdeng_shell.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/libdeng_shell.so to \%files of doomsday-2.3.1-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.; st.; p test.; 
doomsday-2.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.; 
dosbox-staging-0.82.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.; 
dosbox-x-2024.10.01-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.; 
ecwolf-1.4.1-alt1.gitd1de69a.x86_64	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/ecwolf.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).; 
emulationstation-batocera-39-alt15.gitc3d5c67.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.; 
emulationstation-batocera-39-alt15.gitc3d5c67.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.; ; 
emulationstation-batocera-39-alt15.gitc3d5c67.x86_64	iconsdir	experimental	Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.; 
emulationstation-de-3.2.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.; 
emulationstation-de-3.2.0-alt1.x86_64	iconsdir	experimental	Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.; 
enyo-doom-1.1.1-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/enyo-doom.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).; 
enyo-doom-1.1.1-alt1.x86_64	rpm-package-is-obsoleted	warn	The package is  obsoleted by the package enyo-launcher-2.0.6-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 enyo-launcher-2.0.6-alt1.x86_64 to remove Obsoletes: tag.; 
enyo-launcher-2.0.6-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/enyo-launcher.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).; 
enyo-launcher-2.0.6-alt1.x86_64	rpm-obsolete-live-package	info	The package obsoletes the package enyo-doom-1.1.1-alt1.x86_64, but the package enyo-doom-1.1.1-alt1.x86_64 is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.; 
f3-qt-2.1.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/f3-qt.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).; 
foobillardplus-3.43-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.; 
foobillardplus-3.43-alt2.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/foobillardplus.desktop: warning: value "3D OpenGL billiard game" for key "Comment" in group "Desktop Entry" looks the same as that of key "GenericName"; /usr/share/applications/foobillardplus.desktop: warning: value "3D-OpenGL-Billard-Spiel" for key "Comment[de]" in group "Desktop Entry" looks the same as that of key "GenericName[de]"; /usr/share/applications/foobillardplus.desktop: warning: value "Jeu de billard en 3D OpenGL" for key "Comment[fr]" in group "Desktop Entry" looks the same as that of key "GenericName[fr]"; 
furnace-0.6.8.2-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/furnace.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).; 
furnace-doc-0.6.8.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.; 
gcolor3-2.4.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/nl.hjdskes.gcolor3.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).; 
glaxnimate-0.5.4-alt3.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.; 
glaxnimate-0.5.4-alt3.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.mattbas.Glaxnimate.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).; 
gptokeyb-0.2.9-alt3.gitb85b098.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/gptokeyb-0.2.9-alt3.gitb85b098.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/65-gptokeyb-uinput.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
gptokeyb-handheld-control-0.2.9-alt3.gitb85b098.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
gsplus-0.14-alt2.x86_64	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/gsplus.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).; 
gzdoom-4.13.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.; 
hurrican-1.0.9.2-alt5.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.; 
hypnotix-4.9-alt1.noarch	altlinux-find-lang-mo	warn	Language specific files in /usr/share/locale should be marked, for example, using %find_lang. See http://www.altlinux.org/FindLangPolicy for details.; 
icon-theme-Colloid-20230108-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.; 
icon-theme-Colloid-dark-20230108-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.; 
icon-theme-Colloid-green-20230108-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.; 
icon-theme-Colloid-green-dark-20230108-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.; 
icon-theme-Colloid-green-light-20230108-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.; 
icon-theme-Colloid-grey-20230108-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.; 
icon-theme-Colloid-grey-dark-20230108-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.; 
icon-theme-Colloid-grey-light-20230108-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.; 
icon-theme-Colloid-light-20230108-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.; 
icon-theme-Colloid-orange-20230108-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.; 
icon-theme-Colloid-orange-dark-20230108-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.; 
icon-theme-Colloid-orange-light-20230108-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.; 
icon-theme-Colloid-pink-20230108-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.; 
icon-theme-Colloid-pink-dark-20230108-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.; 
icon-theme-Colloid-pink-light-20230108-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.; 
icon-theme-Colloid-purple-20230108-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.; 
icon-theme-Colloid-purple-dark-20230108-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.; 
icon-theme-Colloid-purple-light-20230108-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.; 
icon-theme-Colloid-red-20230108-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.; 
icon-theme-Colloid-red-dark-20230108-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.; 
icon-theme-Colloid-red-light-20230108-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.; 
icon-theme-Colloid-teal-20230108-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.; 
icon-theme-Colloid-teal-dark-20230108-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.; 
icon-theme-Colloid-teal-light-20230108-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.; 
icon-theme-Colloid-yellow-20230108-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.; 
icon-theme-Colloid-yellow-dark-20230108-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.; 
icon-theme-Colloid-yellow-light-20230108-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.; 
icon-theme-Sevi-20230324-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.; 
icon-theme-Sevi-black-20230324-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.; 
icon-theme-Sevi-black-dark-20230324-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.; 
icon-theme-Sevi-blue-20230324-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.; 
icon-theme-Sevi-blue-dark-20230324-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.; 
icon-theme-Sevi-brown-20230324-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.; 
icon-theme-Sevi-brown-dark-20230324-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.; 
icon-theme-Sevi-dark-20230324-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.; 
icon-theme-Sevi-green-20230324-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.; 
icon-theme-Sevi-green-dark-20230324-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.; 
icon-theme-Sevi-grey-20230324-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.; 
icon-theme-Sevi-grey-dark-20230324-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.; 
icon-theme-Sevi-orange-20230324-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.; 
icon-theme-Sevi-orange-dark-20230324-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.; 
icon-theme-Sevi-pink-20230324-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.; 
icon-theme-Sevi-pink-dark-20230324-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.; 
icon-theme-Sevi-purple-20230324-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.; 
icon-theme-Sevi-purple-dark-20230324-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.; 
icon-theme-Sevi-red-20230324-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.; 
icon-theme-Sevi-red-dark-20230324-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.; 
icon-theme-Tela-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-black-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-black-dark-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-blue-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-blue-dark-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-brown-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-brown-dark-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-dark-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-dracula-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-dracula-dark-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-green-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-green-dark-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-grey-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-grey-dark-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-manjaro-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-manjaro-dark-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-nord-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-nord-dark-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-orange-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-orange-dark-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-pink-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-pink-dark-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-purple-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-purple-dark-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-red-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-red-dark-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-ubuntu-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-ubuntu-dark-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-yellow-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Tela-yellow-dark-20230203-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
icon-theme-Zafiro-icons-Dark-1.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.; 
icon-theme-Zafiro-icons-Light-1.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.; 
icon-theme-kora-1.5.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.; 
icon-theme-kora-light-1.5.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.; 
icon-theme-kora-light-panel-1.5.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.; 
icon-theme-kora-pgrey-1.5.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.; 
kde-cdemu-manager-0.8.0-alt1.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/kf5/applications/kf5/org.kde.kde_cdemu.desktop: warning: key "Encoding" in group "Desktop Entry" is deprecated; 
kronos-2.7.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/kronos.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).; 
kronos-2.7.0-alt1.x86_64	iconsdir	experimental	Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.; 
latte-dock-0.10.9-alt3.x86_64	dbus-xml-not-in-devel	info	file /usr/share/dbus-1/interfaces/org.kde.LatteDock.xml is not used in run time. Move it to the <name>-devel subpackage.; 
latte-dock-0.10.9-alt3.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.kde.latte-dock.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).; 
lazy_ips-20200706-alt2.noarch	iconsdir	experimental	Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.; 
libchdr-devel-0.1-alt1.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libchdr.so but just /usr/lib64/libchdr.so.0.2. According to SharedLibs Policy Draft, symlink /usr/lib64/libchdr.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/libchdr.so to \%files of libchdr-devel-0.1-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.; 
libogre-next-devel-2.3.3-alt5.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.; 
libzmusiclite-1.1.14-alt1.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libzmusiclite.so but just /usr/lib64/libzmusiclite.so.1.1.14. According to SharedLibs Policy Draft, symlink /usr/lib64/libzmusiclite.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/libzmusiclite.so to \%files of libzmusiclite-1.1.14-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.; 
livecd-attract-0.1-alt2.noarch	rpm-filesystem-conflict-file-file	warn	File /etc/sysconfig/livecd-runapp conflicts with the package livecd-fgfs-0.2-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
lzdoom-4.11.4-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.; 
mame-data-0.280-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.; 
mame-data-software-lists-0.280-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.; 
mate-dock-applet-21.10.0-alt1.1.noarch	altlinux-find-lang-mo	warn	Language specific files in /usr/share/locale should be marked, for example, using %find_lang. See http://www.altlinux.org/FindLangPolicy for details.; 
neard-0.19-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/neard-0.19-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/99-neard.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
ogre-next-2.3.3-alt5.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.; 
ogre-next-2.3.3-alt5.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.; ; 
openfodder-data-1.8.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.; 
openmsx-21.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.; 
opensd-0.48.0-alt1.1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/opensd-0.48.0-alt1.1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/60-opensd.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
panzerchasm-0.3-alt3.x86_64	freedesktop-categories	fail	Main Categories consist of those categories that every conforming desktop environment MUST support.(http://standards.freedesktop.org/menu-spec/latest/apa.html). None found in /usr/share/applications/panzerchasm.desktop. please, fix. Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/panzerchasm.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).; 
panzerchasm-0.3-alt3.x86_64	freedesktop-desktop	warn	desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/panzerchasm.desktop: error: value "Games/Arcade;" for key "Categories" in group "Desktop Entry" contains an unregistered value "Games/Arcade"; values extending the format should start with "X-"; /usr/share/applications/panzerchasm.desktop: hint: value "Games/Arcade;" for key "Categories" in group "Desktop Entry" does not contain a registered main category; application might only show up in a "catch-all" section of the application menu; 
pdfshuffler-0.7.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/pdfshuffler.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).; 
picodrive-1.99-alt2.x86_64	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/picodrive.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).; 
picodrive-1.99-alt2.x86_64	iconsdir	experimental	Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.; 
pipe-viewer-0.5.3-alt1.1.noarch	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/gtk-pipe-viewer.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).; 
plymouth-theme-altemu-1.0-alt1.noarch	missing-url	info	Missing Url: in a package.; 
polkit-rule-allow-timedatectl-1.0-alt1.noarch	missing-url	info	Missing Url: in a package.; 
qchdman-0.243.14-alt1.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/qchdman.desktop: warning: value "Qt CHDMAN GUI" for key "Comment" in group "Desktop Entry" looks the same as that of key "GenericName"; 
qjoypad-qt5-4.3.1-alt2.x86_64	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/qjoypad.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).; 
qmc2-0.243.14-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.; 
qmc2-arcade-0.243.14-alt1.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/qmc2-arcade.desktop: warning: value "QMC2 Arcade Mode" for key "Comment" in group "Desktop Entry" looks the same as that of key "GenericName"; 
rakarrack-plus-data-1.2.4-alt1.noarch	iconsdir	experimental	Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.; 
raze-1.10.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.; 
relive-1.0.9-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/relive-ae.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).; 
relive-1.0.9-alt1.x86_64	iconsdir	experimental	Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.; 
retroarch-1.21.0-alt4.x86_64	iconsdir	experimental	Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.; 
roadfighter-1.0.1269-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.; 
roadfighter-1.0.1269-alt1.x86_64	iconsdir	experimental	Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.; 
rpcemu-0.9.4-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.; ; 
russian-doom-7.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.; 
russian-hexen-7.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.; 
sc-controller-0.4.8.11-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.; 
sc-controller-0.4.8.11-alt1.x86_64	iconsdir	experimental	Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.; 
sc-controller-0.4.8.11-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/bin/scc conflicts with the package scc-3.5.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.; 
sdl2-gamepad-mapper-0.0.9-alt1.git2c7a017.x86_64	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/sdl2-gamepad-mapper.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).; 
simutrans-123.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.; 
speed-dreams-2.3.0-alt1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib64/libtgfclient.so is different from the same symlink in the package TORCS-1.3.7-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.; ; 
speed-dreams-data-2.3.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.; 
speed-dreams-debuginfo-2.3.0-alt1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libtgfclient.so.debug is different from the same symlink in the package TORCS-debuginfo-1.3.7-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.; ; 
srb2-data-2.2.13-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.; 
srb2kart-1.6-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.; 
srb2kart-data-1.6-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.; 
stella-6.7.0-alt1.x86_64	altlinux-policy-debian-menu-is-deprecated	warn	package contains deprecated /usr/lib/menu/ files. Please, convert to .desktop files; 
supermodel-0.3a-alt1.git4e7356a.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.; 
surgescript-0.5.6.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; 
sway-autostart-0.2-alt1.noarch	missing-url	info	Missing Url: in a package.; 
systemd-powerbutton-off-1.0-alt1.noarch	missing-url	info	Missing Url: in a package.; 
tsugaru-tests-20241003-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.; 
tsugaru-tests-20241003-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/bin/wildcard conflicts with the package wildcard-0.3.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.; 
tvheadend-4.2.8-alt6.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.; 
tvheadend-4.2.8-alt6.x86_64	init-lsb	warn	/etc/rc.d/init.d/tvheadend: lsb init header missing.  See http://www.altlinux.org/Services_Policy for details.; 
udev-rules-MIG-goodix-touchpad-1.0-alt1.noarch	missing-url	info	Missing Url: in a package.; 
udev-rules-MIG-goodix-touchpad-1.0-alt1.noarch	rpm-package-is-obsoleted	warn	The package is  obsoleted by the package udev-rules-goodix-touchscreen-4-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 udev-rules-goodix-touchscreen-4-alt1.x86_64 to remove Obsoletes: tag.; 
udev-rules-MIG-goodix-touchpad-1.0-alt1.noarch	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/noarch/RPMS/udev-rules-MIG-goodix-touchpad-1.0-alt1.noarch.rpm: invalid udev rules path: /usr/lib/udev/rules.d/99-goodix-MIG-touchscreen.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
udev-rules-brightness-user-control-1.0-alt1.noarch	missing-url	info	Missing Url: in a package.; 
udev-rules-brightness-user-control-1.0-alt1.noarch	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/noarch/RPMS/udev-rules-brightness-user-control-1.0-alt1.noarch.rpm: invalid udev rules path: /usr/lib/udev/rules.d/90-udev-rules-brightness-user-control.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
udev-rules-da280-accelerometer-1.0-alt1.noarch	missing-url	info	Missing Url: in a package.; 
udev-rules-da280-accelerometer-1.0-alt1.noarch	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/noarch/RPMS/udev-rules-da280-accelerometer-1.0-alt1.noarch.rpm: invalid udev rules path: /usr/lib/udev/rules.d/99-da280-accelerometer.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
udev-rules-goodix-touchscreen-4-alt1.x86_64	missing-url	info	Missing Url: in a package.; 
udev-rules-goodix-touchscreen-4-alt1.x86_64	rpm-obsolete-live-package	info	The package obsoletes the package udev-rules-MIG-goodix-touchpad-1.0-alt1.noarch, but the package udev-rules-MIG-goodix-touchpad-1.0-alt1.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.; 
udev-rules-goodix-touchscreen-4-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
udev-rules-retroid-gamepad-1.0-alt1.noarch	missing-url	info	Missing Url: in a package.; 
udev-rules-retroid-gamepad-1.0-alt1.noarch	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/noarch/RPMS/udev-rules-retroid-gamepad-1.0-alt1.noarch.rpm: invalid udev rules path: /usr/lib/udev/rules.d/99-udev-rules-retroid-gamepad.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
udev-rules-sway-touchscreen-name-1.0-alt1.noarch	missing-url	info	Missing Url: in a package.; 
udev-rules-sway-touchscreen-name-1.0-alt1.noarch	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/noarch/RPMS/udev-rules-sway-touchscreen-name-1.0-alt1.noarch.rpm: invalid udev rules path: /usr/lib/udev/rules.d/90-rules-sway-touchscreen-name.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
vde2-2.3.3-alt1.x86_64	init-but-no-native-systemd	info	The package have SysV init script(s) but no native systemd files.; 
vde2-2.3.3-alt1.x86_64	init-lsb	fail	/etc/rc.d/init.d/vde2: not systemd compatible: lsb init header missing and vde2.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
vde2-2.3.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.; 
wf-recorder-0.5.0-alt1.x86_64	freedesktop-desktop	warn	desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/wf-recorder-start.desktop: error: value "wf_record.sh &" for key "Exec" in group "Desktop Entry" contains a reserved character '&' outside of a quote; /usr/share/applications/wf-recorder-start.desktop: error: (will be fatal in the future): value item "Video" in key "Categories" in group "Desktop Entry" requires another category to be present among the following categories: AudioVideo; /usr/share/applications/wf-recorder-start.desktop: error: value "Phosh;" for key "OnlyShowIn" in group "Desktop Entry" contains an unregistered value "Phosh"; values extending the format should start with "X-"; 
wondershaper-1.4.1-alt1.noarch	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
wrath-rev20140513-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/wrath.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).; 
wrath-rev20140513-alt1.x86_64	freedesktop-desktop	warn	desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/wrath.desktop: error: value "Game;ArcadeGames;" for key "Categories" in group "Desktop Entry" contains an unregistered value "ArcadeGames"; values extending the format should start with "X-"; 
wrath-rev20140513-alt1.x86_64	iconsdir	experimental	Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.; 
x-cursor-theme-Colloid-cursors-20230108-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.; 
x-cursor-theme-Colloid-dark-cursors-20230108-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.; 
x16-emulator-r46-alt1.x86_64	freedesktop-categories	fail	Main Categories consist of those categories that every conforming desktop environment MUST support.(http://standards.freedesktop.org/menu-spec/latest/apa.html). None found in /usr/share/applications/x16-emulator.desktop. please, fix.; 
x16-emulator-r46-alt1.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/x16-emulator.desktop: hint: value item "Emulator" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: System, or Game; /usr/share/applications/x16-emulator.desktop: hint: value "Emulator;" for key "Categories" in group "Desktop Entry" does not contain a registered main category; application might only show up in a "catch-all" section of the application menu; 
xnp21kai-rev.22-alt1.git4b109ea.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/xnp21kai.desktop: warning: value "PC-9801 Emulator" for key "Comment" in group "Desktop Entry" looks the same as that of key "GenericName"; /usr/share/applications/xnp21kai.desktop: warning: value "PC-9801??????" for key "Comment[ja]" in group "Desktop Entry" looks the same as that of key "GenericName[ja]"; 
xroar-1.5.5-alt2.x86_64	freedesktop-categories	fail	Main Categories consist of those categories that every conforming desktop environment MUST support.(http://standards.freedesktop.org/menu-spec/latest/apa.html). None found in /usr/share/applications/xroar.desktop. please, fix.; 
xroar-1.5.5-alt2.x86_64	freedesktop-desktop	warn	desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/xroar.desktop: error: value "Games;Emulator;" for key "Categories" in group "Desktop Entry" contains an unregistered value "Games"; values extending the format should start with "X-"; /usr/share/applications/xroar.desktop: hint: value item "Emulator" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: System, or Game; /usr/share/applications/xroar.desktop: hint: value "Games;Emulator;" for key "Categories" in group "Desktop Entry" does not contain a registered main category; application might only show up in a "catch-all" section of the application menu; 
zennode-1.2.1-alt1.1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/bin/compare conflicts with the package schilytools-2024.03.21-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.; 
