ceph-base-17.2.6-alt2.x86_64 altlinux-policy-shared-lib-contains-devel-so info SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libosd_tp.so but just /usr/lib64/libosd_tp.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libosd_tp.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/libosd_tp.so to \%files of ceph-base-17.2.6-alt2.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.; ceph-base-17.2.6-alt2.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts. ceph-common-17.2.6-alt2.x86_64 arch-dep-package-has-big-usr-share info The package has a significant amount of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; ceph-common-17.2.6-alt2.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts. ceph-fuse-17.2.6-alt2.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts. ceph-immutable-object-cache-17.2.6-alt2.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts. ceph-mds-17.2.6-alt2.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts. ceph-mgr-17.2.6-alt2.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts. ceph-mgr-cephadm-17.2.6-alt2.x86_64 arch-dep-package-consists-of-usr-share info The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; ceph-mgr-dashboard-17.2.6-alt2.x86_64 arch-dep-package-consists-of-usr-share info The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; ceph-mgr-diskprediction-local-17.2.6-alt2.x86_64 arch-dep-package-consists-of-usr-share info The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; ceph-mgr-modules-core-17.2.6-alt2.x86_64 arch-dep-package-consists-of-usr-share info The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; ceph-mgr-rook-17.2.6-alt2.x86_64 arch-dep-package-consists-of-usr-share info The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; ceph-mon-17.2.6-alt2.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts. ceph-osd-17.2.6-alt2.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts. ceph-radosgw-17.2.6-alt2.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts. ceph-volume-17.2.6-alt2.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts. cephfs-mirror-17.2.6-alt2.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts. rbd-mirror-17.2.6-alt2.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts.