Repocop reports by srpm

  rpm id test Status message
libxenomai-2.4.8-alt1.qa1.x86_64 altlinux-policy-shared-lib-contains-devel-so info SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libnative.so but just /usr/lib64/libnative.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libnative.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libnative.so to \%files of libxenomai-2.4.8-alt1.qa1.x86_64. Otherwise, move the symlink into the subpackage lib-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/libpsos.so but just /usr/lib64/libpsos.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libpsos.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libpsos.so to \%files of libxenomai-2.4.8-alt1.qa1.x86_64. Otherwise, move the symlink into the subpackage lib-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/libpthread_rt.so but just /usr/lib64/libpthread_rt.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libpthread_rt.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libpthread_rt.so to \%files of libxenomai-2.4.8-alt1.qa1.x86_64. Otherwise, move the symlink into the subpackage lib-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/librtai.so but just /usr/lib64/librtai.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/librtai.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/librtai.so to \%files of libxenomai-2.4.8-alt1.qa1.x86_64. Otherwise, move the symlink into the subpackage lib-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/librtdk.so but just /usr/lib64/librtdk.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/librtdk.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/librtdk.so to \%files of libxenomai-2.4.8-alt1.qa1.x86_64. Otherwise, move the symlink into the subpackage lib-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/librtdm.so but just /usr/lib64/librtdm.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/librtdm.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/librtdm.so to \%files of libxenomai-2.4.8-alt1.qa1.x86_64. Otherwise, move the symlink into the subpackage lib-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/libuitron.so but just /usr/lib64/libuitron.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libuitron.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libuitron.so to \%files of libxenomai-2.4.8-alt1.qa1.x86_64. Otherwise, move the symlink into the subpackage lib-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/libvrtx.so but just /usr/lib64/libvrtx.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libvrtx.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libvrtx.so to \%files of libxenomai-2.4.8-alt1.qa1.x86_64. Otherwise, move the symlink into the subpackage lib-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/libvxworks.so but just /usr/lib64/libvxworks.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libvxworks.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libvxworks.so to \%files of libxenomai-2.4.8-alt1.qa1.x86_64. Otherwise, move the symlink into the subpackage lib-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.
xenomai-2.4.8-alt1.qa1.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.

generated by repocop at Sat Feb 23 06:30:57 2019