Repocop reports by acl

  packager rpm id test Status message
boyarsh branding-altlinux-office-server-5.9.9-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.
boyarsh branding-altlinux-office-server-indexhtml-5.9.9-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 (6 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 (6 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 (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-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-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 (6 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.
There are file conflicts with the package branding-sisyphus-server-light-indexhtml-1.9.3-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.
boyarsh branding-altlinux-office-server-notes-5.9.9-alt1.noarch rpm-obsolete-live-package info The package obsoletes the package alt-license-office-server-0.1-alt1.noarch, but the package alt-license-office-server-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.
boyarsh branding-altlinux-office-server-release-5.9.9-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.
boyarsh branding-school-lite-5.9.9-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.
boyarsh branding-school-lite-indexhtml-5.9.9-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 (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-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-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.
There are file conflicts with the package branding-sisyphus-server-light-indexhtml-1.9.3-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.
boyarsh branding-school-lite-notes-5.9.9-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-sisyphus-server-light-notes-1.9.3-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.
boyarsh branding-school-lite-release-5.9.9-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-sisyphus-server-light-release-1.9.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.
boyarsh branding-school-lite-xfce-settings-5.9.9-alt1.noarch rpm-filesystem-conflict-file-file warn File /etc/skel/.config/xfce4/panel/launcher-11888137035.rc conflicts with the package xfce-settings-lite-office-lite-1.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 /etc/skel/.config/xfce4/panel/panels.xml /etc/skel/.local/share/applications/defaults.list /usr/share/xfce4/backdrops/xdm.png conflict with the package xfce-settings-lite-school-0.6-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/skel/.config/xfce4/panel/launcher-10.rc conflicts with the package xfce-settings-lite-school-network-0.6-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/skel/.config/xfce4/panel/launcher-11888137035.rc conflicts with the package xfce-settings-lite-school-office-lite-0.6-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/skel/.Xdefaults conflicts with the package xfce-settings-simple-1.0-alt6.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
boyarsh branding-school-lite-xfce-settings-5.9.9-alt1.noarch rpm-obsolete-live-package info The package obsoletes the package xfce-settings-lite-1.0-alt7.noarch, but the package xfce-settings-lite-1.0-alt7.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 firefox-settings-desktop-5.0-alt3.noarch missing-url info Missing Url: in a package.
boyarsh installer-distro-desktop-5.0-alt23.noarch rpm-filesystem-conflict-file-file warn File /usr/share/install2/help/ru_RU/license.html conflicts with the package installer-server-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.
File /usr/share/install2/help/ru_RU/license.html conflicts with the package installer-server-lite-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.
boyarsh installer-distro-desktop-5.0-alt23.src beehive-log-unpackaged-files-found-x86_64 info warning: Installed (but unpackaged) file(s) found:
/usr/share/alterator/help/ru_RU/basesystem.html
/usr/share/alterator/help/ru_RU/kbd.html
/usr/share/alterator/help/ru_RU/license.html
/usr/share/alterator/help/ru_RU/lilo.html
/usr/share/alterator/help/ru_RU/network.html
/usr/share/alterator/help/ru_RU/root.html
/usr/share/alterator/help/ru_RU/time.html
/usr/share/alterator/help/ru_RU/user.html
/usr/share/alterator/help/ru_RU/vm.html
/usr/share/alterator/help/ru_UA
/usr/share/alterator/steps/desktop-discs.desktop
/usr/share/alterator/steps/desktop-finish.desktop
/usr/share/alterator/steps/office-desktop-auth.desktop
boyarsh installer-distro-desktop-stage2-5.0-alt23.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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 installer-distro-altlinux-generic-stage2-7.0.3-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-altlinux-server-stage2-7.0.2-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.
Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps 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 (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 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-junior-stage2-8.1-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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 installer-distro-lxdesktop-stage2-6.0-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-order-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 (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 installer-distro-server-light-stage2-8.0-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-simply-linux-stage2-8.3-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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 installer-distro-tablet-stage2-6.0-alt3.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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 installer-distro-token-desktop-stage2-0.1.1-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.
Files /usr/share/install2/initinstall.d/05-vm-profile /usr/share/install2/installer-steps conflict with the package installer-distro-workbench-stage2-5.0-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-office-desktop-stage2-5.0-alt7.noarch, for example, /usr/share/install2/initinstall.d/05-vm-profile (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-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/initinstall.d/05-vm-profile /usr/share/install2/installer-steps 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.
boyarsh installer-distro-junior-8.1-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/install2/help/ru_RU/license.html conflicts with the package installer-server-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.
File /usr/share/install2/help/ru_RU/license.html conflicts with the package installer-server-lite-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.
boyarsh installer-distro-junior-stage2-8.1-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package installer-distro-altlinux-desktop-stage2-8.1.0-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.
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-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.
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-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 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 (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 installer-distro-chainmail-stage2-3.0.0-alt8.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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 installer-distro-desktop-stage2-5.0-alt23.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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 installer-distro-lxdesktop-stage2-6.0-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (6 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 (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.
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-server-light-stage2-8.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-simply-linux-stage2-8.3-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (6 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-tablet-stage2-6.0-alt3.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-token-desktop-stage2-0.1.1-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.
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 (6 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/postinstall.d/01-remove-installer-desktop-pkgs.sh /usr/share/install2/preinstall.d/80-setup-user-groups conflict 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.
File /usr/share/install2/installer-steps conflicts 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.
File /usr/share/install2/installer-steps conflicts 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.
cas 1c-preinstall-full-8.3-alt11.noarch requires-microsoft-fonts-ttf warn Free Software packages should not require @ fonts! But dependency on fonts-ttf-ms is found.
cas 389-adminutil-1.1.23-alt1.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
cas 389-ds-base-1.3.7.1-alt2.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/sbin/db2bak
cas 389-ds-base-1.3.7.1-alt2.x86_64 init-lsb warn /etc/rc.d/init.d/dirsrv: not systemd compatible: lsb init header missing and dirsrv.service is not present. /etc/rc.d/init.d/dirsrv-snmp: lsb init header missing. See http://www.altlinux.org/Services_Policy for details.
cas alt-test-1.1.4-alt1.noarch checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/alt-test-functions
cas alterator-ca-0.5.5-alt1.noarch checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/sbin/ca-sko
cas alterator-mass-management-0.1.7-alt1.noarch 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/lib/alterator/backend3/mass-management: $ grep -A5 -B5 /tmp/ /usr/lib/alterator/backend3/mass-management mkdir -p "$TASKS_DIR/task-$number" cat >"$TASKS_DIR/task-$number.yml" <> /tmp/mode.log echo "$(set|grep -a "in_")" >> /tmp/mode.log case "$in_action" in type) write_type_item hostlist hostname-list #write_type_item add_host hostname ;;
cas alterator-rd-0.0.3-alt2.noarch checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/rd-profile-info /usr/bin/rd-list-profiles
cas alterator-rd-freerdp-0.0.3-alt2.noarch checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/rd-freerdp
cas alterator-rd-rdesktop-0.0.3-alt2.noarch checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/rd-rdesktop
cas alterator-usersource-functions-0.8.5-alt1.noarch checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/alterator-usersource-functions
cas ananas-0.9.5-alt9.src unmet-dependency-build-missing-package fail build dependency kdepim-devel not found.
cas ananas-0.9.5-alt9.x86_64 altlinux-policy-shared-lib-contains-devel-so info SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libananas.so but just /usr/lib64/libananas.so.1.0.1. According to SharedLibs Policy Draft, symlink /usr/lib64/libananas.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/libananas.so to \%files of ananas-0.9.5-alt9.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.
cas ananas-0.9.5-alt9.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/ananas.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).
cas ananas-0.9.5-alt9.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.
cas anykiosk-0.0.2.20101210-alt2.1.qa1.noarch freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/anykiosk.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).
cas anykiosk-0.0.2.20101210-alt2.1.qa1.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/anykiosk.desktop: warning: value "Kiosk editor" for key "Comment" in group "Desktop Entry" looks redundant with value "Kiosk editor" of key "GenericName"
/usr/share/applications/anykiosk.desktop: warning: value "????????? ??????" for key "Comment[ru_RU]" in group "Desktop Entry" looks redundant with value "????????? ??????" of key "GenericName[ru_RU]"
cas anykiosk-0.0.2.20101210-alt2.1.qa1.src beehive-log-unpackaged-files-found-x86_64 info warning: Installed (but unpackaged) file(s) found:
/usr/share/anykiosk/LICENSE
/usr/share/anykiosk/Makefile
/usr/share/anykiosk/README
/usr/share/anykiosk/anykiosk
/usr/share/anykiosk/anykiosk.desktop
/usr/share/anykiosk/anykiosk.pamd
/usr/share/anykiosk/anykiosk.security
/usr/share/anykiosk/ver.id_set002_.txt
cas apache2-mod_ngobjweb-3.2.10-alt2.x86_64 altlinux-policy-obsolete-httpd2-reload info This package contains httpd2 restart/reload calls in its post/un scripts. But those calls are deprecated by httpd2.filetrigger that activates by files in /etc/httpd2/ or %_libdir/apache2/modules/. It should be safe to remove those calls and rely on the filetrigger instead.
cas apache2-mod_wsgi-4.5.24-alt1.x86_64 altlinux-policy-obsolete-httpd2-reload info This package contains httpd2 restart/reload calls in its post/un scripts. But those calls are deprecated by httpd2.filetrigger that activates by files in /etc/httpd2/ or %_libdir/apache2/modules/. It should be safe to remove those calls and rely on the filetrigger instead.
cas appstream-doc-0.11.8-alt1.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.
cas aqbanking-5.6.12-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.
cas basic256-0.9.6-alt8.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/basic256.desktop: hint: value "Education;Science;ComputerScience;Development;IDE;" 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/basic256.desktop: hint: value "Education;Science;ComputerScience;Development;IDE;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
cas basqet-0.2.0-alt2.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/basqet.desktop: error: value "0.2.0" for key "Version" in group "Desktop Entry" is not a known version
cas basqet-0.2.0-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.
cas bleachbit-1.12-alt1.noarch freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/bleachbit.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).
cas bleachbit-1.12-alt1.noarch iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.
cas branding-school-master-7.0.5-alt2.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.
cas branding-school-master-alterator-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package branding-altlinux-backup-server-alterator-6.0.0-alt3.noarch, but the package branding-altlinux-backup-server-alterator-6.0.0-alt3.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 branding-informika-schoolmaster-alterator-6.0.0-alt47.noarch, but the package branding-informika-schoolmaster-alterator-6.0.0-alt47.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.
cas branding-school-master-bootloader-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package branding-informika-schoolmaster-bootloader-6.0.0-alt47.noarch, but the package branding-informika-schoolmaster-bootloader-6.0.0-alt47.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.
cas branding-school-master-bootsplash-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package branding-informika-schoolmaster-bootsplash-6.0.0-alt47.noarch, but the package branding-informika-schoolmaster-bootsplash-6.0.0-alt47.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.
cas branding-school-master-graphics-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package branding-informika-schoolmaster-graphics-6.0.0-alt47.noarch, but the package branding-informika-schoolmaster-graphics-6.0.0-alt47.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.
cas branding-school-master-indexhtml-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package branding-informika-schoolmaster-indexhtml-6.0.0-alt47.noarch, but the package branding-informika-schoolmaster-indexhtml-6.0.0-alt47.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.
cas branding-school-master-kde4-settings-7.0.5-alt2.noarch rpm-filesystem-conflict-file-file warn File /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-altlinux-kdesktop-indexhtml-8.0.0-alt0.6.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/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-informika-schoolmaster-indexhtml-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 /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-school-junior-indexhtml-7.0.5-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-school-teacher-indexhtml-7.0.5-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-xalt-kworkstation-indexhtml-8.2.0-alt3.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.
cas branding-school-master-kde4-settings-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package branding-informika-schoolmaster-kde4-settings-6.0.0-alt47.noarch, but the package branding-informika-schoolmaster-kde4-settings-6.0.0-alt47.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.
cas branding-school-master-menu-7.0.5-alt2.noarch rpm-filesystem-conflict-file-file warn File /usr/share/slinux-style/applications/dropbox.desktop conflicts with the package branding-school-server-menu-7.0.5-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 branding-simply-linux-menu-8.2.0-alt1.noarch, for example, /usr/share/slinux-style/applications/Ri-li.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.
cas branding-school-master-notes-7.0.5-alt2.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package alt-notes-school-server-4.1-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.
cas branding-school-master-notes-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package branding-informika-schoolmaster-notes-6.0.0-alt47.noarch, but the package branding-informika-schoolmaster-notes-6.0.0-alt47.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.
cas branding-school-master-release-7.0.5-alt2.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.
cas branding-school-master-release-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package branding-informika-schoolmaster-release-6.0.0-alt47.noarch, but the package branding-informika-schoolmaster-release-6.0.0-alt47.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.
cas branding-school-master-slideshow-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package branding-informika-schoolmaster-slideshow-6.0.0-alt47.noarch, but the package branding-informika-schoolmaster-slideshow-6.0.0-alt47.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.
cas branding-school-master-xfce-settings-7.0.5-alt2.noarch rpm-filesystem-conflict-file-file warn File /etc/skel/.gconf/apps/%gconf.xml conflicts with the package livecd-gnome-nowarn-space-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.
Files /etc/skel/.config/xfce4/desktop/icons.screen0.rc /etc/skel/.config/xfce4/helpers.rc conflict with the package xfce-settings-lite-school-0.6-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 xfce-settings-simple-1.0-alt6.noarch, for example, /etc/skel/.config/xfce4/Xcursor.xrdb (8 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.
cas branding-school-master-xfce-settings-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package xfce-settings-lite-1.0-alt7.noarch, but the package xfce-settings-lite-1.0-alt7.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.
cas bsc-4.1.0-alt1.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.
cas bup-web-0.29.1-alt1.x86_64 systemd-but-no-native-init warn The package have native systemd file(s) but no SysV init scripts.
cas card-actions-1.10-alt7.noarch missing-url info Missing Url: in a package.
cas cfdg-fe-v20061127-alt1.qa2.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/cfdg-fe.desktop: hint: value item "VectorGraphics" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: Graphics;2DGraphics
cas chef-doc-12.15.11-alt1.noarch rpm-filesystem-conflict-file-file warn Files /usr/share/ri/site/String/cdesc-String.ri /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflict with the package asciidoctor-doc-1.5.6.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 ohai-doc-14.0.1-alt1.noarch, for example, /usr/share/ri/site/Chef/cdesc-Chef.ri (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/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/String/cdesc-String.ri /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflict with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.noarch, for example, /usr/share/ri/site/Chef/Node/cdesc-Node.ri (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/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-cleanroom-doc-1.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Win32/cdesc-Win32.ri conflicts with the package ruby-facter-doc-2.0.1-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-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.
Files /usr/share/ri/site/FFI/Pointer/cdesc-Pointer.ri /usr/share/ri/site/FFI/cdesc-FFI.ri conflict with the package ruby-ffi-doc-1.9.21-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 ruby-ffi-yajl-doc-2.3.1-alt1.2.noarch, for example, /usr/share/ri/site/FalseClass/cdesc-FalseClass.ri (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.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-http-cookie-doc-1.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/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.2.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package ruby-json-pure-doc-2.1.0-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Net/cdesc-Net.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-mail-doc-2.6.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/String/cdesc-String.ri /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflict with the package ruby-mcollective-client-doc-2.11.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package ruby-mechanize-doc-0.9.3-alt1.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package ruby-mini_portile2-doc-2.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package ruby-mongo-doc-2.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package ruby-msgpack-doc-1.1.0-alt1.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package ruby-multipart-post-doc-2.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-dhcp-doc-1.3.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.
File /usr/share/ri/site/Net/SSH/cdesc-SSH.ri conflicts with the package ruby-net-ssh-doc-4.2.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package ruby-net-ssh-multi-doc-1.2.0-alt1.1.noarch, for example, /usr/share/ri/site/Net/SSH/Multi/Server/busy%3f-i.ri (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.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-puppet-lint-doc-3.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/RSpec/Core/cdesc-Core.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-core-doc-3.7.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-expectations-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-mocks-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-puppet-doc-0.1.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-support-doc-3.7.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 ruby-sequel-doc-4.49.0-alt2.1.noarch, for example, /usr/share/ri/site/FalseClass/cdesc-FalseClass.ri (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.
Files /usr/share/ri/site/Gem/cdesc-Gem.ri /usr/share/ri/site/RSpec/Core/cdesc-Core.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-spec_helper-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-1.6.8-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-unf-doc-0.1.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.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.
cas cqrlog-2.2.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.
cas cqrlog-2.2.0-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/cqrlog.desktop: hint: value item "Database" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: Office, or Development, or AudioVideo
/usr/share/applications/cqrlog.desktop: hint: value item "HamRadio" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: Network, or Audio
cas cuneiform-qt-0.1.2-alt1.qa1.src beehive-log-unpackaged-files-found-x86_64 info warning: Installed (but unpackaged) file(s) found:
/usr/share/pixmaps/cuneiform-qt.png
cas cuneiform-qt-0.1.2-alt1.qa1.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.
cas cuneiform-qt-0.1.2-alt1.qa1.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/cuneiform-qt.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).
cas cuneiform-qt-0.1.2-alt1.qa1.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/cuneiform-qt.desktop: error: file contains key "GenericName[u?]" in group "Desktop Entry", but key names must contain only the characters A-Za-z0-9- (they may have a "[LOCALE]" postfix)
/usr/share/applications/cuneiform-qt.desktop: warning: value "Cuneiform OCR" for key "Comment" in group "Desktop Entry" looks redundant with value "Cuneiform OCR" of key "GenericName"
/usr/share/applications/cuneiform-qt.desktop: warning: value "????????????? ???????" for key "Comment[ru]" in group "Desktop Entry" looks redundant with value "????????????? ???????" of key "GenericName[ru]"
cas cura-3.0.3-alt2.noarch freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/cura.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).
cas disable-usb-autosuspend-1.1-alt1.noarch missing-url info Missing Url: in a package.
cas eas-0.2.2-alt0.7cvs20070731.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/eas.desktop: warning: value "E/AS Enterprise Automation System" for key "Comment" in group "Desktop Entry" looks redundant with value "E/AS Enterprise Automation System" of key "GenericName"
cas eas-server-0.2.2-alt0.7cvs20070731.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.
cas eas-server-0.2.2-alt0.7cvs20070731.x86_64 init-condrestart warn /etc/rc.d/init.d/easd: 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.
cas eas-server-0.2.2-alt0.7cvs20070731.x86_64 init-lsb fail /etc/rc.d/init.d/easd: not systemd compatible: lsb init header missing and easd.service is not present. See http://www.altlinux.org/Services_Policy for details.
cas easypaint-0.6.0-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.
cas eggdrop-1.8.3-alt1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.
cas eggdrop-1.8.3-alt1.x86_64 init-lsb fail /etc/rc.d/init.d/eggdrop: not systemd compatible: lsb init header missing and eggdrop.service is not present. See http://www.altlinux.org/Services_Policy for details.
cas eggdrop-1.8.3-alt1.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.
cas eigen3-docs-3.3.4-alt4.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.
cas erubis-doc-2.7.0-alt3.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-em-synchrony-doc-1.0.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-json-pure-doc-2.1.0-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-polyglot-doc-0.3.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package yajl-ruby-doc-1.3.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.
cas eviacam-2.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.
cas eviacam-2.0.1-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.
cas fldigi-4.0.15-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.
cas freebasic-1.05.0-alt2.x86_64 arch-dep-package-has-big-usr-share info The package has a significant amount of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.
cas freecad-0.16-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/freecad.desktop: hint: value "Education;Graphics;Science;Engineering;" 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/freecad.desktop: hint: value "Education;Graphics;Science;Engineering;" 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/freecad.desktop: warning: value "Feature-basierter parametrischer Modellierer" for key "Comment[de_DE]" in group "Desktop Entry" looks redundant with value "Feature-basierter parametrischer Modellierer" of key "GenericName[de_DE]"
cas freehep-io-2.2.2-alt3.src unmet-dependency-build-missing-package fail build dependency maven-shared-artifact-resolver not found.
cas freehep-vectorgraphics-2.4-alt1.src unmet-dependency-build-missing-package fail build dependency maven-shared-artifact-resolver not found.
cas gambas3-runtime-3.10.0-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.
cas gamine-1.5-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.
cas gamine-1.5-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/gamine.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).
cas gamine-1.5-alt1.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/gamine.desktop: error: file contains key "comment" in group "Desktop Entry", but keys extending the format should start with "X-"
/usr/share/applications/gamine.desktop: error: file contains key "comment" in group "Desktop Entry", but keys extending the format should start with "X-"
cas gcompris-15.10-alt6.src altlinux-policy-tex-buildreq-tetex info TeX policy forbids explicit dependencies on obsolete TeTeX. But build dependency on tetex-core is found. Please, replace with TeX-neutral or TexLive dependency.
cas gcompris-15.10-alt6.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.
cas gcompris-15.10-alt6.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/gcompris-edit.desktop: warning: value "????? ??????" for key "Comment[ar]" in group "Desktop Entry" looks redundant with value "????? ??????" of key "Name[ar]"
/usr/share/applications/gcompris-edit.desktop: warning: value "Alministraci?n de gcompris" for key "Comment[ast]" in group "Desktop Entry" looks redundant with value "Alministraci?n de GCompris" of key "Name[ast]"
/usr/share/applications/gcompris-edit.desktop: warning: value "?????????????? ?? GCompris" for key "Comment[bg]" in group "Desktop Entry" looks redundant with value "?????????????? ?? GCompris" of key "Name[bg]"
/usr/share/applications/gcompris-edit.desktop: warning: value "GCompris-Administration" for key "Comment[de]" in group "Desktop Entry" looks redundant with value "GCompris-Administration" of key "Name[de]"
/usr/share/applications/gcompris-edit.desktop: warning: value "Administraci?n de gcompris" for key "Comment[es]" in group "Desktop Entry" looks redundant with value "Administraci?n de GCompris" of key "Name[es]"
/usr/share/applications/gcompris-edit.desktop: warning: value "GCompris-en administrazioa" for key "Comment[eu]" in group "Desktop Entry" looks redundant with value "GCompris-en administrazioa" of key "Name[eu]"
/usr/share/applications/gcompris-edit.desktop: warning: value "Administration de GCompris" for key "Comment[fr]" in group "Desktop Entry" looks redundant with value "Administration de GCompris" of key "Name[fr]"
/usr/share/applications/gcompris-edit.desktop: warning: value "GCompris administravimas" for key "Comment[lt]" in group "Desktop Entry" looks redundant with value "GCompris administravimas" of key "Name[lt]"
/usr/share/applications/gcompris-edit.desktop: warning: value "GCompris administr?cija" for key "Comment[lv]" in group "Desktop Entry" looks redundant with value "GCompris administr?cija" of key "Name[lv]"
/usr/share/applications/gcompris-edit.desktop: warning: value "Administra??o do GCompris" for key "Comment[pt]" in group "Desktop Entry" looks redundant with value "Administra??o do GCompris" of key "Name[pt]"
/usr/share/applications/gcompris-edit.desktop: warning: value "Administra??o do GCompris" for key "Comment[pt_BR]" in group "Desktop Entry" looks redundant with value "Administra??o do GCompris" of key "Name[pt_BR]"
/usr/share/applications/gcompris-edit.desktop: warning: value "gcompris ????" for key "Comment[zh_HK]" in group "Desktop Entry" looks redundant with value "GCompris ????" of key "Name[zh_HK]"
/usr/share/applications/gcompris-edit.desktop: warning: value "gcompris ????" for key "Comment[zh_TW]" in group "Desktop Entry" looks redundant with value "GCompris ????" of key "Name[zh_TW]"
/usr/share/applications/gcompris-edit.desktop: hint: value "Settings;Game;KidsGame;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
desktop-file-validate utility printed the following message(s): /usr/share/applications/gcompris.desktop: hint: value "Education;Game;KidsGame;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
cas gdesklets-0.36.3-alt3.src altlinux-policy-obsolete-buildreq warn Build dependency on menu-devel is obsolete and should be dropped to get rid of menu-devel package.
cas gdesklets-0.36.3-alt3.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.
cas girar-utils-1.5.9-alt1.noarch checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/girar-show
cas girar-utils-1.5.9-alt1.noarch missing-url info Missing Url: in a package.
cas gmanedit-0.4.2-alt3.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/gmanedit.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).
cas gmanedit-0.4.2-alt3.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/gmanedit.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/gmanedit.desktop: error: value "Editor de p\xe1ginas man de GNOME" for locale string key "Comment[es]" in group "Desktop Entry" contains invalid UTF-8 characters, locale string values should be encoded in UTF-8
[Invalid UTF-8] /usr/share/applications/gmanedit.desktop: error: value "Editor de p\xe1xinas man de GNOME" for locale string key "Comment[gl]" in group "Desktop Entry" contains invalid UTF-8 characters, locale string values should be encoded in UTF-8
cas gmanedit-0.4.2-alt3.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.
cas gnome-libs-1.4.2-alt11.3.qa2.x86_64 file-in-usr-marked-as-conffile warn Files below /usr may not be marked as conffiles, since
/usr might be mounted read-only and thus, the local system
administrator would not have a chance to modify this configuration
file.
cas gnome-libs-1.4.2-alt11.3.qa2.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
cas gnome-libs-devel-1.4.2-alt11.3.qa2.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/gnome-config
cas gnucash-2.6.19-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.
cas gost-crypto-gui-0.3-alt0.4.a.git201ea87.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/gost-crypto-gui.desktop: hint: value "Qt;HardwareSettings;Settings;System;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
cas gost-crypto-gui-0.3-alt0.4.a.git201ea87.noarch iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.
cas gpaint-0.3.3-alt2.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/gpaint.desktop: warning: boolean key "Terminal" in group "Desktop Entry" has value "0", which is deprecated: boolean values should be "false" or "true"
cas gpaint-0.3.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.
cas gpointing-device-settings-1.5.1-alt5.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/gpointing-device-settings.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).
cas gpointing-device-settings-1.5.1-alt5.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/gpointing-device-settings.desktop: hint: value item "GNOME" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: GTK
cas gpointing-device-settings-1.5.1-alt5.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.
cas gpointing-device-settings-1.5.1-alt5.x86_64 rpm-obsolete-live-package info The package obsoletes the package gsynaptics-0.9.16-alt3.qa1.x86_64, but the package gsynaptics-0.9.16-alt3.qa1.x86_64 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.
cas gpsim-0.30.0-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.
cas grass-7.2.2-alt2.x86_64 arch-dep-package-has-big-usr-share info The package has a significant amount of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.
cas grass-7.2.2-alt2.x86_64 buildroot fail found paths to buildroot: /usr/lib64/grass-7.2.2/demolocation/.grassrc72: GISDBASE: /usr/src/tmp/grass-buildroot/usr/grass-7.2.2
cas grass-7.2.2-alt2.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/grass.desktop: hint: value "Education;Science;Geoscience;Geography;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
cas grub-customizer-5.0.6-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/grub-customizer.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).
cas grub-customizer-5.0.6-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/grub-customizer.desktop: hint: value "System;Settings;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
cas guake-0.8.12-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/guake.desktop: hint: value "GNOME;GTK;System;Utility;TerminalEmulator;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
cas guake-0.8.12-alt1.x86_64 freedesktop-desktop-file-proposed-patch warn Please, apply the repocop patch for /usr/share/applications/guake.desktop.
cas iceb-18.2-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/i_admint.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).
Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/startxbu.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).
cas iceb-18.2-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/i_admint.desktop: warning: value "Ukrainian bookkeeping suite of programs iceB" for key "Comment" in group "Desktop Entry" looks redundant with value "Ukrainian bookkeeping suite of programs iceB" of key "Name"
desktop-file-validate utility printed the following message(s): /usr/share/applications/startxbu.desktop: warning: value "Ukrainian bookkeeping suite of programs iceB" for key "Comment" in group "Desktop Entry" looks redundant with value "Ukrainian bookkeeping suite of programs iceB" of key "Name"
cas iceb-18.2-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.
cas iceb-18.2-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/bin/spec conflicts with the package python-module-spec-1.4.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas icon-theme-bespin-0.1.0.1658-alt1.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.
cas installed-db-office-server-1.4-alt13.noarch missing-url info Missing Url: in a package.
cas installed-db-office-server-mediawiki-1.4-alt13.noarch missing-url info Missing Url: in a package.
cas installed-db-office-server-moodle-1.4-alt13.noarch missing-url info Missing Url: in a package.
cas installed-db-office-server-owncloud-1.4-alt13.noarch missing-url info Missing Url: in a package.
cas installed-db-office-server-rujel-1.4-alt13.noarch missing-url info Missing Url: in a package.
cas installer-distro-school-server-stage2-7.0-alt9.noarch rpm-filesystem-conflict-file-file warn Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/preinstall.d/80-setup-user-groups conflict 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.
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-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.
Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list conflict 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/20-alterator-menu.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 (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 installer-distro-chainmail-stage2-3.0.0-alt8.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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 installer-distro-desktop-stage2-5.0-alt23.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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 installer-distro-junior-stage2-8.1-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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 installer-distro-lxdesktop-stage2-6.0-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (6 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 (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 installer-distro-server-light-stage2-8.0-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-simply-linux-stage2-8.3-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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 installer-distro-tablet-stage2-6.0-alt3.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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 installer-distro-token-desktop-stage2-0.1.1-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.
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 (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.
Files /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict 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.
cas jackbeat-0.7.6-alt2.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/jackbeat.desktop: error: value "0.7.6" for key "Version" in group "Desktop Entry" is not a known version
/usr/share/applications/jackbeat.desktop: error: (will be fatal in the future): value item "Audio" in key "Categories" in group "Desktop Entry" requires another category to be present among the following categories: AudioVideo
/usr/share/applications/jackbeat.desktop: hint: value item "Midi" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: AudioVideo;Audio
/usr/share/applications/jackbeat.desktop: hint: value item "Sequencer" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: AudioVideo;Audio
/usr/share/applications/jackbeat.desktop: error: value "Audio;Midi;Sequencer;X-Alsa;X-Jack;Gtk;" for key "Categories" in group "Desktop Entry" contains an unregistered value "Gtk"; values extending the format should start with "X-"
cas jitsi-2.11.5553-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.
cas juffed-0.10-alt1.4.x86_64 altlinux-policy-shared-lib-contains-devel-so info SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libjuff.so but just /usr/lib64/libjuff.so.0.10. According to SharedLibs Policy Draft, symlink /usr/lib64/libjuff.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/libjuff.so to \%files of juffed-0.10-alt1.4.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/libjuffed-engine-qsci.so but just /usr/lib64/libjuffed-engine-qsci.so.0.10. According to SharedLibs Policy Draft, symlink /usr/lib64/libjuffed-engine-qsci.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/libjuffed-engine-qsci.so to \%files of juffed-0.10-alt1.4.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.
cas juffed-0.10-alt1.4.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/juffed.desktop: warning: value "Advanced text editor" for key "Comment" in group "Desktop Entry" looks redundant with value "Advanced text editor" of key "GenericName"
/usr/share/applications/juffed.desktop: warning: value "??????????? ????????? ????????" for key "Comment[ru]" in group "Desktop Entry" looks redundant with value "??????????? ????????? ????????" of key "GenericName[ru]"
/usr/share/applications/juffed.desktop: warning: value "Zaawansowany edytor tekstu" for key "Comment[pl]" in group "Desktop Entry" looks redundant with value "Zaawansowany edytor tekstu" of key "GenericName[pl]"
/usr/share/applications/juffed.desktop: warning: value "Ein erweiterter Texteditor" for key "Comment[de]" in group "Desktop Entry" looks redundant with value "Ein erweiterter Texteditor" of key "GenericName[de]"
/usr/share/applications/juffed.desktop: warning: value "Un avanc? ?diteur de texte" for key "Comment[fr]" in group "Desktop Entry" looks redundant with value "Un avanc? ?diteur de texte" of key "GenericName[fr]"
/usr/share/applications/juffed.desktop: warning: value "????????" for key "Comment[zh_CN]" in group "Desktop Entry" looks redundant with value "????????" of key "GenericName[zh_CN]"
/usr/share/applications/juffed.desktop: warning: value "Pokro?il? textov? editor" for key "Comment[sk]" in group "Desktop Entry" looks redundant with value "Pokro?il? textov? editor" of key "GenericName[sk]"
cas juffed-0.10-alt1.4.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.
cas juffed-0.10-alt1.4.x86_64 missing-url info Missing Url: in a package.
cas juffed-debuginfo-0.10-alt1.4.x86_64 missing-url info Missing Url: in a package.
cas juffed-devel-0.10-alt1.4.noarch missing-url info Missing Url: in a package.
cas kbfx-0.4.9.3.1-alt11.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/kde/applications/kde/kbfxconfigapp.desktop: warning: value "????????? KBFX" for key "Comment[ru]" in group "Desktop Entry" looks redundant with value "????????? KBFX" of key "Name[ru]"
cas kbookocr-2.1.0-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/KBookocr.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).
cas kbookocr-2.1.0-alt2.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/KBookocr.desktop: error: value "1.4.1" for key "Version" in group "Desktop Entry" is not a known version
cas kde4-styles-bespin-0.1.0.1658-alt1.src specfile-macros-get_dep-is-deprecated experimental Versioned Requires: foo >= %{get_dep something} using %get_dep and %get_version macros on a library are deprecated by set:versions. You probably should drop %get_dep/%get_version Requires: to avoid RPM database pollution.
cas kde4-styles-bespin-kdm-0.1.0.1658-alt1.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.
cas kde4-styles-bespin-ksplash-0.1.0.1658-alt1.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.
cas kdvdcreator-0.3.2-alt1.x86_64 desktop-exec-fill-code warn kdvdcreator.desktop: found MimeType= entry, but to handle it properly you have to declare one of %f,%F,%u,%U in Exec= entry. Note that %m is deprecated. See http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-1.0.html#exec-variables
cas kdvdcreator-0.3.2-alt1.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/kde4/kdvdcreator.desktop: warning: key "Encoding" in group "Desktop Entry" is deprecated
/usr/share/applications/kde4/kdvdcreator.desktop: warning: value "Qt;KDE;Application;AudioVideo;Multimedia" for key "Categories" in group "Desktop Entry" contains a deprecated value "Application"
/usr/share/applications/kde4/kdvdcreator.desktop: error: value "Qt;KDE;Application;AudioVideo;Multimedia" for key "Categories" in group "Desktop Entry" contains an unregistered value "Multimedia"; values extending the format should start with "X-"
cas kmymoney-4.8.1.1-alt1.src specfile-macros-get_dep-is-deprecated experimental Versioned Requires: foo >= %{get_dep something} using %get_dep and %get_version macros on a library are deprecated by set:versions. You probably should drop %get_dep/%get_version Requires: to avoid RPM database pollution.
cas kmymoney-4.8.1.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.
cas kmymoney-4.8.1.1-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "Personal Finance Manager" for key "Comment" in group "Desktop Entry" looks redundant with value "Personal Finance Manager" of key "GenericName"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "Li?nni upravlja? finansija" for key "Comment[bs]" in group "Desktop Entry" looks redundant with value "Li?nni upravlja? finansija" of key "GenericName[bs]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "Gestor de les finances personals" for key "Comment[ca]" in group "Desktop Entry" looks redundant with value "Gestor de les finances personals" of key "GenericName[ca]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "Gestor de les finances personals" for key "Comment[ca@valencia]" in group "Desktop Entry" looks redundant with value "Gestor de les finances personals" of key "GenericName[ca@valencia]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "Styring af privat?konomi" for key "Comment[da]" in group "Desktop Entry" looks redundant with value "Styring af privat?konomi" of key "GenericName[da]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "Pers?nliche Finanzenverwaltung" for key "Comment[de]" in group "Desktop Entry" looks redundant with value "Pers?nliche Finanzenverwaltung" of key "GenericName[de]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "?????????? ???????????? ???????????" for key "Comment[el]" in group "Desktop Entry" looks redundant with value "?????????? ???????????? ???????????" of key "GenericName[el]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "Personal Finance Manager" for key "Comment[en_GB]" in group "Desktop Entry" looks redundant with value "Personal Finance Manager" of key "GenericName[en_GB]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "Gestor de finanzas personales" for key "Comment[es]" in group "Desktop Entry" looks redundant with value "Gestor de finanzas personales" of key "GenericName[es]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "Isiklike rahaasjade haldur" for key "Comment[et]" in group "Desktop Entry" looks redundant with value "Isiklike rahaasjade haldur" of key "GenericName[et]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "Finantza pertsonalen kudeatzailea" for key "Comment[eu]" in group "Desktop Entry" looks redundant with value "Finantza pertsonalen kudeatzailea" of key "GenericName[eu]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "Henkil?kohtainen taloushallinta" for key "Comment[fi]" in group "Desktop Entry" looks redundant with value "Henkil?kohtainen taloushallinta" of key "GenericName[fi]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "Gestionnaire de finances personnelles" for key "Comment[fr]" in group "Desktop Entry" looks redundant with value "Gestionnaire de finances personnelles" of key "GenericName[fr]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "Xestor das finanzas persoais" for key "Comment[gl]" in group "Desktop Entry" looks redundant with value "Xestor das finanzas persoais" of key "GenericName[gl]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "Szem?lyes p?nz?gyi kezel?" for key "Comment[hu]" in group "Desktop Entry" looks redundant with value "Szem?lyes p?nz?gyi kezel?" of key "GenericName[hu]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "Gestore delle finanze personali" for key "Comment[it]" in group "Desktop Entry" looks redundant with value "Gestore delle finanze personali" of key "GenericName[it]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "?????? ????? ?????????" for key "Comment[kk]" in group "Desktop Entry" looks redundant with value "?????? ????? ?????????" of key "GenericName[kk]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "???????? ????? ??????????" for key "Comment[mr]" in group "Desktop Entry" looks redundant with value "???????? ????? ??????????" of key "GenericName[mr]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "Geldsaken plegen" for key "Comment[nds]" in group "Desktop Entry" looks redundant with value "Geldsaken plegen" of key "GenericName[nds]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "Zarz?dzanie finansami osobistymi" for key "Comment[pl]" in group "Desktop Entry" looks redundant with value "Zarz?dzanie finansami osobistymi" of key "GenericName[pl]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "Gestor de Finan?as Pessoais" for key "Comment[pt]" in group "Desktop Entry" looks redundant with value "Gestor de Finan?as Pessoais" of key "GenericName[pt]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "Gerenciador de Finan?as Pessoais" for key "Comment[pt_BR]" in group "Desktop Entry" looks redundant with value "Gerenciador de Finan?as Pessoais" of key "GenericName[pt_BR]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "???? ????????" for key "Comment[ru]" in group "Desktop Entry" looks redundant with value "???? ????????" of key "GenericName[ru]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "Osobn? mana??r financi?" for key "Comment[sk]" in group "Desktop Entry" looks redundant with value "Osobn? mana??r financi?" of key "GenericName[sk]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "Hemekonomihantering" for key "Comment[sv]" in group "Desktop Entry" looks redundant with value "Hemekonomihantering" of key "GenericName[sv]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "Ki?isel Finans Y?neticisi" for key "Comment[tr]" in group "Desktop Entry" looks redundant with value "Ki?isel Finans Y?neticisi" of key "GenericName[tr]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "??????? ???????? ????????" for key "Comment[ug]" in group "Desktop Entry" looks redundant with value "??????? ???????? ????????" of key "GenericName[ug]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "???????? ????????? ?????????" for key "Comment[uk]" in group "Desktop Entry" looks redundant with value "???????? ????????? ?????????" of key "GenericName[uk]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "xxPersonal Finance Managerxx" for key "Comment[x-test]" in group "Desktop Entry" looks redundant with value "xxPersonal Finance Managerxx" of key "GenericName[x-test]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "???????" for key "Comment[zh_CN]" in group "Desktop Entry" looks redundant with value "???????" of key "GenericName[zh_CN]"
/usr/share/applications/kde4/org.kde.kmymoney.desktop: warning: value "????????" for key "Comment[zh_TW]" in group "Desktop Entry" looks redundant with value "????????" of key "GenericName[zh_TW]"
cas kontakter-0.2-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.
cas kontakter-server-0.2-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.
cas ktoblzcheck-1.49-alt1.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
cas kunit-0.5-alt10.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/kde/kunit.desktop: warning: value "Units converter" for key "Comment" in group "Desktop Entry" looks redundant with value "Units converter" of key "GenericName"
/usr/share/applications/kde/kunit.desktop: warning: value "????????? ?????????? ???????" for key "Comment[ru]" in group "Desktop Entry" looks redundant with value "????????? ?????????? ???????" of key "GenericName[ru]"
cas laptop-mode-tools-1.72.2-alt1.noarch executable-manpage fail Manual pages are not meant to be executed.
cas laptop-mode-tools-1.72.2-alt1.noarch uncompressed-manpages info Package contains uncompressed manual pages.
cas lazarus-1.8.0-alt1.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/lazarus.desktop: error: file contains group "Property::X-KDE-NativeExtension", but groups extending the format should start with "X-"
cas lazarus-1.8.0-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.
cas libarpack-ng-devel-3.5.0-alt1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib64/libarpack.so is different from the same symlink in the package libarpack-devel-96-alt11.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.
cas libchipcard-tools-5.0.4-alt1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.
cas libchipcard-tools-5.0.4-alt1.x86_64 init-lsb fail /etc/rc.d/init.d/chipcardd: not systemd compatible: lsb init header missing and chipcardd.service is not present. See http://www.altlinux.org/Services_Policy for details.
cas libclam-devel-1.4.0-alt1.x86_64 buildroot fail found paths to buildroot: /usr/lib64/pkgconfig/clam_core.pc: prefix = /usr/src/tmp/libclam-buildroot/usr /usr/lib64/pkgconfig/clam_audioio.pc: prefix = /usr/src/tmp/libclam-buildroot/usr /usr/lib64/pkgconfig/clam_processing.pc: prefix = /usr/src/tmp/libclam-buildroot/usr
cas libcwiid-utils-0.6.00-alt2.20100505gitfadf11e.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/wmgui.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).
cas libcwiid-utils-0.6.00-alt2.20100505gitfadf11e.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/wmgui.desktop: hint: value "GTK;Utility;System;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
cas libgnomeprint-2.18.8-alt4.x86_64 missing-url info Missing Url: in a package.
cas libgnomeprint-debuginfo-2.18.8-alt4.x86_64 missing-url info Missing Url: in a package.
cas libgnomeprint-devel-2.18.8-alt4.x86_64 missing-url info Missing Url: in a package.
cas libgnomeprint-devel-doc-2.18.8-alt4.noarch missing-url info Missing Url: in a package.
cas libgnomeprintui-2.18.6-alt2.x86_64 big-changelog info Package contains big ChangeLog. Gzip it.
cas libgnucash-2.6.19-alt1.x86_64 altlinux-policy-shared-lib-contains-devel-so info SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libgnc-backend-sql.so but just /usr/lib64/libgnc-backend-sql.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libgnc-backend-sql.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/libgnc-backend-sql.so to \%files of libgnucash-2.6.19-alt1.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/libgnc-backend-xml-utils.so but just /usr/lib64/libgnc-backend-xml-utils.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libgnc-backend-xml-utils.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/libgnc-backend-xml-utils.so to \%files of libgnucash-2.6.19-alt1.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/libgnc-business-ledger.so but just /usr/lib64/libgnc-business-ledger.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libgnc-business-ledger.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/libgnc-business-ledger.so to \%files of libgnucash-2.6.19-alt1.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/libgnc-core-utils.so but just /usr/lib64/libgnc-core-utils.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libgnc-core-utils.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/libgnc-core-utils.so to \%files of libgnucash-2.6.19-alt1.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/libgnc-gnome.so but just /usr/lib64/libgnc-gnome.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libgnc-gnome.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/libgnc-gnome.so to \%files of libgnucash-2.6.19-alt1.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/libgnc-module.so but just /usr/lib64/libgnc-module.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libgnc-module.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/libgnc-module.so to \%files of libgnucash-2.6.19-alt1.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/libgnc-qof.so but just /usr/lib64/libgnc-qof.so.1.0.4. According to SharedLibs Policy Draft, symlink /usr/lib64/libgnc-qof.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/libgnc-qof.so to \%files of libgnucash-2.6.19-alt1.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.
cas libgnucash-devel-2.6.19-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.
cas libgpsim-0.30.0-alt1.x86_64 big-changelog info Package contains big ChangeLog. Gzip it.
cas libgtk-engines-default-common-2.20.2-alt3.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.
cas libgtk-engines-default-common-2.20.2-alt3.x86_64 big-changelog info Package contains big ChangeLog. Gzip it.
cas libisdn-devel-0.0.1-alt1.qa1.x86_64 arch-dep-package-has-big-usr-share info The package has a significant amount of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.
cas libleatherman-1.3.0-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.
cas libmapi-2.4-alt22.zentyal23.S1.5.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 zarafa-client-7.1.15-alt17.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.
cas libmapi-debuginfo-2.4-alt22.zentyal23.S1.5.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 zarafa-client-debuginfo-7.1.15-alt17.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.
cas libpacemaker-devel-1.1.17-alt2.x86_64 arch-dep-package-has-big-usr-share info The package has a significant amount of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.
cas libpacemaker-devel-1.1.17-alt2.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/pacemaker/tests/cli/regression.sh: $ grep -A5 -B5 /tmp/ /usr/share/pacemaker/tests/cli/regression.sh desc="Allow CIB erasure with --force" cmd="cibadmin -E --force" test_assert 0 desc="Query CIB" cmd="cibadmin -Q > /tmp/$$.existing.xml" test_assert 0 desc="Set cluster option" cmd="crm_attribute -n cluster-delay -v 60s" test_assert 0 -- desc="Query new cluster option" cmd="cibadmin -Q -o crm_config | grep cib-bootstrap-options-cluster-delay" test_assert 0 desc="Query cluster options" cmd="cibadmin -Q -o crm_config > /tmp/$$.opt.xml" test_assert 0 desc="Set no-quorum policy" cmd="crm_attribute -n no-quorum-policy -v ignore" test_assert 0 -- desc="Delete nvpair" cmd="cibadmin -D -o crm_config --xml-text ''" test_assert 0 desc="Create operaton should fail" cmd="cibadmin -C -o crm_config --xml-file /tmp/$$.opt.xml" test_assert 76 desc="Modify cluster options section" cmd="cibadmin -M -o crm_config --xml-file /tmp/$$.opt.xml" test_assert 0 desc="Query updated cluster option" cmd="cibadmin -Q -o crm_config | grep cib-bootstrap-options-cluster-delay" test_assert 0 -- cmd="cibadmin -Q | cibadmin -5 -p 2>&1 > /dev/null" test_assert 0 # This update will fail because it has version numbers desc="Replace operation should fail" cmd="cibadmin -R --xml-file /tmp/$$.existing.xml" test_assert 205 desc="Default standby value" cmd="crm_standby -N node1 -G" test_assert 0 -- desc="Create a resource meta attribute in the parent" cmd="crm_resource -r test-clone --meta -p is-managed -v true --force" test_assert 0 desc="Copy resources" cmd="cibadmin -Q -o resources > /tmp/$$.resources.xml" test_assert 0 0 desc="Delete resource paremt meta attribute (force)" cmd="crm_resource -r test-clone --meta -d is-managed --force" test_assert 0 desc="Restore duplicates" cmd="cibadmin -R -o resources --xml-file /tmp/$$.resources.xml" test_assert 0 desc="Delete resource child meta attribute" cmd="crm_resource -r test-primitive --meta -d is-managed" test_assert 0 rm -f /tmp/$$.existing.xml /tmp/$$.resources.xml } function test_dates() { desc="2014-01-01 00:30:00 - 1 Hour" cmd="iso8601 -d '2014-01-01 00:30:00Z' -D P-1H -E '2013-12-31 23:30:00Z'" -- export CIB_user=betteridea desc="$CIB_user: Query configuration - explicit deny" cmd="cibadmin -Q" test_assert 0 0 CIB_user=root cibadmin -Q > /tmp/$$.haxor.xml CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin --delete --xml-text '' CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin -Ql export CIB_user=niceguy desc="$CIB_user: Replace - remove acls" cmd="cibadmin --replace --xml-file /tmp/$$.haxor.xml" test_assert 13 0 CIB_user=root cibadmin -Q > /tmp/$$.haxor.xml CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin -C -o resources --xml-text '' CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin -Ql desc="$CIB_user: Replace - create resource" cmd="cibadmin --replace --xml-file /tmp/$$.haxor.xml" test_assert 13 0 CIB_user=root cibadmin -Q > /tmp/$$.haxor.xml CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" crm_attribute -n enable-acl -v false CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin -Ql desc="$CIB_user: Replace - modify attribute (deny)" cmd="cibadmin --replace --xml-file /tmp/$$.haxor.xml" test_assert 13 0 CIB_user=root cibadmin -Q > /tmp/$$.haxor.xml CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin --replace --xml-text '' CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin -Ql desc="$CIB_user: Replace - delete attribute (deny)" cmd="cibadmin --replace --xml-file /tmp/$$.haxor.xml" test_assert 13 0 CIB_user=root cibadmin -Q > /tmp/$$.haxor.xml CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin --modify --xml-text '' CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin -Ql desc="$CIB_user: Replace - create attribute (deny)" cmd="cibadmin --replace --xml-file /tmp/$$.haxor.xml" test_assert 13 0 rm -rf /tmp/$$.haxor.xml CIB_user=bob CIB_user=root cibadmin -Q > /tmp/$$.haxor.xml CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin --modify --xml-text '' CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin -Ql desc="$CIB_user: Replace - create attribute (allow)" cmd="cibadmin --replace -o resources --xml-file /tmp/$$.haxor.xml" test_assert 0 0 CIB_user=root cibadmin -Q > /tmp/$$.haxor.xml CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin --modify --xml-text '' CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin -Ql desc="$CIB_user: Replace - modify attribute (allow)" cmd="cibadmin --replace -o resources --xml-file /tmp/$$.haxor.xml" test_assert 0 0 CIB_user=root cibadmin -Q > /tmp/$$.haxor.xml CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin --replace -o resources --xml-text '' CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin -Ql desc="$CIB_user: Replace - delete attribute (allow)" cmd="cibadmin --replace -o resources --xml-file /tmp/$$.haxor.xml" test_assert 0 0 } function test_acls() { export CIB_shadow_dir=$test_home $VALGRIND_CMD crm_shadow --batch --force --create-empty $shadow --validate-with pacemaker-1.3 2>&1 export CIB_shadow=$shadow cat </tmp/$$.acls.xml -- EOF desc="Configure some ACLs" cmd="cibadmin -M -o acls --xml-file /tmp/$$.acls.xml" test_assert 0 desc="Enable ACLs" cmd="crm_attribute -n enable-acl -v true" test_assert 0 -- export PCMK_stderr=1 cibadmin -C -o resources --xml-text '' cibadmin -C -o resources --xml-text '' cibadmin -C -o constraints --xml-text '' cibadmin -Q > /tmp/$$.good-1.2.xml desc="Try to make resulting CIB invalid (enum violation)" cmd="cibadmin -M -o constraints --xml-text ''" test_assert 203 sed 's|"start"|"break"|' /tmp/$$.good-1.2.xml > /tmp/$$.bad-1.2.xml desc="Run crm_simulate with invalid CIB (enum violation)" cmd="crm_simulate -x /tmp/$$.bad-1.2.xml -S" test_assert 126 0 desc="Try to make resulting CIB invalid (unrecognized validate-with)" cmd="cibadmin -M --xml-text ''" test_assert 203 sed 's|"pacemaker-1.2"|"pacemaker-9999.0"|' /tmp/$$.good-1.2.xml > /tmp/$$.bad-1.2.xml desc="Run crm_simulate with invalid CIB (unrecognized validate-with)" cmd="crm_simulate -x /tmp/$$.bad-1.2.xml -S" test_assert 126 0 desc="Try to make resulting CIB invalid, but possibly recoverable (valid with X.Y+1)" cmd="cibadmin -C -o configuration --xml-text ''" test_assert 203 sed 's||\0|' /tmp/$$.good-1.2.xml > /tmp/$$.bad-1.2.xml desc="Run crm_simulate with invalid, but possibly recoverable CIB (valid with X.Y+1)" cmd="crm_simulate -x /tmp/$$.bad-1.2.xml -S" test_assert 0 0 sed 's|\s\s*validate-with="[^"]*"||' /tmp/$$.good-1.2.xml > /tmp/$$.bad-1.2.xml desc="Make resulting CIB valid, although without validate-with attribute" cmd="cibadmin -R --xml-file /tmp/$$.bad-1.2.xml" test_assert 0 desc="Run crm_simulate with valid CIB, but without validate-with attribute" cmd="crm_simulate -x /tmp/$$.bad-1.2.xml -S" test_assert 0 0 # this will just disable validation and accept the config, outputting # validation errors sed -e 's|\s\s*validate-with="[^"]*"||' \ -e 's|\(\s\s*epoch="[^"]*\)"|\10"|' -e 's|"start"|"break"|' \ /tmp/$$.good-1.2.xml > /tmp/$$.bad-1.2.xml desc="Make resulting CIB invalid, and without validate-with attribute" cmd="cibadmin -R --xml-file /tmp/$$.bad-1.2.xml" test_assert 0 desc="Run crm_simulate with invalid CIB, also without validate-with attribute" cmd="crm_simulate -x /tmp/$$.bad-1.2.xml -S" test_assert 0 0 rm -f /tmp/$$.good-1.2.xml /tmp/$$.bad-1.2.xml } for t in $tests; do echo "Testing $t" test_$t > $test_home/regression.$t.out -- -e 's/Created new pacemaker-.* configuration/Created new pacemaker configuration/'\ -e 's/.*__xml_acl_check/__xml_acl_check/g'\ -e 's/.*__xml_acl_post_process/__xml_acl_post_process/g'\ -e 's/.*error: unpack_resources:/error: unpack_resources:/g'\ -e 's/ last-rc-change=\"[0-9]*\"//'\ -e 's|^/tmp/[0-9][0-9]*\.||'\ -e 's/^Entity: line [0-9][0-9]*: //'\ -e 's/schemas\.c:\([0-9][0-9]*\)/schemas.c:NNN/' \ -e 's/\(validation ([0-9][0-9]* of \)[0-9][0-9]*\().*\)/\1X\2/' $test_home/regression.$t.out if [ $do_save = 1 ]; then
cas libsope-devel-3.2.10-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package libgnustep-gdl2-devel-0.12.0-alt5.svn20130819.1.x86_64, for example, /usr/include/EOControl/EOArrayDataSource.h (15 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.
cas libsope-devel-3.2.10-alt2.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib64/libEOControl.so is different from the same symlink in the package libgnustep-gdl2-devel-0.12.0-alt5.svn20130819.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/libWOExtensions.so is different from the same symlink in the package libgnustep-gsweb-devel-1.3.0-alt2.svn20131221.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/libXmlRpc.so is different from the same symlink in the package libxmlrpcxx-devel-0.7-alt2.git20100306.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.
cas libv8-nodejs-5.1.281.75-alt1.x86_64 big-changelog info Package contains big ChangeLog. Gzip it.
cas libwbclient-DC-4.6.12-alt2.S1.x86_64 alt-alternatives-vs-ghost info Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-sssd-1.15.3-alt5.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0.13 is an alternative in package libwbclient-4.6.12-alt2.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.13.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-4.6.12-alt2.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0.13 is an alternative in package libwbclient-DC-4.6.12-alt2.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.13.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-DC-4.6.12-alt2.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.
cas libwbclient-DC-debuginfo-4.6.12-alt2.S1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.13.debug is different from the same symlink in the package libwbclient-debuginfo-4.6.12-alt2.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.
value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-sssd-debuginfo-1.15.3-alt5.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.
value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-debuginfo-4.6.12-alt2.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.
cas libwbclient-DC-devel-4.6.12-alt2.S1.x86_64 alt-alternatives-vs-ghost info Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-sssd-devel-1.15.3-alt5.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-DC-devel-4.6.12-alt2.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-devel-4.6.12-alt2.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.
cas libwvstreams-devel-doc-4.6.1-alt3.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.
cas logisim-2.7.1-alt1.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/logisim.desktop: hint: value "Education;Science;ComputerScience;Java;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
cas logisim-2.7.1-alt1.noarch iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.
cas luckybackup-0.4.9-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.
cas luckybackup-0.4.9-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/luckybackup-gnome-su.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).
Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/luckybackup.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).
cas luckybackup-0.4.9-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.
cas lxde-icon-theme-0.5.1-alt1.noarch obsolete-call-in-post-gtk-update-icon-cache warn gtk-update-icon-cache call in post/postun is deprecated
cas mazen-1.0.1-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.
cas mediaelch-2.4-alt1.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/MediaElch.desktop: error: value "2.4" for key "Version" in group "Desktop Entry" is not a known version
cas mediaelch-2.4-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.
cas minetest-0.4.16-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.
cas minetest-0.4.16-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/minetest.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).
cas minetest-server-0.4.16-alt1.x86_64 systemd-but-no-native-init warn The package have native systemd file(s) but no SysV init scripts.
cas mint-translations-2018.01.06-alt1.noarch 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.
cas modem-manager-gui-0.0.18-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/modem-manager-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).
cas modem-manager-gui-0.0.18-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.
cas mpi-selector-1.0.3-alt3.noarch missing-url info Missing Url: in a package.
cas netactview-0.6.4-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.
cas netsurf-3.5-alt2.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/netsurf.desktop: error: file contains key "MultipleArgs" in group "Desktop Entry", but keys extending the format should start with "X-"
cas netsurf-3.5-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.
cas ninja-ide-2.3-alt2.noarch altlinux-python-test-is-packaged experimental /usr/lib/python2.7/site-packages/ninja_tests/core/examples/__init__.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/ninja_tests/core/examples/__init__.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/ninja_tests/core/examples/__init__.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/ninja_tests/core/examples/file_for_tests.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/ninja_tests/core/examples/file_for_tests.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/ninja_tests/core/examples/file_for_tests.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
cas ninja-ide-2.3-alt2.noarch iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.
cas notepadqq-1.2.0-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/notepadqq.desktop: hint: value "Development;Utility;TextEditor;" 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/notepadqq.desktop: warning: key "OnlyShowIn" in group "Desktop Action Window" is deprecated
/usr/share/applications/notepadqq.desktop: warning: key "OnlyShowIn" in group "Desktop Action Document" is deprecated
cas nss-ldapd-0.9.8-alt1.x86_64 init-lsb warn /etc/rc.d/init.d/nslcd: lsb init header missing. See http://www.altlinux.org/Services_Policy for details.
cas nss-ldapd-0.9.8-alt1.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.
cas nss-ldapd-0.9.8-alt1.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/nslcd.conf to \%_tmpfilesdir/.
cas octave-4.2.1-alt3.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.
cas octave-4.2.1-alt3.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/www.octave.org-octave.desktop: hint: value "Education;Science;Math;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
cas ohai-doc-14.0.1-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package chef-doc-12.15.11-alt1.noarch, for example, /usr/share/ri/site/Chef/cdesc-Chef.ri (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/ri/site/RbConfig/cdesc-RbConfig.ri conflicts with the package ruby-amqp-doc-1.8.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Chef/cdesc-Chef.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri conflicts with the package ruby-dalli-doc-2.7.6-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri /usr/share/ri/site/Win32/cdesc-Win32.ri conflict with the package ruby-facter-doc-2.0.1-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri conflicts with the package ruby-spoon-doc-0.0.6-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.
cas omnibus-software-4.0.0-alt1.gita5aef20.src unmet-dependency-build-missing-package fail build dependency omnibus not found.
cas onboard-1.4.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.
cas onboard-1.4.1-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/onboard-settings.desktop: hint: value "Settings;Accessibility;Utility;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
cas opencc-1.0.3-alt1.x86_64 arch-dep-package-has-big-usr-share info The package has a significant amount of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.
cas opencc-doc-1.0.3-alt1.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.
cas openchange-devel-2.4-alt22.zentyal23.S1.5.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 zarafa-devel-7.1.15-alt17.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.
cas openchange-ocsmanager-2.4-alt22.zentyal23.S1.5.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.
cas openerp-7.0-alt4.20140326.noarch altlinux-python-test-is-packaged info /usr/lib/python2.7/site-packages/openerp/addons/account/test/test_edi_invoice.yml: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/account/test/test_parent_structure.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/account/test/test_parent_structure.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/account/test/test_parent_structure.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/account/test/test_parent_structure.yml: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/account/tests/test_search.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/account/tests/test_search.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/account/tests/test_search.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/account/tests/test_tax.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/account/tests/test_tax.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/account/tests/test_tax.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/account_followup/tests/test_account_followup.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/account_followup/tests/test_account_followup.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/account_followup/tests/test_account_followup.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base/test/test_auth.yml: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base/test/test_context.xml: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base/test/test_ir_rule.yml: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base/test/test_osv_expression.yml: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base/tests/test_base.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base/tests/test_base.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base/tests/test_base.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base/tests/test_expression.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base/tests/test_expression.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base/tests/test_expression.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base/tests/test_ir_attachment.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base/tests/test_ir_attachment.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base/tests/test_ir_attachment.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base/tests/test_ir_values.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base/tests/test_ir_values.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base/tests/test_ir_values.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base/tests/test_menu.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base/tests/test_menu.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base/tests/test_menu.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base/tests/test_search.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base/tests/test_search.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base/tests/test_search.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base/tests/test_views.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base/tests/test_views.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base/tests/test_views.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base_calendar/test/test_crm_recurrent_meeting_case2.yml: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base_import/tests/test_cases.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base_import/tests/test_cases.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/base_import/tests/test_cases.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/email_template/tests/test_mail.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/email_template/tests/test_mail.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/email_template/tests/test_mail.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/hr_contract/test/test_hr_contract.yml: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/hr_evaluation/test/test_hr_evaluation.yml: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/hr_holidays/test/test_hr_holiday.yml: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/hr_timesheet/test/test_hr_timesheet.yml: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/hr_timesheet_invoice/test/test_hr_timesheet_invoice.yml: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/hr_timesheet_invoice/test/test_hr_timesheet_invoice_no_prod_tax.yml: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/hr_timesheet_sheet/test/test_hr_timesheet_sheet.yml: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/lunch/tests/test_lunch.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/lunch/tests/test_lunch.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/lunch/tests/test_lunch.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/mail/tests/test_invite.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/mail/tests/test_invite.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/mail/tests/test_invite.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/mail/tests/test_mail_base.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/mail/tests/test_mail_base.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/mail/tests/test_mail_base.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/mail/tests/test_mail_features.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/mail/tests/test_mail_features.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/mail/tests/test_mail_features.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/mail/tests/test_mail_gateway.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/mail/tests/test_mail_gateway.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/mail/tests/test_mail_gateway.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/mail/tests/test_mail_message.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/mail/tests/test_mail_message.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/mail/tests/test_mail_message.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/mail/tests/test_message_read.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/mail/tests/test_message_read.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/mail/tests/test_message_read.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/membership/test/test_membership.yml: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/mrp/tests/test_multicompany.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/mrp/tests/test_multicompany.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/mrp/tests/test_multicompany.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/mrp_repair/test/test_mrp_repair_afterinv.yml: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/mrp_repair/test/test_mrp_repair_b4inv.yml: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/mrp_repair/test/test_mrp_repair_cancel.yml: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/mrp_repair/test/test_mrp_repair_fee.yml: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/mrp_repair/test/test_mrp_repair_noneinv.yml: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/note/tests/test_note.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/note/tests/test_note.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/note/tests/test_note.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/portal/tests/test_portal.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/portal/tests/test_portal.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/portal/tests/test_portal.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/portal_project/tests/test_access_rights.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/portal_project/tests/test_access_rights.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/portal_project/tests/test_access_rights.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/portal_project_issue/tests/test_access_rights.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/portal_project_issue/tests/test_access_rights.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/portal_project_issue/tests/test_access_rights.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/product/tests/test_uom.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/product/tests/test_uom.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/product/tests/test_uom.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/stock/tests/test_multicompany.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/stock/tests/test_multicompany.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/stock/tests/test_multicompany.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/web/tests/test_dataset.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/web/tests/test_dataset.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/web/tests/test_dataset.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/web/tests/test_js.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/web/tests/test_js.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/web/tests/test_js.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/web/tests/test_menu.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/web/tests/test_menu.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/web/tests/test_menu.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/web/tests/test_serving_base.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/web/tests/test_serving_base.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/web/tests/test_serving_base.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_exceptions/__init__.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_exceptions/__init__.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_exceptions/__init__.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_exceptions/__openerp__.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_exceptions/__openerp__.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_exceptions/__openerp__.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_exceptions/ir.model.access.csv: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_exceptions/models.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_exceptions/models.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_exceptions/models.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_exceptions/view.xml: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_impex/__init__.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_impex/__init__.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_impex/__init__.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_impex/__openerp__.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_impex/__openerp__.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_impex/__openerp__.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_impex/ir.model.access.csv: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_impex/models.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_impex/models.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_impex/models.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/__init__.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/__init__.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/__init__.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/contacts.json: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/contacts_big.json: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/test_export.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/test_export.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/test_export.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/test_import.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/test_import.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/test_import.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/test_load.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/test_load.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/test_load.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_limits/__init__.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_limits/__init__.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_limits/__init__.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_limits/__openerp__.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_limits/__openerp__.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_limits/__openerp__.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_limits/ir.model.access.csv: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_limits/models.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_limits/models.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_limits/models.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_uninstall/__init__.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_uninstall/__init__.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_uninstall/__init__.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_uninstall/__openerp__.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_uninstall/__openerp__.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_uninstall/__openerp__.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_uninstall/ir.model.access.csv: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_uninstall/models.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_uninstall/models.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/addons/test_uninstall/models.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_acl.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_acl.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_acl.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_basecase.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_basecase.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_basecase.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_db_cursor.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_db_cursor.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_db_cursor.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_expression.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_expression.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_expression.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_fields.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_fields.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_fields.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_ir_filters.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_ir_filters.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_ir_filters.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_ir_sequence.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_ir_sequence.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_ir_sequence.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_mail.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_misc.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_misc.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_misc.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_orm.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_orm.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_orm.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_osv.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_osv.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_osv.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_translate.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_translate.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_translate.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_uninstall.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_uninstall.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_uninstall.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_view_validation.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_view_validation.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_view_validation.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_xmlrpc.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_xmlrpc.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/tests/test_xmlrpc.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
cas openerp-7.0-alt4.20140326.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.
cas openerp-risk-management-7.0-alt4.20140326.noarch altlinux-python-test-is-packaged info /usr/lib/python2.7/site-packages/openerp/addons/risk_management/test/test_risk_management.yml: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/risk_management/tests/test_risks.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/risk_management/tests/test_risks.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/openerp/addons/risk_management/tests/test_risks.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
cas osync-1.2-alt1.noarch init-condrestart fail /etc/rc.d/init.d/osync-srv: missing condstop target. ERROR: alt-specific script %_sbindir/preun_service (used in your %preun_service macro) depends on condstop. Please, fix.
cas pacemaker-cli-1.1.17-alt2.x86_64 systemd-but-no-native-init warn The package have native systemd file(s) but no SysV init scripts.
cas pcsc-tools-gui-1.4.27-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/gscriptor.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).
cas plater-20131019-alt1.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/plater.desktop: hint: value "GNOME;GTK;Utility;Graphics;3DGraphics;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
cas pology-0.12-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.
cas postgis-2.3.3-alt2.x86_64 arch-dep-package-has-big-usr-share info The package has a significant amount of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.
cas postgresql-postgis-2.3.3-alt2.x86_64 arch-dep-package-has-big-usr-share info The package has a significant amount of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.
cas postgrey-1.37-alt1.noarch init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.
cas postgrey-1.37-alt1.noarch init-lsb fail /etc/rc.d/init.d/postgrey: not systemd compatible: lsb init header missing and postgrey.service is not present. See http://www.altlinux.org/Services_Policy for details.
cas postgrey-1.37-alt1.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.
cas pronsole-20131019-alt1.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/pronsole.desktop: hint: value "Utility;Graphics;3DGraphics;ConsoleOnly;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
cas pronsole-20131019-alt1.noarch iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.
cas pronterface-20131019-alt1.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/pronterface.desktop: hint: value "GNOME;GTK;Utility;Graphics;3DGraphics;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
cas pronterface-20131019-alt1.noarch iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.
cas pronterface-20131019-alt1.noarch symlink-extra-slash info /usr/share/pronterface/locale:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
cas pysycache-3.1-alt2.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/pysycachenf.desktop: hint: value "Game;KidsGame;Education;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
desktop-file-validate utility printed the following message(s): /usr/share/applications/pysycache.desktop: hint: value "Game;KidsGame;Education;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
desktop-file-validate utility printed the following message(s): /usr/share/applications/pysycache-admin.desktop: hint: value "Game;KidsGame;Education;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
cas pysycache-3.1-alt2.noarch iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.
cas python-module-PyQwt-devel-5.2.0-alt3.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.
cas python-module-nose2-0.6.5-alt1.1.noarch altlinux-python-test-is-packaged info /usr/lib/python2.7/site-packages/nose2/tests/functional/test_attrib_plugin.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_attrib_plugin.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_attrib_plugin.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_collect_plugin.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_collect_plugin.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_collect_plugin.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_coverage.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_coverage.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_coverage.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_decorators.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_decorators.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_decorators.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_discovery_loader.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_discovery_loader.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_discovery_loader.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_doctests_plugin.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_doctests_plugin.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_doctests_plugin.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_dundertest_plugin.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_dundertest_plugin.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_dundertest_plugin.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_eggdiscovery_loader.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_eggdiscovery_loader.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_eggdiscovery_loader.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_junitxml_plugin.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_junitxml_plugin.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_junitxml_plugin.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_layers_plugin.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_layers_plugin.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_layers_plugin.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_loading.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_loading.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_loading.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_loadtests_plugin.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_loadtests_plugin.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_loadtests_plugin.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_logcapture_plugin.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_logcapture_plugin.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_logcapture_plugin.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_main.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_main.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_main.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_mp_plugin.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_mp_plugin.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_mp_plugin.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_printhooks_plugin.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_printhooks_plugin.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_printhooks_plugin.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_session.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_session.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_session.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_such_dsl.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_such_dsl.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_such_dsl.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_util.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_util.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/functional/test_util.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_attrib_plugin.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_attrib_plugin.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_attrib_plugin.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_buffer_plugin.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_buffer_plugin.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_buffer_plugin.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_collect_plugin.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_collect_plugin.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_collect_plugin.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_collector.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_collector.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_collector.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_config.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_config.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_config.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_debugger_plugin.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_debugger_plugin.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_debugger_plugin.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_decorators.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_decorators.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_decorators.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_doctest_plugin.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_doctest_plugin.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_doctest_plugin.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_dundertest_plugin.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_dundertest_plugin.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_dundertest_plugin.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_failfast.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_failfast.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_failfast.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_functions_loader.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_functions_loader.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_functions_loader.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_generators_plugin.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_generators_plugin.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_generators_plugin.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_junitxml.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_junitxml.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_junitxml.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_layers_plugin.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_layers_plugin.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_layers_plugin.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_loader.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_loader.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_loader.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_logcapture_plugin.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_logcapture_plugin.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_logcapture_plugin.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_mp_plugin.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_mp_plugin.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_mp_plugin.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_outcomes_plugin.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_outcomes_plugin.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_outcomes_plugin.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_params_plugin.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_params_plugin.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_params_plugin.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_plugin_api.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_plugin_api.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_plugin_api.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_printhooks_plugin.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_printhooks_plugin.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_printhooks_plugin.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_prof_plugin.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_prof_plugin.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_prof_plugin.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_result.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_result.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_result.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_session.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_session.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_session.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_testcase_loader.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_testcase_loader.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_testcase_loader.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_testclass_loader.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_testclass_loader.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_testclass_loader.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_testid_plugin.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_testid_plugin.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_testid_plugin.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_util.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_util.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/nose2/tests/unit/test_util.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
cas python-module-openchange-2.4-alt22.zentyal23.S1.5.x86_64 altlinux-python-test-is-packaged info /usr/lib64/python2.7/site-packages/openchange/tests/test_mailbox.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/openchange/tests/test_mailbox.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/openchange/tests/test_mailbox.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/openchange/tests/test_migration.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/openchange/tests/test_migration.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/openchange/tests/test_migration.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/openchange/tests/test_provision.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/openchange/tests/test_provision.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/openchange/tests/test_provision.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
cas python-module-xlrd-1.1.0-alt1.noarch bin-permissions info not executable file /usr/bin/runxlrd
cas python-module-xlutils-2.0.0-alt1.noarch altlinux-python-test-is-packaged info /usr/lib/python2.7/site-packages/xlutils/tests/test_copy.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/xlutils/tests/test_copy.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/xlutils/tests/test_copy.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/xlutils/tests/test_docs.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/xlutils/tests/test_docs.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/xlutils/tests/test_docs.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/xlutils/tests/test_filter.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/xlutils/tests/test_filter.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/xlutils/tests/test_filter.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/xlutils/tests/test_save.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/xlutils/tests/test_save.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/xlutils/tests/test_save.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/xlutils/tests/test_styles.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/xlutils/tests/test_styles.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/xlutils/tests/test_styles.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/xlutils/tests/test_view.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/xlutils/tests/test_view.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/xlutils/tests/test_view.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details.
cas pyzy-0.1.0-alt3.x86_64 library-pkgnames info package contains public library which is used in external packages: name should be lib* according to http://altlinux.org/Drafts/SharedLibs
cas qcad-3.19.2.3-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/qcad.desktop: hint: value "Graphics;VectorGraphics;Engineering;Construction;2DGraphics;Science;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
cas qelectrotech-0.5-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.
cas qelectrotech-0.5-alt1.x86_64 freedesktop-categories fail Main Categories consist of those categories that every conforming desktop environment MUST support.(http://standards.freedesktop.org/menu-spec/latest/apa.html). None found in /usr/share/applications/qelectrotech.desktop. please, fix.
cas qelectrotech-0.5-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/qelectrotech.desktop: hint: value "Engineering;" for key "Categories" in group "Desktop Entry" does not contain a registered main category; application might only show up in a "catch-all" section of the application menu
/usr/share/applications/qelectrotech.desktop: warning: value "Editor v?kres? elektrick?ch obvod?" for key "Comment[cs]" in group "Desktop Entry" looks redundant with value "Editor v?kres? elektrick?ch obvod?" of key "GenericName[cs]"
cas qgoogletranslator-1.2.1-alt2.1.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/qgoogletranslator.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).
cas qgoogletranslator-1.2.1-alt2.1.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/qgoogletranslator.desktop: error: file contains key "Value" in group "Desktop Entry", but keys extending the format should start with "X-"
/usr/share/applications/qgoogletranslator.desktop: error: file contains multiple keys named "Type" in group "Desktop Entry"
cas qgoogletranslator-1.2.1-alt2.1.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.
cas qrdc-0.0.1-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/qrdc.desktop: warning: value "Qt Remote Desktop Connection" for key "Comment" in group "Desktop Entry" looks redundant with value "Qt Remote Desktop Connection" of key "GenericName"
cas qrdc-0.0.1-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.
cas rosa-crypto-tool-0.1.5-alt1.noarch freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/rosa-crypto-tool.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).
cas rosa-crypto-tool-0.1.5-alt1.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/rosa-crypto-tool.desktop: hint: value "Utility;System;" 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/rosa-crypto-tool.desktop: warning: value "" for key "Path" in group "Desktop Entry" does not look like an absolute path
/usr/share/applications/rosa-crypto-tool.desktop: warning: key "TerminalOptions" in group "Desktop Entry" is deprecated
cas rosa-imagewriter-2.6.1.0-alt2.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/rosa-imagewriter.desktop: hint: value "System;Utility;Archiving;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
cas rosa-media-player-1.6.11-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.
cas rox-base-2.5-alt1.1.qa2.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.
cas rpminstall-1.1.3-alt1.qa1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/rpminstall.desktop: hint: value "System;PackageManager;Settings;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
cas rsibreak-0.12.8-alt1.x86_64 big-changelog info Package contains big ChangeLog. Gzip it.
cas ruby-activerecord-mysql2-adapter-doc-0.0.3-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package ruby-em-synchrony-doc-1.0.6-alt1.noarch, for example, /usr/share/ri/site/ActiveRecord/ConnectionAdapters/ConnectionPool/cdesc-ConnectionPool.ri (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/ri/site/ActiveRecord/cdesc-ActiveRecord.ri /usr/share/ri/site/Mysql2/cdesc-Mysql2.ri conflict with the package ruby-mysql2-doc-0.4.10-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.
cas ruby-addressable-doc-2.5.2-alt1.noarch rpm-filesystem-conflict-file-file warn Files /usr/share/ri/site/Addressable/URI/cdesc-URI.ri /usr/share/ri/site/Addressable/URI/normalized_query-i.ri /usr/share/ri/site/Addressable/cdesc-Addressable.ri conflict with the package ruby-faraday_middleware-doc-0.12.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.
cas ruby-amazon-ec2-doc-0.9.17-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-deep_merge-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-http-cookie-doc-1.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/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-rr-doc-1.2.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas ruby-amq-protocol-doc-2.3.0-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package ruby-amqp-doc-1.8.0-alt1.noarch, for example, /usr/share/ri/site/AMQ/Protocol/Basic/cdesc-Basic.ri (9 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.
cas ruby-amqp-doc-1.8.0-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri conflicts with the package ohai-doc-14.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package ruby-amq-protocol-doc-2.3.0-alt1.noarch, for example, /usr/share/ri/site/AMQ/Protocol/Basic/cdesc-Basic.ri (9 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/ri/site/RbConfig/cdesc-RbConfig.ri conflicts with the package ruby-dalli-doc-2.7.6-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri conflicts with the package ruby-facter-doc-2.0.1-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri conflicts with the package ruby-spoon-doc-0.0.6-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.
cas ruby-aws-sdk-doc-2.10.129-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/Aws/cdesc-Aws.ri conflicts with the package ruby-aws-sigv4-doc-1.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.
cas ruby-aws-sigv4-doc-1.0.2-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/Aws/cdesc-Aws.ri conflicts with the package ruby-aws-sdk-doc-2.10.129-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.
cas ruby-azure-core-doc-0.1.14-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package chef-doc-12.15.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Azure/cdesc-Azure.ri conflicts with the package ruby-azure-doc-0.7.10-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-http-cookie-doc-1.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/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.2.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-mail-doc-2.6.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-mcollective-client-doc-2.11.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-puppet-lint-doc-3.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-1.6.8-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-unf-doc-0.1.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.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.
cas ruby-azure-doc-0.7.10-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/Azure/cdesc-Azure.ri conflicts with the package ruby-azure-core-doc-0.1.14-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.
cas ruby-benchmark-ips-doc-1.2.0-alt1.gite47e416.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/Benchmark/cdesc-Benchmark.ri conflicts with the package ruby-benchmark_suite-doc-1.0.0-alt1.git5bded6.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas ruby-benchmark_suite-doc-1.0.0-alt1.git5bded6.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/Benchmark/cdesc-Benchmark.ri conflicts with the package ruby-benchmark-ips-doc-1.2.0-alt1.gite47e416.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas ruby-chef-sugar-doc-3.4.0-alt1.noarch rpm-filesystem-conflict-file-file warn Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package asciidoctor-doc-1.5.6.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 chef-doc-12.15.11-alt1.noarch, for example, /usr/share/ri/site/Chef/Node/cdesc-Node.ri (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/ri/site/Chef/cdesc-Chef.ri conflicts with the package ohai-doc-14.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-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.
Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-ffi-yajl-doc-2.3.1-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-http-cookie-doc-1.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/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.2.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-mail-doc-2.6.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-mcollective-client-doc-2.11.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-puppet-lint-doc-3.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-rgen-doc-0.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-rr-doc-1.2.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Object/blank%3f-i.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-1.6.8-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-unf-doc-0.1.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.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.
cas ruby-cleanroom-doc-1.0.0-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package chef-doc-12.15.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-core-doc-3.7.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-expectations-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-mocks-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-puppet-doc-0.1.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-support-doc-3.7.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-spec_helper-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas ruby-deep_merge-doc-1.0.1-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-amazon-ec2-doc-0.9.17-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-http-cookie-doc-1.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/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-rr-doc-1.2.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas ruby-em-hiredis-doc-0.3.1-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/EM/cdesc-EM.ri conflicts with the package ruby-em-mongo-doc-0.5.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-redis-doc-0.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-socksify-doc-0.3.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.
There are file conflicts with the package ruby-em-synchrony-doc-1.0.6-alt1.noarch, for example, /usr/share/ri/site/EM/cdesc-EM.ri (9 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/ri/site/EM/cdesc-EM.ri /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflict with the package ruby-eventmachine-doc-1.2.5-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-faraday-doc-0.13.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.
cas ruby-em-http-request-doc-1.1.5-alt1.1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package chef-doc-12.15.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-hiredis-doc-0.3.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-redis-doc-0.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-socksify-doc-0.3.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/ri/site/EventMachine/HTTPMethods/cdesc-HTTPMethods.ri /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflict with the package ruby-em-synchrony-doc-1.0.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-eventmachine-doc-1.2.5-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-faraday-doc-0.13.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-http-cookie-doc-1.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/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.2.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-mail-doc-2.6.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-mcollective-client-doc-2.11.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-puppet-lint-doc-3.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-1.6.8-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-unf-doc-0.1.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.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.
cas ruby-em-jack-doc-0.1.5-alt1.noarch rpm-filesystem-conflict-file-file warn Files /usr/share/ri/site/EMJack/Connection/cdesc-Connection.ri /usr/share/ri/site/EMJack/Connection/use-i.ri /usr/share/ri/site/EMJack/cdesc-EMJack.ri conflict with the package ruby-em-synchrony-doc-1.0.6-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.
cas ruby-em-mongo-doc-0.5.1-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/EM/cdesc-EM.ri conflicts with the package ruby-em-hiredis-doc-0.3.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 ruby-em-synchrony-doc-1.0.6-alt1.noarch, for example, /usr/share/ri/site/EM/Mongo/Collection/cdesc-Collection.ri (10 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/ri/site/EM/cdesc-EM.ri conflicts with the package ruby-eventmachine-doc-1.2.5-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas ruby-em-redis-doc-0.3.0-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-hiredis-doc-0.3.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-socksify-doc-0.3.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.
There are file conflicts with the package ruby-em-synchrony-doc-1.0.6-alt1.noarch, for example, /usr/share/ri/site/EventMachine/Protocols/Redis/call_command-i.ri (6 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/ri/site/EventMachine/Protocols/cdesc-Protocols.ri /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflict with the package ruby-eventmachine-doc-1.2.5-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-faraday-doc-0.13.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.
cas ruby-em-socksify-doc-0.3.2-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-hiredis-doc-0.3.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-redis-doc-0.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-synchrony-doc-1.0.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-eventmachine-doc-1.2.5-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-faraday-doc-0.13.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.
cas ruby-em-synchrony-doc-1.0.6-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package erubis-doc-2.7.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.
There are file conflicts with the package ruby-activerecord-mysql2-adapter-doc-0.0.3-alt1.noarch, for example, /usr/share/ri/site/ActiveRecord/ConnectionAdapters/ConnectionPool/cdesc-ConnectionPool.ri (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/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-dalli-doc-2.7.6-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package ruby-em-hiredis-doc-0.3.1-alt1.noarch, for example, /usr/share/ri/site/EM/cdesc-EM.ri (9 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/ri/site/EventMachine/HTTPMethods/cdesc-HTTPMethods.ri /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflict with the package ruby-em-http-request-doc-1.1.5-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/EMJack/Connection/cdesc-Connection.ri /usr/share/ri/site/EMJack/Connection/use-i.ri /usr/share/ri/site/EMJack/cdesc-EMJack.ri conflict with the package ruby-em-jack-doc-0.1.5-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 ruby-em-mongo-doc-0.5.1-alt1.noarch, for example, /usr/share/ri/site/EM/Mongo/Collection/cdesc-Collection.ri (10 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 ruby-em-redis-doc-0.3.0-alt1.noarch, for example, /usr/share/ri/site/EventMachine/Protocols/Redis/call_command-i.ri (6 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/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-socksify-doc-0.3.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.
There are file conflicts with the package ruby-eventmachine-doc-1.2.5-alt1.2.noarch, for example, /usr/share/ri/site/EM/cdesc-EM.ri (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.
File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-faraday-doc-0.13.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-haml-doc-5.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/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-json-pure-doc-2.1.0-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Mongo/cdesc-Mongo.ri conflicts with the package ruby-mongo-doc-2.5.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 ruby-mysql2-doc-0.4.10-alt1.noarch, for example, /usr/share/ri/site/ActiveRecord/VERSION/cdesc-VERSION.ri (8 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/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-polyglot-doc-0.3.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Memcached/cdesc-Memcached.ri conflicts with the package ruby-remcached-doc-0.4.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-simplecov-doc-0.15.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package yajl-ruby-doc-1.3.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.
cas ruby-eventmachine-doc-1.2.5-alt1.2.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/IO/cdesc-IO.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/IO/cdesc-IO.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/EM/cdesc-EM.ri /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflict with the package ruby-em-hiredis-doc-0.3.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/EM/cdesc-EM.ri conflicts with the package ruby-em-mongo-doc-0.5.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/EventMachine/Protocols/cdesc-Protocols.ri /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflict with the package ruby-em-redis-doc-0.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-socksify-doc-0.3.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.
There are file conflicts with the package ruby-em-synchrony-doc-1.0.6-alt1.noarch, for example, /usr/share/ri/site/EM/cdesc-EM.ri (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.
File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-faraday-doc-0.13.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/IO/cdesc-IO.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/IO/cdesc-IO.ri conflicts with the package ruby-io-extra-doc-1.2.7-alt1.4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas ruby-faraday_middleware-doc-0.12.2-alt1.noarch rpm-filesystem-conflict-file-file warn Files /usr/share/ri/site/Addressable/URI/cdesc-URI.ri /usr/share/ri/site/Addressable/URI/normalized_query-i.ri /usr/share/ri/site/Addressable/cdesc-Addressable.ri conflict with the package ruby-addressable-doc-2.5.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/ri/site/Faraday/Request/cdesc-Request.ri /usr/share/ri/site/Faraday/Response/cdesc-Response.ri /usr/share/ri/site/Faraday/cdesc-Faraday.ri conflict with the package ruby-faraday-doc-0.13.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.
cas ruby-fast_gettext-doc-1.1.0-alt2.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package chef-doc-12.15.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-http-cookie-doc-1.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/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.2.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-mail-doc-2.6.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-mcollective-client-doc-2.11.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/String/%25-i.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-puppet-lint-doc-3.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-1.6.8-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-unf-doc-0.1.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.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.
cas ruby-ffi-yajl-doc-2.3.1-alt1.2.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package asciidoctor-doc-1.5.6.1-alt1.noarch, for example, /usr/share/ri/site/Array/cdesc-Array.ri (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 chef-doc-12.15.11-alt1.noarch, for example, /usr/share/ri/site/FalseClass/cdesc-FalseClass.ri (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.
File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-amazon-ec2-doc-0.9.17-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-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 ruby-backports-doc-3.7.0-alt1.noarch, for example, /usr/share/ri/site/Array/cdesc-Array.ri (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.
Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-chef-sugar-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/ActiveSupport/cdesc-ActiveSupport.ri conflicts with the package ruby-dalli-doc-2.7.6-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-deep_merge-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-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.
Files /usr/share/ri/site/String/cdesc-String.ri /usr/share/ri/site/StringIO/cdesc-StringIO.ri conflict with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Hash/cdesc-Hash.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-http-cookie-doc-1.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/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.2.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package ruby-json-pure-doc-2.1.0-alt1.2.noarch, for example, /usr/share/ri/site/Date/cdesc-Date.ri (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/ri/site/Net/cdesc-Net.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-mail-doc-2.6.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/String/cdesc-String.ri /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflict with the package ruby-mcollective-client-doc-2.11.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mechanize-doc-0.9.3-alt1.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mini_portile2-doc-2.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package ruby-mongo-doc-2.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package ruby-msgpack-doc-1.1.0-alt1.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-dhcp-doc-1.3.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.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-ssh-multi-doc-1.2.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-puppet-lint-doc-3.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-rgen-doc-0.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Hash/cdesc-Hash.ri conflict with the package ruby-rr-doc-1.2.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 ruby-sequel-doc-4.49.0-alt2.1.noarch, for example, /usr/share/ri/site/Array/cdesc-Array.ri (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.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-1.6.8-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-unf-doc-0.1.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.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.
File /usr/share/ri/site/Yajl/cdesc-Yajl.ri conflicts with the package yajl-ruby-doc-1.3.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.
cas ruby-hashie-doc-3.5.7-alt1.noarch rpm-filesystem-conflict-file-file warn Files /usr/share/ri/site/Hashie/Mash/cdesc-Mash.ri /usr/share/ri/site/Hashie/cdesc-Hashie.ri conflict with the package ruby-rash-doc-0.4.5-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.
cas ruby-hiera-doc-3.4.2-alt1.noarch rpm-filesystem-conflict-file-file warn Files /usr/share/ri/site/Hiera/Backend/cdesc-Backend.ri /usr/share/ri/site/Hiera/cdesc-Hiera.ri conflict with the package ruby-hiera-eyaml-doc-2.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.
cas ruby-hiera-eyaml-doc-2.1.0-alt1.noarch rpm-filesystem-conflict-file-file warn Files /usr/share/ri/site/Hiera/Backend/cdesc-Backend.ri /usr/share/ri/site/Hiera/cdesc-Hiera.ri conflict with the package ruby-hiera-doc-3.4.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.
cas ruby-http-cookie-doc-1.0.3-alt1.noarch rpm-filesystem-conflict-file-file warn Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Hash/cdesc-Hash.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package asciidoctor-doc-1.5.6.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package chef-doc-12.15.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-amazon-ec2-doc-0.9.17-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-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 ruby-backports-doc-3.7.0-alt1.noarch, for example, /usr/share/ri/site/Array/cdesc-Array.ri (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.
Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-chef-sugar-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-deep_merge-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-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.
Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Hash/cdesc-Hash.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-ffi-yajl-doc-2.3.1-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/HTTP/cdesc-HTTP.ri conflicts with the package ruby-http_parser.rb-doc-0.6.0-alt3.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/HTTP/cdesc-HTTP.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-httpclient-doc-2.8.2.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-mail-doc-2.6.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-mcollective-client-doc-2.11.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-puppet-lint-doc-3.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-rgen-doc-0.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Hash/cdesc-Hash.ri conflict with the package ruby-rr-doc-1.2.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Hash/cdesc-Hash.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-1.6.8-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-unf-doc-0.1.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.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.
cas ruby-http_parser.rb-doc-0.6.0-alt3.2.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/HTTP/cdesc-HTTP.ri conflicts with the package ruby-http-cookie-doc-1.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/ri/site/HTTP/cdesc-HTTP.ri conflicts with the package ruby-httpclient-doc-2.8.2.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas ruby-idn-doc-0.1.0-alt3.2.noarch rpm-filesystem-conflict-file-file warn Files /usr/share/ri/site/Enumerable/cdesc-Enumerable.ri /usr/share/ri/site/File/cdesc-File.ri conflict with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Installer/cdesc-Installer.ri /usr/share/ri/site/Installer/new-c.ri conflict with the package ruby-makeconf-doc-0.3.0-alt1.svn20130509.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Enumerable/cdesc-Enumerable.ri conflicts with the package ruby-rr-doc-1.2.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/File/cdesc-File.ri conflicts with the package ruby-rspec-support-doc-3.7.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 ruby-sigar-doc-0.7.3-alt1.2.noarch, for example, /usr/share/ri/site/page-LICENSE.ri (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/ri/site/File/cdesc-File.ri conflicts with the package ruby-spec_helper-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas ruby-json-pure-doc-2.1.0-alt1.2.noarch rpm-filesystem-conflict-file-file warn Files /usr/share/ri/site/Regexp/cdesc-Regexp.ri /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflict with the package asciidoctor-doc-1.5.6.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package chef-doc-12.15.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package erubis-doc-2.7.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.
There are file conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch, for example, /usr/share/ri/site/Complex/cdesc-Complex.ri (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.
File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-em-synchrony-doc-1.0.6-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 ruby-ffi-yajl-doc-2.3.1-alt1.2.noarch, for example, /usr/share/ri/site/Date/cdesc-Date.ri (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/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package ruby-mcollective-client-doc-2.11.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package ruby-mongo-doc-2.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package ruby-msgpack-doc-1.1.0-alt1.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package ruby-oj-doc-3.4.0-alt1.noarch, for example, /usr/share/ri/site/JSON/Ext/cdesc-Ext.ri (18 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/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-polyglot-doc-0.3.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Range/cdesc-Range.ri /usr/share/ri/site/Regexp/cdesc-Regexp.ri conflict with the package ruby-rr-doc-1.2.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Class/cdesc-Class.ri conflicts with the package ruby-rspec-mocks-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Range/cdesc-Range.ri /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflict with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package yajl-ruby-doc-1.3.1-alt1.noarch, for example, /usr/share/ri/site/JSON/GeneratorError/cdesc-GeneratorError.ri (6 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.
cas ruby-mail-doc-2.6.6-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Net/cdesc-Net.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package chef-doc-12.15.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/String/cdesc-String.ri /usr/share/ri/site/String/constantize-i.ri conflict with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-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.
Files /usr/share/ri/site/Net/cdesc-Net.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-ffi-yajl-doc-2.3.1-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-http-cookie-doc-1.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/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.2.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-mcollective-client-doc-2.11.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mechanize-doc-0.9.3-alt1.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mini_portile2-doc-2.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-multipart-post-doc-2.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-dhcp-doc-1.3.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.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-ssh-multi-doc-1.2.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-puppet-lint-doc-3.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/String/cdesc-String.ri /usr/share/ri/site/String/constantize-i.ri conflict with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-1.6.8-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-unf-doc-0.1.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.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.
cas ruby-mini_portile2-doc-2.3.0-alt1.noarch rpm-filesystem-conflict-file-file warn Files /usr/share/ri/site/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package chef-doc-12.15.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mail-doc-2.6.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package ruby-mechanize-doc-0.9.3-alt1.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package ruby-multipart-post-doc-2.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-dhcp-doc-1.3.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.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-ssh-multi-doc-1.2.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas ruby-mixlib-authentication-doc-1.3.0-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-cli-doc-1.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-config-doc-2.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/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-log-doc-1.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-shellout-doc-2.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-versioning-doc-1.2.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.
cas ruby-mixlib-cli-doc-1.5.0-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-authentication-doc-1.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-config-doc-2.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/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-log-doc-1.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-shellout-doc-2.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-versioning-doc-1.2.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.
cas ruby-mixlib-config-doc-2.1.0-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-authentication-doc-1.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-cli-doc-1.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-log-doc-1.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-shellout-doc-2.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-versioning-doc-1.2.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.
cas ruby-mixlib-log-doc-1.4.0-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-authentication-doc-1.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-cli-doc-1.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-config-doc-2.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/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-shellout-doc-2.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-versioning-doc-1.2.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.
cas ruby-mixlib-shellout-doc-2.0.1-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-authentication-doc-1.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-cli-doc-1.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-config-doc-2.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/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-log-doc-1.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-versioning-doc-1.2.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.
cas ruby-mixlib-versioning-doc-1.2.3-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-authentication-doc-1.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-cli-doc-1.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-config-doc-2.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/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-log-doc-1.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-shellout-doc-2.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas ruby-mongo-doc-2.5.0-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package chef-doc-12.15.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Mongo/cdesc-Mongo.ri conflicts with the package ruby-em-synchrony-doc-1.0.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package ruby-json-pure-doc-2.1.0-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package ruby-mcollective-client-doc-2.11.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package ruby-msgpack-doc-1.1.0-alt1.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas ruby-mysql2-doc-0.4.10-alt1.noarch rpm-filesystem-conflict-file-file warn Files /usr/share/ri/site/ActiveRecord/cdesc-ActiveRecord.ri /usr/share/ri/site/Mysql2/cdesc-Mysql2.ri conflict with the package ruby-activerecord-mysql2-adapter-doc-0.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.
There are file conflicts with the package ruby-em-synchrony-doc-1.0.6-alt1.noarch, for example, /usr/share/ri/site/ActiveRecord/VERSION/cdesc-VERSION.ri (8 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.
cas ruby-net-dhcp-doc-1.3.2-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package chef-doc-12.15.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mail-doc-2.6.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mechanize-doc-0.9.3-alt1.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mini_portile2-doc-2.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-multipart-post-doc-2.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-ssh-multi-doc-1.2.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas ruby-net-ssh-multi-doc-1.2.0-alt1.1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package chef-doc-12.15.11-alt1.noarch, for example, /usr/share/ri/site/Net/SSH/Multi/Server/busy%3f-i.ri (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.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mail-doc-2.6.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mechanize-doc-0.9.3-alt1.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mini_portile2-doc-2.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-multipart-post-doc-2.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-dhcp-doc-1.3.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.
File /usr/share/ri/site/Net/SSH/cdesc-SSH.ri conflicts with the package ruby-net-ssh-doc-4.2.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas ruby-oj-doc-3.4.0-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package chef-doc-12.15.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-http-cookie-doc-1.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/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.2.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package ruby-json-pure-doc-2.1.0-alt1.2.noarch, for example, /usr/share/ri/site/JSON/Ext/cdesc-Ext.ri (18 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/ri/site/String/cdesc-String.ri conflicts with the package ruby-mail-doc-2.6.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-mcollective-client-doc-2.11.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-puppet-lint-doc-3.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-1.6.8-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-unf-doc-0.1.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.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.
File /usr/share/ri/site/JSON/cdesc-JSON.ri conflicts with the package yajl-ruby-doc-1.3.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.
cas ruby-plist-doc-3.1.0-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package ruby-facter-doc-2.0.1-alt2.1.noarch, for example, /usr/share/ri/site/Plist/Emit/cdesc-Emit.ri (51 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.
cas ruby-polyglot-doc-0.3.5-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package erubis-doc-2.7.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/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-em-synchrony-doc-1.0.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-json-pure-doc-2.1.0-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package yajl-ruby-doc-1.3.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.
cas ruby-proxifier-doc-1.0.3-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/URI/cdesc-URI.ri conflicts with the package ruby-escape_utils-doc-1.2.1-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/URI/cdesc-URI.ri conflicts with the package ruby-httpclient-doc-2.8.2.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas ruby-puppet-lint-doc-3.0.0-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package chef-doc-12.15.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/String/cdesc-String.ri /usr/share/ri/site/String/prepend-i.ri conflict with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/String/%25-i.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-fast_gettext-doc-1.1.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-http-cookie-doc-1.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/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.2.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-mail-doc-2.6.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-mcollective-client-doc-2.11.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/PuppetLint/cdesc-PuppetLint.ri conflicts with the package ruby-spec_helper-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-1.6.8-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-unf-doc-0.1.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.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.
cas ruby-rash-doc-0.4.5-alt1.noarch rpm-filesystem-conflict-file-file warn Files /usr/share/ri/site/Hashie/Mash/cdesc-Mash.ri /usr/share/ri/site/Hashie/cdesc-Hashie.ri conflict with the package ruby-hashie-doc-3.5.7-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.
cas ruby-rbnacl-doc-5.0.0-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/RbNaCl/cdesc-RbNaCl.ri conflicts with the package ruby-rbnacl-libsodium-doc-1.0.16-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.
cas ruby-rbnacl-libsodium-doc-1.0.16-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/RbNaCl/cdesc-RbNaCl.ri conflicts with the package ruby-rbnacl-doc-5.0.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.
cas ruby-remcached-doc-0.4.1-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/Memcached/cdesc-Memcached.ri conflicts with the package ruby-em-synchrony-doc-1.0.6-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.
cas ruby-rgen-doc-0.7.0-alt1.1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-http-cookie-doc-1.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/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-mcollective-client-doc-2.11.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-rr-doc-1.2.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas ruby-rr-doc-1.2.1-alt1.noarch rpm-filesystem-conflict-file-file warn Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Hash/cdesc-Hash.ri /usr/share/ri/site/Regexp/cdesc-Regexp.ri conflict with the package asciidoctor-doc-1.5.6.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-amazon-ec2-doc-0.9.17-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 ruby-backports-doc-3.7.0-alt1.noarch, for example, /usr/share/ri/site/Array/cdesc-Array.ri (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.
File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-deep_merge-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Hash/cdesc-Hash.ri conflict with the package ruby-ffi-yajl-doc-2.3.1-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Hash/cdesc-Hash.ri conflict with the package ruby-http-cookie-doc-1.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/ri/site/Enumerable/cdesc-Enumerable.ri conflicts with the package ruby-idn-doc-0.1.0-alt3.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Range/cdesc-Range.ri /usr/share/ri/site/Regexp/cdesc-Regexp.ri conflict with the package ruby-json-pure-doc-2.1.0-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-mcollective-client-doc-2.11.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-rgen-doc-0.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/RR/Errors/cdesc-Errors.ri /usr/share/ri/site/RR/cdesc-RR.ri conflict with the package ruby-rspec-core-doc-3.7.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Hash/cdesc-Hash.ri /usr/share/ri/site/Range/cdesc-Range.ri conflict with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Enumerable/cdesc-Enumerable.ri conflicts with the package ruby-sigar-doc-0.7.3-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Object/new-c.ri conflicts with the package ruby-spec_helper-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas ruby-rspec-core-doc-3.7.1-alt1.noarch rpm-filesystem-conflict-file-file warn Files /usr/share/ri/site/RSpec/Core/cdesc-Core.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package chef-doc-12.15.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-cleanroom-doc-1.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/RR/Errors/cdesc-Errors.ri /usr/share/ri/site/RR/cdesc-RR.ri conflict with the package ruby-rr-doc-1.2.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/RSpec/Support/cdesc-Support.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-expectations-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/RSpec/Support/cdesc-Support.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-mocks-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-puppet-doc-0.1.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/RSpec/Support/cdesc-Support.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-support-doc-3.7.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/RSpec/Core/cdesc-Core.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-spec_helper-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas ruby-rspec-expectations-doc-3.7.0-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package chef-doc-12.15.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/BasicObject/cdesc-BasicObject.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-cleanroom-doc-1.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/RSpec/Support/cdesc-Support.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-core-doc-3.7.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 ruby-rspec-mocks-doc-3.7.0-alt1.noarch, for example, /usr/share/ri/site/BasicObject/cdesc-BasicObject.ri (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.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-puppet-doc-0.1.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/RSpec/Support/cdesc-Support.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-support-doc-3.7.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/RSpec/Matchers/cdesc-Matchers.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-spec_helper-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas ruby-rspec-mocks-doc-3.7.0-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package chef-doc-12.15.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/BasicObject/cdesc-BasicObject.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-cleanroom-doc-1.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Class/cdesc-Class.ri conflicts with the package ruby-json-pure-doc-2.1.0-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/RSpec/Support/cdesc-Support.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-core-doc-3.7.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 ruby-rspec-expectations-doc-3.7.0-alt1.noarch, for example, /usr/share/ri/site/BasicObject/cdesc-BasicObject.ri (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.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-puppet-doc-0.1.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/RSpec/Support/cdesc-Support.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-support-doc-3.7.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-spec_helper-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas ruby-rspec-puppet-doc-0.1.6-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package chef-doc-12.15.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-cleanroom-doc-1.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-core-doc-3.7.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-expectations-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-mocks-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-support-doc-3.7.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-spec_helper-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas ruby-rspec-support-doc-3.7.1-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package chef-doc-12.15.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/File/cdesc-File.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-cleanroom-doc-1.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/File/cdesc-File.ri conflicts with the package ruby-idn-doc-0.1.0-alt3.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/RSpec/Support/cdesc-Support.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-core-doc-3.7.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/RSpec/Support/cdesc-Support.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-expectations-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/RSpec/Support/cdesc-Support.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-mocks-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-puppet-doc-0.1.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/File/cdesc-File.ri conflicts with the package ruby-sigar-doc-0.7.3-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/File/cdesc-File.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-spec_helper-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas ruby-sigar-doc-0.7.3-alt1.2.noarch rpm-filesystem-conflict-file-file warn Files /usr/share/ri/site/Enumerable/cdesc-Enumerable.ri /usr/share/ri/site/File/cdesc-File.ri conflict with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package ruby-idn-doc-0.1.0-alt3.2.noarch, for example, /usr/share/ri/site/page-LICENSE.ri (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/ri/site/Installer/cdesc-Installer.ri /usr/share/ri/site/Installer/new-c.ri conflict with the package ruby-makeconf-doc-0.3.0-alt1.svn20130509.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Enumerable/cdesc-Enumerable.ri conflicts with the package ruby-rr-doc-1.2.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/File/cdesc-File.ri conflicts with the package ruby-rspec-support-doc-3.7.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/File/cdesc-File.ri conflicts with the package ruby-spec_helper-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas ruby-simplecov-doc-0.15.1-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-dalli-doc-2.7.6-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-em-synchrony-doc-1.0.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-haml-doc-5.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.
Files /usr/share/ri/site/SimpleCov/Formatter/cdesc-Formatter.ri /usr/share/ri/site/SimpleCov/cdesc-SimpleCov.ri conflict with the package ruby-simplecov-html-doc-0.10.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.
cas ruby-simplecov-html-doc-0.10.2-alt1.noarch rpm-filesystem-conflict-file-file warn Files /usr/share/ri/site/SimpleCov/Formatter/cdesc-Formatter.ri /usr/share/ri/site/SimpleCov/cdesc-SimpleCov.ri conflict with the package ruby-simplecov-doc-0.15.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.
cas ruby-spec_helper-doc-1.0.1-alt1.noarch rpm-filesystem-conflict-file-file warn Files /usr/share/ri/site/Gem/cdesc-Gem.ri /usr/share/ri/site/RSpec/Core/cdesc-Core.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package chef-doc-12.15.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/File/cdesc-File.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-cleanroom-doc-1.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Puppet/cdesc-Puppet.ri conflicts with the package ruby-facter-doc-2.0.1-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/File/cdesc-File.ri conflicts with the package ruby-idn-doc-0.1.0-alt3.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/PuppetLint/cdesc-PuppetLint.ri conflicts with the package ruby-puppet-lint-doc-3.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Object/new-c.ri conflicts with the package ruby-rr-doc-1.2.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/RSpec/Core/cdesc-Core.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-core-doc-3.7.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/RSpec/Matchers/cdesc-Matchers.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-expectations-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-mocks-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-puppet-doc-0.1.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/File/cdesc-File.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-support-doc-3.7.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Gem/cdesc-Gem.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/File/cdesc-File.ri conflicts with the package ruby-sigar-doc-0.7.3-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas ruby-text-doc-1.3.1-alt2.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/Text/cdesc-Text.ri conflicts with the package ruby-text-format-doc-1.0.0-alt3.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas ruby-thor-0.19.1-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package thor-0.20.0-alt1.noarch, for example, /usr/lib/ruby/site_ruby/thor.rb (26 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.
cas ruby-thor-doc-0.19.1-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package thor-doc-0.20.0-alt1.noarch, for example, /usr/share/ri/site/Object/namespace-i.ri (203 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.
cas ruby-treetop-doc-1.6.8-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package chef-doc-12.15.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-http-cookie-doc-1.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/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.2.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-mail-doc-2.6.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-mcollective-client-doc-2.11.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-puppet-lint-doc-3.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/String/blank%3f-i.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-unf-doc-0.1.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.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.
cas ruby-unf-doc-0.1.4-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package chef-doc-12.15.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-http-cookie-doc-1.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/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.2.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-mail-doc-2.6.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-mcollective-client-doc-2.11.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-puppet-lint-doc-3.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-1.6.8-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/UNF/Normalizer/cdesc-Normalizer.ri /usr/share/ri/site/UNF/cdesc-UNF.ri conflict with the package ruby-unf_ext-doc-0.0.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.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.
cas ruby-unf_ext-doc-0.0.7.5-alt1.noarch rpm-filesystem-conflict-file-file warn Files /usr/share/ri/site/UNF/Normalizer/cdesc-Normalizer.ri /usr/share/ri/site/UNF/cdesc-UNF.ri conflict with the package ruby-unf-doc-0.1.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas ruleuser-1.1.0-alt2.git935e687.noarch freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/ruleuser.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).
cas rviewer-0.5-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/rviewer.desktop: warning: value "Qt image viewer" for key "Comment" in group "Desktop Entry" looks redundant with value "Qt image viewer" of key "GenericName"
cas rviewer-0.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.
cas samba-DC-4.6.12-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.
cas samba-DC-common-4.6.12-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.
cas samba-DC-winbind-clients-4.6.12-alt2.S1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /lib64/libnss_winbind.so.2 is different from the same symlink in the package samba-winbind-clients-4.6.12-alt2.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.
value of symlink /lib64/libnss_wins.so.2 is different from the same symlink in the package samba-winbind-clients-4.6.12-alt2.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.
cas scilab-6.0.0-alt3.2.x86_64 altlinux-java-forbidden-requires fail The package has JVM-specific Requires: java-1.8.0-openjdk. Those requires are often due to packaging errors and also specifically forbidden by Java Packageing Policy. If you really really need it, write it in more indirect way.
cas scilab-6.0.0-alt3.2.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.
cas scilab-6.0.0-alt3.2.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/scinotes.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).
cas scilab-6.0.0-alt3.2.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/scilab.desktop: hint: value "Education;Science;Math;Physics;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
desktop-file-validate utility printed the following message(s): /usr/share/applications/scinotes.desktop: warning: value "???????? ???????? Scilab" for key "Comment[ru]" in group "Desktop Entry" looks redundant with value "???????? ???????? Scilab" of key "GenericName[ru]"
desktop-file-validate utility printed the following message(s): /usr/share/applications/xcos.desktop: hint: value "Education;Science;Math;Physics;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
cas scratch-1.4.0.7-alt3.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/scratch.desktop: hint: value "Development;IDE;Education;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
cas scratch-1.4.0.7-alt3.noarch iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.
cas skeinforge-12.03.14-alt1.noarch freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/skeinforge.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).
cas sogo3-3.2.10.20171010-alt2.x86_64 arch-dep-package-has-big-usr-share info The package has a significant amount of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.
cas sogo3-3.2.10.20171010-alt2.x86_64 big-changelog info Package contains big ChangeLog. Gzip it.
cas sogo3-3.2.10.20171010-alt2.x86_64 buildroot fail found paths to buildroot: /usr/lib64/GNUstep/Frameworks/SOGo.framework/Versions/3/sogo/libSOGo.so.3.2.10: Binary file /usr/lib64/GNUstep/Frameworks/SOGo.framework/Versions/3/sogo/libSOGo.so.3.2.10 matches
cas sogo3-3.2.10.20171010-alt2.x86_64 subdir-in-var-run info Found a subdir in /var/run or /var/lock. /var/run and /var/lock may be mounted as temporary filesystems, so the init.d scripts must handle this correctly. This will typically amount to creating any required subdirectories dynamically when the init.d script is run, rather than including them in the package and relying on rpm to create them.
cas sogo3-debuginfo-3.2.10.20171010-alt2.x86_64 buildroot fail found paths to buildroot: /usr/lib/debug/usr/lib64/GNUstep/Frameworks/SOGo.framework/Versions/3/sogo/libSOGo.so.3.2.10.debug: Binary file /usr/lib/debug/usr/lib64/GNUstep/Frameworks/SOGo.framework/Versions/3/sogo/libSOGo.so.3.2.10.debug matches /usr/src/debug/SOGo-3.2.10.20171010/SoObjects/SOGo/derived_src/NSFramework_SOGo.m: + (NSString *)frameworkPath { return @"/usr/src/tmp/sogo3-buildroot/usr/lib64/GNUstep/Frameworks"; }
cas solaar-0.9.2-alt1.1.noarch freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/solaar.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).
cas specspo-10.07-alt2.noarch altlinux-policy-rpm-macros-packaging-rpm4 fail package contains rpm macro files with dot in name. Those files should be renamed and placed in separate package named rpm-build-* or rpm-macros-* according to http://www.altlinux.org/Drafts/RPMMacrosPackaging
cas specspo-10.07-alt2.noarch missing-url info Missing Url: in a package.
cas task-rutoken-1.0-alt2.noarch invalid-url warn Package has invalid Url:. It looks like a protocol part (http:,ftp:,etc.) is missing.
cas taskjuggler-3.6.0-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package chef-doc-12.15.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/Diff/cdesc-Diff.ri conflicts with the package ruby-diff-lcs-doc-1.2.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-http-cookie-doc-1.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/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.2.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-mail-doc-2.6.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-mcollective-client-doc-2.11.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-puppet-lint-doc-3.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-1.6.8-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-unf-doc-0.1.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
cas tellico-3.1.1-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/kf5/org.kde.tellico.desktop: warning: value "?????????? ?? ????????" for key "Comment[bg]" in group "Desktop Entry" looks redundant with value "?????????? ?? ????????" of key "GenericName[bg]"
/usr/share/applications/kf5/org.kde.tellico.desktop: warning: value "Menad?er kolekcija" for key "Comment[bs]" in group "Desktop Entry" looks redundant with value "Menad?er kolekcija" of key "GenericName[bs]"
/usr/share/applications/kf5/org.kde.tellico.desktop: warning: value "Spr?vce sb?rek" for key "Comment[cs]" in group "Desktop Entry" looks redundant with value "Spr?vce sb?rek" of key "GenericName[cs]"
/usr/share/applications/kf5/org.kde.tellico.desktop: warning: value "Mastrumilo de Kolektoj" for key "Comment[eo]" in group "Desktop Entry" looks redundant with value "Mastrumilo de Kolektoj" of key "GenericName[eo]"
/usr/share/applications/kf5/org.kde.tellico.desktop: warning: value "Kogude haldur" for key "Comment[et]" in group "Desktop Entry" looks redundant with value "Kogude haldur" of key "GenericName[et]"
/usr/share/applications/kf5/org.kde.tellico.desktop: warning: value "Kokoelmienhallinta" for key "Comment[fi]" in group "Desktop Entry" looks redundant with value "Kokoelmienhallinta" of key "GenericName[fi]"
/usr/share/applications/kf5/org.kde.tellico.desktop: warning: value "Bainisteoir baili?ch?n" for key "Comment[ga]" in group "Desktop Entry" looks redundant with value "Bainisteoir Baili?ch?n" of key "GenericName[ga]"
/usr/share/applications/kf5/org.kde.tellico.desktop: warning: value "Gy?jtem?nykezel?" for key "Comment[hu]" in group "Desktop Entry" looks redundant with value "Gy?jtem?nykezel?" of key "GenericName[hu]"
/usr/share/applications/kf5/org.kde.tellico.desktop: warning: value "???????? ?????????" for key "Comment[kk]" in group "Desktop Entry" looks redundant with value "???????? ?????????" of key "GenericName[kk]"
/usr/share/applications/kf5/org.kde.tellico.desktop: warning: value "Kolekcij? tvarkykl?" for key "Comment[lt]" in group "Desktop Entry" looks redundant with value "Kolekcij? tvarkykl?" of key "GenericName[lt]"
/usr/share/applications/kf5/org.kde.tellico.desktop: warning: value "?????? ??????????" for key "Comment[mr]" in group "Desktop Entry" looks redundant with value "?????? ??????????" of key "GenericName[mr]"
/usr/share/applications/kf5/org.kde.tellico.desktop: warning: value "Pengurus koleksi" for key "Comment[ms]" in group "Desktop Entry" looks redundant with value "Pengurus Koleksi" of key "GenericName[ms]"
/usr/share/applications/kf5/org.kde.tellico.desktop: warning: value "Zarz?dzanie kolekcjami" for key "Comment[pl]" in group "Desktop Entry" looks redundant with value "Zarz?dzanie kolekcjami" of key "GenericName[pl]"
/usr/share/applications/kf5/org.kde.tellico.desktop: warning: value "???????? ?????????" for key "Comment[ru]" in group "Desktop Entry" looks redundant with value "???????? ?????????" of key "GenericName[ru]"
/usr/share/applications/kf5/org.kde.tellico.desktop: warning: value "Spr?vca zbierok" for key "Comment[sk]" in group "Desktop Entry" looks redundant with value "Spr?vca zbierok" of key "GenericName[sk]"
/usr/share/applications/kf5/org.kde.tellico.desktop: warning: value "Upravljalnik zbirk" for key "Comment[sl]" in group "Desktop Entry" looks redundant with value "Upravljalnik zbirk" of key "GenericName[sl]"
/usr/share/applications/kf5/org.kde.tellico.desktop: warning: value "?????????? ????????? ????????" for key "Comment[uk]" in group "Desktop Entry" looks redundant with value "?????????? ????????? ????????" of key "GenericName[uk]"
/usr/share/applications/kf5/org.kde.tellico.desktop: warning: value "?????" for key "Comment[zh_CN]" in group "Desktop Entry" looks redundant with value "?????" of key "GenericName[zh_CN]"
/usr/share/applications/kf5/org.kde.tellico.desktop: warning: value "?????" for key "Comment[zh_TW]" in group "Desktop Entry" looks redundant with value "?????" of key "GenericName[zh_TW]"
cas tesseract-3.04.01-alt2.x86_64 library-pkgnames info package contains public library which is used in external packages: name should be lib* according to http://altlinux.org/Drafts/SharedLibs
cas thor-0.20.0-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package ruby-thor-0.19.1-alt1.noarch, for example, /usr/lib/ruby/site_ruby/thor.rb (26 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.
cas thor-doc-0.20.0-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package ruby-thor-doc-0.19.1-alt1.noarch, for example, /usr/share/ri/site/Object/namespace-i.ri (203 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.
cas token-manager-0.12-alt3.git1143028.noarch bin-permissions info not executable file /usr/bin/token-manager.py
cas token-manager-0.12-alt3.git1143028.noarch freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/token-manager.desktop: error: key "Comment[ru]" in group "Desktop Entry" is a localized key, but there is no non-localized key "Comment"
/usr/share/applications/token-manager.desktop: hint: value "Qt;HardwareSettings;Settings;System;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
cas token-manager-0.12-alt3.git1143028.noarch iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.
cas trustedqsl-2.3.1-alt5.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.
cas verlihub-0.9.8e-alt2.x86_64 subdir-in-var-run info Found a subdir in /var/run or /var/lock. /var/run and /var/lock may be mounted as temporary filesystems, so the init.d scripts must handle this correctly. This will typically amount to creating any required subdirectories dynamically when the init.d script is run, rather than including them in the package and relying on rpm to create them.
cas volumes-profile-lite-0.4-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.11-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/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-server-0.14-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/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-kdesktop-0.7.4-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.
File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-master-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.
File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-regular-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.
cas wcmcommander-0.20.0-alt1.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/wcm.desktop: hint: value item "FileManager" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: System;FileTools
/usr/share/applications/wcm.desktop: error: action group "Desktop Action NewWindow" exists, but there is no matching action "NewWindow"
cas wcmcommander-0.20.0-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.
cas wicd-common-1.7.4-alt1.noarch freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/wicd.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).
cas wmsystray-0.1.1-alt1.1.qa2.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/wmsystray.desktop: warning: boolean key "Terminal" in group "Desktop Entry" has value "0", which is deprecated: boolean values should be "false" or "true"
cas x2goclient-4.1.1.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/x2goclient.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).
cas x2goplugin-provider-4.1.1.0-alt1.x86_64 symlink-extra-slash info /usr/share/x2go/plugin/x2goplugin.html:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
cas xqf-1.0.6.2-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.
cas xsensors-0.80-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/xsensors.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).
cas yagf-0.9.5-alt2.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/YAGF.desktop: hint: value item "OCR" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: Graphics;Scanning
cas yagf-0.9.5-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.
cas yandex-disk-indicator-1.9.18-alt1.noarch freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/Yandex.Disk-indicator.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).
cas yandex-disk-indicator-1.9.18-alt1.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/Yandex.Disk-indicator.desktop: warning: value "Yandex.Disk indicator" for key "Comment" in group "Desktop Entry" looks redundant with value "Yandex.Disk indicator" of key "Name"
lav libclip-1.2.0cvs-alt3.qa4.x86_64 file-in-usr-marked-as-conffile warn Files below /usr may not be marked as conffiles, since
/usr might be mounted read-only and thus, the local system
administrator would not have a chance to modify this configuration
file.
lav libclip-gtk2-1.2.0cvs-alt5.x86_64 file-in-usr-marked-as-conffile warn Files below /usr may not be marked as conffiles, since
/usr might be mounted read-only and thus, the local system
administrator would not have a chance to modify this configuration
file.
lav librecad-2.1.3-alt1.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/librecad.desktop: error: file contains multiple keys named "Comment[ru]" in group "Desktop Entry"
/usr/share/applications/librecad.desktop: warning: value "??????? ??????????????????? ??????????????" for key "Comment[ru]" in group "Desktop Entry" looks redundant with value "??????? ??????????????????? ??????????????" of key "GenericName[ru]"
legion thunderbird-devel-52.6.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.
migor libofx-devel-0.9.10-alt1.3.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 libqtermwidget-debuginfo-0.8.0-alt2.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/usr/lib64/libqtermwidget5.so.0.debug is different from the same symlink in the package libqtermwidget-qt5-debuginfo-0.7.1-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.
mike libqtermwidget-devel-0.8.0-alt2.x86_64 rpm-filesystem-conflict-file-file warn Files /usr/include/qtermwidget5/qtermwidget.h /usr/lib64/pkgconfig/qtermwidget5.pc /usr/share/cmake/qtermwidget5/qtermwidget5-config.cmake conflict with the package libqtermwidget-qt5-devel-0.7.1-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.
mike qterminal-0.8.0-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/qterminal.desktop: warning: value "Terminal emulator" for key "Comment" in group "Desktop Entry" looks redundant with value "Terminal emulator" of key "GenericName"
mike seamonkey-devel-2.49.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.
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.
zerg kde4-i18n-ru-15.12.1-alt1.noarch symlink-extra-slash info /usr/share/kde4/doc/HTML/ru/akregator/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/amor/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/cervisia/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/fundamentals/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/gwenview/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/juk/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kalzium/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcachegrind/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/autostart/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/bell/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/cache/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/clock/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/colors/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/cookies/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/ebrowsing/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/filemanager/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/filetypes/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/fontinst/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/icons/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/kcmcss/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/kcmlaunch/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/kcmnotify/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/kcmsmserver/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/keyboard/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/keys/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/kremotecontrol/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/language/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/netpref/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/performance/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/proxy/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/screensaver/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/smb/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/spellchecking/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/useragent/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kcontrol/windowspecific/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kdebugdialog/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kdesu/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kdf/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kdm/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kfind/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kfloppy/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kget/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/khelpcenter/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/khelpcenter/documentationnotfound/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/khelpcenter/glossary/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kig/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kigo/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kioslave/audiocd/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kioslave/data/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kioslave/file/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kioslave/finger/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kioslave/floppy/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kioslave/ftp/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kioslave/gzip/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kioslave/help/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kioslave/imap/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kioslave/info/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kioslave/ldap/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kioslave/mailto/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kioslave/mbox/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kioslave/news/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kioslave/nfs/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kioslave/nntp/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kioslave/pop3/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kioslave/rlogin/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kioslave/sftp/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kioslave/sieve/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kioslave/smtp/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kioslave/tar/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kioslave/telnet/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kioslave/thumbnail/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kioslave/webdav/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kjots/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kleopatra/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/klinkstatus/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/klipper/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kmahjongg/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kmail/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kmenuedit/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kmix/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kmousetool/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/knetattach/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/knotes/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kolf/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kolourpaint/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/konqueror/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/konquest/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/konsole/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/konsolekalendar/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kontact/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kopete/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/korganizer/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kppp/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/krdc/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kreversi/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kruler/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/ksnapshot/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kspaceduel/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/ksudoku/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/ksysguard/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/ktimetracker/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kuser/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kwalletmanager/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kwatchgnupg/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/kwrite/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/lskat/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/palapeli/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/plasma-desktop/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/sonnet/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
/usr/share/kde4/doc/HTML/ru/systemsettings/common:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible.
zerg menu-icons-default-0.2.0.20-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.

generated by repocop at Tue Feb 13 06:37:54 2018