bashdb-4.0-alt2.src	altlinux-policy-tex-buildreq-tetex	info	TeX policy forbids explicit dependencies on obsolete TeTeX. But build dependency on tetex-core is found. Please, replace with TeX-neutral or TexLive dependency.; 
browser-plugins-npapi-3.0-alt1.x86_64	missing-url	info	Missing Url: in a package.; 
browser-plugins-npapi-devel-3.0-alt1.x86_64	missing-url	info	Missing Url: in a package.; 
cgrep-1.0-alt1.noarch	missing-url	info	Missing Url: in a package.; 
console-scripts-1.15.3-alt0.20110502.noarch	init-lsb	warn	/etc/rc.d/init.d//consolesaver: lsb init header missing. /etc/rc.d/init.d//keytable: lsb init header missing.  See http://www.altlinux.org/Services_Policy for details.; 
consolelocker-0.0.1-alt5.x86_64	init-condrestart	warn	/etc/rc.d/init.d/consolelocker: 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/consolelocker: 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.; 
consolelocker-0.0.1-alt5.x86_64	init-lsb	warn	/etc/rc.d/init.d//consolelocker: lsb init header missing.  See http://www.altlinux.org/Services_Policy for details.; 
consolelocker-0.0.1-alt5.x86_64	missing-url	info	Missing Url: in a package.; 
firefox-6.0.2-alt0.M60P.2.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/firefox.desktop: warning: key "Encoding" in group "Desktop Entry" is deprecated; 
firefox-6.0.2-alt0.M60P.2.x86_64	rpm-obsolete-live-package	info	The package obsoletes the package firefox-settings-desktop-5.0-alt3.noarch, but the package firefox-settings-desktop-5.0-alt3.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.; The package obsoletes the package firefox-settings-kdesktop-5.0-alt5.noarch, but the package firefox-settings-kdesktop-5.0-alt5.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.; 
firefox-all-in-one_sidebar-0.7.14-alt1.noarch	macos-ds-store-file-in-package	warn	There is a file in the package named <tt>.DS_Store</tt> or <tt>.DS_Store.gz</tt>, the file name used by Mac OS X to store folder attributes.  Such files are generally useless in packages and were usually accidentally included by copying complete directories from the source tarball.; ; 
firefox-ru-6.0.2-alt0.M60P.1.noarch	rpm-obsolete-live-package	info	The package obsoletes the package firefox-ru_ie-dictionary-0.1-alt1.noarch, but the package firefox-ru_ie-dictionary-0.1-alt1.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.; 
groff-extra-1.20.1-alt0.20091013.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.; 
groff-extra-1.20.1-alt0.20091013.1.x86_64	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
jikes-1.22-alt1.1.x86_64	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
kinit-utils-1.5.17-alt1.x86_64	missing-url	info	Missing Url: in a package.; 
libm17n-db-1.6.2-alt1.noarch	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package m17n-db-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-amharic-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-arabic-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-armenian-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-assamese-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-bengali-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-chinese-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-common-cjk-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-croatian-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-datafiles-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-dhivehi-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-farsi-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-generic-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-georgian-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-greek-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-gujarati-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-hebrew-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-hindi-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-japanese-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-kannada-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-kazakh-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-khmer-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-korean-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-lao-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-latin-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-malayalam-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-myanmar-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-oriya-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-punjabi-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-russian-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-serbian-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-sinhala-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-slovak-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-swedish-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-syriac-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-tamil-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-telugu-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-thai-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-tibetan-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package m17n-db-vietnamese-1.3.3-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
libmemcached-0.23-alt1.1.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libmemcached.so but just /usr/lib64/libmemcached.so.2.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libmemcached.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/libmemcached.so to \%files of libmemcached-0.23-alt1.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.; 
libmemcached-devel-0.23-alt1.1.x86_64	library-pkgnames-static	warn	package contains static library which has the same name as a shared library in the repository, but neither package name ends with -devel-static according to http://altlinux.org/Drafts/SharedLibs nor the package explicitly conflicts with the package with .so library; 
libnss-devel-static-3.12.11-alt2.M60P.1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package libssl-devel-static-1.0.0e-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.; 
libshell-0.1.4-alt1.noarch	missing-url	info	Missing Url: in a package.; 
make-initrd-0.6.0-alt1.x86_64	missing-url	info	Missing Url: in a package.; 
make-initrd-debuginfo-0.6.0-alt1.x86_64	missing-url	info	Missing Url: in a package.; 
make-initrd-devmapper-0.6.0-alt1.x86_64	missing-url	info	Missing Url: in a package.; 
make-initrd-luks-0.6.0-alt1.x86_64	missing-url	info	Missing Url: in a package.; 
make-initrd-lvm-0.6.0-alt1.x86_64	missing-url	info	Missing Url: in a package.; 
make-initrd-mdadm-0.6.0-alt1.x86_64	missing-url	info	Missing Url: in a package.; 
make-initrd-multipath-0.6.0-alt1.x86_64	missing-url	info	Missing Url: in a package.; 
make-initrd-nfs-0.6.0-alt1.x86_64	missing-url	info	Missing Url: in a package.; 
make-initrd-plymouth-0.6.0-alt1.x86_64	missing-url	info	Missing Url: in a package.; 
man-1.6f-alt11.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.; 
man-sh-0.1.2-alt1.noarch	missing-url	info	Missing Url: in a package.; 
mkimage-0.1.9-alt1.noarch	missing-url	info	Missing Url: in a package.; 
mkimage-0.1.9-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/share/mkimage/tools/mki-build-propagator: $ grep -A5 -B5 /tmp/ /usr/share/mkimage/tools/mki-build-propagator kimage="\$(find /boot -type f -name 'vmlinuz-*' -print -quit)" fi kver="\${kimage#/boot/vmlinuz-}" if type mkmodpack >/dev/null 2>&1; then mkmodpack -p '/.in/${mar_modules##*/}' -o /tmp/modules -k "\$kver" else mkmar -r / -p '/.in/${mar_modules##*/}' -o /tmp/modules -k "\$kver" fi printf '%s\n' "${PROPAGATOR_VERSION:-}" > /tmp/.VERSION rm -f /boot/full.cz [ ! -f /tmp/modules ] || cat "\$libdir/propagator/initfs" /tmp/modules > /boot/full.cz sed \ -e "s,@LIBDIR@,\$libdir," \ -e "s,@TMPDIR@,/tmp,g" \ < '/.in/${initfs##*/}' | gencpio - | gzip -c >> /boot/full.cz rm -rf -- /tmp/.VERSION EOF rc=0 mki-run "/.host/packimage.sh" || rc=$? rm -f -- "$chroot/.host/packimage.sh"; 
mkrpmbox-0.0.1-alt4.noarch	missing-url	info	Missing Url: in a package.; 
moc-player-2.5.0-alt0.7.x86_64	freedesktop-desktop	warn	desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/moc.desktop: warning: key "Encoding" in group "Desktop Entry" is deprecated; /usr/share/applications/moc.desktop: error: value "Audio;Player" for string list key "Categories" in group "Desktop Entry" does not have a semicolon (';') as trailing character; 
mozldap-6.0.7-alt1.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libldap60.so but just /usr/lib64/libldap60.so.6.0.7. According to SharedLibs Policy Draft, symlink /usr/lib64/libldap60.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/libldap60.so to \%files of mozldap-6.0.7-alt1.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libldif60.so but just /usr/lib64/libldif60.so.6.0.7. According to SharedLibs Policy Draft, symlink /usr/lib64/libldif60.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/libldif60.so to \%files of mozldap-6.0.7-alt1.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libprldap60.so but just /usr/lib64/libprldap60.so.6.0.7. According to SharedLibs Policy Draft, symlink /usr/lib64/libprldap60.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/libprldap60.so to \%files of mozldap-6.0.7-alt1.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libssldap60.so but just /usr/lib64/libssldap60.so.6.0.7. According to SharedLibs Policy Draft, symlink /usr/lib64/libssldap60.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/libssldap60.so to \%files of mozldap-6.0.7-alt1.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; 
mozldap-6.0.7-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; 
netpipes-4.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package timelimit-1.5-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.; 
nss-utils-3.12.11-alt2.M60P.1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package conflict-6.2-alt1_20040901.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.; 
python-module-xpcom-0.0.0-alt2.20110502.src	unmet-dependency-build-missing-package	fail	build dependency xulrunner-2.0 not found.; build dependency xulrunner-2.0-devel not found.; 
python-module-xpcom-0.0.0-alt2.20110502.x86_64	missing-url	info	Missing Url: in a package.; 
python-module-xpcom-debuginfo-0.0.0-alt2.20110502.x86_64	missing-url	info	Missing Url: in a package.; 
python-module-xpcom-devel-0.0.0-alt2.20110502.x86_64	missing-url	info	Missing Url: in a package.; 
rxvt-unicode-9.10-alt1.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/rxvt-unicode.desktop: warning: key "Encoding" in group "Desktop Entry" is deprecated; 
sisyphus_list-1.4.1.4-alt1.noarch	missing-url	info	Missing Url: in a package.; 
stunnel4-4.35-alt1.x86_64	subdir-in-var-run	info	Found a subdir in /var/run or /var/lock. /var/run and /var/lock may be mounted as temporary filesystems, so the init.d scripts must handle this correctly. This will typically amount to creating any required subdirectories dynamically when the init.d script is run, rather than including them in the package and relying on rpm to create them.; 
stunnel4-standalone-4.35-alt1.x86_64	init-lsb	warn	/etc/rc.d/init.d//stunnel: lsb init header missing.  See http://www.altlinux.org/Services_Policy for details.; 
syslinux4-4.03-alt6.x86_64	missing-url	info	Missing Url: in a package.; 
syslinux4-4.03-alt6.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package syslinux1-1.62-alt4.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.; 
syslinux4-devel-4.03-alt6.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.; 
syslinux4-devel-4.03-alt6.x86_64	missing-url	info	Missing Url: in a package.; 
syslinux4-doc-4.03-alt6.x86_64	missing-url	info	Missing Url: in a package.; 
syslinux4-extlinux-4.03-alt6.x86_64	missing-url	info	Missing Url: in a package.; 
system-report-0.0.7-alt1.noarch	missing-url	info	Missing Url: in a package.; 
thunderbird-6.0.1-alt0.M60P.1.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/thunderbird.desktop: warning: key "Encoding" in group "Desktop Entry" is deprecated; 
thunderbird-devel-6.0.1-alt0.M60P.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.; 
ucarp-1.3-alt2.x86_64	missing-url	info	Missing Url: in a package.; 
util-linux-2.19.1-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.; 
xulrunner-devel-6.0-alt0.M60P.3.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.; 
xulrunner-kmozillahelper-0.0.0-alt1.noarch	missing-url	info	Missing Url: in a package.; 
xulrunner-libs-6.0-alt0.M60P.3.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;