asy quagga-1.2.4-alt1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.; boyarsh installer-common-stage2-1.8.40-alt1.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/cp-metadata; boyarsh installer-common-stage2-1.8.40-alt1.x86_64 rpm-obsolete-live-package info The package obsoletes the package installer-feature-cmdline-parameters-stage2-0.2-alt1.noarch, but the package installer-feature-cmdline-parameters-stage2-0.2-alt1.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.; The package obsoletes the package installer-feature-setup-bootloader-stage2-0.1-alt1.noarch, but the package installer-feature-setup-bootloader-stage2-0.1-alt1.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.; The package obsoletes the package installer-feature-setup-network-stage2-0.22-alt1.noarch, but the package installer-feature-setup-network-stage2-0.22-alt1.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.; boyarsh installer-common-stage3-1.8.40-alt1.noarch rpm-obsolete-live-package info The package obsoletes the package installer-feature-setup-network-stage3-0.22-alt1.noarch, but the package installer-feature-setup-network-stage3-0.22-alt1.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.; boyarsh installer-feature-setup-network-stage2-0.22-alt1.noarch rpm-package-is-obsoleted warn The package is obsoleted by the package installer-common-stage2-1.8.40-alt1.x86_64, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of installer-common-stage2-1.8.40-alt1.x86_64 to remove Obsoletes: tag.; boyarsh installer-feature-setup-network-stage3-0.22-alt1.noarch rpm-package-is-obsoleted warn The package is obsoleted by the package installer-common-stage3-1.8.40-alt1.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of installer-common-stage3-1.8.40-alt1.noarch to remove Obsoletes: tag.; boyarsh startup-rescue-0.29-alt1.noarch init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.; boyarsh startup-rescue-0.29-alt1.noarch init-condrestart fail /etc/rc.d/init.d/rescue-remote: 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/sysreport: missing condrestart target. ERROR: alt-specific script %_sbindir/post_service (used in your %post_service macro) depends on condrestart. Please, fix.; boyarsh startup-rescue-0.29-alt1.noarch init-lsb fail /etc/rc.d/init.d/rescue-remote: not systemd compatible: lsb init header missing and rescue-remote.service is not present. /etc/rc.d/init.d/sysreport: not systemd compatible: lsb init header missing and sysreport.service is not present. See http://www.altlinux.org/Services_Policy for details.; ender lm_sensors3-utils-3.4.0-alt4.x86_64 systemd-but-no-native-init warn The package have native systemd file(s) but no SysV init scripts.; george 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.; george 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.; george cups-2.2.6-alt1.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /etc/rc.d/init.d/cups; george 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; george 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.; george 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.; greycat psi-1.3-alt2.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.; kurakin php-base-2.7-alt3.x86_64 missing-url info Missing Url: in a package.; ldv libflac-devel-1.3.2-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.; mike apache-base-1.3.42rusPL30.24-alt9.1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.; mike apache-base-1.3.42rusPL30.24-alt9.1.x86_64 init-lsb fail /etc/rc.d/init.d/httpd: not systemd compatible: lsb init header missing and httpd.service is not present. See http://www.altlinux.org/Services_Policy for details.; mike apache-base-1.3.42rusPL30.24-alt9.1.x86_64 rpm-filesystem-conflict-symlink-file warn symlink /usr/sbin/apachectl is a file in the package apache2-base-2.4.33-alt1.S1.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.; mike apache-common-1.3.42rusPL30.24-alt9.1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/share/man/man8/suexec.8.xz conflicts with the package apache2-suexec-2.4.33-alt1.S1.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/man/man8/httpd.8.xz conflicts with the package bozohttpd-20170201-alt1.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/bin/htpasswd conflicts with the package mini_httpd-htpasswd-1.19-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.; mike apache-mod_perl-base-1.3.42rusPL30.24-alt9.1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.; mike apache-mod_perl-base-1.3.42rusPL30.24-alt9.1.x86_64 init-lsb fail /etc/rc.d/init.d/httpd-perl: not systemd compatible: lsb init header missing and httpd-perl.service is not present. See http://www.altlinux.org/Services_Policy for details.; mike apache-suexec-1.3.42rusPL30.24-alt9.1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/sbin/suexec conflicts with the package apache2-suexec-2.4.33-alt1.S1.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.; mike collectd-5.8.0-alt2.x86_64 big-changelog info Package contains big ChangeLog. Gzip it.; mike ethtool-4.11-alt1.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /etc/rc.d/init.d/ethtool; mike ethtool-4.11-alt1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.; mike ethtool-4.11-alt1.x86_64 init-lsb fail /etc/rc.d/init.d/ethtool: not systemd compatible: lsb init header missing and ethtool.service is not present. See http://www.altlinux.org/Services_Policy for details.; mike unfs3-0.9.22-alt4.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.; mike unfs3-0.9.22-alt4.x86_64 init-lsb warn /etc/rc.d/init.d/nfs: lsb init header missing. See http://www.altlinux.org/Services_Policy for details.; mithraen nginx-1.12.1-alt2.S1.1.x86_64 init-lsb warn /etc/rc.d/init.d/nginx: lsb init header missing. See http://www.altlinux.org/Services_Policy for details.; mithraen nginx-1.12.1-alt2.S1.1.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.; morozov goldendict-1.0.1-alt7.git.qa1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/goldendict.desktop: hint: value "Office;Dictionary;Education;Qt;Applications;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; /usr/share/applications/goldendict.desktop: warning: value "Office;Dictionary;Education;Qt;Applications;" for key "Categories" in group "Desktop Entry" contains a deprecated value "Applications"; /usr/share/applications/goldendict.desktop: warning: value "GoldenDict" for key "Comment" in group "Desktop Entry" looks redundant with value "GoldenDict" of key "Name"; morozov goldendict-1.0.1-alt7.git.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.; oddity kiki-1.0.2-alt1.qa5.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/kiki.desktop: warning: file contains lines that are not UTF-8 encoded. There is no guarantee the validator will correctly work.; [Invalid UTF-8] /usr/share/applications/kiki.desktop: error: value "\xd0~[\xd0\xbe\xd0\xb3\xd0\xb8\xd1~G\xd0\xb5\xd1\x81\xd0\xba\xd0\xb0\xd1\x8f 3D \xd0\xb8\xd0\xb3\xd1\x80\xd0\xb0" for locale string key "Comment[ru]" in group "Desktop Entry" contains invalid UTF-8 characters, locale string values should be encoded in UTF-8; rider MySQL-server-5.7.21-alt4.S1.x86_64 rpm-filesystem-conflict-file-file warn File /etc/control.d/facilities/mysqld-chroot conflicts with the package mariadb-server-control-10.1.30-alt1.S1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; rider aeskulap-0.2.2-alt3.git2ac922d.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/aeskulap.desktop: hint: value item "MedicalSoftware" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: Education, or Science; rider apache2-base-2.4.33-alt1.S1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/share/man/man8/httpd.8.xz conflicts with the package bozohttpd-20170201-alt1.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.; rider apache2-base-2.4.33-alt1.S1.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.; rider apache2-base-2.4.33-alt1.S1.x86_64 systemd-files-in-etc warn Systemd files Policy Draft violation: etc/tmpfiles.d/ is reserved for sysadmin overrides. Please, move /etc/tmpfiles.d/apache2.conf to \%_tmpfilesdir/.; rider apache2-devel-2.4.33-alt1.S1.x86_64 bin-permissions info not executable file /usr/sbin/envvars; rider apache2-htpasswd-2.4.33-alt1.S1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/bin/htpasswd conflicts with the package mini_httpd-htpasswd-1.19-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.; rider apache2-suexec-2.4.33-alt1.S1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/share/man/man8/suexec.8.xz conflicts with the package apache-common-1.3.42rusPL30.24-alt9.1.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/sbin/suexec conflicts with the package apache-suexec-1.3.42rusPL30.24-alt9.1.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.; rider audit-2.8.3-alt3.S1.x86_64 init-lsb warn /etc/rc.d/init.d/auditd: lsb init header missing. See http://www.altlinux.org/Services_Policy for details.; rider branding-sisyphus-server-light-1.9.3-alt1.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.; rider branding-sisyphus-server-light-alterator-1.9.3-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package branding-altlinux-backup-server-alterator-6.0.0-alt3.noarch, for example, /usr/share/alterator/design/images/groups/datetime.png (31 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.; There are file conflicts with the package branding-altlinux-centaurus-alterator-7.0.5-alt1.noarch, for example, /usr/share/alterator/design/images/attention.gif (7 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.; There are file conflicts with the package branding-altlinux-lxdesktop-alterator-6.0.0-alt7.noarch, for example, /usr/share/alterator/design/images/groups/datetime.png (31 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.; There are file conflicts with the package branding-altlinux-spt-alterator-7.0.0-alt1.noarch, for example, /usr/share/alterator/design/images/attention.gif (7 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.; There are file conflicts with the package branding-altlinux-tablet-alterator-6.0.0-alt3.noarch, for example, /usr/share/alterator/design/images/groups/datetime.png (31 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.; There are file conflicts with the package branding-informika-schoolmaster-alterator-6.0.0-alt47.noarch, for example, /usr/share/alterator/design/images/groups/datetime.png (5 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.; There are file conflicts with the package branding-ivk-chainmail-alterator-3.0-alt2.noarch, for example, /usr/share/alterator/design/images/groups/datetime.png (31 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.; rider branding-sisyphus-server-light-indexhtml-1.9.3-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package branding-altlinux-backup-server-indexhtml-6.0.0-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (5 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.; There are file conflicts with the package branding-altlinux-centaurus-indexhtml-7.0.5-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 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.; There are file conflicts with the package branding-altlinux-desktop-indexhtml-5.9.9-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (5 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.; There are file conflicts with the package branding-altlinux-kdesktop-indexhtml-8.0.0-alt0.6.noarch, for example, /usr/share/applications/indexhtml.desktop (4 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.; There are file conflicts with the package branding-altlinux-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 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.; There are file conflicts with the package branding-altlinux-lxdesktop-indexhtml-6.0.0-alt7.noarch, for example, /usr/share/applications/indexhtml.desktop (4 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.; There are file conflicts with the package branding-altlinux-office-server-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (5 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.; There are file conflicts with the package branding-altlinux-spt-indexhtml-7.0.0-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 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.; There are file conflicts with the package branding-altlinux-tablet-indexhtml-6.0.0-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (4 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.; There are file conflicts with the package branding-informika-schoolmaster-indexhtml-6.0.0-alt47.noarch, for example, /usr/share/applications/indexhtml.desktop (4 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.; There are file conflicts with the package branding-ivk-chainmail-indexhtml-3.0-alt2.noarch, for example, /usr/share/applications/indexhtml.desktop (5 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.; There are file conflicts with the package branding-school-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (5 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.; There are file conflicts with the package branding-simply-linux-indexhtml-8.2.0-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 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.; rider branding-sisyphus-server-light-notes-1.9.3-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package branding-altlinux-backup-server-notes-6.0.0-alt3.noarch, for example, /usr/share/alt-notes/license.all.html (4 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.; There are file conflicts with the package branding-altlinux-lxdesktop-notes-6.0.0-alt7.noarch, for example, /usr/share/alt-notes/license.all.html (4 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.; There are file conflicts with the package branding-altlinux-tablet-notes-6.0.0-alt3.noarch, for example, /usr/share/alt-notes/license.all.html (4 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.; There are file conflicts with the package branding-informika-schoolmaster-notes-6.0.0-alt47.noarch, for example, /usr/share/alt-notes/license.all.html (4 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.; There are file conflicts with the package branding-school-lite-notes-5.9.9-alt1.noarch, for example, /usr/share/alt-notes/license.all.html (4 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.; rider branding-sisyphus-server-light-release-1.9.3-alt1.noarch rpm-filesystem-conflict-file-file warn File /etc/altlinux-release conflicts with the package altlinux-release-icarus-20160328-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 /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-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 /etc/altlinux-release conflicts with the package branding-altlinux-backup-server-release-6.0.0-alt3.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 /etc/altlinux-release conflicts with the package branding-altlinux-lxdesktop-release-6.0.0-alt7.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 /etc/altlinux-release conflicts with the package branding-altlinux-tablet-release-6.0.0-alt3.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 /etc/altlinux-release conflicts with the package branding-informika-schoolmaster-release-6.0.0-alt47.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 /etc/altlinux-release conflicts with the package branding-school-lite-release-5.9.9-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.; rider cups-filters-1.20.3-alt2.x86_64 init-lsb warn /etc/rc.d/init.d/cups-browsed: lsb init header missing. See http://www.altlinux.org/Services_Policy for details.; rider dansguardian-2.12.0.3-alt1.S1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.; rider dansguardian-2.12.0.3-alt1.S1.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.; rider ddcprobe-3.0-alt1.qa1.x86_64 missing-url info Missing Url: in a package.; rider ddcprobe-debuginfo-3.0-alt1.qa1.x86_64 missing-url info Missing Url: in a package.; rider design-icewm-themes-1.0-alt5.noarch missing-url info Missing Url: in a package.; rider dvdstyler-3.0.3-alt2.S1.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.; rider fbreader-0.99.5-alt5.S1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/FBReader.desktop: warning: value "???? ????? ???????????" for key "Comment[ar]" in group "Desktop Entry" looks redundant with value "???? ????? ???????????" of key "GenericName[ar]"; /usr/share/applications/FBReader.desktop: hint: value item "Literature" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: Education, or Science; rider fcgiwrap-1.1.0-alt3.S1.x86_64 systemd-but-no-native-init warn The package have native systemd file(s) but no SysV init scripts.; rider freeipmi-bmc-watchdog-1.6.2-alt1.S1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.; rider freeipmi-bmc-watchdog-1.6.2-alt1.S1.x86_64 init-lsb fail /etc/rc.d/init.d/bmc-watchdog: not systemd compatible: lsb init header missing and bmc-watchdog.service is not present. See http://www.altlinux.org/Services_Policy for details.; rider freeipmi-ipmidetectd-1.6.2-alt1.S1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.; rider freeipmi-ipmiseld-1.6.2-alt1.S1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.; rider freeipmi-ipmiseld-1.6.2-alt1.S1.x86_64 init-lsb fail /etc/rc.d/init.d/ipmiseld: not systemd compatible: lsb init header missing and ipmiseld.service is not present. See http://www.altlinux.org/Services_Policy for details.; rider freeswitch-daemon-1.6.19-alt3.S1.1.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.; rider freeswitch-daemon-1.6.19-alt3.S1.1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.; rider freeswitch-daemon-1.6.19-alt3.S1.1.x86_64 init-lsb fail /etc/rc.d/init.d/freeswitch: not systemd compatible: lsb init header missing and freeswitch.service is not present. See http://www.altlinux.org/Services_Policy for details.; rider freeswitch-daemon-1.6.19-alt3.S1.1.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.; rider freeswitch-webui-1.6.19-alt3.S1.1.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.; rider fwupd-1.0.7-alt1.S1.x86_64 dbus-xml-not-in-devel info file /usr/share/dbus-1/interfaces/org.freedesktop.fwupd.xml is not used in run time. Move it to the -devel subpackage.; rider fwupd-1.0.7-alt1.S1.x86_64 systemd-but-no-native-init warn The package have native systemd file(s) but no SysV init scripts.; rider fwupd-labels-1.0.7-alt1.S1.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.; rider fwupd-labels-1.0.7-alt1.S1.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.; rider fwupdate-common-11-alt1.S1.x86_64 systemd-but-no-native-init warn The package have native systemd file(s) but no SysV init scripts.; rider getstream-20120411-alt2.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.; rider gnote-3.28.0-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.; rider gnote-3.28.0-alt1.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/gnote.desktop. Please add it or report a bug against this test if you already have registered one (not including menu unrelated ones as Core or Qt).; rider grub-common-2.02-alt9.S1.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.; rider hwdatabase-0.3.32-alt1.noarch missing-url info Missing Url: in a package.; rider incron-0.5.12-alt1.S1.x86_64 init-lsb warn /etc/rc.d/init.d/incrond: lsb init header missing. See http://www.altlinux.org/Services_Policy for details.; rider installer-distro-server-light-stage2-8.0-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-desktop-stage2-8.1.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/install2/installer-steps conflicts with the package installer-distro-altlinux-generic-stage2-7.0.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/install2/installer-steps conflicts with the package installer-distro-altlinux-server-stage2-7.0.2-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/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/99-services.sh conflict with the package installer-distro-backup-server-stage2-6.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.; There are file conflicts with the package installer-distro-centaurus-stage2-8.2-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 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.; There are file conflicts with the package installer-distro-chainmail-stage2-3.0.0-alt8.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 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.; There are file conflicts with the package installer-distro-desktop-stage2-5.0-alt23.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-junior-stage2-8.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.; There are file conflicts with the package installer-distro-lxdesktop-stage2-6.0-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 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.; There are file conflicts with the package installer-distro-office-server-stage2-5.0-alt28.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 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.; There are file conflicts with the package installer-distro-school-server-stage2-7.0-alt9.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-simply-linux-stage2-8.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-distro-tablet-stage2-6.0-alt3.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/install2/installer-steps conflicts with the package installer-distro-token-desktop-stage2-0.1.1-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.; There are file conflicts with the package installer-distro-workbench-stage2-5.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 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.; File /usr/share/install2/installer-steps conflicts with the package installer-office-desktop-stage2-5.0-alt7.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/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-server-lite-stage2-0.2-alt1.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.; Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-server-stage2-0.2-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.; rider keepalived-1.4.3-alt1.S1.x86_64 big-changelog info Package contains big ChangeLog. Gzip it.; rider knock-server-0.7.8-alt1.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/sbin/knock_add /etc/rc.d/init.d/knockd; rider knock-server-0.7.8-alt1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.; rider knock-server-0.7.8-alt1.x86_64 init-lsb fail /etc/rc.d/init.d/knockd: not systemd compatible: lsb init header missing and knockd.service is not present. See http://www.altlinux.org/Services_Policy for details.; rider libfprint-0.7.0-alt1.x86_64 udev-files-in-etc warn Systemd files Policy Draft violation: etc/udev/rules.d/ is reserved for sysadmin. Please, move /etc/udev/rules.d/60-fprint-autosuspend.rules to \%_udevrulesdir/.; rider liblinebreak-devel-2.1-alt1.x86_64 rpm-filesystem-conflict-file-file warn Files /usr/include/linebreak.h /usr/include/linebreakdef.h conflict with the package libunibreak-devel-3.0-alt1.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.; rider libmysqlclient20-devel-5.7.21-alt4.S1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package libmysqlclient-devel-10.1.30-alt1.S1.x86_64, for example, /usr/bin/mysql_config (36 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.; rider libmysqlclient20-devel-5.7.21-alt4.S1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib64/libmysqlclient.so is different from the same symlink in the package libmysqlclient-devel-10.1.30-alt1.S1.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.; rider libopencv2.4-2.4.13.3-alt2.src unmet-dependency-build-missing-package fail build dependency libcvmser not found.; rider lightsquid-1.8-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.; rider lirc-0.9.4d-alt1.S1.x86_64 init-lsb warn /etc/rc.d/init.d/lircd: lsb init header missing. See http://www.altlinux.org/Services_Policy for details.; rider lirc-0.9.4d-alt1.S1.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.; rider mldonkey-3.1.6-alt1.x86_64 systemd-but-no-native-init warn The package have native systemd file(s) but no SysV init scripts.; rider ocaml-lablgtk-doc-2.18.6-alt1.S1.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.; rider ocaml-ocamlgraph-devel-1.8.8-alt1.S1.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.; rider ocfs2-tools-1.8.5-alt1.0378c47.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.; rider ocfs2-tools-1.8.5-alt1.0378c47.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.; rider opam-doc-2.0.0-alt1.S1.rc.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.; rider openipmi-2.0.25-alt1.S1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.; rider openipmi-2.0.25-alt1.S1.x86_64 init-condrestart warn /etc/rc.d/init.d/ipmi: 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.; rider openttd-data-1.8.0-alt1.S1.noarch freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/openttd.desktop. Please add it or report a bug against this test if you already have registered one (not including menu unrelated ones as Core or Qt).; rider php5-5.6.36-alt1.S1.x86_64 obsolete-call-in-post-alternatives-0.3 warn alternatives-* calls in post/preun and in triggers are deprecated; rider php5-bz2-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-bz2-debuginfo-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-calendar-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-calendar-debuginfo-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-curl-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-curl-debuginfo-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-dba-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-dba-debuginfo-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-devel-5.6.36-alt1.S1.x86_64 library-pkgnames-static warn package contains static library which has the same name as a shared library in the repository, but neither package name ends with -devel-static according to http://altlinux.org/Drafts/SharedLibs nor the package explicitly conflicts with the package with .so library; rider php5-dom-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-dom-debuginfo-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-exif-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-exif-debuginfo-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-fileinfo-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-fileinfo-debuginfo-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-fpm-fcgi-5.6.36.20180425-alt1.S1.2.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.; rider php5-fpm-fcgi-5.6.36.20180425-alt1.S1.2.x86_64 systemd-files-in-etc warn Systemd files Policy Draft violation: etc/tmpfiles.d/ is reserved for sysadmin overrides. Please, move /etc/tmpfiles.d/php5-fpm.conf to \%_tmpfilesdir/.; rider php5-gd2-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-gd2-debuginfo-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-gmp-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-gmp-debuginfo-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-imap-5.6.36.20180425-alt1.S1.1.x86_64 missing-url info Missing Url: in a package.; rider php5-imap-debuginfo-5.6.36.20180425-alt1.S1.1.x86_64 missing-url info Missing Url: in a package.; rider php5-interbase-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-interbase-debuginfo-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-intl-5.6.36.20180425-alt1.S1.1.x86_64 missing-url info Missing Url: in a package.; rider php5-intl-debuginfo-5.6.36.20180425-alt1.S1.1.x86_64 missing-url info Missing Url: in a package.; rider php5-ldap-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-ldap-debuginfo-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-libs-5.6.36-alt1.S1.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; rider php5-mbstring-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-mbstring-debuginfo-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-mcrypt-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-mcrypt-debuginfo-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-mongo-1.3.7-alt1.5.6.36.20180425.alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-mongo-debuginfo-1.3.7-alt1.5.6.36.20180425.alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-mysql-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-mysql-debuginfo-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-mysqlnd-mysql-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-mysqlnd-mysql-debuginfo-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-openssl-5.6.36.20180425-alt1.S1.1.x86_64 missing-url info Missing Url: in a package.; rider php5-openssl-debuginfo-5.6.36.20180425-alt1.S1.1.x86_64 missing-url info Missing Url: in a package.; rider php5-pcntl-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-pcntl-debuginfo-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-pgsql-5.6.36.20180425-alt1.S1.2.x86_64 missing-url info Missing Url: in a package.; rider php5-pgsql-debuginfo-5.6.36.20180425-alt1.S1.2.x86_64 missing-url info Missing Url: in a package.; rider php5-readline-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-readline-debuginfo-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-snmp-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-snmp-debuginfo-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-soap-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-soap-debuginfo-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-sockets-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-sockets-debuginfo-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-sybase_ct-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-sybase_ct-debuginfo-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-xdebug-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-xdebug-debuginfo-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-xmlreader-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-xmlreader-debuginfo-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-xmlrpc-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-xmlrpc-debuginfo-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-xsl-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-xsl-debuginfo-5.6.36.20180425-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php5-zip-5.6.36.20180425-alt1.S1.1.x86_64 missing-url info Missing Url: in a package.; rider php5-zip-debuginfo-5.6.36.20180425-alt1.S1.1.x86_64 missing-url info Missing Url: in a package.; rider php7-bz2-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-bz2-debuginfo-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-calendar-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-calendar-debuginfo-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-curl-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-curl-debuginfo-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-dba-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-dba-debuginfo-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-devel-7.2.5-alt1.S1.x86_64 library-pkgnames-static warn package contains static library which has the same name as a shared library in the repository, but neither package name ends with -devel-static according to http://altlinux.org/Drafts/SharedLibs nor the package explicitly conflicts with the package with .so library; rider php7-dom-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-dom-debuginfo-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-exif-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-exif-debuginfo-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-fileinfo-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-fileinfo-debuginfo-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-fpm-fcgi-7.2.5-alt1.S1.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.; rider php7-fpm-fcgi-7.2.5-alt1.S1.x86_64 systemd-files-in-etc warn Systemd files Policy Draft violation: etc/tmpfiles.d/ is reserved for sysadmin overrides. Please, move /etc/tmpfiles.d/php7-fpm.conf to \%_tmpfilesdir/.; rider php7-gd2-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-gd2-debuginfo-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-gmp-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-gmp-debuginfo-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-imap-7.2.5-alt1.S1.1.x86_64 missing-url info Missing Url: in a package.; rider php7-imap-debuginfo-7.2.5-alt1.S1.1.x86_64 missing-url info Missing Url: in a package.; rider php7-ldap-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-ldap-debuginfo-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-libs-7.2.5-alt1.S1.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; rider php7-mbstring-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-mbstring-debuginfo-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-mcrypt-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-mcrypt-debuginfo-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-openssl-7.2.5-alt1.S1.1.x86_64 missing-url info Missing Url: in a package.; rider php7-openssl-debuginfo-7.2.5-alt1.S1.1.x86_64 missing-url info Missing Url: in a package.; rider php7-pcntl-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-pcntl-debuginfo-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-pgsql-7.2.5-alt1.S1.2.x86_64 missing-url info Missing Url: in a package.; rider php7-pgsql-debuginfo-7.2.5-alt1.S1.2.x86_64 missing-url info Missing Url: in a package.; rider php7-snmp-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-snmp-debuginfo-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-soap-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-soap-debuginfo-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-sockets-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-sockets-debuginfo-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-xmlreader-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider php7-xmlreader-debuginfo-7.2.5-alt1.S1.x86_64 missing-url info Missing Url: in a package.; rider povray-common-3.7.0.4-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.; rider powertop-2.9-alt1.S1.x86_64 init-lsb warn /etc/rc.d/init.d/powertop: lsb init header missing. See http://www.altlinux.org/Services_Policy for details.; rider psutils-debuginfo-p17-alt3.x86_64 missing-url info Missing Url: in a package.; rider psutils-p17-alt3.x86_64 missing-url info Missing Url: in a package.; rider python3-module-waf-1.9.15-alt1.noarch altlinux-python-python3-requires-python warn python3 package requires python-modules.; rider selinux-policy-alt-0.0.43-alt1.noarch checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/slrun2; rider selinux-policy-alt-0.0.43-alt1.noarch missing-url info Missing Url: in a package.; rider selinux-policy-alt-0.0.43-alt1.noarch systemd-but-no-native-init warn The package have native systemd file(s) but no SysV init scripts.; rider shapercontrol-1.5.7-alt2.noarch init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.; rider spawn-fcgi-1.6.4-alt2.S1.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /etc/rc.d/init.d/spawn-fcgi; rider spawn-fcgi-1.6.4-alt2.S1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.; rider spawn-fcgi-1.6.4-alt2.S1.x86_64 init-lsb fail /etc/rc.d/init.d/spawn-fcgi: not systemd compatible: lsb init header missing and spawn-fcgi.service is not present. See http://www.altlinux.org/Services_Policy for details.; rider spawn-fcgi-1.6.4-alt2.S1.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.; rider sphinx-2.2.11-alt6.S1.x86_64 init-lsb warn /etc/rc.d/init.d/searchd: lsb init header missing. See http://www.altlinux.org/Services_Policy for details.; rider tcpreplay-4.2.6-alt1.S1.x86_64 uncompressed-manpages info Package contains uncompressed manual pages.; rider tor-0.3.3.6-alt1.S1.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.; rider tor-0.3.3.6-alt1.S1.x86_64 big-changelog info Package contains big ChangeLog. Gzip it.; rider tor-0.3.3.6-alt1.S1.x86_64 init-lsb warn /etc/rc.d/init.d/tor: lsb init header missing. See http://www.altlinux.org/Services_Policy for details.; rider tor-0.3.3.6-alt1.S1.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.; rider transmission-common-2.92-alt5.S1.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.; rider transmission-daemon-2.92-alt5.S1.x86_64 init-lsb warn /etc/rc.d/init.d/transmission-daemon: lsb init header missing. See http://www.altlinux.org/Services_Policy for details.; rider vlc-mini-3.0.1-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.; rider vlc-mini-3.0.1-alt1.x86_64 unsafe-tmp-usage-in-scripts fail The test discovered scripts with errors which may be used by a user for damaging important system files. For example if a script uses in its work a temp file which is created in /tmp directory, then every user can create symlinks with the same name (pattern) in this directory in order to destroy or rewrite some system or another user's files. Scripts _must_ _use_ mktemp/tempfile or must use $TMPDIR. mktemp/tempfile is safest. $TMPDIR is safer than /tmp/ because libpam-tmpdir creates a subdirectory of /tmp that is only accessible by that user, and then sets TMPDIR and other variables to that. Hence, it doesn't matter nearly as much if you create a non-random filename, because nobody but you can access it. Found error in /usr/share/vlc/utils/audio-vlc-default.sh: $ grep -A5 -B5 /tmp/ /usr/share/vlc/utils/audio-vlc-default.sh MIME_FILE=~/.local/share/applications/defaults.list if [ ! -f $MIME_FILE ] then echo "[Default Applications]" > $MIME_FILE else grep -v 'audio/' $MIME_FILE > /tmp/vlc.defaults.list.tmp mv /tmp/vlc.defaults.list.tmp $MIME_FILE fi ls /usr/share/mime/audio/* | sed -e 's@/usr/share/mime/@@' -e 's/\.xml/=vlc.desktop/' >> $MIME_FILE Found error in /usr/share/vlc/utils/video-vlc-default.sh: $ grep -A5 -B5 /tmp/ /usr/share/vlc/utils/video-vlc-default.sh MIME_FILE=~/.local/share/applications/defaults.list if [ ! -f $MIME_FILE ] then echo "[Default Applications]" > $MIME_FILE else grep -v 'video/' $MIME_FILE > /tmp/vlc.defaults.list.tmp mv /tmp/vlc.defaults.list.tmp $MIME_FILE fi ls /usr/share/mime/video/* | sed -e 's@/usr/share/mime/@@' -e 's/\.xml/=vlc.desktop/' >> $MIME_FILE; rider wireshark-base-2.6.0-alt2.S1.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.; rider wxsvg-1.5.12-alt2.src unmet-dependency-build-missing-package fail build dependency libagg-devel not found.; rider xl2tpd-1.3.10-alt1.S1.x86_64 init-lsb warn /etc/rc.d/init.d/xl2tpd: lsb init header missing. See http://www.altlinux.org/Services_Policy for details.; rider zoneminder-1.30.4-alt3.S1.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.; rider zoneminder-1.30.4-alt3.S1.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /etc/rc.d/init.d/zoneminder; rider zoneminder-1.30.4-alt3.S1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.; rider zoneminder-1.30.4-alt3.S1.x86_64 init-condrestart fail /etc/rc.d/init.d/zoneminder: missing condstop target. ERROR: alt-specific script %_sbindir/preun_service (used in your %preun_service macro) depends on condstop. Please, fix.; rider zoneminder-1.30.4-alt3.S1.x86_64 init-lsb fail /etc/rc.d/init.d/zoneminder: not systemd compatible: lsb init header missing and zoneminder.service is not present. See http://www.altlinux.org/Services_Policy for details.; rt cuneiform-1.0-alt4.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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libccom.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libced.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libcfcompat.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libcfio.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libcimage.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libcline.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libcpage.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libcpu32.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libcstr.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libctb32.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libcuneiform.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libdif32.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libevn32.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libexc.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libfon32.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libleo32.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/liblns32.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libloc32.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libmmx32.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libmsk32.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libpass2.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libr3532.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/librbal.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/librblock.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/librcorrkegl.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/librcutp.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/librdib.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/librfrmt.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/librimage.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/librline.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/librling.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/librlings.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/librmarker.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/librneg.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/librout.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/librpic.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/librpstr.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/librreccom.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/librsadd.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/librselstr.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/librshelllines.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/librstr.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/librstuff.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/librverline.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libsmetric.so to \%files of cuneiform-1.0-alt4.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/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-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libstd32.so to \%files of cuneiform-1.0-alt4.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.; sbolshakov etcnet-0.9.14-alt1.noarch init-condrestart warn /etc/rc.d/init.d/network: 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/network: 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.; sbolshakov kodi-17.6-alt2.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/kodi /usr/bin/kodi-standalone; sbolshakov wpa_gui-2.6-alt2.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/wpa_gui.desktop. Please add it or report a bug against this test if you already have registered one (not including menu unrelated ones as Core or Qt).; sem hostname-hook-hosts-5.1.0-alt1.noarch missing-url info Missing Url: in a package.; sem libselinux-2.5-alt4.1.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.; sem libsemanage-2.5-alt1.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.; sem policycoreutils-gui-2.5-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/system-config-selinux.desktop: hint: value "System;Security;Settings;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; sem policycoreutils-gui-2.5-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.; sem policycoreutils-mcstransd-2.5-alt1.x86_64 init-lsb warn /etc/rc.d/init.d/mcstrans: lsb init header missing. See http://www.altlinux.org/Services_Policy for details.; sem policycoreutils-restorecond-2.5-alt1.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /etc/rc.d/init.d/restorecond; sem policycoreutils-restorecond-2.5-alt1.x86_64 init-lsb warn /etc/rc.d/init.d/restorecond: lsb init header missing. See http://www.altlinux.org/Services_Policy for details.; sem policycoreutils-sandbox-2.5-alt1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.; sem policycoreutils-sandbox-2.5-alt1.x86_64 init-condrestart warn /etc/rc.d/init.d/sandbox: 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/sandbox: 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.; sem policycoreutils-sandbox-2.5-alt1.x86_64 init-lsb fail /etc/rc.d/init.d/sandbox: not systemd compatible: lsb init header missing and sandbox.service is not present. See http://www.altlinux.org/Services_Policy for details.; shaba clvm-2.02.177-alt4.x86_64 systemd-but-no-native-init warn The package have native systemd file(s) but no SysV init scripts.; shaba dmeventd-1.02.146-alt4.x86_64 systemd-but-no-native-init warn The package have native systemd file(s) but no SysV init scripts.; shaba libdevmapper-event-1.02.146-alt4.x86_64 altlinux-policy-shared-lib-contains-devel-so info SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libdevmapper-event-lvm2.so but just /usr/lib64/libdevmapper-event-lvm2.so.2.02. According to SharedLibs Policy Draft, symlink /usr/lib64/libdevmapper-event-lvm2.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/libdevmapper-event-lvm2.so to \%files of libdevmapper-event-1.02.146-alt4.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.; snejok zarafa-client-7.1.15-alt19.S1.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.; snejok zarafa-client-7.1.15-alt19.S1.x86_64 altlinux-policy-shared-lib-contains-devel-so info SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libzarafasync.so but just /usr/lib64/libzarafasync.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libzarafasync.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/libzarafasync.so to \%files of zarafa-client-7.1.15-alt19.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.; snejok zarafa-client-7.1.15-alt19.S1.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; snejok zarafa-client-7.1.15-alt19.S1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib64/libmapi.so.0 is different from the same symlink in the package libmapi-2.4-alt24.zentyal23.S1.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.; snejok zarafa-client-debuginfo-7.1.15-alt19.S1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/usr/lib64/libmapi.so.0.debug is different from the same symlink in the package libmapi-debuginfo-2.4-alt24.zentyal23.S1.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.; snejok zarafa-dagent-7.1.15-alt19.S1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.; snejok zarafa-devel-7.1.15-alt19.S1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib64/libmapi.so is different from the same symlink in the package monetdb-common-11.27.11-alt1.1.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/lib64/libmapi.so is different from the same symlink in the package openchange-devel-2.4-alt24.zentyal23.S1.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.; snejok zarafa-gateway-7.1.15-alt19.S1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.; snejok zarafa-ical-7.1.15-alt19.S1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.; snejok zarafa-libarchiver-7.1.15-alt19.S1.x86_64 altlinux-policy-shared-lib-contains-devel-so info SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libarchiver-core.so but just /usr/lib64/libarchiver-core.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libarchiver-core.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/libarchiver-core.so to \%files of zarafa-libarchiver-7.1.15-alt19.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.; snejok zarafa-monitor-7.1.15-alt19.S1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.; snejok zarafa-search-7.1.15-alt19.S1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.; snejok zarafa-server-7.1.15-alt19.S1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.; snejok zarafa-spooler-7.1.15-alt19.S1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.; solo libvirt-client-4.2.0-alt1.S1.x86_64 init-condrestart fail /etc/rc.d/init.d/libvirt-guests: 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/libvirt-guests: missing condstop target. ERROR: alt-specific script %_sbindir/preun_service (used in your %preun_service macro) depends on condstop. Please, fix.; solo libvirt-daemon-4.2.0-alt1.S1.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.; solo libvirt-daemon-4.2.0-alt1.S1.x86_64 systemd-check-socket-name experimental in libvirt-daemon-4.2.0-alt1.S1.x86_64: there is a socket virtlockd-admin.socket but no service virtlockd-admin.service. Ask ildar@ why it is not right.; in libvirt-daemon-4.2.0-alt1.S1.x86_64: there is a socket virtlogd-admin.socket but no service virtlogd-admin.service. Ask ildar@ why it is not right.; solo libvirt-daemon-config-network-4.2.0-alt1.S1.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.; solo libvirt-libs-4.2.0-alt1.S1.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.; solo libvirt-lxc-4.2.0-alt1.S1.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.; solo libvirt-qemu-common-4.2.0-alt1.S1.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.; viy php5-array2arraymap-sdb-0.13-alt8.5.6.36.20180425.alt1.S1.x86_64 missing-url info Missing Url: in a package.; viy php5-array2arraymap-sdb-debuginfo-0.13-alt8.5.6.36.20180425.alt1.S1.x86_64 missing-url info Missing Url: in a package.;