Repocop reports by srpm

  rpm id test Status message
cups-2.2.6-alt1.x86_64 altlinux-find-lang-mo warn Language specific files in /usr/share/locale should be marked, for example, using %find_lang. See http://www.altlinux.org/FindLangPolicy for details.
cups-2.2.6-alt1.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.
cups-2.2.6-alt1.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /etc/rc.d/init.d/cups
cups-2.2.6-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/cups.desktop: hint: value item "Printing" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: HardwareSettings;Settings
/usr/share/applications/cups.desktop: hint: value item "HardwareSettings" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: Settings
cups-2.2.6-alt1.x86_64 systemd-check-socket-name experimental in cups-2.2.6-alt1.x86_64: there is a socket cups-lpd.socket but no service cups-lpd.service. Ask ildar@ why it is not right.
in cups-2.2.6-alt1.x86_64: there is a socket org.cups.cups-lpd.socket but no service org.cups.cups-lpd.service. Ask ildar@ why it is not right.
cups-ipptool-2.2.6-alt1.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 Tue Feb 13 06:37:52 2018