Repocop reports for by-leader sin

  rpm id test status message
apt-conf-tmp-cache-1.0-alt1.noarch systemd-but-no-native-init warn The package have native systemd file(s) but no SysV init scripts.
ctdb-4.9.4-alt2.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /etc/rc.d/init.d/ctdb
hypre-2.13.0-alt2.src unmet-dependency-build-missing-package fail build dependency emacs24-nox not found.
build dependency w3c-libwww-devel not found.
kbibtex-0.4.1-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/kde4/kbibtex.desktop: hint: value "Qt;KDE;Office;Database;Science;Literature;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
kile-2.1.3-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.
kile-2.1.3-alt1.x86_64 dbus-xml-not-in-devel info file /usr/share/dbus-1/interfaces/net.sourceforge.kile.main.xml is not used in run time. Move it to the -devel subpackage.
lesstif-0.95.2-alt3.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
libbabel-devel-2.0.0-alt2.qa1.x86_64 altlinux-python-obsolete-buildreq-python-dev warn python-dev is obsolete according to Python Policy (http://www.altlinux.org/Python_Policy). Please, use BuildRequires: python-devel.
libcca-spec-babel-devel-0.8.6-alt8.svn20090721.x86_64 altlinux-python-obsolete-buildreq-python-dev warn python-dev is obsolete according to Python Policy (http://www.altlinux.org/Python_Policy). Please, use BuildRequires: python-devel.
libcca-spec-babel-j-0.8.6-alt8.svn20090721.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.
libcca-spec-neo-debuginfo-0.2.8-alt12.2.x86_64 buildroot fail found paths to buildroot: /usr/lib/debug/usr/lib64/libGo-0.1.0.so.0.0.0.debug: Binary file /usr/lib/debug/usr/lib64/libGo-0.1.0.so.0.0.0.debug matches /usr/lib/debug/usr/lib64/libParameter-0.1.0.so.0.0.0.debug: Binary file /usr/lib/debug/usr/lib64/libParameter-0.1.0.so.0.0.0.debug matches /usr/lib/debug/usr/lib64/libSimpleStamper-0.9.0.so.0.0.0.debug: Binary file /usr/lib/debug/usr/lib64/libSimpleStamper-0.9.0.so.0.0.0.debug matches
libsmbclient-devel-4.9.4-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/include/samba-4.0/libsmbclient.h conflicts with the package samba-DC-devel-4.9.4-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.
libsss_autofs-2.0.0-alt3.gitf0603645f.x86_64 systemd-but-no-native-init warn The package have native systemd file(s) but no SysV init scripts.
libsss_sudo-2.0.0-alt3.gitf0603645f.x86_64 systemd-but-no-native-init warn The package have native systemd file(s) but no SysV init scripts.
libv-devel-1.90-alt9.2.x86_64 windows-thumbnail-database-in-package warn /usr/share/doc/libv-devel-1.90/fig/Thumbs.db: It is the file in the package named Thumbs.db or Thumbs.db.gz, which is normally a Windows image thumbnail database. Such databases are generally useless in packages and were usually accidentally included by copying complete directories from the source tarball.
libwbclient-4.9.4-alt2.x86_64 alt-alternatives-vs-ghost info Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-sssd-2.0.0-alt3.gitf0603645f.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0.14 is an alternative in package libwbclient-4.9.4-alt2.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.14.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-4.9.4-alt2.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0.14 is an alternative in package libwbclient-DC-4.9.4-alt2.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.14.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-DC-4.9.4-alt2.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.
libwbclient-DC-4.9.4-alt2.x86_64 alt-alternatives-vs-ghost info Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-sssd-2.0.0-alt3.gitf0603645f.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0.14 is an alternative in package libwbclient-4.9.4-alt2.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.14.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-4.9.4-alt2.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0.14 is an alternative in package libwbclient-DC-4.9.4-alt2.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.14.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-DC-4.9.4-alt2.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.
libwbclient-DC-debuginfo-4.9.4-alt2.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.14.debug is different from the same symlink in the package libwbclient-debuginfo-4.9.4-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.
value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-sssd-debuginfo-2.0.0-alt3.gitf0603645f.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/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-debuginfo-4.9.4-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.
libwbclient-DC-devel-4.9.4-alt2.x86_64 alt-alternatives-vs-ghost info Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-sssd-devel-2.0.0-alt3.gitf0603645f.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-DC-devel-4.9.4-alt2.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-devel-4.9.4-alt2.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.
libwbclient-debuginfo-4.9.4-alt2.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.14.debug is different from the same symlink in the package libwbclient-DC-debuginfo-4.9.4-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.
value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-sssd-debuginfo-2.0.0-alt3.gitf0603645f.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/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-DC-debuginfo-4.9.4-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.
libwbclient-devel-4.9.4-alt2.x86_64 alt-alternatives-vs-ghost info Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-sssd-devel-2.0.0-alt3.gitf0603645f.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-DC-devel-4.9.4-alt2.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-devel-4.9.4-alt2.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.
libwbclient-sssd-2.0.0-alt3.gitf0603645f.x86_64 alt-alternatives-vs-ghost info Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0.14.0 is an alternative in package libwbclient-sssd-2.0.0-alt3.gitf0603645f.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.14.0.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-sssd-2.0.0-alt3.gitf0603645f.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-4.9.4-alt2.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-DC-4.9.4-alt2.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.
libwbclient-sssd-debuginfo-2.0.0-alt3.gitf0603645f.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-DC-debuginfo-4.9.4-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.
value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-debuginfo-4.9.4-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.
libwbclient-sssd-devel-2.0.0-alt3.gitf0603645f.x86_64 alt-alternatives-vs-ghost info Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-sssd-devel-2.0.0-alt3.gitf0603645f.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-DC-devel-4.9.4-alt2.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-devel-4.9.4-alt2.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.
noip-2.1.9-alt2.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /etc/rc.d/init.d/noip
noip-2.1.9-alt2.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.
ponyprog2000-2.07c-alt4.src requires-ImageMagick info Dependency on ImageMagick (compat package) found. It probably should be replaced with more specific dependency like /usr/bin/convert or ImageMagick-tools, or it can be already autodetected by findreq-shell.
python-module-kerberos-1.3.0-alt1.S1.1.src altlinux-python-obsolete-buildreq-python-dev warn python-dev is obsolete according to Python Policy (http://www.altlinux.org/Python_Policy). Please, use BuildRequires: python-devel.
python3-module-samba-4.9.4-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package python3-module-samba-DC-4.9.4-alt2.x86_64, for example, /usr/lib64/python3/site-packages/samba/__pycache__/__init__.cpython-36.opt-1.pyc (242 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
python3-module-samba-DC-4.9.4-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package python3-module-samba-4.9.4-alt2.x86_64, for example, /usr/lib64/python3/site-packages/samba/__pycache__/__init__.cpython-36.opt-1.pyc (242 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
python3-module-samba-DC-devel-4.9.4-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pkgconfig/samba-policy.cpython-36m.pc conflicts with the package python3-module-samba-devel-4.9.4-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.
python3-module-samba-devel-4.9.4-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pkgconfig/samba-policy.cpython-36m.pc conflicts with the package python3-module-samba-DC-devel-4.9.4-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.
ruby-httpclient-doc-2.8.2.4-alt1.2.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package asciidoctor-doc-1.5.7.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package chef-doc-15.0.120-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.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package maruku-doc-0.7.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ohai-doc-15.0.25-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.
Files /usr/share/ri/site/OpenSSL/cdesc-OpenSSL.ri /usr/share/ri/site/String/cdesc-String.ri /usr/share/ri/site/URI/cdesc-URI.ri conflict with the package puma-doc-3.12.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.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-awesome-print-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-storage-doc-0.15.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/URI/cdesc-URI.ri conflicts with the package ruby-escape_utils-doc-1.2.1-alt1.5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/URI/Generic/cdesc-Generic.ri /usr/share/ri/site/URI/Generic/hostname-i.ri /usr/share/ri/site/URI/cdesc-URI.ri conflict with the package ruby-excon-doc-0.62.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/String/cdesc-String.ri /usr/share/ri/site/URI/cdesc-URI.ri conflict with the package ruby-facets-doc-3.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.7.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.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fission-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-gettext_i18n_rails-doc-1.8.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.
File /usr/share/ri/site/URI/cdesc-URI.ri conflicts with the package ruby-globalid-doc-0.4.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.6.21-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.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-hoe-doc-3.17.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.
Files /usr/share/ri/site/HTTP/cdesc-HTTP.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-http-cookie-doc-1.0.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/HTTP/cdesc-HTTP.ri conflicts with the package ruby-http_parser.rb-doc-0.6.0-alt3.5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/cache.ri /usr/share/ri/site/created.rid conflict with the package ruby-iconv-1.0.5-alt1.2.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.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-kindlerb-doc-1.2.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.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-logging-doc-2.2.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/OpenSSL/cdesc-OpenSSL.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-mcollective-client-doc-2.12.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.
File /usr/share/ri/site/HTTP/cdesc-HTTP.ri conflicts with the package ruby-net-http-pipeline-doc-1.0.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/cache.ri /usr/share/ri/site/created.rid conflict with the package ruby-oauth-doc-0.5.4-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.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.7.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.
Files /usr/share/ri/site/cache.ri /usr/share/ri/site/created.rid conflict with the package ruby-parseconfig-doc-0.5-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-parser-doc-3.11.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-pedump-doc-0.5.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/URI/cdesc-URI.ri conflicts with the package ruby-proxifier-doc-1.0.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-puppet-lint-doc-3.0.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/cache.ri /usr/share/ri/site/created.rid conflict with the package ruby-rails-i18n-doc-5.1.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.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-rbvmomi-doc-1.13.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.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-scrub_rb-doc-1.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.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-sequel-doc-5.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-specinfra-doc-2.76.3-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.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-tins-doc-1.17.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.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-1.6.8-alt1.1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-unf-doc-0.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-unicode-display-width-doc-1.4.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-zhexdump-doc-0.0.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.6.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
samba-4.9.4-alt2.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /etc/rc.d/init.d/nmb /etc/rc.d/init.d/smb
samba-DC-4.9.4-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.
samba-DC-4.9.4-alt2.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /etc/rc.d/init.d/samba /etc/rc.d/init.d/nmb /etc/rc.d/init.d/smb
samba-DC-common-4.9.4-alt2.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.
samba-DC-ctdb-4.9.4-alt2.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /etc/rc.d/init.d/ctdb
samba-DC-devel-4.9.4-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/include/samba-4.0/libsmbclient.h conflicts with the package libsmbclient-devel-4.9.4-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.
samba-DC-winbind-4.9.4-alt2.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /etc/rc.d/init.d/winbind
samba-DC-winbind-clients-4.9.4-alt2.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /lib64/libnss_winbind.so.2 is different from the same symlink in the package samba-winbind-clients-4.9.4-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.
value of symlink /lib64/libnss_wins.so.2 is different from the same symlink in the package samba-winbind-clients-4.9.4-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.
samba-client-libs-4.9.4-alt2.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
samba-common-4.9.4-alt2.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.
samba-winbind-4.9.4-alt2.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /etc/rc.d/init.d/winbind
samba-winbind-clients-4.9.4-alt2.x86_64 altlinux-policy-shared-lib-contains-devel-so info SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libnss_winbind.so but just /usr/lib64/libnss_winbind.so.2. According to SharedLibs Policy Draft, symlink /usr/lib64/libnss_winbind.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/libnss_winbind.so to \%files of samba-winbind-clients-4.9.4-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.
SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libnss_wins.so but just /usr/lib64/libnss_wins.so.2. According to SharedLibs Policy Draft, symlink /usr/lib64/libnss_wins.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/libnss_wins.so to \%files of samba-winbind-clients-4.9.4-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.
samba-winbind-clients-4.9.4-alt2.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /lib64/libnss_winbind.so.2 is different from the same symlink in the package samba-DC-winbind-clients-4.9.4-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.
value of symlink /lib64/libnss_wins.so.2 is different from the same symlink in the package samba-DC-winbind-clients-4.9.4-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.
socket_wrapper-1.1.9-alt2.S1.x86_64 altlinux-policy-shared-lib-contains-devel-so info SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libsocket_wrapper.so but just /usr/lib64/libsocket_wrapper.so.0.1.9. According to SharedLibs Policy Draft, symlink /usr/lib64/libsocket_wrapper.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/libsocket_wrapper.so to \%files of socket_wrapper-1.1.9-alt2.S1.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.
sssd-2.0.0-alt3.gitf0603645f.x86_64 systemd-check-socket-name experimental in sssd-2.0.0-alt3.gitf0603645f.x86_64: there is a socket sssd-pam-priv.socket but no service sssd-pam-priv.service. Ask ildar@ why it is not right.
sssd-kcm-2.0.0-alt3.gitf0603645f.x86_64 systemd-but-no-native-init warn The package have native systemd file(s) but no SysV init scripts.
sssd-pac-2.0.0-alt3.gitf0603645f.x86_64 systemd-but-no-native-init warn The package have native systemd file(s) but no SysV init scripts.
vifm-0.10-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/vifm.desktop: hint: value "System;FileTools;FileManager;Utility;ConsoleOnly;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
vifm-0.10-alt1.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.
virtualbox-5.2.22-alt4.src altlinux-python-obsolete-buildreq-python-dev warn python-dev is obsolete according to Python Policy (http://www.altlinux.org/Python_Policy). Please, use BuildRequires: python-devel.
virtualbox-5.2.22-alt4.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.
virtualbox-common-5.2.22-alt4.noarch init-lsb warn /etc/rc.d/init.d/virtualbox: lsb init header missing. See http://www.altlinux.org/Services_Policy for details.
virtualbox-guest-utils-5.2.22-alt4.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.
virtualbox-guest-utils-5.2.22-alt4.x86_64 init-condrestart warn /etc/rc.d/init.d/vboxadd-service: 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/vboxadd-service: 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.
virtualbox-webservice-5.2.22-alt4.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.
virtualbox-webservice-5.2.22-alt4.x86_64 init-condrestart warn /etc/rc.d/init.d/vboxweb-service: 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/vboxweb-service: 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.

generated by repocop at Wed Jan 16 04:48:39 2019