alt-notes-server-lite-0.1-alt1.noarch	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package alt-notes-children-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 alt-notes-junior-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.; There are file conflicts with the package alt-notes-junior-sj-0.2-alt4.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 alt-notes-junior-sm-0.2-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
callweaver-1.2-alt1.svn5593.1.2.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.; 
callweaver-docs-1.2-alt1.svn5593.1.2.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.; 
connexion-0.4.6-alt7.svn1392.1.noarch	init-condrestart	warn	/etc/rc.d/init.d/connexion: 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/connexion: 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.; 
connexion-0.4.6-alt7.svn1392.1.noarch	init-lsb	warn	/etc/rc.d/init.d//connexion: lsb init header missing.  See http://www.altlinux.org/Services_Policy for details.; 
connexion-0.4.6-alt7.svn1392.1.noarch	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.; 
fw-scripts-0.5-alt1.noarch	missing-url	info	Missing Url: in a package.; 
gdm-theme-altlinux-0.0-alt1.noarch	missing-url	info	Missing Url: in a package.; 
had-1.0.8-alt2.x86_64	init-lsb	warn	/etc/rc.d/init.d//had: lsb init header missing.  See http://www.altlinux.org/Services_Policy for details.; 
had-1.0.8-alt2.x86_64	missing-url	info	Missing Url: in a package.; 
installer-server-lite-0.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package installer-distro-desktop-5.0-alt22.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-junior-5.0-alt21.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-simply-linux-6.0-alt6.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-workbench-5.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.; There are file conflicts with the package installer-office-desktop-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.; There are file conflicts with the package installer-server-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.; 
installer-server-lite-stage2-0.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts 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-6.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.; There are file conflicts with the package installer-distro-chainmail-stage2-2.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-desktop-stage2-5.0-alt22.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-junior-stage2-5.0-alt21.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-lxdesktop-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-office-server-stage2-5.0-alt28.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-server-light-stage2-6.0-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-simply-linux-stage2-6.0-alt6.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-workbench-stage2-5.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.; There are file conflicts 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.; There are file conflicts 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.; 
installer-server-lite-stage3-0.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package installer-server-stage3-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.; 
java-service-0.1-alt2.noarch	altlinux-java-forbidden-requires	fail	The package has JVM-specific Requires: java-1.6.0-sun. Those requires are often due to packaging errors and also specifically forbidden by Java Packageing Policy. If you really really need it, write it in more indirect way.; 
java-service-0.1-alt2.noarch	missing-url	info	Missing Url: in a package.; 
live-hooks-tftp-20110406-alt1.noarch	init-lsb	warn	/etc/rc.d/init.d//live-hooks-tftp: lsb init header missing.  See http://www.altlinux.org/Services_Policy for details.; 
live-hooks-tftp-20110406-alt1.noarch	missing-url	info	Missing Url: in a package.; 
monetdb-client-11.5.3-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package maui-3.3-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
monetdb-common-11.5.3-alt1.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libmapi.so but just /usr/lib64/libmapi.so.3.1.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libmapi.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/libmapi.so to \%files of monetdb-common-11.5.3-alt1.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libstream.so but just /usr/lib64/libstream.so.2.0.2. According to SharedLibs Policy Draft, symlink /usr/lib64/libstream.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/libstream.so to \%files of monetdb-common-11.5.3-alt1.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; 
monetdb-common-11.5.3-alt1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib64/libmapi.so is different from the same symlink in the package openchange-devel-0.11-alt0.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/lib64/libmapi.so is different from the same symlink in the package zarafa-devel-7.0.2-alt0.M60P.3.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.; 
monetdb-common-debuginfo-11.5.3-alt1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libmapi.so.debug is different from the same symlink in the package libmapi-debuginfo-0.11-alt0.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/libmapi.so.debug is different from the same symlink in the package zarafa-client-debuginfo-7.0.2-alt0.M60P.3.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.; 
monetdb-server-11.5.3-alt1.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libbat.so but just /usr/lib64/libbat.so.4.0.1. According to SharedLibs Policy Draft, symlink /usr/lib64/libbat.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/libbat.so to \%files of monetdb-server-11.5.3-alt1.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libmonetdb5.so but just /usr/lib64/libmonetdb5.so.8.0.1. According to SharedLibs Policy Draft, symlink /usr/lib64/libmonetdb5.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/libmonetdb5.so to \%files of monetdb-server-11.5.3-alt1.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; 
ser2net-2.5-alt1.x86_64	init-lsb	warn	/etc/rc.d/init.d//ser2net: lsb init header missing.  See http://www.altlinux.org/Services_Policy for details.; 
ulog-acctd-0.4.3-alt6.qa1.x86_64	init-lsb	warn	/etc/rc.d/init.d//ulog-acctd: lsb init header missing.  See http://www.altlinux.org/Services_Policy for details.; 
xfce-settings-simple-1.0-alt4.noarch	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package branding-altlinux-desktop-xfce-settings-5.9.9-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.; There are file conflicts with the package branding-altlinux-lite-xfce-settings-5.9.9-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 branding-altlinux-sisyphus-xfce-settings-20101228-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 branding-school-lite-xfce-settings-5.9.9-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 branding-simply-linux-xfce-settings-6.0.0-alt29.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
xfwm4-theme-simple-0.1-alt1.noarch	missing-url	info	Missing Url: in a package.;