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.
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.
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.
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.
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.
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.
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.
/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
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.
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.
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.
value of symlink /usr/lib/debug/.build-id/0f/48c7e95d7565d8ce31632d3d187bb119055519.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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/lib/debug/.build-id/13/88859e8ef861bbcda5ea73eefe6ef4c28a800a is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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/lib/debug/.build-id/13/88859e8ef861bbcda5ea73eefe6ef4c28a800a.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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/lib/debug/.build-id/15/d54e6e3797d017da38617706b2ea0bf0627a0a is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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/lib/debug/.build-id/15/d54e6e3797d017da38617706b2ea0bf0627a0a.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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/lib/debug/.build-id/25/e5051d1202c5f7f3d80c4bb30f4cf28ad0dba9 is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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/lib/debug/.build-id/25/e5051d1202c5f7f3d80c4bb30f4cf28ad0dba9.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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/lib/debug/.build-id/31/8d32f7b9bdb01be4649399c774e00c06fde5de is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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/lib/debug/.build-id/31/8d32f7b9bdb01be4649399c774e00c06fde5de.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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/lib/debug/.build-id/49/61a49fba8b9a9966805179808a17b814cdd262 is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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/lib/debug/.build-id/49/61a49fba8b9a9966805179808a17b814cdd262.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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/lib/debug/.build-id/75/265c1fa6a3a4aa7968ad34833fff04ab177b08 is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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/lib/debug/.build-id/75/265c1fa6a3a4aa7968ad34833fff04ab177b08.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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/lib/debug/.build-id/77/0815a13a795c26f3e50b4da1bdbf3756473a40 is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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/lib/debug/.build-id/77/0815a13a795c26f3e50b4da1bdbf3756473a40.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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/lib/debug/.build-id/84/155ee703c8678e65a044307d6ef184b3aafb37 is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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/lib/debug/.build-id/84/155ee703c8678e65a044307d6ef184b3aafb37.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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/lib/debug/.build-id/88/0b7753a4bbd886382a3def64d1ba1253fa0f2f is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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/lib/debug/.build-id/88/0b7753a4bbd886382a3def64d1ba1253fa0f2f.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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/lib/debug/.build-id/8b/053c1b5d2386e6310402694d9529b4533defbc is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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/lib/debug/.build-id/8b/053c1b5d2386e6310402694d9529b4533defbc.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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/lib/debug/.build-id/a0/f1e8ad0cb818882008fd024f4618cdf31e0e21 is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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/lib/debug/.build-id/a0/f1e8ad0cb818882008fd024f4618cdf31e0e21.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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/lib/debug/.build-id/a2/52a1af7fb62b941bf3a0a811ff4902dc92d3fe is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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/lib/debug/.build-id/a2/52a1af7fb62b941bf3a0a811ff4902dc92d3fe.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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/lib/debug/.build-id/fc/e03f456364aa66aca1748a9b9fa83e9cfbe053 is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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/lib/debug/.build-id/fc/e03f456364aa66aca1748a9b9fa83e9cfbe053.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-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.
desktop-file-validate utility printed the following message(s): /usr/share/applications/math.desktop: hint: value "Office;Spreadsheet;Education;Science;Math;X-Red-Hat-Base;X-MandrivaLinux-Office-Other;" 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/math.desktop: hint: value "Office;Spreadsheet;Education;Science;Math;X-Red-Hat-Base;X-MandrivaLinux-Office-Other;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
value of symlink /usr/lib/debug/.build-id/01/461bfd0bfd4633259d28d1176a105fec5c2cb4.debug is different from the same symlink in the package LibreOffice-kde4-debuginfo-6.0.1.1-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.
/usr/share/applications/opencascade-draw.desktop: hint: value "ConsoleOnly;Graphics;3DGraphics;DataVisualization;Education;Science;" 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/anykiosk.desktop: warning: value "????????? ??????" for key "Comment[ru_RU]" in group "Desktop Entry" looks redundant with value "????????? ??????" of key "GenericName[ru_RU]"
/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
/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
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.
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.
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.
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.
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.
There are file conflicts with the package ohai-doc-14.1.5-alt1.noarch, for example, /usr/share/ri/site/Chef/cdesc-Chef.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-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.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/FFI/Pointer/cdesc-Pointer.ri /usr/share/ri/site/FFI/cdesc-FFI.ri conflict with the package ruby-ffi-doc-1.9.23-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.
There are file conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.4.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.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.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mail-doc-2.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/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.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/Symbol/cdesc-Symbol.ri conflicts with the package ruby-msgpack-doc-1.1.0-alt1.4.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.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/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-5.5.0-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.
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.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-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.
/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
/usr/share/pixmaps/cuneiform-qt.png
/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]"
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.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.
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.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.
/usr/share/applications/freecad.desktop: hint: value "Graphics;Science;Education;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 "Graphics;Science;Education;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/gamine.desktop: error: file contains key "comment" in group "Desktop Entry", but keys extending the format should start with "X-"
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
[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
/usr might be mounted read-only and thus, the local system
administrator would not have a chance to modify this configuration
file.
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).
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"
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.
/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-"
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
/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]"
/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-"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "???? ?????? ?????" for key "Comment[ar]" in group "Desktop Entry" looks redundant with value "???? ?????? ?????" of key "GenericName[ar]"
/usr/share/applications/kf5/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/kf5/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/kf5/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/kf5/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/kf5/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/kf5/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/kf5/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/kf5/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/kf5/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/kf5/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/kf5/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/kf5/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/kf5/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/kf5/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/kf5/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/kf5/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/kf5/org.kde.kmymoney.desktop: warning: value "Asmenini? finans? tvarkytuv?" for key "Comment[lt]" in group "Desktop Entry" looks redundant with value "Asmenini? finans? tvarkytuv?" of key "GenericName[lt]"
/usr/share/applications/kf5/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/kf5/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/kf5/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/kf5/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/kf5/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/kf5/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/kf5/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/kf5/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/kf5/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/kf5/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/kf5/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/kf5/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/kf5/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/kf5/org.kde.kmymoney.desktop: warning: value "????????" for key "Comment[zh_TW]" in group "Desktop Entry" looks redundant with value "????????" of key "GenericName[zh_TW]"
/usr/share/applications/kde/kunit.desktop: warning: value "????????? ?????????? ???????" for key "Comment[ru]" in group "Desktop Entry" looks redundant with value "????????? ?????????? ???????" of key "GenericName[ru]"
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
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
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
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
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
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
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.
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.7.7-alt1.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.14 is an alternative in package libwbclient-DC-4.7.7-alt1.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.14.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-DC-4.7.7-alt1.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 is an alternative in package libwbclient-sssd-1.16.1-alt5.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.
value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-debuginfo-4.7.7-alt1.S1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
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.16.1-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.
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.7.7-alt1.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-sssd-devel-1.16.1-alt5.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.
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).
/usr/share/applications/modem-manager-gui.desktop: hint: value "GTK;System;Utility;Network;TelephonyTools;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
/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.
/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
The package obsoletes the package openerp-httpd-fonts-access-7.0-alt4.20140326.noarch, but the package openerp-httpd-fonts-access-7.0-alt4.20140326.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.
There are file conflicts with the package chef-doc-12.15.11-alt1.noarch, for example, /usr/share/ri/site/Chef/cdesc-Chef.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/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/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.
Files /usr/share/ri/site/Chef/cdesc-Chef.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/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/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/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/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-alt2.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-ffi-yajl-doc-2.3.1-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.
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/String/cdesc-String.ri conflicts with the package ruby-oj-doc-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/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-5.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/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.
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.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-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.
value of symlink /usr/lib64/libmapi.so is different from the same symlink in the package zarafa-devel-7.1.15-alt19.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.
/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.
/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.
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
/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.
/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.
/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.
/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]"
/usr/share/applications/qgoogletranslator.desktop: error: file contains multiple keys named "Type" in group "Desktop Entry"
/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
/usr/share/applications/rox.desktop: hint: value item "FileManager" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: System;FileTools
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.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/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.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.
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-5.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-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.
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 ohai-doc-14.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.
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.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-ffi-yajl-doc-2.3.1-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.
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/String/cdesc-String.ri conflicts with the package ruby-oj-doc-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/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-5.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/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.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-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.
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.
Files /usr/share/ri/site/Chef/cdesc-Chef.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ohai-doc-14.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.
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.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/String/cdesc-String.ri conflict with the package ruby-ffi-yajl-doc-2.3.1-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.
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.
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.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/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-5.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/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.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-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/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.
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.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.
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-5.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.
Files /usr/share/ri/site/EM/cdesc-EM.ri /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflict with the package ruby-em-mongo-doc-0.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/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.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.
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 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 ohai-doc-14.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.
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-mongo-doc-0.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/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.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.
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.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-ffi-yajl-doc-2.3.1-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.
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/String/cdesc-String.ri conflicts with the package ruby-oj-doc-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/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-5.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/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.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-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/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-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/Mongo/Collection/cdesc-Collection.ri (11 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.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.
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/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-mongo-doc-0.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/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.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.
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/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-mongo-doc-0.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/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.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.
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.
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.6.0-alt1.noarch, for example, /usr/share/ri/site/EM/Mongo/Collection/cdesc-Collection.ri (11 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.7-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/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.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.
File /usr/share/ri/site/Mongo/cdesc-Mongo.ri conflicts with the package ruby-mongo-doc-2.5.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-mysql2-doc-0.5.1-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.16.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.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/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.
Files /usr/share/ri/site/EM/cdesc-EM.ri /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflict with the package ruby-em-mongo-doc-0.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.
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.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.
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.
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 ohai-doc-14.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.
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.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.
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/String/cdesc-String.ri conflicts with the package ruby-oj-doc-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.
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-5.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/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.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-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.
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/String/cdesc-String.ri conflicts with the package ohai-doc-14.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.
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.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/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.4.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/Net/cdesc-Net.ri conflicts with the package ruby-mail-doc-2.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/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.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/Symbol/cdesc-Symbol.ri conflicts with the package ruby-msgpack-doc-1.1.0-alt1.4.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.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/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-5.5.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.
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.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-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.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 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 ohai-doc-14.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.
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.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 /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-ffi-yajl-doc-2.3.1-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.
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.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.
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.
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.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/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-5.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/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.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-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/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.
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.4.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.
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.4.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.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/Symbol/cdesc-Symbol.ri conflicts with the package ruby-msgpack-doc-1.1.0-alt1.4.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.6.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-5.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 yajl-ruby-doc-1.4.0-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.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-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.
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/Net/cdesc-Net.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-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.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mail-doc-2.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/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.
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.
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.
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.
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.
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.
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/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.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.
File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package ruby-json-pure-doc-2.1.0-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.
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.4.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-5.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-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.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-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.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mail-doc-2.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/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.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-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.
File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mail-doc-2.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/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.
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 ohai-doc-14.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.
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.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-ffi-yajl-doc-2.3.1-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.
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.4.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-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-5.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/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.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-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.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/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.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.
File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package yajl-ruby-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/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.
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 ohai-doc-14.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.
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.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-ffi-yajl-doc-2.3.1-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.
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/String/cdesc-String.ri conflicts with the package ruby-oj-doc-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/String/cdesc-String.ri conflicts with the package ruby-sequel-doc-5.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/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.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-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/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.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.
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-5.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/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.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.
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.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.
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.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.
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-5.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/Enumerable/cdesc-Enumerable.ri conflicts with the package ruby-sigar-doc-0.7.3-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.
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.
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.
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.
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.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.
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.
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.
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.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.
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.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.
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.
There are file conflicts with the package ruby-idn-doc-0.1.0-alt3.4.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.
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.
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.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.
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-5.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/File/cdesc-File.ri conflicts with the package ruby-sigar-doc-0.7.3-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.
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 ohai-doc-14.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.
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.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-ffi-yajl-doc-2.3.1-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.
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/String/cdesc-String.ri conflicts with the package ruby-oj-doc-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/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-5.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/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.
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 ohai-doc-14.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.
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.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-ffi-yajl-doc-2.3.1-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.
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/String/cdesc-String.ri conflicts with the package ruby-oj-doc-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/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-5.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/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.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.
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.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 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.
value of symlink /lib64/libnss_wins.so.2 is different from the same symlink in the package samba-winbind-clients-4.7.7-alt1.S1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
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/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
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 ohai-doc-14.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.
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.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-ffi-yajl-doc-2.3.1-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.
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/String/cdesc-String.ri conflicts with the package ruby-oj-doc-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/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-5.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/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.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-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.
/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]"
/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
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.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.
/usr/share/applications/wcm.desktop: error: action group "Desktop Action NewWindow" exists, but there is no matching action "NewWindow"
Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/qhandjoob.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/qvideoob.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/qflatboob.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/qcookboob.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/weboob-config-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).
Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/qcineoob.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/qwebcontentedit.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/qboobmsg.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).
/usr might be mounted read-only and thus, the local system
administrator would not have a chance to modify this configuration
file.
/usr might be mounted read-only and thus, the local system
administrator would not have a chance to modify this configuration
file.
/usr/share/applications/librecad.desktop: warning: value "??????? ??????????????????? ??????????????" for key "Comment[ru]" in group "Desktop Entry" looks redundant with value "??????? ??????????????????? ??????????????" of key "GenericName[ru]"
/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.