cas	1c-preinstall-full-8.3-alt11.noarch	requires-microsoft-fonts-ttf	warn	Free Software packages should not require @ fonts! But dependency on fonts-ttf-ms is found.; 
cas	aceproxy-0.6-alt1.src	specfile-python2-in-spec	warn	spec file explicitly calls /usr/bin/python. It is deprecated binary. Use /usr/bin/python2.; 
cas	alt-test-1.1.4-alt1.noarch	checkbashisms	experimental	checkbashisms utility found possible bashisms in: /usr/bin/alt-test-functions; 
cas	alterator-mass-management-0.1.7-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/alterator/backend3/mass-management: $ grep -A5 -B5 /tmp/ /usr/lib/alterator/backend3/mass-management mkdir -p "$TASKS_DIR/task-$number" cat >"$TASKS_DIR/task-$number.yml" <<EOF --- - hosts: $group pre_tasks: - file: path=/tmp/amm-task-{{ task }}.{{ try }} state=directory roles: - $profile post_tasks: - file: path=/tmp/amm-task-{{ task }}.{{ try }} state=absent EOF return 0 } -- ### on_message() { date >> /tmp/mode.log echo "$(set|grep -a "in_")" >> /tmp/mode.log case "$in_action" in type) write_type_item hostlist hostname-list #write_type_item add_host hostname ;;; 
cas	altlinux-repos-0.5-alt1.noarch	missing-url	info	Missing Url: in a package.; 
cas	apf-0.1-alt1.noarch	missing-url	info	Missing Url: in a package.; 
cas	apf-update-0.1-alt1.noarch	missing-url	info	Missing Url: in a package.; 
cas	autologin-sh-functions-0.2.1-alt1.noarch	checkbashisms	experimental	checkbashisms utility found possible bashisms in: /usr/bin/autologin-sh-functions; 
cas	caffeine-2.8.2-alt1.M70P.1.noarch	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/caffeine.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).; 
cas	chef-12.4.1-alt1.src	unmet-dependency-build-missing-package	fail	build dependency ruby-ucf not found.; 
cas	chef-doc-12.4.1-alt1.noarch	rpm-filesystem-conflict-file-file	warn	Files /usr/share/ri/site/Chef/cdesc-Chef.ri /usr/share/ri/site/Mash/cdesc-Mash.ri conflict with the package ohai-doc-8.0.1-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.; There are file conflicts with the package ruby-chef-sugar-doc-3.1.0-alt1.noarch, for example, /usr/share/ri/site/Chef/Node/cdesc-Node.ri (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.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-cleanroom-doc-1.0.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.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.2-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.; Files /usr/share/ri/site/FFI/Pointer/cdesc-Pointer.ri /usr/share/ri/site/FFI/cdesc-FFI.ri conflict with the package ruby-ffi-doc-1.9.6-alt0.M70P.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.; There are file conflicts with the package ruby-ffi-yajl-doc-1.3.1-alt0.M70P.1.noarch, for example, /usr/share/ri/site/FalseClass/cdesc-FalseClass.ri (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.; File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package ruby-json-pure-doc-1.8.1-alt0.M70P.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.; Files /usr/share/ri/site/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package ruby-mechanize-doc-0.9.3-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.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-dhcp-doc-1.3.2-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.; File /usr/share/ri/site/Net/SSH/cdesc-SSH.ri conflicts with the package ruby-net-ssh-doc-2.0.15-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.; There are file conflicts with the package ruby-net-ssh-multi-doc-1.2.0-alt1.noarch, for example, /usr/share/ri/site/Net/SSH/Multi/Server/busy%3f-i.ri (7 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.; Files /usr/share/ri/site/RSpec/Core/cdesc-Core.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-core-doc-3.2.3-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.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-mocks-doc-3.2.1-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.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-support-doc-3.2.2-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.; 
cas	conky-manager-2.3.4-alt0.M70T.1.x86_64	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/conky-manager.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).; 
cas	conky-manager-2.3.4-alt0.M70T.1.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.; 
cas	cqrlog-1.9.0-alt2.M70P.1.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.; 
cas	cqrlog-1.9.0-alt2.M70P.1.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/cqrlog.desktop: hint: value item "Database" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: Office, or Development, or AudioVideo; /usr/share/applications/cqrlog.desktop: hint: value item "HamRadio" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: Network, or Audio; /usr/share/applications/cqrlog.desktop: hint: value "Utility;Database;HamRadio;Education;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; 
cas	cqrlog-1.9.0-alt2.M70P.1.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.; 
cas	cura-15.04.4-alt1.M70P.1.noarch	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/cura.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).; 
cas	cura-15.04.4-alt1.M70P.1.noarch	symlink-extra-slash	info	/usr/share/cura/locale:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.; 
cas	docky-2.2.0-alt1.M70P.1.x86_64	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/docky.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).; 
cas	erubis-doc-2.7.0-alt1.noarch	rpm-filesystem-conflict-file-file	warn	Files /usr/share/ri/site/ActionController/cdesc-ActionController.ri /usr/share/ri/site/ActionView/TemplateHandlers/cdesc-TemplateHandlers.ri /usr/share/ri/site/ActionView/cdesc-ActionView.ri conflict with the package ruby-actionpack-doc-2.3.11-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.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-em-synchrony-doc-1.0.4-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.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-ffi-yajl-doc-1.3.1-alt0.M70P.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.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-json-pure-doc-1.8.1-alt0.M70P.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.; 
cas	freebasic-1.05.0-alt0.M70P.1.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.; 
cas	gambit-dsock-1.1-alt1.x86_64	missing-url	info	Missing Url: in a package.; 
cas	gambit-dsock-debuginfo-1.1-alt1.x86_64	missing-url	info	Missing Url: in a package.; 
cas	gambit-dsock-devel-1.1-alt1.noarch	missing-url	info	Missing Url: in a package.; 
cas	golang-1.3-alt0.M70P.1.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.; 
cas	golang-vim-1.3-alt0.M70P.1.noarch	sisyphus_check-check-dirlist	warn	sisyphus_check --check-dirlist failed: package contains a directory /usr/share/vim/vimfiles/autoload that exclusively belongs to package vim-common; sisyphus_check --check-dirlist failed: package contains a directory /usr/share/vim/vimfiles/compiler that exclusively belongs to package vim-common; sisyphus_check --check-dirlist failed: package contains a directory /usr/share/vim/vimfiles/ftdetect that exclusively belongs to package vim-common; sisyphus_check --check-dirlist failed: package contains a directory /usr/share/vim/vimfiles/ftplugin that exclusively belongs to package vim-common; sisyphus_check --check-dirlist failed: package contains a directory /usr/share/vim/vimfiles/indent that exclusively belongs to package vim-common; sisyphus_check --check-dirlist failed: package contains a directory /usr/share/vim/vimfiles/plugin that exclusively belongs to package vim-common; sisyphus_check --check-dirlist failed: package contains a directory /usr/share/vim/vimfiles/syntax that exclusively belongs to package vim-common; 
cas	gostcryptogui-0.3-alt0.2.a.git0c6d930.noarch	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/gost-crypto-gui.desktop: hint: value "Qt;HardwareSettings;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; 
cas	gostcryptogui-0.3-alt0.2.a.git0c6d930.noarch	iconsdir	experimental	Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.; 
cas	gostcryptogui-0.3-alt0.2.a.git0c6d930.src	specfile-python2-in-spec	warn	spec file explicitly calls /usr/bin/python. It is deprecated binary. Use /usr/bin/python2.; 
cas	gpointing-device-settings-1.5.1-alt4.x86_64	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/gpointing-device-settings.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).; 
cas	gpointing-device-settings-1.5.1-alt4.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/gpointing-device-settings.desktop: hint: value item "GNOME" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: GTK; 
cas	gpointing-device-settings-1.5.1-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.; 
cas	gpointing-device-settings-1.5.1-alt4.x86_64	rpm-obsolete-live-package	info	The package obsoletes the package gsynaptics-0.9.16-alt3.qa1.x86_64, but the package gsynaptics-0.9.16-alt3.qa1.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.; 
cas	grub-customizer-4.0.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/grub-customizer.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).; 
cas	grub-customizer-4.0.4-alt2.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/grub-customizer.desktop: hint: value "System;Settings;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; 
cas	haspd-7.40-alt4.0.M70P.1.src	unmet-dependency-build-missing-package	fail	build dependency ld-linux.so.2 not found.; build dependency libpthread.so.0 not found.; 
cas	hedgewars-0.9.20.5-alt0.M70P.1.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libhwphysfs.so but just /usr/lib64/libhwphysfs.so.2.1.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libhwphysfs.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/libhwphysfs.so to \%files of hedgewars-0.9.20.5-alt0.M70P.1.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.; 
cas	im-chooser-1.6.4-alt1.M70P.1.x86_64	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/im-chooser.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).; 
cas	im-chooser-1.6.4-alt1.M70P.1.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/im-chooser.desktop: warning: value "Applications;Settings;X-GNOME-PersonalSettings;" for key "Categories" in group "Desktop Entry" contains a deprecated value "Applications"; 
cas	im-chooser-common-1.6.4-alt1.M70P.1.x86_64	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
cas	imagewriter-1.10-alt3.M70P.1.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/imagewriter.desktop: hint: value "System;Utility;Archiving;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; 
cas	imsettings-1.6.7-alt1.M70P.1.x86_64	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
cas	imsettings-cinnamon-1.6.7-alt1.M70P.1.x86_64	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
cas	imsettings-devel-1.6.7-alt1.M70P.1.x86_64	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
cas	imsettings-gsettings-1.6.7-alt1.M70P.1.x86_64	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
cas	imsettings-libs-1.6.7-alt1.M70P.1.x86_64	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
cas	imsettings-libs-1.6.7-alt1.M70P.1.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; 
cas	imsettings-lxde-1.6.7-alt1.M70P.1.x86_64	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
cas	imsettings-mate-1.6.7-alt1.M70P.1.x86_64	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
cas	imsettings-qt-1.6.7-alt1.M70P.1.x86_64	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
cas	imsettings-xfce-1.6.7-alt1.M70P.1.x86_64	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
cas	imsettings-xim-1.6.7-alt1.M70P.1.x86_64	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
cas	installer-distro-school-server-stage2-7.0-alt9.noarch	rpm-filesystem-conflict-file-file	warn	Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list conflict with the package installer-distro-altlinux-desktop-stage2-7.0.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.; 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-altlinux-generic-stage2-7.0.3-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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list conflict with the package installer-distro-altlinux-server-stage2-7.0.2-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.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/20-alterator-menu.sh conflict with the package installer-distro-backup-server-stage2-6.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.; There are file conflicts with the package installer-distro-centaurus-stage2-7.0-alt7.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; There are file conflicts with the package installer-distro-chainmail-stage2-3.0.0-alt8.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (7 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.; There are file conflicts with the package installer-distro-desktop-stage2-5.0-alt23.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; There are file conflicts with the package installer-distro-junior-stage2-7.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; There are file conflicts with the package installer-distro-lxdesktop-stage2-6.0-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; There are file conflicts with the package installer-distro-office-server-stage2-5.0-alt28.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; There are file conflicts with the package installer-distro-server-light-stage2-6.0-alt3.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; There are file conflicts with the package installer-distro-simply-linux-stage2-7.0-alt12.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; There are file conflicts with the package installer-distro-tablet-stage2-6.0-alt3.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; There are file conflicts with the package installer-distro-workbench-stage2-5.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; Files /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-office-desktop-stage2-5.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-server-lite-stage2-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.; Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-server-stage2-0.2-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.; 
cas	jitsi-2.8.5426-alt0.M70P.1.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.; 
cas	kbibtex-0.4.1-alt0.M70P.1.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/kde4/kbibtex.desktop: hint: value "Qt;KDE;Office;Database;Science;Literature;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; 
cas	kernel-source-3.14-1.0.0-alt1.noarch	missing-url	info	Missing Url: in a package.; 
cas	kile-2.1.3-alt0.M70P.1.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.; 
cas	kile-2.1.3-alt0.M70P.1.x86_64	dbus-xml-not-in-devel	info	file /usr/share/dbus-1/interfaces/net.sourceforge.kile.main.xml is not used in run time. Move it to the <name>-devel subpackage.; 
cas	kile-2.1.3-alt0.M70P.1.x86_64	rpm-obsolete-live-package	info	The package obsoletes the package kde4-kile-2.1b4-alt1.x86_64, but the package kde4-kile-2.1b4-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.; 
cas	ktechlab-0.3.7-alt1.M70P.1.20090304.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/ktechlab.desktop: warning: value "kde3 ktechlab %i %m -caption "%c"" for key "Exec" in group "Desktop Entry" contains a deprecated field code "%m"; /usr/share/applications/ktechlab.desktop: hint: value "Qt;KDE;Education;Science;Electronics;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; 
cas	libQt4Pas5-2.5-alt0.M70P.1.x86_64	missing-url	info	Missing Url: in a package.; 
cas	libQt4Pas5-debuginfo-2.5-alt0.M70P.1.x86_64	missing-url	info	Missing Url: in a package.; 
cas	libQt4Pas5-devel-2.5-alt0.M70P.1.x86_64	missing-url	info	Missing Url: in a package.; 
cas	libappindicator-12.10.0-alt2.M70P.1.src	altlinux-python-obsolete-buildreq-python-dev	warn	python-dev is obsolete according to Python Policy (http://www.altlinux.org/Python_Policy). Please, use BuildRequires: python-devel.; 
cas	libcg-3.1_April2012-alt1.x86_64	vendor-tag	warn	Bad Vendor: tag in a package.; 
cas	libcg-devel-3.1_April2012-alt1.noarch	vendor-tag	warn	Bad Vendor: tag in a package.; 
cas	libcggl-3.1_April2012-alt1.x86_64	vendor-tag	warn	Bad Vendor: tag in a package.; 
cas	libcggl-devel-3.1_April2012-alt1.noarch	vendor-tag	warn	Bad Vendor: tag in a package.; 
cas	libcwiid-utils-0.6.00-alt2.20100505gitfadf11e.x86_64	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/wmgui.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).; 
cas	libcwiid-utils-0.6.00-alt2.20100505gitfadf11e.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/wmgui.desktop: hint: value "GTK;Utility;System;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; 
cas	libgnomeprint-2.18.8-alt3.M70P.1.x86_64	missing-url	info	Missing Url: in a package.; 
cas	libgnomeprint-debuginfo-2.18.8-alt3.M70P.1.x86_64	missing-url	info	Missing Url: in a package.; 
cas	libgnomeprint-devel-2.18.8-alt3.M70P.1.x86_64	missing-url	info	Missing Url: in a package.; 
cas	libgnomeprint-devel-doc-2.18.8-alt3.M70P.1.noarch	missing-url	info	Missing Url: in a package.; 
cas	libgnomeprintui-2.18.6-alt1.M70P.1.x86_64	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
cas	libmbedtls-devel-1.3.10-alt1.M70P.1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package libpolarssl-devel-1.3.9-alt0.M70P.1.x86_64, for example, /usr/include/polarssl/aes.h (65 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.; 
cas	libpolarssl-devel-1.3.9-alt0.M70P.1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package libmbedtls-devel-1.3.10-alt1.M70P.1.x86_64, for example, /usr/include/polarssl/aes.h (65 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.; 
cas	libuthash-devel-1.9.8-alt0.M70P.1.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/include/uthash.h conflicts with the package libtorque-devel-4.2.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.; 
cas	libwbclient-DC-4.5.12-alt1.M70P.1.x86_64	alt-alternatives-vs-ghost	info	Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0.13 is an alternative in package libwbclient-4.5.12-alt1.M70P.1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.13.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-4.5.12-alt1.M70P.1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0.13 is an alternative in package libwbclient-DC-4.5.12-alt1.M70P.1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.13.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-DC-4.5.12-alt1.M70P.1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-sssd-1.14.2-alt0.M70P.1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.; 
cas	libwbclient-DC-debuginfo-4.5.12-alt1.M70P.1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.13.debug is different from the same symlink in the package libwbclient-debuginfo-4.5.12-alt1.M70P.1.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.; value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-debuginfo-4.5.12-alt1.M70P.1.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.; value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-sssd-debuginfo-1.14.2-alt0.M70P.1.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.; 
cas	libwbclient-DC-devel-4.5.12-alt1.M70P.1.x86_64	alt-alternatives-vs-ghost	info	Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-DC-devel-4.5.12-alt1.M70P.1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-devel-4.5.12-alt1.M70P.1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-sssd-devel-1.14.2-alt0.M70P.1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.; 
cas	logisim-2.7.1-alt1.noarch	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/logisim.desktop: hint: value "Education;Science;ComputerScience;Java;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; 
cas	logisim-2.7.1-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.; 
cas	luckybackup-0.4.8-alt1.M70P.1.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.; 
cas	luckybackup-0.4.8-alt1.M70P.1.x86_64	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/luckybackup.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).; Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/luckybackup-gnome-su.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).; 
cas	luckybackup-0.4.8-alt1.M70P.1.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.; 
cas	luma-3.0.7-alt1.noarch	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/luma.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).; 
cas	luma-3.0.7-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.; 
cas	minetest-0.4.11-alt0.M70P.1.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.; 
cas	minetest-0.4.11-alt0.M70P.1.x86_64	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/minetest.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).; 
cas	minetest-server-0.4.11-alt0.M70P.1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.; 
cas	minidlna-1.1.4-alt0.M70P.1.x86_64	init-lsb	warn	/etc/rc.d/init.d/minidlna: lsb init header missing.  See http://www.altlinux.org/Services_Policy for details.; 
cas	minidlna-1.1.4-alt0.M70P.1.x86_64	subdir-in-var-run	info	Found a subdir in /var/run or /var/lock. /var/run and /var/lock may be mounted as temporary filesystems, so the init.d scripts must handle this correctly. This will typically amount to creating any required subdirectories dynamically when the init.d script is run, rather than including them in the package and relying on rpm to create them.; 
cas	modem-manager-gui-0.0.18-alt0.M70P.1.x86_64	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/modem-manager-gui.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).; 
cas	modem-manager-gui-0.0.18-alt0.M70P.1.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.; 
cas	mono4-core-4.3.1.1-alt5.M70P.1.x86_64	bin-permissions	info	not executable file /usr/bin/mono-gdb.py; not executable file /usr/bin/mono-sgen-gdb.py; 
cas	mono4-core-4.3.1.1-alt5.M70P.1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/bin/mono-sgen-gdb.py conflicts with the package libmonosgen-devel-2.10.11-alt3.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.; Files /usr/lib/mono/gac/Mono.CSharp/4.0.0.0__0738eb9f132ed756/Mono.CSharp.dll /usr/lib/mono/gac/Mono.CSharp/4.0.0.0__0738eb9f132ed756/Mono.CSharp.dll.mdb /usr/share/man/man1/csharp.1.gz conflict with the package mono-csharp-2.10.11-alt3.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.; There are file conflicts with the package mono-devel-2.10.11-alt3.x86_64, for example, /usr/bin/mono-gdb.py (15 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.; There are file conflicts with the package mono-mcs-2.10.11-alt3.x86_64, for example, /usr/bin/dmcs (7 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.; Files /usr/lib/mono/gac/System.Runtime.DurableInstancing/4.0.0.0__31bf3856ad364e35/System.Runtime.DurableInstancing.dll /usr/lib/mono/gac/System.Runtime.DurableInstancing/4.0.0.0__31bf3856ad364e35/System.Runtime.DurableInstancing.dll.mdb conflict with the package mono-wcf-2.10.11-alt3.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.; Files /usr/lib/mono/gac/System.ComponentModel.Composition/4.0.0.0__b77a5c561934e089/System.ComponentModel.Composition.dll /usr/lib/mono/gac/System.ComponentModel.Composition/4.0.0.0__b77a5c561934e089/System.ComponentModel.Composition.dll.mdb conflict with the package mono-web-2.10.11-alt3.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.; 
cas	mono4-core-4.3.1.1-alt5.M70P.1.x86_64	uncompressed-manpages	info	Package contains uncompressed manual pages.; 
cas	mono4-core-debuginfo-4.3.1.1-alt5.M70P.1.x86_64	rpm-filesystem-conflict-symlink-file	warn	symlink /usr/lib/debug/usr/bin/mono.debug is a file in the package mono-debuginfo-2.10.11-alt3.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.; symlink /usr/lib/debug/usr/lib64/libmono-2.0.so.1.0.0.debug is a file in the package libmono-debuginfo-2.10.11-alt3.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.; 
cas	mono4-core-debuginfo-4.3.1.1-alt5.M70P.1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libmono-2.0.so.1.debug is different from the same symlink in the package libmono-debuginfo-2.10.11-alt3.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.; 
cas	mono4-data-4.3.1.1-alt5.M70P.1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib/mono/gac/System.Transactions/4.0.0.0__b77a5c561934e089/System.Transactions.dll /usr/lib/mono/gac/System.Transactions/4.0.0.0__b77a5c561934e089/System.Transactions.dll.mdb conflict with the package mono-2.10.11-alt3.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.; There are file conflicts with the package mono-data-2.10.11-alt3.x86_64, for example, /usr/lib/mono/gac/Mono.Data.Tds/4.0.0.0__0738eb9f132ed756/Mono.Data.Tds.dll (19 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.; There are file conflicts with the package mono-wcf-2.10.11-alt3.x86_64, for example, /usr/lib/mono/gac/System.Data.Services/4.0.0.0__b77a5c561934e089/System.Data.Services.dll (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.; 
cas	mono4-data-oracle-4.3.1.1-alt5.M70P.1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib/mono/gac/System.Data.OracleClient/4.0.0.0__b77a5c561934e089/System.Data.OracleClient.dll /usr/lib/mono/gac/System.Data.OracleClient/4.0.0.0__b77a5c561934e089/System.Data.OracleClient.dll.mdb conflict with the package mono-data-oracle-2.10.11-alt3.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.; 
cas	mono4-data-sqlite-4.3.1.1-alt5.M70P.1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib/mono/gac/Mono.Data.Sqlite/4.0.0.0__0738eb9f132ed756/Mono.Data.Sqlite.dll /usr/lib/mono/gac/Mono.Data.Sqlite/4.0.0.0__0738eb9f132ed756/Mono.Data.Sqlite.dll.mdb conflict with the package mono-data-sqlite-2.10.11-alt3.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.; 
cas	mono4-devel-4.3.1.1-alt5.M70P.1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package libmono-devel-2.10.11-alt3.x86_64, for example, /usr/include/mono-2.0/mono/cil/opcode.def (29 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.; File /usr/lib64/pkgconfig/monosgen-2.pc conflicts with the package libmonosgen-devel-2.10.11-alt3.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.; File /usr/lib64/libikvm-native.so conflicts with the package mono-2.10.11-alt3.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.; There are file conflicts with the package mono-devel-2.10.11-alt3.x86_64, for example, /usr/bin/pedump (27 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.; File /usr/share/man/man1/mono-xmltool.1.gz conflicts with the package mono-extras-2.10.11-alt3.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.; File /usr/lib64/pkgconfig/wcf.pc conflicts with the package mono-wcf-devel-2.10.11-alt3.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.; File /usr/bin/monodis conflicts with the package monodis-2.10.11-alt3.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.; 
cas	mono4-devel-4.3.1.1-alt5.M70P.1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib64/libmono-2.0.so is different from the same symlink in the package libmono-devel-2.10.11-alt3.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.; value of symlink /usr/lib64/libmonosgen-2.0.so is different from the same symlink in the package libmonosgen-devel-2.10.11-alt3.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.; 
cas	mono4-devel-4.3.1.1-alt5.M70P.1.x86_64	uncompressed-manpages	info	Package contains uncompressed manual pages.; 
cas	mono4-dyndata-4.3.1.1-alt5.M70P.1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib/mono/gac/System.Web.DynamicData/4.0.0.0__31bf3856ad364e35/System.Web.DynamicData.dll /usr/lib/mono/gac/System.Web.DynamicData/4.0.0.0__31bf3856ad364e35/System.Web.DynamicData.dll.mdb conflict with the package mono-mvc-2.10.11-alt3.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.; 
cas	mono4-extras-4.3.1.1-alt5.M70P.1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package mono-extras-2.10.11-alt3.x86_64, for example, /usr/lib/mono/gac/Mono.Messaging.RabbitMQ/4.0.0.0__0738eb9f132ed756/Mono.Messaging.RabbitMQ.dll (20 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.; 
cas	mono4-ibm-data-db2-4.3.1.1-alt5.M70P.1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib/mono/gac/IBM.Data.DB2/1.0.0.0__7c307b91aa13d208/IBM.Data.DB2.dll /usr/lib/mono/gac/IBM.Data.DB2/1.0.0.0__7c307b91aa13d208/IBM.Data.DB2.dll.mdb conflict with the package ibm-data-db2-2.10.11-alt3.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.; 
cas	mono4-locale-extras-4.3.1.1-alt5.M70P.1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package mono-2.10.11-alt3.x86_64, for example, /usr/lib/mono/gac/I18N.MidEast/4.0.0.0__0738eb9f132ed756/I18N.MidEast.dll (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.; Files /usr/lib/mono/gac/I18N.CJK/4.0.0.0__0738eb9f132ed756/I18N.CJK.dll /usr/lib/mono/gac/I18N.CJK/4.0.0.0__0738eb9f132ed756/I18N.CJK.dll.mdb conflict with the package mono-locale-extras-2.10.11-alt3.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.; 
cas	mono4-monodoc-4.3.1.1-alt5.M70P.1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package monodoc-2.10.11-alt3.x86_64, for example, /usr/lib/mono/gac/monodoc/1.0.0.0__0738eb9f132ed756/monodoc.dll (7 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.; 
cas	mono4-monodoc-devel-4.3.1.1-alt5.M70P.1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pkgconfig/monodoc.pc conflicts with the package monodoc-devel-2.10.11-alt3.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.; 
cas	mono4-mvc-4.3.1.1-alt5.M70P.1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package mono-mvc-2.10.11-alt3.x86_64, for example, /usr/lib/mono/gac/System.Web.Extensions.Design/4.0.0.0__31bf3856ad364e35/System.Web.Extensions.Design.dll (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.; 
cas	mono4-wcf-4.3.1.1-alt5.M70P.1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package mono-wcf-2.10.11-alt3.x86_64, for example, /usr/lib/mono/gac/System.IdentityModel.Selectors/4.0.0.0__b77a5c561934e089/System.IdentityModel.Selectors.dll (12 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.; 
cas	mono4-web-4.3.1.1-alt5.M70P.1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/share/man/man1/httpcfg.1.gz conflicts with the package mono-devel-2.10.11-alt3.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.; There are file conflicts with the package mono-web-2.10.11-alt3.x86_64, for example, /usr/lib/mono/gac/Microsoft.Web.Infrastructure/1.0.0.0__31bf3856ad364e35/Microsoft.Web.Infrastructure.dll (20 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.; 
cas	mono4-winforms-4.3.1.1-alt5.M70P.1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package mono-winforms-2.10.11-alt3.x86_64, for example, /usr/lib/mono/gac/Accessibility/4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll (10 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.; 
cas	mono4-winfx-4.3.1.1-alt5.M70P.1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib/mono/gac/WindowsBase/4.0.0.0__31bf3856ad364e35/WindowsBase.dll /usr/lib/mono/gac/WindowsBase/4.0.0.0__31bf3856ad364e35/WindowsBase.dll.mdb conflict with the package mono-winfxcore-2.10.11-alt3.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.; 
cas	ninja-ide-2.3-alt0.M70P.1.noarch	altlinux-python-test-is-packaged	experimental	/usr/lib/python2.7/site-packages/ninja_tests/core/examples/__init__.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples  or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/ninja_tests/core/examples/__init__.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples  or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/ninja_tests/core/examples/__init__.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples  or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/ninja_tests/core/examples/file_for_tests.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples  or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/ninja_tests/core/examples/file_for_tests.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples  or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/ninja_tests/core/examples/file_for_tests.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples  or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.; 
cas	ninja-ide-2.3-alt0.M70P.1.noarch	iconsdir	experimental	Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.; 
cas	nvidia-cg-toolkit-3.1_April2012-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.; 
cas	nvidia-cg-toolkit-3.1_April2012-alt1.x86_64	vendor-tag	warn	Bad Vendor: tag in a package.; 
cas	ohai-doc-8.0.1-alt1.noarch	rpm-filesystem-conflict-file-file	warn	Files /usr/share/ri/site/Chef/cdesc-Chef.ri /usr/share/ri/site/Mash/cdesc-Mash.ri conflict with the package chef-doc-12.4.1-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.; File /usr/share/ri/site/Chef/cdesc-Chef.ri conflicts with the package ruby-chef-sugar-doc-3.1.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.; File /usr/share/ri/site/Plist/cdesc-Plist.ri conflicts with the package ruby-plist-doc-3.0.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
cas	open-vm-tools-10.0.7-alt1.M70P.1.x86_64	checkbashisms	experimental	checkbashisms utility found possible bashisms in: /usr/bin/vm-support; 
cas	opencc-0.4.3-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.; 
cas	opencc-doc-0.4.3-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.; 
cas	pcsc-perl-1.4.13-alt0.M70P.1.x86_64	rpm-package-is-obsoleted	warn	The package is  obsoleted by the package perl-pcsc-1.4.14-alt1.M70P.2.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 perl-pcsc-1.4.14-alt1.M70P.2.x86_64 to remove Obsoletes: tag.; 
cas	pcsc-tools-gui-1.4.27-alt0.M70P.1.x86_64	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/gscriptor.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).; 
cas	pdfchain-0.4.4-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/pdfchain.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).; 
cas	perl-Gear-Remotes-0.009-alt1.noarch	altlinux-policy-description-has-tags	fail	Description contains tags such as Provides/Requires/BuildRequires. Beware of errors with %ifs/%endifs!; 
cas	perl-Gear-Remotes-0.009-alt1.noarch	altlinux-policy-description-too-much-space	info	Description has 3 empty lines in a row. Format description properly. Beware of errors with %ifs/%endifs.; 
cas	perl-Gear-Remotes-0.009-alt1.noarch	checkbashisms	experimental	checkbashisms utility found possible bashisms in: /usr/bin/gear-remotes-set-from-url; 
cas	plater-20131019-alt0.M70P.1.noarch	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/plater.desktop: hint: value "GNOME;GTK;Utility;Graphics;3DGraphics;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; 
cas	projectlibre-1.6.2-alt0.M70P.1.noarch	iconsdir	experimental	Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.; 
cas	pronsole-20131019-alt0.M70P.1.noarch	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/pronsole.desktop: hint: value "Utility;Graphics;3DGraphics;ConsoleOnly;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; 
cas	pronsole-20131019-alt0.M70P.1.noarch	iconsdir	experimental	Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.; 
cas	pronterface-20131019-alt0.M70P.1.noarch	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/pronterface.desktop: hint: value "GNOME;GTK;Utility;Graphics;3DGraphics;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; 
cas	pronterface-20131019-alt0.M70P.1.noarch	iconsdir	experimental	Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.; 
cas	pronterface-20131019-alt0.M70P.1.noarch	symlink-extra-slash	info	/usr/share/pronterface/locale:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.; 
cas	pspp-0.8.4-alt0.M70P.1.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/pspp.desktop: hint: value "GTK;Education;Science;Math;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; 
cas	python-module-PyQwt-devel-5.2.0-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.; 
cas	python-module-ioflo-1.0.2-alt0.M70P.1.src	altlinux-python-obsolete-buildreq-python-dev	warn	python-dev is obsolete according to Python Policy (http://www.altlinux.org/Python_Policy). Please, use BuildRequires: python-devel.; 
cas	python-module-junos-eznc-1.0.2-alt0.M70P.1.src	altlinux-python-obsolete-buildreq-python-dev	warn	python-dev is obsolete according to Python Policy (http://www.altlinux.org/Python_Policy). Please, use BuildRequires: python-devel.; 
cas	python-module-libnacl-1.4.2-alt0.M70P.1.src	altlinux-python-obsolete-buildreq-python-dev	warn	python-dev is obsolete according to Python Policy (http://www.altlinux.org/Python_Policy). Please, use BuildRequires: python-devel.; 
cas	python-module-ncclient-0.4.2-alt0.M70P.1.src	altlinux-python-obsolete-buildreq-python-dev	warn	python-dev is obsolete according to Python Policy (http://www.altlinux.org/Python_Policy). Please, use BuildRequires: python-devel.; 
cas	python-module-pelican-3.5.0-alt0.M70P.1.noarch	altlinux-python-test-is-packaged	info	/usr/lib/python2.7/site-packages/pelican/tests/test_contents.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/pelican/tests/test_contents.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/pelican/tests/test_contents.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/pelican/tests/test_generators.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/pelican/tests/test_generators.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/pelican/tests/test_generators.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/pelican/tests/test_importer.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/pelican/tests/test_importer.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/pelican/tests/test_importer.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/pelican/tests/test_paginator.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/pelican/tests/test_paginator.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/pelican/tests/test_paginator.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/pelican/tests/test_pelican.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/pelican/tests/test_pelican.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/pelican/tests/test_pelican.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/pelican/tests/test_readers.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/pelican/tests/test_readers.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/pelican/tests/test_readers.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/pelican/tests/test_settings.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/pelican/tests/test_settings.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/pelican/tests/test_settings.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/pelican/tests/test_utils.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/pelican/tests/test_utils.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/pelican/tests/test_utils.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; 
cas	python-module-pelican-3.5.0-alt0.M70P.1.src	specfile-python2-in-spec	warn	spec file explicitly calls /usr/bin/python. It is deprecated binary. Use /usr/bin/python2.; 
cas	python-module-power-1.4-alt0.M70P.1.src	specfile-python2-in-spec	warn	spec file explicitly calls /usr/bin/python. It is deprecated binary. Use /usr/bin/python2.; 
cas	python-module-raet-0.6.1-alt1.M70P.1.src	altlinux-python-obsolete-buildreq-python-dev	warn	python-dev is obsolete according to Python Policy (http://www.altlinux.org/Python_Policy). Please, use BuildRequires: python-devel.; 
cas	python-module-samba-DC-4.5.12-alt1.M70P.1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/python2.7/site-packages/samba/dcerpc/auth.so conflicts with the package python-module-samba-4.5.12-alt1.M70P.1.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.; 
cas	python-module-scour-0.29-alt0.M70P.1.git20140726.src	specfile-python2-in-spec	warn	spec file explicitly calls /usr/bin/python. It is deprecated binary. Use /usr/bin/python2.; 
cas	python-module-ws4py-0.3.4-alt0.M70P.1.src	altlinux-python-obsolete-buildreq-python-dev	warn	python-dev is obsolete according to Python Policy (http://www.altlinux.org/Python_Policy). Please, use BuildRequires: python-devel.; 
cas	python-module-xlrd-0.9.2-alt1.M70P.1.noarch	bin-permissions	info	not executable file /usr/bin/runxlrd; 
cas	python-module-xlutils-1.7.0-alt0.M70P.1.noarch	altlinux-python-test-is-packaged	info	/usr/lib/python2.7/site-packages/xlutils/tests/test_copy.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/xlutils/tests/test_copy.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/xlutils/tests/test_copy.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/xlutils/tests/test_docs.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/xlutils/tests/test_docs.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/xlutils/tests/test_docs.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/xlutils/tests/test_filter.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/xlutils/tests/test_filter.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/xlutils/tests/test_filter.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/xlutils/tests/test_save.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/xlutils/tests/test_save.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/xlutils/tests/test_save.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/xlutils/tests/test_styles.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/xlutils/tests/test_styles.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/xlutils/tests/test_styles.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/xlutils/tests/test_view.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/xlutils/tests/test_view.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/xlutils/tests/test_view.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; 
cas	pyzy-0.1.0-alt2.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; 
cas	qelectrotech-0.5-alt0.M70P.1.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.; 
cas	qelectrotech-0.5-alt0.M70P.1.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/qelectrotech.desktop. please, fix.; 
cas	qelectrotech-0.5-alt0.M70P.1.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/qelectrotech.desktop: hint: value "Engineering;" 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; /usr/share/applications/qelectrotech.desktop: warning: value "Editor v?kres? elektrick?ch obvod?" for key "Comment[cs]" in group "Desktop Entry" looks redundant with value "Editor v?kres? elektrick?ch obvod?" of key "GenericName[cs]"; 
cas	qextserialport-1.2rc-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; 
cas	rosa-imagewriter-2.4.0.0-alt0.M70P.1.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/rosa-imagewriter.desktop: hint: value "System;Utility;Archiving;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; 
cas	ruby-benchmark-ips-doc-1.2.0-alt1.gite47e416.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/share/ri/site/Benchmark/cdesc-Benchmark.ri conflicts with the package ruby-benchmark_suite-doc-1.0.0-alt1.git5bded6.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
cas	ruby-benchmark_suite-doc-1.0.0-alt1.git5bded6.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/share/ri/site/Benchmark/cdesc-Benchmark.ri conflicts with the package ruby-benchmark-ips-doc-1.2.0-alt1.gite47e416.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
cas	ruby-chef-sugar-doc-3.1.0-alt1.noarch	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package chef-doc-12.4.1-alt1.noarch, for example, /usr/share/ri/site/Chef/Node/cdesc-Node.ri (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.; File /usr/share/ri/site/Chef/cdesc-Chef.ri conflicts with the package ohai-doc-8.0.1-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.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.2-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.; Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-ffi-yajl-doc-1.3.1-alt0.M70P.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.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-rr-doc-1.1.2-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.; 
cas	ruby-cleanroom-doc-1.0.0-alt1.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package chef-doc-12.4.1-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.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-core-doc-3.2.3-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.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-mocks-doc-3.2.1-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.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-support-doc-3.2.2-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.; 
cas	ruby-em-http-request-doc-1.1.2-alt1.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package chef-doc-12.4.1-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.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.1.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.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-socksify-doc-0.3.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.; Files /usr/share/ri/site/EventMachine/HTTPMethods/cdesc-HTTPMethods.ri /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflict with the package ruby-em-synchrony-doc-1.0.4-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.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-eventmachine-doc-1.0.3-alt0.M70P.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.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-ffi-yajl-doc-1.3.1-alt0.M70P.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.; 
cas	ruby-em-socksify-doc-0.3.0-alt1.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-http-request-doc-1.1.2-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.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-synchrony-doc-1.0.4-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.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-eventmachine-doc-1.0.3-alt0.M70P.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.; 
cas	ruby-em-synchrony-1.0.4-alt1.src	unmet-dependency-build-missing-package	fail	build dependency ruby-activerecord-mysql2-adapter not found.; 
cas	ruby-em-synchrony-doc-1.0.4-alt1.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package erubis-doc-2.7.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.; There are file conflicts with the package ruby-activerecord-doc-2.3.11-alt1.1.noarch, for example, /usr/share/ri/site/ActiveRecord/ConnectionAdapters/ConnectionPool/cdesc-ConnectionPool.ri (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.; Files /usr/share/ri/site/EventMachine/HTTPMethods/cdesc-HTTPMethods.ri /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflict with the package ruby-em-http-request-doc-1.1.2-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.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-socksify-doc-0.3.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.; There are file conflicts with the package ruby-eventmachine-doc-1.0.3-alt0.M70P.1.noarch, for example, /usr/share/ri/site/EventMachine/Protocols/Memcache/cdesc-Memcache.ri (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.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-ffi-yajl-doc-1.3.1-alt0.M70P.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.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-json-pure-doc-1.8.1-alt0.M70P.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.; 
cas	ruby-eventmachine-doc-1.0.3-alt0.M70P.1.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-http-request-doc-1.1.2-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.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-socksify-doc-0.3.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.; There are file conflicts with the package ruby-em-synchrony-doc-1.0.4-alt1.noarch, for example, /usr/share/ri/site/EventMachine/Protocols/Memcache/cdesc-Memcache.ri (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.; File /usr/share/ri/site/IO/cdesc-IO.ri conflicts with the package ruby-io-extra-doc-1.2.2-alt1.1.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.; 
cas	ruby-ffi-yajl-doc-1.3.1-alt0.M70P.1.noarch	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package chef-doc-12.4.1-alt1.noarch, for example, /usr/share/ri/site/FalseClass/cdesc-FalseClass.ri (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.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package erubis-doc-2.7.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.; Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-chef-sugar-doc-3.1.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.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.2-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.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-em-synchrony-doc-1.0.4-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.; There are file conflicts with the package ruby-json-pure-doc-1.8.1-alt0.M70P.1.noarch, for example, /usr/share/ri/site/Date/cdesc-Date.ri (13 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.; Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Hash/cdesc-Hash.ri conflict with the package ruby-rr-doc-1.1.2-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.; 
cas	ruby-idn-doc-0.1.0-alt0.M70P.1.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/share/ri/site/Enumerable/cdesc-Enumerable.ri conflicts with the package ruby-rr-doc-1.1.2-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.; 
cas	ruby-json-pure-doc-1.8.1-alt0.M70P.1.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package chef-doc-12.4.1-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.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package erubis-doc-2.7.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.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-em-synchrony-doc-1.0.4-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.; There are file conflicts with the package ruby-ffi-yajl-doc-1.3.1-alt0.M70P.1.noarch, for example, /usr/share/ri/site/Date/cdesc-Date.ri (13 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.; Files /usr/share/ri/site/Range/cdesc-Range.ri /usr/share/ri/site/Regexp/cdesc-Regexp.ri conflict with the package ruby-rr-doc-1.1.2-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.; File /usr/share/ri/site/Class/cdesc-Class.ri conflicts with the package ruby-rspec-mocks-doc-3.2.1-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.; 
cas	ruby-mixlib-authentication-doc-1.3.0-alt1.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-cli-doc-1.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.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-config-doc-2.1.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.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-log-doc-1.4.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.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-shellout-doc-2.0.1-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.; 
cas	ruby-mixlib-cli-doc-1.5.0-alt1.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-authentication-doc-1.3.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.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-config-doc-2.1.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.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-log-doc-1.4.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.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-shellout-doc-2.0.1-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.; 
cas	ruby-mixlib-config-doc-2.1.0-alt1.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-authentication-doc-1.3.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.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-cli-doc-1.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.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-log-doc-1.4.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.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-shellout-doc-2.0.1-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.; 
cas	ruby-mixlib-log-doc-1.4.0-alt1.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-authentication-doc-1.3.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.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-cli-doc-1.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.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-config-doc-2.1.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.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-shellout-doc-2.0.1-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.; 
cas	ruby-mixlib-shellout-doc-2.0.1-alt1.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-authentication-doc-1.3.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.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-cli-doc-1.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.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-config-doc-2.1.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.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-log-doc-1.4.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.; 
cas	ruby-net-dhcp-doc-1.3.2-alt1.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package chef-doc-12.4.1-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.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mechanize-doc-0.9.3-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.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-ssh-multi-doc-1.2.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.; 
cas	ruby-net-ssh-multi-doc-1.2.0-alt1.noarch	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package chef-doc-12.4.1-alt1.noarch, for example, /usr/share/ri/site/Net/SSH/Multi/Server/busy%3f-i.ri (7 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.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mechanize-doc-0.9.3-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.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-dhcp-doc-1.3.2-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.; File /usr/share/ri/site/Net/SSH/cdesc-SSH.ri conflicts with the package ruby-net-ssh-doc-2.0.15-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.; 
cas	ruby-plist-doc-3.0.0-alt2.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/share/ri/site/Plist/cdesc-Plist.ri conflicts with the package ohai-doc-8.0.1-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.; 
cas	ruby-rr-doc-1.1.2-alt1.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-chef-sugar-doc-3.1.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.; Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Hash/cdesc-Hash.ri conflict with the package ruby-ffi-yajl-doc-1.3.1-alt0.M70P.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.; File /usr/share/ri/site/Enumerable/cdesc-Enumerable.ri conflicts with the package ruby-idn-doc-0.1.0-alt0.M70P.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.; Files /usr/share/ri/site/Range/cdesc-Range.ri /usr/share/ri/site/Regexp/cdesc-Regexp.ri conflict with the package ruby-json-pure-doc-1.8.1-alt0.M70P.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.; Files /usr/share/ri/site/RR/Errors/cdesc-Errors.ri /usr/share/ri/site/RR/cdesc-RR.ri conflict with the package ruby-rspec-core-doc-3.2.3-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.; 
cas	ruby-rspec-core-doc-3.2.3-alt1.noarch	rpm-filesystem-conflict-file-file	warn	Files /usr/share/ri/site/RSpec/Core/cdesc-Core.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package chef-doc-12.4.1-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.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-cleanroom-doc-1.0.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.; Files /usr/share/ri/site/RR/Errors/cdesc-Errors.ri /usr/share/ri/site/RR/cdesc-RR.ri conflict with the package ruby-rr-doc-1.1.2-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.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-mocks-doc-3.2.1-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.; Files /usr/share/ri/site/RSpec/Support/cdesc-Support.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-support-doc-3.2.2-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.; 
cas	ruby-rspec-mocks-doc-3.2.1-alt1.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package chef-doc-12.4.1-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.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-cleanroom-doc-1.0.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.; File /usr/share/ri/site/Class/cdesc-Class.ri conflicts with the package ruby-json-pure-doc-1.8.1-alt0.M70P.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.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-core-doc-3.2.3-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.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-support-doc-3.2.2-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.; 
cas	ruby-rspec-support-doc-3.2.2-alt1.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package chef-doc-12.4.1-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.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-cleanroom-doc-1.0.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.; Files /usr/share/ri/site/RSpec/Support/cdesc-Support.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-core-doc-3.2.3-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.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-mocks-doc-3.2.1-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.; 
cas	ruleuser-1.0.3-alt5.noarch	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/ruleuser.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).; 
cas	runawfe4-server-4.2.0-alt19.noarch	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/runawfe4-server-stop.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).; Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/runawfe4-server-start.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).; 
cas	runawfe4-server-4.2.0-alt19.noarch	iconsdir	experimental	Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.; 
cas	runawfe4-server-4.2.0-alt19.noarch	init-condrestart	warn	/etc/rc.d/init.d/runawfe4-server: 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/runawfe4-server: 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.; 
cas	runawfe4-server-4.2.0-alt19.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/share/jboss-as/standalone/deployments/runawfe.ear conflicts with the package runawfe4-server-local-4.2.0-alt13.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
cas	samba-DC-4.5.12-alt1.M70P.1.src	altlinux-policy-obsolete-buildreq	warn	Build dependency on rpm-build-ubt is obsolete and should be dropped to get rid of rpm-build-ubt package.; 
cas	samba-DC-4.5.12-alt1.M70P.1.src	specfile-macros-ubt-is-deprecated	warn	macros %ubt is deprecated and will be removed.; 
cas	samba-DC-4.5.12-alt1.M70P.1.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.; 
cas	samba-DC-4.5.12-alt1.M70P.1.x86_64	checkbashisms	experimental	checkbashisms utility found possible bashisms in: /etc/rc.d/init.d/smb /etc/rc.d/init.d/samba /etc/rc.d/init.d/nmb; 
cas	samba-DC-common-4.5.12-alt1.M70P.1.x86_64	subdir-in-var-run	info	Found a subdir in /var/run or /var/lock. /var/run and /var/lock may be mounted as temporary filesystems, so the init.d scripts must handle this correctly. This will typically amount to creating any required subdirectories dynamically when the init.d script is run, rather than including them in the package and relying on rpm to create them.; 
cas	samba-DC-ctdb-4.5.12-alt1.M70P.1.x86_64	checkbashisms	experimental	checkbashisms utility found possible bashisms in: /usr/sbin/ctdbd_wrapper /etc/rc.d/init.d/ctdb; 
cas	samba-DC-winbind-4.5.12-alt1.M70P.1.x86_64	checkbashisms	experimental	checkbashisms utility found possible bashisms in: /etc/rc.d/init.d/winbind; 
cas	samba-DC-winbind-clients-4.5.12-alt1.M70P.1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /lib64/libnss_winbind.so.2 is different from the same symlink in the package samba-winbind-clients-4.5.12-alt1.M70P.1.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.; value of symlink /lib64/libnss_wins.so.2 is different from the same symlink in the package samba-winbind-clients-4.5.12-alt1.M70P.1.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.; 
cas	scilab-5.5.1-alt0.M70P.1.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.; 
cas	scilab-5.5.1-alt0.M70P.1.x86_64	checkbashisms	experimental	checkbashisms utility found possible bashisms in: /usr/bin/scinotes /usr/bin/scilab-adv-cli /usr/bin/scilab-cli /usr/bin/xcos /usr/bin/scilab; 
cas	scilab-5.5.1-alt0.M70P.1.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/scinotes.desktop: warning: value "???????? ???????? Scilab" for key "Comment[ru]" in group "Desktop Entry" looks redundant with value "???????? ???????? Scilab" of key "GenericName[ru]"; /usr/share/applications/scinotes.desktop: hint: value "Education;Science;Math;Development;Physics;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; /usr/share/applications/scinotes.desktop: hint: value "Education;Science;Math;Development;Physics;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; desktop-file-validate utility printed the following message(s): /usr/share/applications/xcos.desktop: hint: value "Education;Science;Math;Development;Physics;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; /usr/share/applications/xcos.desktop: hint: value "Education;Science;Math;Development;Physics;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; desktop-file-validate utility printed the following message(s): /usr/share/applications/scilab.desktop: hint: value "Education;Science;Math;Development;Physics;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; /usr/share/applications/scilab.desktop: hint: value "Education;Science;Math;Development;Physics;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; 
cas	scim-pinyin-0.5.92-alt1.M70P.1.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.; 
cas	skeinforge-12.03.14-alt0.M70P.1.noarch	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/skeinforge.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).; 
cas	solaar-0.9.2-alt0.M70P.1.noarch	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/solaar.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).; 
cas	supervisor-3.1.3-alt0.M70P.1.noarch	altlinux-python-test-is-packaged	info	/usr/lib/python2.7/site-packages/supervisor/tests/test_childutils.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_childutils.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_childutils.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_confecho.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_confecho.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_confecho.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_datatypes.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_datatypes.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_datatypes.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_dispatchers.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_dispatchers.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_dispatchers.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_events.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_events.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_events.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_http.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_http.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_http.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_loggers.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_loggers.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_loggers.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_options.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_options.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_options.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_process.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_process.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_process.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_rpcinterfaces.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_rpcinterfaces.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_rpcinterfaces.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_socket_manager.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_socket_manager.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_socket_manager.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_states.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_states.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_states.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_supervisorctl.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_supervisorctl.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_supervisorctl.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_supervisord.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_supervisord.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_supervisord.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_web.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_web.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_web.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_xmlrpc.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_xmlrpc.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; /usr/lib/python2.7/site-packages/supervisor/tests/test_xmlrpc.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.; 
cas	supervisor-3.1.3-alt0.M70P.1.noarch	init-but-no-native-systemd	info	The package have SysV init script(s) but no native systemd files.; 
cas	supervisor-3.1.3-alt0.M70P.1.noarch	init-condrestart	warn	/etc/rc.d/init.d/supervisord: 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.; 
cas	supervisor-3.1.3-alt0.M70P.1.noarch	init-lsb	fail	/etc/rc.d/init.d/supervisord: not systemd compatible: lsb init header missing and supervisord.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
cas	tano-1.2.1-alt0.M70P.1.x86_64	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/tano.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).; 
cas	tellico-2.3.10-alt0.M70P.1.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.; 
cas	tellico-2.3.10-alt0.M70P.1.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/kde4/tellico.desktop: warning: value "?????????? ?? ????????" for key "Comment[bg]" in group "Desktop Entry" looks redundant with value "?????????? ?? ????????" of key "GenericName[bg]"; /usr/share/applications/kde4/tellico.desktop: warning: value "Menad?er kolekcija" for key "Comment[bs]" in group "Desktop Entry" looks redundant with value "Menad?er kolekcija" of key "GenericName[bs]"; /usr/share/applications/kde4/tellico.desktop: warning: value "Spr?vce sb?rek" for key "Comment[cs]" in group "Desktop Entry" looks redundant with value "Spr?vce sb?rek" of key "GenericName[cs]"; /usr/share/applications/kde4/tellico.desktop: warning: value "Mastrumilo de Kolektoj" for key "Comment[eo]" in group "Desktop Entry" looks redundant with value "Mastrumilo de Kolektoj" of key "GenericName[eo]"; /usr/share/applications/kde4/tellico.desktop: warning: value "Kogude haldur" for key "Comment[et]" in group "Desktop Entry" looks redundant with value "Kogude haldur" of key "GenericName[et]"; /usr/share/applications/kde4/tellico.desktop: warning: value "Kokoelmienhallinta" for key "Comment[fi]" in group "Desktop Entry" looks redundant with value "Kokoelmienhallinta" of key "GenericName[fi]"; /usr/share/applications/kde4/tellico.desktop: warning: value "Bainisteoir baili?ch?n" for key "Comment[ga]" in group "Desktop Entry" looks redundant with value "Bainisteoir Baili?ch?n" of key "GenericName[ga]"; /usr/share/applications/kde4/tellico.desktop: warning: value "Gy?jtem?nykezel?" for key "Comment[hu]" in group "Desktop Entry" looks redundant with value "Gy?jtem?nykezel?" of key "GenericName[hu]"; /usr/share/applications/kde4/tellico.desktop: warning: value "???????? ?????????" for key "Comment[kk]" in group "Desktop Entry" looks redundant with value "???????? ?????????" of key "GenericName[kk]"; /usr/share/applications/kde4/tellico.desktop: warning: value "Kolekcij? tvarkykl?" for key "Comment[lt]" in group "Desktop Entry" looks redundant with value "Kolekcij? tvarkykl?" of key "GenericName[lt]"; /usr/share/applications/kde4/tellico.desktop: warning: value "?????? ??????????" for key "Comment[mr]" in group "Desktop Entry" looks redundant with value "?????? ??????????" of key "GenericName[mr]"; /usr/share/applications/kde4/tellico.desktop: warning: value "Pengurus koleksi" for key "Comment[ms]" in group "Desktop Entry" looks redundant with value "Pengurus Koleksi" of key "GenericName[ms]"; /usr/share/applications/kde4/tellico.desktop: warning: value "???????? ?????????" for key "Comment[ru]" in group "Desktop Entry" looks redundant with value "???????? ?????????" of key "GenericName[ru]"; /usr/share/applications/kde4/tellico.desktop: warning: value "Spr?vca zbierok" for key "Comment[sk]" in group "Desktop Entry" looks redundant with value "Spr?vca zbierok" of key "GenericName[sk]"; /usr/share/applications/kde4/tellico.desktop: warning: value "Upravljalnik zbirk" for key "Comment[sl]" in group "Desktop Entry" looks redundant with value "Upravljalnik zbirk" of key "GenericName[sl]"; /usr/share/applications/kde4/tellico.desktop: warning: value "?????????? ????????? ????????" for key "Comment[uk]" in group "Desktop Entry" looks redundant with value "?????????? ????????? ????????" of key "GenericName[uk]"; /usr/share/applications/kde4/tellico.desktop: warning: value "?????" for key "Comment[zh_CN]" in group "Desktop Entry" looks redundant with value "?????" of key "GenericName[zh_CN]"; /usr/share/applications/kde4/tellico.desktop: warning: value "?????" for key "Comment[zh_TW]" in group "Desktop Entry" looks redundant with value "?????" of key "GenericName[zh_TW]"; 
cas	terminator-0.97-alt1.noarch	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/terminator.desktop: hint: value "GNOME;GTK;Utility;TerminalEmulator;System;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; 
cas	token-manager-0.12-alt2.git1143028.noarch	bin-permissions	info	not executable file /usr/bin/token-manager.py; 
cas	token-manager-0.12-alt2.git1143028.noarch	freedesktop-desktop	warn	desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/token-manager.desktop: error: key "Comment[ru]" in group "Desktop Entry" is a localized key, but there is no non-localized key "Comment"; /usr/share/applications/token-manager.desktop: hint: value "Qt;HardwareSettings;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; 
cas	token-manager-0.12-alt2.git1143028.noarch	iconsdir	experimental	Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.; 
cas	token-manager-0.12-alt2.git1143028.noarch	missing-url	info	Missing Url: in a package.; 
cas	torsocks-2.0.0-alt2.M70P.1.x86_64	checkbashisms	experimental	checkbashisms utility found possible bashisms in: /usr/bin/torsocks; 
cas	trustedqsl-2.1.2-alt0.M70P.1.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.; 
cas	valentina-0.3.0-alt0.M70P.1.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libqmuparser.so but just /usr/lib64/libqmuparser.so.2.2.5. According to SharedLibs Policy Draft, symlink /usr/lib64/libqmuparser.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/libqmuparser.so to \%files of valentina-0.3.0-alt0.M70P.1.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.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libvpropertyexplorer.so but just /usr/lib64/libvpropertyexplorer.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libvpropertyexplorer.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/libvpropertyexplorer.so to \%files of valentina-0.3.0-alt0.M70P.1.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.; 
cas	valentina-0.3.0-alt0.M70P.1.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.; 
cas	wicd-common-1.7.3-alt0.M70P.1.noarch	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/wicd.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).; 
cas	xsensors-0.74-alt1.M70P.1.x86_64	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/xsensors.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).; 
cas	zoneminder-1.27.0-alt1.M70P.1.x86_64	checkbashisms	experimental	checkbashisms utility found possible bashisms in: /etc/rc.d/init.d/zoneminder; 
cas	zoneminder-1.27.0-alt1.M70P.1.x86_64	init-but-no-native-systemd	info	The package have SysV init script(s) but no native systemd files.; 
cas	zoneminder-1.27.0-alt1.M70P.1.x86_64	init-condrestart	warn	/etc/rc.d/init.d/zoneminder: 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.; 
cas	zoneminder-1.27.0-alt1.M70P.1.x86_64	init-lsb	fail	/etc/rc.d/init.d/zoneminder: not systemd compatible: lsb init header missing and zoneminder.service is not present.  See http://www.altlinux.org/Services_Policy for details.;