cuneiform-1.0-alt2.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libccom.so but just /usr/lib64/libccom.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libccom.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/libccom.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libced.so but just /usr/lib64/libced.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libced.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/libced.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libcfcompat.so but just /usr/lib64/libcfcompat.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libcfcompat.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/libcfcompat.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libcfio.so but just /usr/lib64/libcfio.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libcfio.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/libcfio.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libcimage.so but just /usr/lib64/libcimage.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libcimage.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/libcimage.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libcline.so but just /usr/lib64/libcline.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libcline.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/libcline.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libcpage.so but just /usr/lib64/libcpage.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libcpage.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/libcpage.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libcpu32.so but just /usr/lib64/libcpu32.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libcpu32.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/libcpu32.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libcstr.so but just /usr/lib64/libcstr.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libcstr.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/libcstr.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libctb32.so but just /usr/lib64/libctb32.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libctb32.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/libctb32.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libcuneiform.so but just /usr/lib64/libcuneiform.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libcuneiform.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/libcuneiform.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libdif32.so but just /usr/lib64/libdif32.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libdif32.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/libdif32.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libevn32.so but just /usr/lib64/libevn32.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libevn32.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/libevn32.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libexc.so but just /usr/lib64/libexc.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libexc.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/libexc.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libfon32.so but just /usr/lib64/libfon32.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libfon32.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/libfon32.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libleo32.so but just /usr/lib64/libleo32.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libleo32.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/libleo32.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/liblns32.so but just /usr/lib64/liblns32.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/liblns32.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/liblns32.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libloc32.so but just /usr/lib64/libloc32.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libloc32.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/libloc32.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libmmx32.so but just /usr/lib64/libmmx32.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libmmx32.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/libmmx32.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libmsk32.so but just /usr/lib64/libmsk32.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libmsk32.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/libmsk32.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libpass2.so but just /usr/lib64/libpass2.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libpass2.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/libpass2.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libr3532.so but just /usr/lib64/libr3532.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libr3532.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/libr3532.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/librbal.so but just /usr/lib64/librbal.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/librbal.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/librbal.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/librblock.so but just /usr/lib64/librblock.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/librblock.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/librblock.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/librcorrkegl.so but just /usr/lib64/librcorrkegl.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/librcorrkegl.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/librcorrkegl.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/librcutp.so but just /usr/lib64/librcutp.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/librcutp.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/librcutp.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/librdib.so but just /usr/lib64/librdib.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/librdib.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/librdib.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/librfrmt.so but just /usr/lib64/librfrmt.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/librfrmt.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/librfrmt.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/librimage.so but just /usr/lib64/librimage.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/librimage.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/librimage.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/librline.so but just /usr/lib64/librline.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/librline.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/librline.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/librling.so but just /usr/lib64/librling.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/librling.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/librling.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/librlings.so but just /usr/lib64/librlings.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/librlings.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/librlings.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/librmarker.so but just /usr/lib64/librmarker.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/librmarker.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/librmarker.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/librneg.so but just /usr/lib64/librneg.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/librneg.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/librneg.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/librout.so but just /usr/lib64/librout.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/librout.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/librout.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/librpic.so but just /usr/lib64/librpic.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/librpic.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/librpic.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/librpstr.so but just /usr/lib64/librpstr.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/librpstr.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/librpstr.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/librreccom.so but just /usr/lib64/librreccom.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/librreccom.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/librreccom.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/librsadd.so but just /usr/lib64/librsadd.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/librsadd.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/librsadd.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/librselstr.so but just /usr/lib64/librselstr.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/librselstr.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/librselstr.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/librshelllines.so but just /usr/lib64/librshelllines.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/librshelllines.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/librshelllines.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/librstr.so but just /usr/lib64/librstr.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/librstr.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/librstr.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/librstuff.so but just /usr/lib64/librstuff.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/librstuff.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/librstuff.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/librverline.so but just /usr/lib64/librverline.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/librverline.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/librverline.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libsmetric.so but just /usr/lib64/libsmetric.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libsmetric.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/libsmetric.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libstd32.so but just /usr/lib64/libstd32.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libstd32.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/libstd32.so to \%files of cuneiform-1.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; 
gnustep-base-1.14.1-alt6.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; 
gq-1.3.6-alt0.1.qa1.x86_64	altlinux-find-lang-gnome	warn	Language specific gnome files in /usr/share/omf should be marked, for example, using %find_lang --with-gnome. See http://www.altlinux.org/FindLangPolicy for details.; 
gq-1.3.6-alt0.1.qa1.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.; 
pavucontrol-0.9.10-alt2.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/pavucontrol.desktop: warning: key "Encoding" in group "Desktop Entry" is deprecated; 
python-module-basicproperty-0.6.12a-alt1.x86_64	altlinux-python-test-is-packaged	info	/usr/lib64/python2.6/site-packages/basicproperty/tests/test_basic.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/lib64/python2.6/site-packages/basicproperty/tests/test_basic.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/lib64/python2.6/site-packages/basicproperty/tests/test_basic.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/lib64/python2.6/site-packages/basicproperty/tests/test_boundary.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/lib64/python2.6/site-packages/basicproperty/tests/test_boundary.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/lib64/python2.6/site-packages/basicproperty/tests/test_boundary.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/lib64/python2.6/site-packages/basicproperty/tests/test_classbyname.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/lib64/python2.6/site-packages/basicproperty/tests/test_classbyname.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/lib64/python2.6/site-packages/basicproperty/tests/test_classbyname.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/lib64/python2.6/site-packages/basicproperty/tests/test_date.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/lib64/python2.6/site-packages/basicproperty/tests/test_date.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/lib64/python2.6/site-packages/basicproperty/tests/test_date.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/lib64/python2.6/site-packages/basicproperty/tests/test_factories.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/lib64/python2.6/site-packages/basicproperty/tests/test_factories.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/lib64/python2.6/site-packages/basicproperty/tests/test_factories.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/lib64/python2.6/site-packages/basicproperty/tests/test_linearise.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/lib64/python2.6/site-packages/basicproperty/tests/test_linearise.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/lib64/python2.6/site-packages/basicproperty/tests/test_linearise.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/lib64/python2.6/site-packages/basicproperty/tests/test_lists.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/lib64/python2.6/site-packages/basicproperty/tests/test_lists.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/lib64/python2.6/site-packages/basicproperty/tests/test_lists.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/lib64/python2.6/site-packages/basicproperty/tests/test_wx.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/lib64/python2.6/site-packages/basicproperty/tests/test_wx.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/lib64/python2.6/site-packages/basicproperty/tests/test_wx.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/lib64/python2.6/site-packages/basicproperty/tests/test_xmlencode.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/lib64/python2.6/site-packages/basicproperty/tests/test_xmlencode.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/lib64/python2.6/site-packages/basicproperty/tests/test_xmlencode.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.; 
python-module-pip-0.8.3-alt1.noarch	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package perl-pip-1.19-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.; 
python-module-pip-0.8.3-alt1.noarch	vendor-tag	warn	Bad Vendor: tag in a package.; 
python-module-starpy-1.0.0a13-alt3.noarch	altlinux-python-test-is-packaged	experimental	/usr/lib/python2.6/site-packages/starpy/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.6/site-packages/starpy/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.6/site-packages/starpy/examples/amicommand.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.6/site-packages/starpy/examples/amicommand.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.6/site-packages/starpy/examples/autosurvey/extensions.conf: 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.6/site-packages/starpy/examples/autosurvey/index.html: 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.6/site-packages/starpy/examples/calldurationcallback.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.6/site-packages/starpy/examples/calldurationcallback.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.6/site-packages/starpy/examples/calldurationextensions.conf: 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.6/site-packages/starpy/examples/connecttoivr.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.6/site-packages/starpy/examples/connecttoivr.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.6/site-packages/starpy/examples/connecttoivrapp.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.6/site-packages/starpy/examples/connecttoivrapp.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.6/site-packages/starpy/examples/fastagisetvariable.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.6/site-packages/starpy/examples/fastagisetvariable.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.6/site-packages/starpy/examples/getvariable.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.6/site-packages/starpy/examples/getvariable.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.6/site-packages/starpy/examples/hellofastagi.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.6/site-packages/starpy/examples/hellofastagi.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.6/site-packages/starpy/examples/hellofastagiapp.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.6/site-packages/starpy/examples/hellofastagiapp.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.6/site-packages/starpy/examples/menutest.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.6/site-packages/starpy/examples/menutest.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.6/site-packages/starpy/examples/menutestextensions.conf: 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.6/site-packages/starpy/examples/priexhaustion.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.6/site-packages/starpy/examples/priexhaustion.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.6/site-packages/starpy/examples/priexhaustionbare.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.6/site-packages/starpy/examples/priexhaustionbare.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.6/site-packages/starpy/examples/readingdigits.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.6/site-packages/starpy/examples/readingdigits.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.6/site-packages/starpy/examples/timestamp.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.6/site-packages/starpy/examples/timestamp.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.6/site-packages/starpy/examples/timestampapp.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.6/site-packages/starpy/examples/timestampapp.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.; 
python-module-twisted-web2-8.1.0-alt2.x86_64	altlinux-python-test-is-packaged	info	/usr/lib64/python2.6/site-packages/twisted/web2/test/test_cgi.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/lib64/python2.6/site-packages/twisted/web2/test/test_cgi.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/lib64/python2.6/site-packages/twisted/web2/test/test_cgi.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/lib64/python2.6/site-packages/twisted/web2/test/test_client.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/lib64/python2.6/site-packages/twisted/web2/test/test_client.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/lib64/python2.6/site-packages/twisted/web2/test/test_client.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/lib64/python2.6/site-packages/twisted/web2/test/test_compat.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/lib64/python2.6/site-packages/twisted/web2/test/test_compat.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/lib64/python2.6/site-packages/twisted/web2/test/test_compat.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/lib64/python2.6/site-packages/twisted/web2/test/test_fastcgi.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/lib64/python2.6/site-packages/twisted/web2/test/test_fastcgi.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/lib64/python2.6/site-packages/twisted/web2/test/test_fastcgi.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/lib64/python2.6/site-packages/twisted/web2/test/test_fileupload.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/lib64/python2.6/site-packages/twisted/web2/test/test_fileupload.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/lib64/python2.6/site-packages/twisted/web2/test/test_fileupload.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/lib64/python2.6/site-packages/twisted/web2/test/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/lib64/python2.6/site-packages/twisted/web2/test/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/lib64/python2.6/site-packages/twisted/web2/test/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/lib64/python2.6/site-packages/twisted/web2/test/test_http_headers.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/lib64/python2.6/site-packages/twisted/web2/test/test_http_headers.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/lib64/python2.6/site-packages/twisted/web2/test/test_http_headers.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/lib64/python2.6/site-packages/twisted/web2/test/test_httpauth.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/lib64/python2.6/site-packages/twisted/web2/test/test_httpauth.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/lib64/python2.6/site-packages/twisted/web2/test/test_httpauth.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/lib64/python2.6/site-packages/twisted/web2/test/test_log.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/lib64/python2.6/site-packages/twisted/web2/test/test_log.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/lib64/python2.6/site-packages/twisted/web2/test/test_log.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/lib64/python2.6/site-packages/twisted/web2/test/test_plugin.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/lib64/python2.6/site-packages/twisted/web2/test/test_plugin.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/lib64/python2.6/site-packages/twisted/web2/test/test_plugin.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/lib64/python2.6/site-packages/twisted/web2/test/test_resource.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/lib64/python2.6/site-packages/twisted/web2/test/test_resource.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/lib64/python2.6/site-packages/twisted/web2/test/test_resource.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/lib64/python2.6/site-packages/twisted/web2/test/test_scgi.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/lib64/python2.6/site-packages/twisted/web2/test/test_scgi.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/lib64/python2.6/site-packages/twisted/web2/test/test_scgi.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/lib64/python2.6/site-packages/twisted/web2/test/test_server.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/lib64/python2.6/site-packages/twisted/web2/test/test_server.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/lib64/python2.6/site-packages/twisted/web2/test/test_server.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/lib64/python2.6/site-packages/twisted/web2/test/test_static.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/lib64/python2.6/site-packages/twisted/web2/test/test_static.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/lib64/python2.6/site-packages/twisted/web2/test/test_static.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/lib64/python2.6/site-packages/twisted/web2/test/test_stream.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/lib64/python2.6/site-packages/twisted/web2/test/test_stream.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/lib64/python2.6/site-packages/twisted/web2/test/test_stream.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/lib64/python2.6/site-packages/twisted/web2/test/test_vhost.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/lib64/python2.6/site-packages/twisted/web2/test/test_vhost.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/lib64/python2.6/site-packages/twisted/web2/test/test_vhost.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/lib64/python2.6/site-packages/twisted/web2/test/test_wsgi.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/lib64/python2.6/site-packages/twisted/web2/test/test_wsgi.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/lib64/python2.6/site-packages/twisted/web2/test/test_wsgi.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/lib64/python2.6/site-packages/twisted/web2/test/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/lib64/python2.6/site-packages/twisted/web2/test/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/lib64/python2.6/site-packages/twisted/web2/test/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.; 
slony1-server-2.0.6-alt1.x86_64	init-condrestart	fail	/etc/rc.d/init.d/slon: missing condrestart target. ERROR: alt-specific script %_sbindir/post_service (used in your %post_service macro) depends on condrestart. Please, fix./etc/rc.d/init.d/slon: 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.; 
slony1-server-2.0.6-alt1.x86_64	init-lsb	warn	/etc/rc.d/init.d//slon: lsb init header missing.  See http://www.altlinux.org/Services_Policy for details.; 
slony1-server-2.0.6-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.; 
spt-profiles-ovz-1C-0.1-alt2.noarch	missing-url	info	Missing Url: in a package.;