warn	3proxy-0.6.1-alt2.x86_64	File /usr/bin/proxy conflicts with the package libproxy-tools-0.4.15-alt5.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.; 
warn	LibreOffice-integrated-7.1.3.2-alt0.p9.1.x86_64	There are file conflicts with the package LibreOffice-still-common-7.0.6.2-alt2.x86_64, for example, /usr/bin/libreoffice (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/metainfo/org.libreoffice.kde.metainfo.xml conflicts with the package LibreOffice-still-kde5-7.0.6.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.; 
warn	LibreOffice-still-common-7.0.6.2-alt2.x86_64	There are file conflicts with the package LibreOffice-integrated-7.1.3.2-alt0.p9.1.x86_64, for example, /usr/bin/libreoffice (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.; 
warn	LibreOffice-still-kde5-7.0.6.2-alt2.x86_64	File /usr/share/metainfo/org.libreoffice.kde.metainfo.xml conflicts with the package LibreOffice-integrated-7.1.3.2-alt0.p9.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.; 
warn	Little-Wire-examples-1.3-alt1.x86_64	File /usr/bin/adc conflicts with the package autodafe-0.1-alt2_6.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/bin/blink conflicts with the package blink-qt-3.2.1-alt0.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.; 
warn	MySQL-server-8.0.26-alt2.x86_64	File /usr/share/man/man8/mysqld.8.xz conflicts with the package mariadb-client-10.4.34-alt0.M90P.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.; 
warn	SNNS-4.3-alt1.1.1.1.x86_64	File /usr/bin/analyze conflicts with the package hunspell-utils-1.7.0-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	altlinux-release-p9-20191210-alt1.noarch	Files /etc/altlinux-release /etc/os-release conflict with the package branding-alt-education-release-9.2-alt4.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/altlinux-release /etc/os-release conflict with the package branding-alt-server-v-release-9.2-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /etc/altlinux-release /etc/os-release conflict with the package branding-alt-starterkit-release-p9-alt9.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/altlinux-release /etc/os-release conflict with the package branding-alt-tonk-release-9.0-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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.; Files /etc/altlinux-release /etc/os-release conflict with the package branding-altlinux-centaurus-release-7.0.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 /etc/altlinux-release conflicts with the package branding-altlinux-desktop-release-5.9.9-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.; Files /etc/altlinux-release /etc/os-release conflict with the package branding-altlinux-kdesktop-release-8.0.0-alt0.6.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-altlinux-lite-release-5.9.9-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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-office-server-release-5.9.9-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /etc/altlinux-release /etc/os-release conflict with the package branding-altlinux-spt-release-7.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 /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-ivk-chainmail-release-3.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-school-lite-release-5.9.9-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /etc/altlinux-release /etc/os-release conflict with the package branding-xalt-kworkstation-release-9.2.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.; 
warn	arprec-2.2.19-alt1.x86_64	File /usr/bin/quads conflicts with the package mesa-demos-8.4.0-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-core-sounds-fr-alaw-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.alaw conflicts with the package asterisk-extra-sounds-fr-alaw-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-core-sounds-fr-g722-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.g722 conflicts with the package asterisk-extra-sounds-fr-g722-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-core-sounds-fr-g729-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.g729 conflicts with the package asterisk-extra-sounds-fr-g729-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-core-sounds-fr-gsm-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.gsm conflicts with the package asterisk-extra-sounds-fr-gsm-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-core-sounds-fr-siren14-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.siren14 conflicts with the package asterisk-extra-sounds-fr-siren14-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-core-sounds-fr-siren7-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.siren7 conflicts with the package asterisk-extra-sounds-fr-siren7-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-core-sounds-fr-sln16-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.sln16 conflicts with the package asterisk-extra-sounds-fr-sln16-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-core-sounds-fr-ulaw-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.ulaw conflicts with the package asterisk-extra-sounds-fr-ulaw-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-core-sounds-fr-wav-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.wav conflicts with the package asterisk-extra-sounds-fr-wav-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-extra-sounds-fr-alaw-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.alaw conflicts with the package asterisk-core-sounds-fr-alaw-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-extra-sounds-fr-g722-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.g722 conflicts with the package asterisk-core-sounds-fr-g722-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-extra-sounds-fr-g729-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.g729 conflicts with the package asterisk-core-sounds-fr-g729-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-extra-sounds-fr-gsm-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.gsm conflicts with the package asterisk-core-sounds-fr-gsm-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-extra-sounds-fr-siren14-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.siren14 conflicts with the package asterisk-core-sounds-fr-siren14-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-extra-sounds-fr-siren7-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.siren7 conflicts with the package asterisk-core-sounds-fr-siren7-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-extra-sounds-fr-sln16-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.sln16 conflicts with the package asterisk-core-sounds-fr-sln16-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-extra-sounds-fr-ulaw-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.ulaw conflicts with the package asterisk-core-sounds-fr-ulaw-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-extra-sounds-fr-wav-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.wav conflicts with the package asterisk-core-sounds-fr-wav-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	atril-gtk-dvi-1.22.3-alt2.x86_64	File /usr/lib64/atril/3/backends/libdvidocument.so conflicts with the package mate-document-viewer-dvi-1.22.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.; 
warn	autodafe-0.1-alt2_6.x86_64	File /usr/bin/adc conflicts with the package Little-Wire-examples-1.3-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.; 
warn	bash-completion-elogind-241.2-alt1.noarch	File /usr/share/bash-completion/completions/loginctl conflicts with the package systemd-services-247.13-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.; 
warn	batik-slideshow-1.10-alt1_2jpp8.noarch	File /usr/bin/slideshow conflicts with the package racket-7.3-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.; 
warn	bitmap-1.0.6-alt1.x86_64	File /usr/bin/bitmap conflicts with the package mesa-demos-8.4.0-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	blackbox-0.74-alt1.x86_64	Files /usr/share/icons/hicolor/16x16/apps/blackbox.png /usr/share/icons/hicolor/32x32/apps/blackbox.png /usr/share/icons/hicolor/48x48/apps/blackbox.png conflict with the package tatham-puzzles-20180227-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.; 
warn	blink-qt-3.2.1-alt0.1.x86_64	File /usr/bin/blink conflicts with the package Little-Wire-examples-1.3-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.; 
warn	branding-alt-education-release-9.2-alt4.noarch	Files /etc/altlinux-release /etc/os-release conflict with the package altlinux-release-p9-20191210-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-alt-education-xfce-settings-9.2-alt4.x86_64	File /etc/skel/.config/gtk-3.0/settings.ini conflicts with the package branding-alt-workstation-mate-settings-9.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 /etc/skel/.config/autostart/tracker-store.desktop /etc/skel/.config/gtk-3.0/settings.ini /etc/skel/.gtkrc-2.0 conflict with the package branding-altlinux-kdesktop-graphics-8.0.0-alt0.6.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /etc/skel/.config/autostart/tracker-store.desktop /etc/skel/.config/gtk-3.0/settings.ini /etc/skel/.gtkrc-2.0 conflict with the package branding-xalt-kworkstation-graphics-9.2.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/skel/.gconf/apps/%gconf.xml conflicts with the package livecd-gnome-nowarn-space-0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /etc/skel/.config/xfce4/desktop/icons.screen0.rc /etc/skel/.config/xfce4/helpers.rc conflict with the package xfce-settings-lite-1.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /etc/skel/.config/xfce4/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.; 
warn	branding-alt-server-v-release-9.2-alt2.noarch	Files /etc/altlinux-release /etc/os-release conflict with the package altlinux-release-p9-20191210-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-alt-starterkit-release-p9-alt9.noarch	Files /etc/altlinux-release /etc/os-release conflict with the package altlinux-release-p9-20191210-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-alt-tonk-release-9.0-alt1.x86_64	Files /etc/altlinux-release /etc/os-release conflict with the package altlinux-release-p9-20191210-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-alt-tonk-xfce-settings-9.0-alt1.x86_64	File /etc/skel/.gconf/apps/%gconf.xml conflicts with the package livecd-gnome-nowarn-space-0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /etc/skel/.config/xfce4/desktop/icons.screen0.rc /etc/skel/.config/xfce4/helpers.rc conflict with the package xfce-settings-lite-school-0.6-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-alt-workstation-mate-settings-9.2-alt1.noarch	File /etc/skel/.config/gtk-3.0/settings.ini conflicts with the package branding-alt-education-xfce-settings-9.2-alt4.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 /etc/skel/.gtkrc-2.0 conflicts with the package branding-simply-linux-xfce-settings-9.1-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.; 
warn	branding-altlinux-backup-server-alterator-6.0.0-alt3.noarch	There are file conflicts with the package branding-altlinux-kdesktop-alterator-8.0.0-alt0.6.noarch, for example, /usr/share/alterator/design/images/clock-face.png (41 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lxdesktop-alterator-6.0.0-alt7.noarch, for example, /usr/share/alterator/design/images/clock-face.png (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 branding-altlinux-tablet-alterator-6.0.0-alt3.noarch, for example, /usr/share/alterator/design/images/clock-face.png (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 branding-informika-schoolmaster-alterator-6.0.0-alt47.noarch, for example, /usr/share/alterator/design/images/clock-face.png (41 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-xalt-kworkstation-alterator-9.2.0-alt3.noarch, for example, /usr/share/alterator/design/images/attention.gif (35 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.; 
warn	branding-altlinux-backup-server-indexhtml-6.0.0-alt3.noarch	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 (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-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-xalt-kworkstation-indexhtml-9.2.0-alt3.x86_64, 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.; 
warn	branding-altlinux-backup-server-notes-6.0.0-alt3.noarch	There are file conflicts with the package branding-altlinux-kdesktop-notes-8.0.0-alt0.6.noarch, for example, /usr/share/alt-notes/index-en.html (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lxdesktop-notes-6.0.0-alt7.noarch, for example, /usr/share/alt-notes/index-en.html (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-tablet-notes-6.0.0-alt3.noarch, for example, /usr/share/alt-notes/index-en.html (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-informika-schoolmaster-notes-6.0.0-alt47.noarch, for example, /usr/share/alt-notes/index-en.html (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-school-lite-notes-5.9.9-alt1.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-xalt-kworkstation-notes-9.2.0-alt3.noarch, for example, /usr/share/alt-notes/index-en.html (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.; 
warn	branding-altlinux-backup-server-release-6.0.0-alt3.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-p9-20191210-alt1.noarch. 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-kdesktop-release-8.0.0-alt0.6.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-altlinux-lxdesktop-release-6.0.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-altlinux-tablet-release-6.0.0-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-informika-schoolmaster-release-6.0.0-alt47.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-school-lite-release-5.9.9-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-xalt-kworkstation-release-9.2.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.; 
warn	branding-altlinux-centaurus-alterator-7.0.5-alt1.noarch	There are file conflicts with the package branding-altlinux-kdesktop-alterator-8.0.0-alt0.6.noarch, for example, /usr/share/alterator/design/images/attention.gif (15 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-informika-schoolmaster-alterator-6.0.0-alt47.noarch, for example, /usr/share/alterator/design/images/attention.gif (15 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-xalt-kworkstation-alterator-9.2.0-alt3.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (14 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.; 
warn	branding-altlinux-centaurus-indexhtml-7.0.5-alt1.noarch	There are file conflicts with the package branding-altlinux-backup-server-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-altlinux-desktop-indexhtml-5.9.9-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-altlinux-kdesktop-indexhtml-8.0.0-alt0.6.noarch, for example, /usr/share/applications/indexhtml.desktop (13 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lxdesktop-indexhtml-6.0.0-alt7.noarch, for example, /usr/share/doc/indexhtml/images/altlinux-logo.png (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 branding-altlinux-office-server-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/applications/indexhtml.desktop /usr/share/doc/indexhtml/index-en.html conflict with the package branding-altlinux-spt-indexhtml-7.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.; There are file conflicts with the package branding-altlinux-tablet-indexhtml-6.0.0-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (12 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 (12 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 (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-school-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-simply-linux-indexhtml-9.1-alt2.noarch, for example, /usr/share/applications/indexhtml.desktop (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 branding-xalt-kworkstation-indexhtml-9.2.0-alt3.x86_64, for example, /usr/share/applications/indexhtml.desktop (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.; 
warn	branding-altlinux-centaurus-kde4-settings-7.0.5-alt1.noarch	File /etc/skel/.kde4/share/config/default-apps conflicts with the package branding-xalt-kworkstation-kde4-settings-9.2.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.; 
warn	branding-altlinux-centaurus-notes-7.0.5-alt1.noarch	There are file conflicts with the package branding-xalt-kworkstation-notes-9.2.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.; 
warn	branding-altlinux-centaurus-release-7.0.5-alt1.noarch	Files /etc/altlinux-release /etc/os-release conflict with the package altlinux-release-p9-20191210-alt1.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/altlinux-release /etc/os-release conflict with the package branding-xalt-kworkstation-release-9.2.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.; 
warn	branding-altlinux-desktop-indexhtml-5.9.9-alt3.noarch	There are file conflicts with the package branding-altlinux-backup-server-indexhtml-6.0.0-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-centaurus-indexhtml-7.0.5-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-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 (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-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-9.1-alt2.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.; 
warn	branding-altlinux-desktop-release-5.9.9-alt3.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-p9-20191210-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-altlinux-desktop-xfce-settings-5.9.9-alt3.noarch	File /etc/skel/.config/xfce4/panel/launcher-11888137035.rc conflicts with the package xfce-settings-lite-office-lite-1.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /etc/skel/.config/xfce4/panel/panels.xml /etc/skel/.local/share/applications/defaults.list /usr/share/xfce4/backdrops/xdm.png conflict with the package xfce-settings-lite-school-0.6-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.config/xfce4/panel/launcher-10.rc conflicts with the package xfce-settings-lite-school-network-0.6-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.config/xfce4/panel/launcher-11888137035.rc conflicts with the package xfce-settings-lite-school-office-lite-0.6-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-altlinux-kdesktop-alterator-8.0.0-alt0.6.noarch	There are file conflicts with the package branding-altlinux-backup-server-alterator-6.0.0-alt3.noarch, for example, /usr/share/alterator/design/images/clock-face.png (41 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-centaurus-alterator-7.0.5-alt1.noarch, for example, /usr/share/alterator/design/images/attention.gif (15 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lxdesktop-alterator-6.0.0-alt7.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (36 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-spt-alterator-7.0.0-alt1.noarch, for example, /usr/share/alterator/design/images/attention.gif (15 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-tablet-alterator-6.0.0-alt3.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (36 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-informika-schoolmaster-alterator-6.0.0-alt47.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (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-ivk-chainmail-alterator-3.0-alt2.noarch, for example, /usr/share/alterator/design/images/clock-face.png (39 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.; 
warn	branding-altlinux-kdesktop-graphics-8.0.0-alt0.6.noarch	Files /etc/skel/.config/autostart/tracker-store.desktop /etc/skel/.config/gtk-3.0/settings.ini /etc/skel/.gtkrc-2.0 conflict with the package branding-alt-education-xfce-settings-9.2-alt4.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 /etc/skel/.gtkrc-2.0 conflicts with the package branding-simply-linux-xfce-settings-9.1-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.; 
warn	branding-altlinux-kdesktop-indexhtml-8.0.0-alt0.6.noarch	There are file conflicts with the package branding-altlinux-backup-server-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-altlinux-centaurus-indexhtml-7.0.5-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (13 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 (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lxdesktop-indexhtml-6.0.0-alt7.noarch, for example, /usr/share/applications/indexhtml.desktop (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-office-server-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-spt-indexhtml-7.0.0-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (13 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 (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-informika-schoolmaster-indexhtml-6.0.0-alt47.noarch, for example, /usr/share/applications/indexhtml.desktop (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-ivk-chainmail-indexhtml-3.0-alt2.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-school-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-simply-linux-indexhtml-9.1-alt2.noarch, for example, /usr/share/applications/indexhtml.desktop (12 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.; 
warn	branding-altlinux-kdesktop-kde4-settings-8.0.0-alt0.6.noarch	File /etc/skel/.kde4/share/config/default-apps conflicts with the package branding-altlinux-tablet-kde4-settings-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.; 
warn	branding-altlinux-kdesktop-notes-8.0.0-alt0.6.noarch	There are file conflicts with the package branding-altlinux-backup-server-notes-6.0.0-alt3.noarch, for example, /usr/share/alt-notes/index-en.html (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lxdesktop-notes-6.0.0-alt7.noarch, for example, /usr/share/alt-notes/index-en.html (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-tablet-notes-6.0.0-alt3.noarch, for example, /usr/share/alt-notes/index-en.html (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.; 
warn	branding-altlinux-kdesktop-release-8.0.0-alt0.6.noarch	Files /etc/altlinux-release /etc/os-release conflict with the package altlinux-release-p9-20191210-alt1.noarch. 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.; 
warn	branding-altlinux-lite-indexhtml-5.9.9-alt1.noarch	There are file conflicts with the package branding-altlinux-backup-server-indexhtml-6.0.0-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-centaurus-indexhtml-7.0.5-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-desktop-indexhtml-5.9.9-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-kdesktop-indexhtml-8.0.0-alt0.6.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lxdesktop-indexhtml-6.0.0-alt7.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-office-server-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-spt-indexhtml-7.0.0-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-tablet-indexhtml-6.0.0-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-informika-schoolmaster-indexhtml-6.0.0-alt47.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-ivk-chainmail-indexhtml-3.0-alt2.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-school-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-simply-linux-indexhtml-9.1-alt2.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.; 
warn	branding-altlinux-lite-release-5.9.9-alt1.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-p9-20191210-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-altlinux-lite-xfce-settings-5.9.9-alt1.noarch	File /etc/skel/.config/xfce4/panel/launcher-11888137035.rc conflicts with the package xfce-settings-lite-office-lite-1.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /etc/skel/.config/xfce4/panel/panels.xml /etc/skel/.local/share/applications/defaults.list /usr/share/xfce4/backdrops/xdm.png conflict with the package xfce-settings-lite-school-0.6-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.config/xfce4/panel/launcher-10.rc conflicts with the package xfce-settings-lite-school-network-0.6-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.config/xfce4/panel/launcher-11888137035.rc conflicts with the package xfce-settings-lite-school-office-lite-0.6-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-altlinux-lxdesktop-alterator-6.0.0-alt7.noarch	There are file conflicts with the package branding-altlinux-backup-server-alterator-6.0.0-alt3.noarch, for example, /usr/share/alterator/design/images/clock-face.png (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 branding-altlinux-kdesktop-alterator-8.0.0-alt0.6.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (36 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-tablet-alterator-6.0.0-alt3.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-informika-schoolmaster-alterator-6.0.0-alt47.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (36 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-xalt-kworkstation-alterator-9.2.0-alt3.noarch, for example, /usr/share/alterator/design/images/attention.gif (37 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.; 
warn	branding-altlinux-lxdesktop-indexhtml-6.0.0-alt7.noarch	There are file conflicts with the package branding-altlinux-backup-server-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-altlinux-centaurus-indexhtml-7.0.5-alt1.noarch, for example, /usr/share/doc/indexhtml/images/altlinux-logo.png (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 branding-altlinux-desktop-indexhtml-5.9.9-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-altlinux-kdesktop-indexhtml-8.0.0-alt0.6.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-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-office-server-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-spt-indexhtml-7.0.0-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (12 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/applications/indexhtml.desktop /usr/share/doc/indexhtml/index-en.html /usr/share/doc/indexhtml/index-ru.html conflict with the package branding-altlinux-tablet-indexhtml-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.; 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 (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-school-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-simply-linux-indexhtml-9.1-alt2.noarch, for example, /usr/share/applications/indexhtml.desktop (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 branding-xalt-kworkstation-indexhtml-9.2.0-alt3.x86_64, 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.; 
warn	branding-altlinux-lxdesktop-notes-6.0.0-alt7.noarch	There are file conflicts with the package branding-altlinux-backup-server-notes-6.0.0-alt3.noarch, for example, /usr/share/alt-notes/index-en.html (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-kdesktop-notes-8.0.0-alt0.6.noarch, for example, /usr/share/alt-notes/index-en.html (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-tablet-notes-6.0.0-alt3.noarch, for example, /usr/share/alt-notes/index-en.html (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-informika-schoolmaster-notes-6.0.0-alt47.noarch, for example, /usr/share/alt-notes/index-en.html (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-school-lite-notes-5.9.9-alt1.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-xalt-kworkstation-notes-9.2.0-alt3.noarch, for example, /usr/share/alt-notes/index-en.html (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.; 
warn	branding-altlinux-lxdesktop-release-6.0.0-alt7.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-p9-20191210-alt1.noarch. 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-kdesktop-release-8.0.0-alt0.6.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-altlinux-tablet-release-6.0.0-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-informika-schoolmaster-release-6.0.0-alt47.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-school-lite-release-5.9.9-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-xalt-kworkstation-release-9.2.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.; 
warn	branding-altlinux-office-server-indexhtml-5.9.9-alt1.noarch	There are file conflicts with the package branding-altlinux-backup-server-indexhtml-6.0.0-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-centaurus-indexhtml-7.0.5-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-desktop-indexhtml-5.9.9-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-kdesktop-indexhtml-8.0.0-alt0.6.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lxdesktop-indexhtml-6.0.0-alt7.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-spt-indexhtml-7.0.0-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-tablet-indexhtml-6.0.0-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-informika-schoolmaster-indexhtml-6.0.0-alt47.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-ivk-chainmail-indexhtml-3.0-alt2.noarch, for example, /usr/share/applications/indexhtml.desktop (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-school-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-simply-linux-indexhtml-9.1-alt2.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.; 
warn	branding-altlinux-office-server-release-5.9.9-alt1.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-p9-20191210-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-altlinux-spt-alterator-7.0.0-alt1.noarch	There are file conflicts with the package branding-altlinux-kdesktop-alterator-8.0.0-alt0.6.noarch, for example, /usr/share/alterator/design/images/attention.gif (15 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-informika-schoolmaster-alterator-6.0.0-alt47.noarch, for example, /usr/share/alterator/design/images/attention.gif (15 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-xalt-kworkstation-alterator-9.2.0-alt3.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (14 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.; 
warn	branding-altlinux-spt-indexhtml-7.0.0-alt1.noarch	There are file conflicts with the package branding-altlinux-backup-server-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.; Files /usr/share/applications/indexhtml.desktop /usr/share/doc/indexhtml/index-en.html conflict with the package branding-altlinux-centaurus-indexhtml-7.0.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 branding-altlinux-desktop-indexhtml-5.9.9-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-altlinux-kdesktop-indexhtml-8.0.0-alt0.6.noarch, for example, /usr/share/applications/indexhtml.desktop (13 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lxdesktop-indexhtml-6.0.0-alt7.noarch, for example, /usr/share/applications/indexhtml.desktop (12 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 (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 (12 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 (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 branding-ivk-chainmail-indexhtml-3.0-alt2.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-school-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-simply-linux-indexhtml-9.1-alt2.noarch, for example, /usr/share/applications/indexhtml.desktop (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 branding-xalt-kworkstation-indexhtml-9.2.0-alt3.x86_64, for example, /usr/share/applications/indexhtml.desktop (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.; 
warn	branding-altlinux-spt-kde4-settings-7.0.0-alt1.noarch	File /etc/skel/.kde4/share/config/default-apps conflicts with the package branding-xalt-kworkstation-kde4-settings-9.2.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.; 
warn	branding-altlinux-spt-notes-7.0.0-alt1.noarch	There are file conflicts with the package branding-xalt-kworkstation-notes-9.2.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.; 
warn	branding-altlinux-spt-release-7.0.0-alt1.noarch	Files /etc/altlinux-release /etc/os-release conflict with the package altlinux-release-p9-20191210-alt1.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/altlinux-release /etc/os-release conflict with the package branding-xalt-kworkstation-release-9.2.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.; 
warn	branding-altlinux-tablet-alterator-6.0.0-alt3.noarch	There are file conflicts with the package branding-altlinux-backup-server-alterator-6.0.0-alt3.noarch, for example, /usr/share/alterator/design/images/clock-face.png (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 branding-altlinux-kdesktop-alterator-8.0.0-alt0.6.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (36 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lxdesktop-alterator-6.0.0-alt7.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-informika-schoolmaster-alterator-6.0.0-alt47.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (36 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-xalt-kworkstation-alterator-9.2.0-alt3.noarch, for example, /usr/share/alterator/design/images/attention.gif (33 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.; 
warn	branding-altlinux-tablet-indexhtml-6.0.0-alt3.noarch	There are file conflicts with the package branding-altlinux-backup-server-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-altlinux-centaurus-indexhtml-7.0.5-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (12 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 (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-kdesktop-indexhtml-8.0.0-alt0.6.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-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/applications/indexhtml.desktop /usr/share/doc/indexhtml/index-en.html /usr/share/doc/indexhtml/index-ru.html conflict with the package branding-altlinux-lxdesktop-indexhtml-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.; There are file conflicts with the package branding-altlinux-office-server-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-spt-indexhtml-7.0.0-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (12 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 (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-school-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-simply-linux-indexhtml-9.1-alt2.noarch, for example, /usr/share/applications/indexhtml.desktop (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 branding-xalt-kworkstation-indexhtml-9.2.0-alt3.x86_64, 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.; 
warn	branding-altlinux-tablet-kde4-settings-6.0.0-alt3.noarch	File /etc/skel/.kde4/share/config/default-apps conflicts with the package branding-altlinux-kdesktop-kde4-settings-8.0.0-alt0.6.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.kde4/share/config/default-apps conflicts with the package branding-informika-schoolmaster-kde4-settings-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/skel/.kde4/share/config/default-apps conflicts with the package branding-xalt-kworkstation-kde4-settings-9.2.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.; 
warn	branding-altlinux-tablet-notes-6.0.0-alt3.noarch	There are file conflicts with the package branding-altlinux-backup-server-notes-6.0.0-alt3.noarch, for example, /usr/share/alt-notes/index-en.html (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-kdesktop-notes-8.0.0-alt0.6.noarch, for example, /usr/share/alt-notes/index-en.html (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lxdesktop-notes-6.0.0-alt7.noarch, for example, /usr/share/alt-notes/index-en.html (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-informika-schoolmaster-notes-6.0.0-alt47.noarch, for example, /usr/share/alt-notes/index-en.html (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-school-lite-notes-5.9.9-alt1.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-xalt-kworkstation-notes-9.2.0-alt3.noarch, for example, /usr/share/alt-notes/index-en.html (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.; 
warn	branding-altlinux-tablet-release-6.0.0-alt3.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-p9-20191210-alt1.noarch. 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-kdesktop-release-8.0.0-alt0.6.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /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-informika-schoolmaster-release-6.0.0-alt47.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-school-lite-release-5.9.9-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-xalt-kworkstation-release-9.2.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.; 
warn	branding-informika-schoolmaster-alterator-6.0.0-alt47.noarch	There are file conflicts with the package branding-altlinux-backup-server-alterator-6.0.0-alt3.noarch, for example, /usr/share/alterator/design/images/clock-face.png (41 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-centaurus-alterator-7.0.5-alt1.noarch, for example, /usr/share/alterator/design/images/attention.gif (15 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-kdesktop-alterator-8.0.0-alt0.6.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (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-lxdesktop-alterator-6.0.0-alt7.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (36 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-spt-alterator-7.0.0-alt1.noarch, for example, /usr/share/alterator/design/images/attention.gif (15 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-tablet-alterator-6.0.0-alt3.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (36 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-ivk-chainmail-alterator-3.0-alt2.noarch, for example, /usr/share/alterator/design/images/clock-face.png (39 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-xalt-kworkstation-alterator-9.2.0-alt3.noarch, for example, /usr/share/alterator/design/images/attention.gif (38 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.; 
warn	branding-informika-schoolmaster-indexhtml-6.0.0-alt47.noarch	There are file conflicts with the package branding-altlinux-backup-server-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-altlinux-centaurus-indexhtml-7.0.5-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (12 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 (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-kdesktop-indexhtml-8.0.0-alt0.6.noarch, for example, /usr/share/applications/indexhtml.desktop (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lxdesktop-indexhtml-6.0.0-alt7.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-office-server-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (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 (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 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-ivk-chainmail-indexhtml-3.0-alt2.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-school-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-simply-linux-indexhtml-9.1-alt2.noarch, for example, /usr/share/applications/indexhtml.desktop (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 branding-xalt-kworkstation-indexhtml-9.2.0-alt3.x86_64, for example, /usr/share/applications/indexhtml.desktop (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.; 
warn	branding-informika-schoolmaster-kde4-settings-6.0.0-alt47.noarch	File /etc/skel/.kde4/share/config/default-apps conflicts with the package branding-altlinux-tablet-kde4-settings-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.; 
warn	branding-informika-schoolmaster-notes-6.0.0-alt47.noarch	There are file conflicts with the package branding-altlinux-backup-server-notes-6.0.0-alt3.noarch, for example, /usr/share/alt-notes/index-en.html (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lxdesktop-notes-6.0.0-alt7.noarch, for example, /usr/share/alt-notes/index-en.html (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-tablet-notes-6.0.0-alt3.noarch, for example, /usr/share/alt-notes/index-en.html (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-school-lite-notes-5.9.9-alt1.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-xalt-kworkstation-notes-9.2.0-alt3.noarch, for example, /usr/share/alt-notes/index-en.html (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.; 
warn	branding-informika-schoolmaster-release-6.0.0-alt47.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-p9-20191210-alt1.noarch. 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-school-lite-release-5.9.9-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-xalt-kworkstation-release-9.2.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.; 
warn	branding-ivk-chainmail-alterator-3.0-alt2.noarch	There are file conflicts with the package branding-altlinux-kdesktop-alterator-8.0.0-alt0.6.noarch, for example, /usr/share/alterator/design/images/clock-face.png (39 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-informika-schoolmaster-alterator-6.0.0-alt47.noarch, for example, /usr/share/alterator/design/images/clock-face.png (39 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-xalt-kworkstation-alterator-9.2.0-alt3.noarch, for example, /usr/share/alterator/design/images/attention.gif (33 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.; 
warn	branding-ivk-chainmail-indexhtml-3.0-alt2.noarch	There are file conflicts with the package branding-altlinux-backup-server-indexhtml-6.0.0-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-centaurus-indexhtml-7.0.5-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-desktop-indexhtml-5.9.9-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-kdesktop-indexhtml-8.0.0-alt0.6.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lxdesktop-indexhtml-6.0.0-alt7.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-office-server-indexhtml-5.9.9-alt1.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-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-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-9.1-alt2.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-xalt-kworkstation-indexhtml-9.2.0-alt3.x86_64, 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.; 
warn	branding-ivk-chainmail-notes-3.0-alt2.noarch	There are file conflicts with the package branding-xalt-kworkstation-notes-9.2.0-alt3.noarch, for example, /usr/share/alt-notes/index-en.html (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.; 
warn	branding-ivk-chainmail-release-3.0-alt2.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-p9-20191210-alt1.noarch. 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-xalt-kworkstation-release-9.2.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.; 
warn	branding-school-lite-indexhtml-5.9.9-alt1.noarch	There are file conflicts with the package branding-altlinux-backup-server-indexhtml-6.0.0-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-centaurus-indexhtml-7.0.5-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-desktop-indexhtml-5.9.9-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-kdesktop-indexhtml-8.0.0-alt0.6.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lxdesktop-indexhtml-6.0.0-alt7.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-office-server-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-spt-indexhtml-7.0.0-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-tablet-indexhtml-6.0.0-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-informika-schoolmaster-indexhtml-6.0.0-alt47.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-ivk-chainmail-indexhtml-3.0-alt2.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-simply-linux-indexhtml-9.1-alt2.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.; 
warn	branding-school-lite-notes-5.9.9-alt1.noarch	There are file conflicts with the package branding-altlinux-backup-server-notes-6.0.0-alt3.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lxdesktop-notes-6.0.0-alt7.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-tablet-notes-6.0.0-alt3.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-informika-schoolmaster-notes-6.0.0-alt47.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-school-lite-release-5.9.9-alt1.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-p9-20191210-alt1.noarch. 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.; 
warn	branding-school-lite-xfce-settings-5.9.9-alt1.noarch	File /etc/skel/.config/xfce4/panel/launcher-11888137035.rc conflicts with the package xfce-settings-lite-office-lite-1.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /etc/skel/.config/xfce4/panel/panels.xml /etc/skel/.local/share/applications/defaults.list /usr/share/xfce4/backdrops/xdm.png conflict with the package xfce-settings-lite-school-0.6-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.config/xfce4/panel/launcher-10.rc conflicts with the package xfce-settings-lite-school-network-0.6-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.config/xfce4/panel/launcher-11888137035.rc conflicts with the package xfce-settings-lite-school-office-lite-0.6-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-simply-linux-indexhtml-9.1-alt2.noarch	There are file conflicts with the package branding-altlinux-centaurus-indexhtml-7.0.5-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (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 branding-altlinux-desktop-indexhtml-5.9.9-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-altlinux-kdesktop-indexhtml-8.0.0-alt0.6.noarch, for example, /usr/share/applications/indexhtml.desktop (12 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lxdesktop-indexhtml-6.0.0-alt7.noarch, for example, /usr/share/applications/indexhtml.desktop (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 branding-altlinux-office-server-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-spt-indexhtml-7.0.0-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (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 branding-altlinux-tablet-indexhtml-6.0.0-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (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 branding-informika-schoolmaster-indexhtml-6.0.0-alt47.noarch, for example, /usr/share/applications/indexhtml.desktop (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 branding-ivk-chainmail-indexhtml-3.0-alt2.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-school-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-xalt-kworkstation-indexhtml-9.2.0-alt3.x86_64, for example, /usr/share/applications/indexhtml.desktop (12 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.; 
warn	branding-simply-linux-xfce-settings-9.1-alt2.x86_64	File /etc/skel/.gtkrc-2.0 conflicts with the package branding-alt-workstation-mate-settings-9.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 /etc/skel/.gtkrc-2.0 conflicts with the package branding-altlinux-kdesktop-graphics-8.0.0-alt0.6.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.gtkrc-2.0 conflicts with the package branding-xalt-kworkstation-graphics-9.2.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/skel/.config/xfce4/helpers.rc conflicts 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.; 
warn	branding-xalt-kworkstation-alterator-9.2.0-alt3.noarch	There are file conflicts with the package branding-altlinux-backup-server-alterator-6.0.0-alt3.noarch, for example, /usr/share/alterator/design/images/attention.gif (35 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-centaurus-alterator-7.0.5-alt1.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (14 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lxdesktop-alterator-6.0.0-alt7.noarch, for example, /usr/share/alterator/design/images/attention.gif (37 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-spt-alterator-7.0.0-alt1.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (14 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-tablet-alterator-6.0.0-alt3.noarch, for example, /usr/share/alterator/design/images/attention.gif (33 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-informika-schoolmaster-alterator-6.0.0-alt47.noarch, for example, /usr/share/alterator/design/images/attention.gif (38 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-ivk-chainmail-alterator-3.0-alt2.noarch, for example, /usr/share/alterator/design/images/attention.gif (33 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.; 
warn	branding-xalt-kworkstation-graphics-9.2.0-alt3.noarch	Files /etc/skel/.config/autostart/tracker-store.desktop /etc/skel/.config/gtk-3.0/settings.ini /etc/skel/.gtkrc-2.0 conflict with the package branding-alt-education-xfce-settings-9.2-alt4.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 /etc/skel/.gtkrc-2.0 conflicts with the package branding-simply-linux-xfce-settings-9.1-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.; 
warn	branding-xalt-kworkstation-indexhtml-9.2.0-alt3.x86_64	There are file conflicts with the package branding-altlinux-backup-server-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-altlinux-centaurus-indexhtml-7.0.5-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (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 branding-altlinux-lxdesktop-indexhtml-6.0.0-alt7.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-spt-indexhtml-7.0.0-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (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 branding-altlinux-tablet-indexhtml-6.0.0-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-informika-schoolmaster-indexhtml-6.0.0-alt47.noarch, for example, /usr/share/applications/indexhtml.desktop (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-ivk-chainmail-indexhtml-3.0-alt2.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-simply-linux-indexhtml-9.1-alt2.noarch, for example, /usr/share/applications/indexhtml.desktop (12 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.; 
warn	branding-xalt-kworkstation-kde4-settings-9.2.0-alt3.noarch	File /etc/skel/.kde4/share/config/default-apps conflicts with the package branding-altlinux-centaurus-kde4-settings-7.0.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 /etc/skel/.kde4/share/config/default-apps conflicts with the package branding-altlinux-spt-kde4-settings-7.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 /etc/skel/.kde4/share/config/default-apps conflicts with the package branding-altlinux-tablet-kde4-settings-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.; 
warn	branding-xalt-kworkstation-notes-9.2.0-alt3.noarch	There are file conflicts with the package branding-altlinux-backup-server-notes-6.0.0-alt3.noarch, for example, /usr/share/alt-notes/index-en.html (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-centaurus-notes-7.0.5-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.; There are file conflicts with the package branding-altlinux-lxdesktop-notes-6.0.0-alt7.noarch, for example, /usr/share/alt-notes/index-en.html (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-spt-notes-7.0.0-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.; There are file conflicts with the package branding-altlinux-tablet-notes-6.0.0-alt3.noarch, for example, /usr/share/alt-notes/index-en.html (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-informika-schoolmaster-notes-6.0.0-alt47.noarch, for example, /usr/share/alt-notes/index-en.html (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-ivk-chainmail-notes-3.0-alt2.noarch, for example, /usr/share/alt-notes/index-en.html (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.; 
warn	branding-xalt-kworkstation-release-9.2.0-alt3.noarch	Files /etc/altlinux-release /etc/os-release conflict with the package altlinux-release-p9-20191210-alt1.noarch. 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.; Files /etc/altlinux-release /etc/os-release conflict with the package branding-altlinux-centaurus-release-7.0.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 /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.; Files /etc/altlinux-release /etc/os-release conflict with the package branding-altlinux-spt-release-7.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 /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-ivk-chainmail-release-3.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.; 
warn	bumper-0.1.8-alt1.git20150215.1.noarch	File /usr/bin/bump conflicts with the package mesa-demos-8.4.0-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	camotics-1.2.0-alt1.x86_64	File /usr/bin/planner conflicts with the package planner-0.14.6-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.; 
warn	clean-3.0-alt1.2.x86_64	File /usr/bin/clm conflicts with the package mcl-1.008.09.149-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.; 
warn	cmark-0.28.3-alt1.S1.x86_64	File /usr/bin/cmark conflicts with the package python-module-commonmark-0.8.1-alt0.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.; 
warn	cni-plugins-0.8.7-alt1.x86_64	Files /usr/libexec/cni/host-local /usr/libexec/cni/loopback conflict with the package origin-sdn-ovs-3.11.0-alt3.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.; 
warn	db4.7-utils-4.7.25-alt9.x86_64	There are file conflicts with the package pks-db-0.9.6-alt3.x86_64, for example, /usr/bin/db_archive (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.; 
warn	db4.8-utils-4.8.30-alt4.x86_64	There are file conflicts with the package pks-db-0.9.6-alt3.x86_64, for example, /usr/bin/db_archive (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.; 
warn	db6.1-utils-6.1.19-alt6.x86_64	There are file conflicts with the package pks-db-0.9.6-alt3.x86_64, for example, /usr/bin/db_archive (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.; 
warn	dca-apps-0.0.5-alt4.qa1.x86_64	File /usr/bin/dcadec conflicts with the package dcadec-0.2.0-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.; 
warn	dcadec-0.2.0-alt1.1.x86_64	File /usr/bin/dcadec conflicts with the package dca-apps-0.0.5-alt4.qa1.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.; 
warn	devscripts-2.19.3-alt2.x86_64	Files /usr/bin/hardening-check /usr/share/man/man1/hardening-check.1.xz conflict with the package hardening-check-2.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.; 
warn	dia-0.97.4-alt0.7.1.x86_64	File /usr/bin/dia conflicts with the package tklib-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.; 
warn	docker-registry-2.6.2-alt1.x86_64	File /etc/docker-registry/config.yml conflicts with the package python-module-docker-registry-0.6.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	dynagen-0.11.0-alt1.qa1.1.1.noarch	Files /usr/lib/python2.7/site-packages/configobj.py /usr/lib/python2.7/site-packages/validate.py conflict with the package python-module-configobj-5.0.6-alt1.1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	etcnet-0.9.19.1-alt1.noarch	File /etc/sysconfig/network conflicts with the package sysconfig-network-1.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	extlinux-6.04.pre1-alt1.5e426532.x86_64	File /usr/share/man/man1/extlinux.1.xz conflicts with the package syslinux-4.04-alt15.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.; 
warn	fbterm-1.7-alt3.x86_64	File /usr/share/terminfo/f/fbterm conflicts with the package terminfo-extra-6.1.20180407-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.; 
warn	fcitx-4.2.9.8-alt2_1.p9.1.x86_64	Files /usr/bin/createPYMB /usr/bin/mb2txt /usr/bin/txt2mb conflict with the package scim-fcitx-tools-3.1.1-alt1.1.qa1.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.; 
warn	fuse-obexfs-0.11-alt0.rc3.qa2.x86_64	Files /usr/bin/obexautofs /usr/bin/obexfs conflict with the package obexftp-0.24.2-alt2.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.; 
warn	gcc4.3-doc-4.3.2-alt22.noarch	File /usr/share/info/gfortran.info.xz conflicts with the package gcc7-fortran-doc-7.3.1-alt9.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/info/gfortran.info.xz conflicts with the package gcc8-fortran-doc-8.4.1-alt0.p9.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.; 
warn	gcc4.4-doc-4.4.7-alt6.noarch	File /usr/share/info/gfortran.info.xz conflicts with the package gcc7-fortran-doc-7.3.1-alt9.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/info/gfortran.info.xz conflicts with the package gcc8-fortran-doc-8.4.1-alt0.p9.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.; 
warn	gcc4.5-doc-4.5.4-alt7.noarch	File /usr/share/info/gfortran.info.xz conflicts with the package gcc7-fortran-doc-7.3.1-alt9.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/info/gfortran.info.xz conflicts with the package gcc8-fortran-doc-8.4.1-alt0.p9.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.; 
warn	gcc4.6-doc-4.6.3-alt14.noarch	File /usr/share/info/gfortran.info.xz conflicts with the package gcc7-fortran-doc-7.3.1-alt9.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/info/gfortran.info.xz conflicts with the package gcc8-fortran-doc-8.4.1-alt0.p9.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.; 
warn	gcc4.7-doc-4.7.2-alt13.noarch	File /usr/share/info/gfortran.info.xz conflicts with the package gcc7-fortran-doc-7.3.1-alt9.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/info/gccgo.info.xz conflicts with the package gcc7-go-doc-7.3.1-alt9.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/info/gfortran.info.xz conflicts with the package gcc8-fortran-doc-8.4.1-alt0.p9.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/info/gccgo.info.xz conflicts with the package gcc8-go-doc-8.4.1-alt0.p9.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.; 
warn	gcc4.8-doc-4.8.2-alt7.noarch	File /usr/share/info/gfortran.info.xz conflicts with the package gcc7-fortran-doc-7.3.1-alt9.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/info/gfortran.info.xz conflicts with the package gcc8-fortran-doc-8.4.1-alt0.p9.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.; 
warn	gcc4.9-doc-4.9.2-alt7.noarch	File /usr/share/info/gfortran.info.xz conflicts with the package gcc7-fortran-doc-7.3.1-alt9.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/info/gfortran.info.xz conflicts with the package gcc8-fortran-doc-8.4.1-alt0.p9.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.; 
warn	gcc5-doc-5.3.1-alt7.noarch	File /usr/share/info/gfortran.info.xz conflicts with the package gcc7-fortran-doc-7.3.1-alt9.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/info/gfortran.info.xz conflicts with the package gcc8-fortran-doc-8.4.1-alt0.p9.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.; 
warn	gcc6-doc-6.3.1-alt5.noarch	File /usr/share/info/gfortran.info.xz conflicts with the package gcc7-fortran-doc-7.3.1-alt9.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/info/gfortran.info.xz conflicts with the package gcc8-fortran-doc-8.4.1-alt0.p9.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.; 
warn	gcc7-fortran-doc-7.3.1-alt9.x86_64	File /usr/share/info/gfortran.info.xz conflicts with the package gcc4.3-doc-4.3.2-alt22.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/info/gfortran.info.xz conflicts with the package gcc4.4-doc-4.4.7-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/info/gfortran.info.xz conflicts with the package gcc4.5-doc-4.5.4-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/info/gfortran.info.xz conflicts with the package gcc4.6-doc-4.6.3-alt14.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/info/gfortran.info.xz conflicts with the package gcc4.7-doc-4.7.2-alt13.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/info/gfortran.info.xz conflicts with the package gcc4.8-doc-4.8.2-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/info/gfortran.info.xz conflicts with the package gcc4.9-doc-4.9.2-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/info/gfortran.info.xz conflicts with the package gcc5-doc-5.3.1-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/info/gfortran.info.xz conflicts with the package gcc6-doc-6.3.1-alt5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	gcc7-go-doc-7.3.1-alt9.x86_64	File /usr/share/info/gccgo.info.xz conflicts with the package gcc4.7-doc-4.7.2-alt13.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	gcc8-fortran-doc-8.4.1-alt0.p9.1.x86_64	File /usr/share/info/gfortran.info.xz conflicts with the package gcc4.3-doc-4.3.2-alt22.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/info/gfortran.info.xz conflicts with the package gcc4.4-doc-4.4.7-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/info/gfortran.info.xz conflicts with the package gcc4.5-doc-4.5.4-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/info/gfortran.info.xz conflicts with the package gcc4.6-doc-4.6.3-alt14.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/info/gfortran.info.xz conflicts with the package gcc4.7-doc-4.7.2-alt13.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/info/gfortran.info.xz conflicts with the package gcc4.8-doc-4.8.2-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/info/gfortran.info.xz conflicts with the package gcc4.9-doc-4.9.2-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/info/gfortran.info.xz conflicts with the package gcc5-doc-5.3.1-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/info/gfortran.info.xz conflicts with the package gcc6-doc-6.3.1-alt5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	gcc8-go-doc-8.4.1-alt0.p9.1.x86_64	File /usr/share/info/gccgo.info.xz conflicts with the package gcc4.7-doc-4.7.2-alt13.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	gdm-data-3.32.0-alt1.noarch	File /usr/share/pixmaps/nobody.png conflicts with the package mint-display-manager-1.0.8-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.; 
warn	gem-cool-io-devel-1.6.0-alt1.1.noarch	Files /usr/include/libev/ev.h /usr/include/libev/ev_vars.h /usr/include/libev/ev_wrap.h conflict with the package gem-nio4r-devel-2.5.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	gem-nio4r-devel-2.5.2-alt1.noarch	Files /usr/include/libev/ev.h /usr/include/libev/ev_vars.h /usr/include/libev/ev_wrap.h conflict with the package gem-cool-io-devel-1.6.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	gem-olddoc-doc-1.6.0-alt1.noarch	Files /usr/share/ri/site/cache.ri /usr/share/ri/site/created.rid conflict with the package ruby-oauth-doc-0.5.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/cache.ri /usr/share/ri/site/created.rid conflict with the package ruby-parseconfig-doc-0.5-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/cache.ri /usr/share/ri/site/created.rid conflict with the package ruby-rails-i18n-doc-5.1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	gem-rack-mount-doc-0.8.3-alt1.noarch	File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-rack-accept-doc-0.4.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-rack-cache-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-rack-jsonp-doc-1.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-rack-openid-doc-1.4.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-typhoeus-doc-1.3.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.; 
warn	gem-vpim-doc-13.11.11-alt1.noarch	File /usr/share/ri/site/Time/cdesc-Time.ri conflicts with the package ruby-archive-zip-doc-0.11.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Time/cdesc-Time.ri conflicts with the package ruby-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ghc7.6.1-hscolour-1.20.3-alt2.x86_64	File /usr/bin/HsColour conflicts with the package ghc8.6.4-hscolour-1.24.4-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.; 
warn	ghc8.6.4-hscolour-1.24.4-alt1.x86_64	File /usr/bin/HsColour conflicts with the package ghc7.6.1-hscolour-1.20.3-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.; 
warn	glibc-devel-2.27-alt14.x86_64	Files /usr/include/rpcsvc/rquota.h /usr/include/rpcsvc/rquota.x conflict with the package quota-devel-4.05.0.3.f2eb-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	glusterfs6-georeplication-6.8-alt1.x86_64	There are file conflicts with the package glusterfs7-georeplication-7.6-alt1.x86_64, for example, /usr/lib/glusterfs/peer_georep-sshkey.py (23 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 glusterfs8-georeplication-8.2-alt2.x86_64, for example, /usr/lib/glusterfs/peer_georep-sshkey.py (44 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 glusterfs9-georeplication-9.0-alt3.x86_64, for example, /usr/lib/glusterfs/peer_georep-sshkey.py (44 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.; 
warn	glusterfs7-georeplication-7.6-alt1.x86_64	There are file conflicts with the package glusterfs6-georeplication-6.8-alt1.x86_64, for example, /usr/lib/glusterfs/peer_georep-sshkey.py (23 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 glusterfs8-georeplication-8.2-alt2.x86_64, for example, /usr/lib/glusterfs/peer_mountbroker.py (42 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 glusterfs9-georeplication-9.0-alt3.x86_64, for example, /usr/lib/glusterfs/peer_mountbroker.py (42 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.; 
warn	glusterfs8-georeplication-8.2-alt2.x86_64	There are file conflicts with the package glusterfs6-georeplication-6.8-alt1.x86_64, for example, /usr/lib/glusterfs/peer_georep-sshkey.py (44 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 glusterfs7-georeplication-7.6-alt1.x86_64, for example, /usr/lib/glusterfs/peer_mountbroker.py (42 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 glusterfs9-georeplication-9.0-alt3.x86_64, for example, /usr/lib/glusterfs/python/syncdaemon/__pycache__/master.cpython-37.opt-1.pyc (12 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.; 
warn	glusterfs9-georeplication-9.0-alt3.x86_64	There are file conflicts with the package glusterfs6-georeplication-6.8-alt1.x86_64, for example, /usr/lib/glusterfs/peer_georep-sshkey.py (44 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 glusterfs7-georeplication-7.6-alt1.x86_64, for example, /usr/lib/glusterfs/peer_mountbroker.py (42 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 glusterfs8-georeplication-8.2-alt2.x86_64, for example, /usr/lib/glusterfs/python/syncdaemon/__pycache__/master.cpython-37.opt-1.pyc (12 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.; 
warn	gnu-efi-3.0.5-3.0.5-alt0.1.x86_64	There are file conflicts with the package gnu-efi-3.0r-3.0r-alt3.x86_64, for example, /usr/include/efi/efi.h (23 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 gnu-efi-3.0u-3.0u-alt4.x86_64, for example, /usr/include/efi/efi.h (21 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.; 
warn	gnu-efi-3.0r-3.0r-alt3.x86_64	There are file conflicts with the package gnu-efi-3.0.5-3.0.5-alt0.1.x86_64, for example, /usr/include/efi/efi.h (23 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 gnu-efi-3.0u-3.0u-alt4.x86_64, for example, /usr/include/efi/efi.h (10 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	gnu-efi-3.0u-3.0u-alt4.x86_64	There are file conflicts with the package gnu-efi-3.0.5-3.0.5-alt0.1.x86_64, for example, /usr/include/efi/efi.h (21 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 gnu-efi-3.0r-3.0r-alt3.x86_64, for example, /usr/include/efi/efi.h (10 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	gnustep-gworkspace-0.9.2-alt4.svn20131218.x86_64	File /usr/bin/mdfind conflicts with the package samba-client-4.14.10-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.; 
warn	go-task-2.4.0-alt1.x86_64	File /usr/bin/task conflicts with the package task-core-2.5.1-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.; 
warn	golang-tools-0-alt7.git24acc66e.x86_64	File /usr/bin/stress conflicts with the package stress-1.0.4-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	hardening-check-2.6-alt1.noarch	Files /usr/bin/hardening-check /usr/share/man/man1/hardening-check.1.xz conflict with the package devscripts-2.19.3-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.; 
warn	hunspell-utils-1.7.0-alt1.x86_64	File /usr/bin/analyze conflicts with the package SNNS-4.3-alt1.1.1.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.; 
warn	iceb-19.14-alt1.x86_64	File /usr/bin/spec conflicts with the package python-module-spec-1.4.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-common-stage2-1.10.10-alt1.x86_64	File /usr/sbin/postinstall conflicts with the package installworld-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.; 
warn	installer-distro-alt-server-v-stage2-9.0.1-alt1.noarch	There are file conflicts with the package installer-distro-alt-workstation-stage2-9.0.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-altlinux-desktop-stage2-8.1.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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 (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-centaurus-stage2-9.0-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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.; Files /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-cliff-common-8.2-alt7.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-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-cliff-stage2-8.2-alt7.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 installer-distro-education-stage2-9.2-alt1.p9.1.x86_64, 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-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-lxdesktop-stage2-6.0-alt5.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-school-server-stage2-7.0-alt9.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-simply-linux-stage2-9.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.; 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-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-alt-workstation-stage2-9.0.0-alt1.noarch	There are file conflicts with the package installer-distro-alt-server-v-stage2-9.0.1-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.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-centaurus-stage2-9.0-alt1.x86_64, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-chainmail-stage2-3.0.0-alt8.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/preinstall.d/80-setup-user-groups conflicts with the package installer-distro-cliff-common-8.2-alt7.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-cliff-stage2-8.2-alt7.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 installer-distro-education-stage2-9.2-alt1.p9.1.x86_64, 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-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.; 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 (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/preinstall.d/80-setup-user-groups conflict with the package installer-distro-school-server-stage2-7.0-alt9.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-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-9.3.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-tablet-stage2-6.0-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch	There are file conflicts with the package installer-distro-alt-server-v-stage2-9.0.1-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.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-centaurus-stage2-9.0-alt1.x86_64, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-chainmail-stage2-3.0.0-alt8.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/preinstall.d/80-setup-user-groups conflicts with the package installer-distro-cliff-common-8.2-alt7.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-cliff-stage2-8.2-alt7.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 installer-distro-education-stage2-9.2-alt1.p9.1.x86_64, 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-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-lxdesktop-stage2-6.0-alt5.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/preinstall.d/80-setup-user-groups conflict with the package installer-distro-school-server-stage2-7.0-alt9.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-simply-linux-stage2-9.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-tablet-stage2-6.0-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch	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-alt-server-v-stage2-9.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/installer-steps conflicts with the package installer-distro-alt-workstation-stage2-9.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/install2/installer-steps conflicts with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-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-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-centaurus-stage2-9.0-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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.; 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-cliff-stage2-8.2-alt7.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-education-stage2-9.2-alt1.p9.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-junior-stage2-8.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-lxdesktop-stage2-6.0-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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-school-server-stage2-7.0-alt9.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-simply-linux-stage2-9.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-tablet-stage2-6.0-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-altlinux-server-stage2-7.0.2-alt1.noarch	There are file conflicts with the package installer-distro-alt-server-v-stage2-9.0.1-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.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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-centaurus-stage2-9.0-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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.; 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-cliff-stage2-8.2-alt7.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-education-stage2-9.2-alt1.p9.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-junior-stage2-8.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-lxdesktop-stage2-6.0-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list conflict with the package installer-distro-school-server-stage2-7.0-alt9.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-simply-linux-stage2-9.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-tablet-stage2-6.0-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-centaurus-stage2-9.0-alt1.x86_64	Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-alt-server-v-stage2-9.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 installer-distro-alt-workstation-stage2-9.0.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-altlinux-desktop-stage2-8.1.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-server-stage2-7.0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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.; Files /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-cliff-common-8.2-alt7.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/services-on /usr/share/install2/systemd-enabled conflict with the package installer-distro-cliff-stage2-8.2-alt7.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 installer-distro-education-stage2-9.2-alt1.p9.1.x86_64, 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-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.; 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-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-9.3.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-tablet-stage2-6.0-alt3.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-token-desktop-stage2-0.1.1-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-chainmail-stage2-3.0.0-alt8.noarch	There are file conflicts with the package installer-distro-alt-server-v-stage2-9.0.1-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-alt-workstation-stage2-9.0.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-altlinux-desktop-stage2-8.1.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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 (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-centaurus-stage2-9.0-alt1.x86_64, 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-cliff-stage2-8.2-alt7.x86_64, 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-education-stage2-9.2-alt1.p9.1.x86_64, 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-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.; 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 (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-school-server-stage2-7.0-alt9.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-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-9.3.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-tablet-stage2-6.0-alt3.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-token-desktop-stage2-0.1.1-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-cliff-common-8.2-alt7.x86_64	Files /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-alt-server-v-stage2-9.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/preinstall.d/80-setup-user-groups conflicts with the package installer-distro-alt-workstation-stage2-9.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/install2/preinstall.d/80-setup-user-groups conflicts with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-centaurus-stage2-9.0-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/preinstall.d/80-setup-user-groups conflicts with the package installer-distro-education-stage2-9.2-alt1.p9.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/preinstall.d/80-setup-user-groups conflicts with the package installer-distro-junior-stage2-8.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/postinstall.d/80-user-dirs.sh /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-lxdesktop-stage2-6.0-alt5.noarch. Moreover, the 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/postinstall.d/01-remove-installer-server-pkgs.sh conflicts with the package installer-distro-school-server-stage2-7.0-alt9.noarch. Moreover, the 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/postinstall.d/01-remove-installer-server-pkgs.sh conflicts 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.; File /usr/share/install2/preinstall.d/80-setup-user-groups conflicts with the package installer-distro-simply-linux-stage2-9.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/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflicts with the package installer-distro-tablet-stage2-6.0-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/preinstall.d/80-setup-user-groups conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-cliff-stage2-8.2-alt7.x86_64	Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-alt-server-v-stage2-9.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/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-alt-workstation-stage2-9.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/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-desktop-stage2-8.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /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/installer-steps /usr/share/install2/services-on /usr/share/install2/systemd-enabled conflict with the package installer-distro-centaurus-stage2-9.0-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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-education-stage2-9.2-alt1.p9.1.x86_64, 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-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-lxdesktop-stage2-6.0-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-skip-list /usr/share/install2/installer-steps conflict with the package installer-distro-simply-linux-stage2-9.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.; 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.; 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-token-desktop-stage2-0.1.1-alt5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-education-9.2-alt1.p9.1.x86_64	File /usr/share/locale/ru/LC_MESSAGES/alterator-simply-linux.mo conflicts with the package installer-distro-junior-8.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-education-stage2-9.2-alt1.p9.1.x86_64	There are file conflicts with the package installer-distro-alt-server-v-stage2-9.0.1-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-alt-workstation-stage2-9.0.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-server-stage2-7.0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-centaurus-stage2-9.0-alt1.x86_64, 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.; File /usr/share/install2/preinstall.d/80-setup-user-groups conflicts with the package installer-distro-cliff-common-8.2-alt7.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 installer-distro-cliff-stage2-8.2-alt7.x86_64, 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-alt2.noarch, for example, /usr/share/install2/postinstall.d/01-remove-installer-desktop-pkgs.sh (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 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-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-9.3.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (10 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package 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-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-junior-8.1-alt2.noarch	File /usr/share/locale/ru/LC_MESSAGES/alterator-simply-linux.mo conflicts with the package installer-distro-education-9.2-alt1.p9.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/locale/ru/LC_MESSAGES/alterator-simply-linux.mo conflicts with the package installer-distro-simply-linux-9.3.0-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-junior-stage2-8.1-alt2.noarch	There are file conflicts with the package installer-distro-alt-server-v-stage2-9.0.1-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-alt-workstation-stage2-9.0.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-server-stage2-7.0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-centaurus-stage2-9.0-alt1.x86_64, 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.; File /usr/share/install2/preinstall.d/80-setup-user-groups conflicts with the package installer-distro-cliff-common-8.2-alt7.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 installer-distro-cliff-stage2-8.2-alt7.x86_64, 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-education-stage2-9.2-alt1.p9.1.x86_64, for example, /usr/share/install2/postinstall.d/01-remove-installer-desktop-pkgs.sh (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 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-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-9.3.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-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-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-lxdesktop-stage2-6.0-alt5.noarch	There are file conflicts with the package installer-distro-alt-server-v-stage2-9.0.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-alt-workstation-stage2-9.0.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-altlinux-server-stage2-7.0.2-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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-centaurus-stage2-9.0-alt1.x86_64, 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-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.; Files /usr/share/install2/postinstall.d/80-user-dirs.sh /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-cliff-common-8.2-alt7.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 installer-distro-cliff-stage2-8.2-alt7.x86_64, 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-education-stage2-9.2-alt1.p9.1.x86_64, 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-junior-stage2-8.1-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.; 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 (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-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-9.3.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-tablet-stage2-6.0-alt3.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-token-desktop-stage2-0.1.1-alt5.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.; 
warn	installer-distro-school-server-stage2-7.0-alt9.noarch	There are file conflicts with the package installer-distro-alt-server-v-stage2-9.0.1-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-alt-workstation-stage2-9.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/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list conflict with the package installer-distro-altlinux-server-stage2-7.0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-centaurus-stage2-9.0-alt1.x86_64, 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.; File /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflicts with the package installer-distro-cliff-common-8.2-alt7.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 installer-distro-cliff-stage2-8.2-alt7.x86_64, 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-education-stage2-9.2-alt1.p9.1.x86_64, 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-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.; 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-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-9.3.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-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-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-server-light-stage2-8.0-alt1.noarch	There are file conflicts with the package installer-distro-alt-server-v-stage2-9.0.1-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.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-alt-workstation-stage2-9.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/install2/installer-steps conflicts with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-server-stage2-7.0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-centaurus-stage2-9.0-alt1.x86_64, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-chainmail-stage2-3.0.0-alt8.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflicts with the package installer-distro-cliff-common-8.2-alt7.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-cliff-stage2-8.2-alt7.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-education-stage2-9.2-alt1.p9.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-junior-stage2-8.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-lxdesktop-stage2-6.0-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-school-server-stage2-7.0-alt9.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-simply-linux-stage2-9.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-distro-tablet-stage2-6.0-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-simply-linux-9.3.0-alt1.x86_64	File /usr/share/locale/ru/LC_MESSAGES/alterator-simply-linux.mo conflicts with the package installer-distro-junior-8.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-simply-linux-stage2-9.3.0-alt1.noarch	Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-alt-server-v-stage2-9.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 installer-distro-alt-workstation-stage2-9.0.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/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/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.; There are file conflicts with the package installer-distro-centaurus-stage2-9.0-alt1.x86_64, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-chainmail-stage2-3.0.0-alt8.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/preinstall.d/80-setup-user-groups conflicts with the package installer-distro-cliff-common-8.2-alt7.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-skip-list /usr/share/install2/installer-steps conflict with the package installer-distro-cliff-stage2-8.2-alt7.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 installer-distro-education-stage2-9.2-alt1.p9.1.x86_64, for example, /usr/share/install2/alterator-menu/module-expert-list (10 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-junior-stage2-8.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-lxdesktop-stage2-6.0-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-school-server-stage2-7.0-alt9.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-tablet-stage2-6.0-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-token-desktop-stage2-0.1.1-alt5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-tablet-stage2-6.0-alt3.noarch	There are file conflicts with the package installer-distro-alt-server-v-stage2-9.0.1-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-alt-workstation-stage2-9.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/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/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/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.; There are file conflicts with the package installer-distro-centaurus-stage2-9.0-alt1.x86_64, 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-chainmail-stage2-3.0.0-alt8.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.; File /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflicts with the package installer-distro-cliff-common-8.2-alt7.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 installer-distro-cliff-stage2-8.2-alt7.x86_64, 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-education-stage2-9.2-alt1.p9.1.x86_64, 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-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-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-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/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh 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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-simply-linux-stage2-9.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-token-desktop-stage2-0.1.1-alt5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-token-desktop-live-0.1.1-alt5.noarch	File /usr/share/livecd-install/alterator-menu/module-expert-list conflicts with the package installer-feature-simply-livecd-9.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.; 
warn	installer-distro-token-desktop-stage2-0.1.1-alt5.noarch	There are file conflicts with the package installer-distro-alt-server-v-stage2-9.0.1-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.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-alt-workstation-stage2-9.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/install2/installer-steps conflicts with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-server-stage2-7.0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-centaurus-stage2-9.0-alt1.x86_64, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-chainmail-stage2-3.0.0-alt8.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/preinstall.d/80-setup-user-groups conflicts with the package installer-distro-cliff-common-8.2-alt7.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-cliff-stage2-8.2-alt7.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 installer-distro-education-stage2-9.2-alt1.p9.1.x86_64, 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-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-lxdesktop-stage2-6.0-alt5.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-school-server-stage2-7.0-alt9.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts 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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-simply-linux-stage2-9.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-tablet-stage2-6.0-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-feature-alphabet-profiles-1.0-alt2.noarch	File /usr/share/install2/prepkg.d/50-groups.sh conflicts with the package installer-feature-centaurus-profiles-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/install2/prepkg.d/50-groups.sh conflicts with the package installer-feature-spt-profiles-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.; 
warn	installer-feature-centaurus-profiles-2.0-alt1.noarch	File /usr/share/install2/prepkg.d/50-groups.sh conflicts with the package installer-feature-alphabet-profiles-1.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/prepkg.d/50-groups.sh conflicts with the package installer-feature-spt-profiles-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.; 
warn	installer-feature-powerbutton-stage2-0.1-alt1.noarch	File /usr/share/install2/postinstall.d/08-powerbutton conflicts with the package installer-feature-powerbutton-stage3-0.2.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.; 
warn	installer-feature-powerbutton-stage3-0.2.2-alt1.noarch	File /usr/share/install2/postinstall.d/08-powerbutton conflicts with the package installer-feature-powerbutton-stage2-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.; 
warn	installer-feature-simply-livecd-9.1.0-alt1.noarch	File /usr/share/livecd-install/alterator-menu/module-expert-list conflicts with the package installer-distro-token-desktop-live-0.1.1-alt5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-feature-spt-profiles-0.6-alt1.noarch	File /usr/share/install2/prepkg.d/50-groups.sh conflicts with the package installer-feature-alphabet-profiles-1.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/prepkg.d/50-groups.sh conflicts with the package installer-feature-centaurus-profiles-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.; 
warn	installer-feature-vm-fs-stage2-0.3-alt2.noarch	File /usr/share/install2/initinstall.d/05-vm-profile-ofs conflicts with the package installer-feature-vm-ofs-stage2-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.; 
warn	installer-feature-vm-fs-stage3-0.3-alt2.noarch	File /usr/share/install2/preinstall.d/01-move-fs-ofs conflicts with the package installer-feature-vm-ofs-stage3-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.; 
warn	installer-feature-vm-ofs-stage2-0.3-alt1.noarch	File /usr/share/install2/initinstall.d/05-vm-profile-ofs conflicts with the package installer-feature-vm-fs-stage2-0.3-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.; 
warn	installer-feature-vm-ofs-stage3-0.3-alt1.noarch	File /usr/share/install2/preinstall.d/01-move-fs-ofs conflicts with the package installer-feature-vm-fs-stage3-0.3-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.; 
warn	installworld-0.1-alt1.noarch	File /usr/sbin/postinstall conflicts with the package installer-common-stage2-1.10.10-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.; 
warn	javascript-jquery-1.7.2-alt1.noarch	File /usr/share/javascript/jquery/jquery.min.js conflicts with the package pve-http-server-3.1.1-alt5.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.; 
warn	jboss-as-vanilla-7.1.1-alt14.noarch	File /usr/bin/jboss-cli conflicts with the package wildfly-as-10.1.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.; 
warn	jpeginfo-1.6.1-alt1.x86_64	File /usr/bin/jpeginfo conflicts with the package libjpeg-utils-2.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.; 
warn	kernel-source-rtl8723de-4.11up-5.1.1.8-alt4.S1.noarch	File /usr/src/kernel/sources/kernel-source-rtl8723de-5.1.1.8.tar.bz2 conflicts with the package kernel-source-rtl8723de-4.15up-5.1.1.8-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	kernel-source-rtl8723de-4.15up-5.1.1.8-alt1.noarch	File /usr/src/kernel/sources/kernel-source-rtl8723de-5.1.1.8.tar.bz2 conflicts with the package kernel-source-rtl8723de-4.11up-5.1.1.8-alt4.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.; 
warn	lcdf-typetools-2.108-alt1.x86_64	File /usr/share/man/man1/mmafm.1.xz conflicts with the package texlive-collection-basic-2018-alt1_5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	lexmark7000linux-990516-alt1.x86_64	File /usr/bin/pbm2l7k conflicts with the package pbm2l7k-990321-alt1.qa2.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.; 
warn	libbobpp-devel-0.2.0-alt1.1.x86_64	File /usr/include/config.h conflicts with the package libpicosat-devel-965-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.; 
warn	libclutter-devel-doc-1.26.2-alt2.noarch	There are file conflicts with the package libmuffin-devel-doc-4.2.2-alt2.noarch, for example, /usr/share/gtk-doc/html/clutter/CallyActor.html (122 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.; 
warn	libcpufreq-devel-008-alt2.x86_64	File /usr/include/cpufreq.h conflicts with the package libcpupower-devel-5.10-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.; 
warn	libcpupower-devel-5.10-alt1.x86_64	File /usr/include/cpufreq.h conflicts with the package libcpufreq-devel-008-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.; 
warn	libdispatch-objc2-devel-1.2-alt5.git20140226.x86_64	File /usr/share/man/man3/dispatch.3.xz conflicts with the package libnetcdf11-seq-doc-4.4.1.1-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.; 
warn	libgoogle-sparsehash-1.5.2-alt1.1.noarch	There are file conflicts with the package libsparsehash-devel-2.0.3-alt1.x86_64, for example, /usr/include/google/dense_hash_map (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.; 
warn	libgtk+extra2-devel-docs-2.1.2-alt3.noarch	There are file conflicts with the package libgtkextra-x11-devel-3.3.4-alt1_1.x86_64, for example, /usr/share/gtk-doc/html/gtkextra/GtkPlotArray.html (10 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libgtkextra-x11-devel-3.3.4-alt1_1.x86_64	There are file conflicts with the package libgtk+extra2-devel-docs-2.1.2-alt3.noarch, for example, /usr/share/gtk-doc/html/gtkextra/GtkPlotArray.html (10 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libjpeg-utils-2.0.2-alt1.x86_64	File /usr/bin/jpeginfo conflicts with the package jpeginfo-1.6.1-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	liblinebreak-devel-2.1-alt1.x86_64	Files /usr/include/linebreak.h /usr/include/linebreakdef.h conflict with the package libunibreak-devel-3.0-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	liblog4cplus-devel-docs-2.0.0-alt2.rc2.1.noarch	File /usr/share/man/man3/config.h.3.xz conflicts with the package libpgf-devel-6.14.12-alt1_10.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.; 
warn	libmozjs52-devel-static-52.7.3-alt2.x86_64	File /usr/lib64/libjs_static.a conflicts with the package libmozjs60-devel-static-60.1.0-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.; 
warn	libmozjs60-devel-static-60.1.0-alt2.x86_64	File /usr/lib64/libjs_static.a conflicts with the package libmozjs52-devel-static-52.7.3-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.; 
warn	libmuffin-devel-doc-4.2.2-alt2.noarch	There are file conflicts with the package libclutter-devel-doc-1.26.2-alt2.noarch, for example, /usr/share/gtk-doc/html/clutter/CallyActor.html (122 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.; 
warn	libnetcdf11-seq-doc-4.4.1.1-alt3.noarch	File /usr/share/man/man3/dispatch.3.xz conflicts with the package libdispatch-objc2-devel-1.2-alt5.git20140226.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.; 
warn	libopenh264-devel-static-2.0.0-alt1.x86_64	File /usr/lib64/libopenh264.a conflicts with the package openh264-devel-static-2.1.1-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libpgf-devel-6.14.12-alt1_10.x86_64	File /usr/share/man/man3/config.h.3.xz conflicts with the package liblog4cplus-devel-docs-2.0.0-alt2.rc2.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.; 
warn	libpicosat-devel-965-alt1.x86_64	File /usr/include/config.h conflicts with the package libbobpp-devel-0.2.0-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.; 
warn	libproxy-tools-0.4.15-alt5.x86_64	File /usr/bin/proxy conflicts with the package 3proxy-0.6.1-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.; 
warn	libquvi-devel-0.4.1-alt2.1.x86_64	File /usr/share/man/man3/libquvi.3.xz conflicts with the package libquvi0.9-devel-0.9.4-alt2.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.; 
warn	libquvi0.9-devel-0.9.4-alt2.1.x86_64	File /usr/share/man/man3/libquvi.3.xz conflicts with the package libquvi-devel-0.4.1-alt2.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.; 
warn	libreadline-devel-7.0.3-alt3.x86_64	There are file conflicts with the package libreadline5-devel-5.2.14-alt6.x86_64, for example, /usr/include/readline/chardefs.h (13 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.; 
warn	libreadline-devel-static-7.0.3-alt3.x86_64	Files /usr/lib64/libhistory.a /usr/lib64/libreadline.a conflict with the package libreadline5-devel-static-5.2.14-alt6.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.; 
warn	libreadline5-devel-5.2.14-alt6.x86_64	There are file conflicts with the package libreadline-devel-7.0.3-alt3.x86_64, for example, /usr/include/readline/chardefs.h (13 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.; 
warn	libreadline5-devel-static-5.2.14-alt6.x86_64	Files /usr/lib64/libhistory.a /usr/lib64/libreadline.a conflict with the package libreadline-devel-static-7.0.3-alt3.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.; 
warn	libshape-1.4.1-alt3.x86_64	File /usr/bin/dbfdump conflicts with the package perl-DBD-XBase-1.08-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.; 
warn	libshout-idjc-devel-2.4.1-alt1_1.x86_64	File /usr/share/aclocal/shout.m4 conflicts with the package libshout2-devel-2.2.2-alt3.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.; 
warn	libshout2-devel-2.2.2-alt3.x86_64	File /usr/share/aclocal/shout.m4 conflicts with the package libshout-idjc-devel-2.4.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.; 
warn	libsparsehash-devel-2.0.3-alt1.x86_64	There are file conflicts with the package libgoogle-sparsehash-1.5.2-alt1.1.noarch, for example, /usr/include/google/dense_hash_map (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.; 
warn	libsx-2.17-alt1_9.noarch	Files /usr/lib/python2.7/site-packages/sx/__init__.py /usr/lib/python2.7/site-packages/sx/__init__.pyc /usr/lib/python2.7/site-packages/sx/__init__.pyo conflict with the package python-module-pisa-3.0.33-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.; 
warn	libticables-devel-1.3.4-alt1_1.x86_64	Files /usr/include/tilp2/ticables.h /usr/lib64/pkgconfig/ticables2.pc conflict with the package libticables2-devel-1.3.5-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/locale/fr/LC_MESSAGES/libticables2.mo conflicts with the package libticables2-i18n-1.3.5-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.; 
warn	libticables2-devel-1.3.5-alt1_4.x86_64	Files /usr/include/tilp2/ticables.h /usr/lib64/pkgconfig/ticables2.pc conflict with the package libticables-devel-1.3.4-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.; 
warn	libticables2-i18n-1.3.5-alt1_4.noarch	File /usr/share/locale/fr/LC_MESSAGES/libticables2.mo conflicts with the package libticables-devel-1.3.4-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.; 
warn	libunibreak-devel-3.0-alt1.x86_64	Files /usr/include/linebreak.h /usr/include/linebreakdef.h conflict with the package liblinebreak-devel-2.1-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	livecd-0ad-0.2-alt1.noarch	File /etc/sysconfig/livecd-runapp conflicts with the package livecd-fgfs-0.2-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.; 
warn	livecd-fgfs-0.2-alt2.noarch	File /etc/sysconfig/livecd-runapp conflicts with the package livecd-0ad-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.; 
warn	livecd-gnome-nowarn-space-0.3-alt1.noarch	File /etc/skel/.gconf/apps/%gconf.xml conflicts with the package branding-alt-education-xfce-settings-9.2-alt4.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 /etc/skel/.gconf/apps/%gconf.xml conflicts with the package branding-alt-tonk-xfce-settings-9.0-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	mariadb-client-10.4.34-alt0.M90P.1.x86_64	File /usr/share/man/man8/mysqld.8.xz conflicts with the package MySQL-server-8.0.26-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.; 
warn	mate-document-viewer-dvi-1.22.2-alt1.x86_64	File /usr/lib64/atril/3/backends/libdvidocument.so conflicts with the package atril-gtk-dvi-1.22.3-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.; 
warn	mcl-1.008.09.149-alt2.x86_64	File /usr/bin/clm conflicts with the package clean-3.0-alt1.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	mesa-demos-8.4.0-alt1.x86_64	File /usr/bin/quads conflicts with the package arprec-2.2.19-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/bin/bitmap conflicts with the package bitmap-1.0.6-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/bin/bump conflicts with the package bumper-0.1.8-alt1.git20150215.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/bin/poly conflicts with the package polyml-5.4.1-alt4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/bin/gearbox conflicts with the package python-module-gearbox-0.1.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.; 
warn	mint-display-manager-1.0.8-alt2.x86_64	File /usr/share/pixmaps/nobody.png conflicts with the package gdm-data-3.32.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	mono-devel-6.12.0.206-alt1.x86_64	File /usr/bin/pedump conflicts with the package ruby-pedump-0.5.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	mysql-utilities-1.6.5-alt1.noarch	File /usr/bin/mysqldiff conflicts with the package mysqldiff-0.60-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	mysqldiff-0.60-alt1.noarch	File /usr/bin/mysqldiff conflicts with the package mysql-utilities-1.6.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.; 
warn	nfft-3.2.3-alt1.x86_64	File /usr/bin/radon conflicts with the package python-module-radon-3.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.; 
warn	obexftp-0.24.2-alt2.4.x86_64	Files /usr/bin/obexautofs /usr/bin/obexfs conflict with the package fuse-obexfs-0.11-alt0.rc3.qa2.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.; 
warn	opal-firmware-6.3.1-alt1.noarch	File /usr/share/qemu/skiboot.lid conflicts with the package pve-qemu-common-5.1.0-alt6.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/qemu/skiboot.lid conflicts with the package qemu-system-ppc-core-5.2.0-alt6.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.; 
warn	openh264-devel-static-2.1.1-alt1.x86_64	File /usr/lib64/libopenh264.a conflicts with the package libopenh264-devel-static-2.0.0-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	origin-sdn-ovs-3.11.0-alt3.x86_64	Files /usr/libexec/cni/host-local /usr/libexec/cni/loopback conflict with the package cni-plugins-0.8.7-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.; 
warn	parmetis-4.0.3-alt2.x86_64	File /usr/bin/ptest conflicts with the package python-module-ptest-1.7.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.; 
warn	pbm2l7k-990321-alt1.qa2.x86_64	File /usr/bin/pbm2l7k conflicts with the package lexmark7000linux-990516-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.; 
warn	pcp-conf-5.0.2-alt1.x86_64	File /etc/pcp.conf conflicts with the package pgpool-II-4.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.; 
warn	pear-Pager-2.4.9-alt1.noarch	File /usr/share/php/pear/Pager/Sliding.php conflicts with the package pear-Pager_Sliding-1.6-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.; 
warn	pear-Pager_Sliding-1.6-alt3.noarch	File /usr/share/php/pear/Pager/Sliding.php conflicts with the package pear-Pager-2.4.9-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	perl-DBD-XBase-1.08-alt2.noarch	File /usr/bin/dbfdump conflicts with the package libshape-1.4.1-alt3.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.; 
warn	perl-Math-Primality-scripts-0.08-alt2.noarch	File /usr/bin/primes.pl conflicts with the package perl-Math-Prime-Util-scripts-0.73-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.; 
warn	perl-Math-Prime-Util-scripts-0.73-alt1.1.x86_64	File /usr/bin/primes.pl conflicts with the package perl-Math-Primality-scripts-0.08-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.; 
warn	perl-pip-1.19-alt1.noarch	File /usr/bin/pip conflicts with the package pip-19.1.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	pgpdump-0.26-alt1.qa1.x86_64	File /usr/bin/pgpdump conflicts with the package pks-utils-0.9.6-alt3.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.; 
warn	pgpool-II-4.0.2-alt1.x86_64	File /etc/pcp.conf conflicts with the package pcp-conf-5.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.; 
warn	pip-19.1.1-alt2.noarch	File /usr/bin/pip conflicts with the package perl-pip-1.19-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	pks-db-0.9.6-alt3.x86_64	There are file conflicts with the package db4.7-utils-4.7.25-alt9.x86_64, for example, /usr/bin/db_archive (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 db4.8-utils-4.8.30-alt4.x86_64, for example, /usr/bin/db_archive (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 db6.1-utils-6.1.19-alt6.x86_64, for example, /usr/bin/db_archive (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.; 
warn	pks-utils-0.9.6-alt3.x86_64	File /usr/bin/pgpdump conflicts with the package pgpdump-0.26-alt1.qa1.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.; 
warn	plan9-wm-1.0-alt1.1.x86_64	File /usr/bin/rio conflicts with the package python3-module-rasterio-1.1.8-alt3.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.; 
warn	planner-0.14.6-alt2.x86_64	File /usr/bin/planner conflicts with the package camotics-1.2.0-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	polyml-5.4.1-alt4.x86_64	File /usr/bin/poly conflicts with the package mesa-demos-8.4.0-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	postgresql10-contrib-10.23-alt0.M90P.1.x86_64	There are file conflicts with the package postgresql11-contrib-11.22-alt0.M90P.1.x86_64, for example, /usr/bin/pgbench (27 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 postgresql12-contrib-12.22-alt0.M90P.1.x86_64, for example, /usr/bin/oid2name (38 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 postgresql9.4-contrib-9.4.26-alt1.x86_64, for example, /usr/bin/oid2name (40 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 postgresql9.5-contrib-9.5.25-alt1.x86_64, for example, /usr/bin/pg_archivecleanup (43 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 postgresql9.6-contrib-9.6.24-alt0.M90P.1.x86_64, for example, /usr/bin/pg_archivecleanup (38 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.; 
warn	postgresql10-perl-10.23-alt0.M90P.1.x86_64	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql11-perl-11.22-alt0.M90P.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.; There are file conflicts with the package postgresql12-perl-12.22-alt0.M90P.1.x86_64, for example, /usr/lib64/pgsql/plperl.so (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/lib64/pgsql/plperl.so conflicts with the package postgresql9.4-perl-9.4.26-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/lib64/pgsql/plperl.so conflicts with the package postgresql9.6-perl-9.6.24-alt0.M90P.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.; 
warn	postgresql10-python-10.23-alt0.M90P.1.x86_64	File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql11-python-11.22-alt0.M90P.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.; There are file conflicts with the package postgresql12-python-12.22-alt0.M90P.1.x86_64, for example, /usr/lib64/pgsql/plpython2.so (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/lib64/pgsql/plpython2.so conflicts with the package postgresql9.4-python-9.4.26-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/lib64/pgsql/plpython2.so conflicts with the package postgresql9.5-python-9.5.25-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/lib64/pgsql/plpython2.so conflicts with the package postgresql9.6-python-9.6.24-alt0.M90P.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.; 
warn	postgresql10-server-10.23-alt0.M90P.1.x86_64	There are file conflicts with the package postgresql11-server-11.22-alt0.M90P.1.x86_64, for example, /usr/bin/initdb (49 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 postgresql12-server-12.22-alt0.M90P.1.x86_64, for example, /usr/bin/initdb (88 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 postgresql9.4-server-9.4.26-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (238 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 postgresql9.5-server-9.5.25-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (172 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 postgresql9.6-server-9.6.24-alt0.M90P.1.x86_64, for example, /etc/rc.d/init.d/postgresql (134 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.; 
warn	postgresql10-tcl-10.23-alt0.M90P.1.x86_64	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql11-tcl-11.22-alt0.M90P.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.; There are file conflicts with the package postgresql12-tcl-12.22-alt0.M90P.1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (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/lib64/pgsql/pltcl.so conflicts with the package postgresql9.4-tcl-9.4.26-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/lib64/pgsql/pltcl.so conflicts with the package postgresql9.5-tcl-9.5.25-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/lib64/pgsql/pltcl.so conflicts with the package postgresql9.6-tcl-9.6.24-alt0.M90P.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.; 
warn	postgresql11-contrib-11.22-alt0.M90P.1.x86_64	There are file conflicts with the package postgresql10-contrib-10.23-alt0.M90P.1.x86_64, for example, /usr/bin/pgbench (27 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 postgresql12-contrib-12.22-alt0.M90P.1.x86_64, for example, /usr/bin/oid2name (31 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql9.4-contrib-9.4.26-alt1.x86_64, for example, /usr/bin/oid2name (47 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 postgresql9.5-contrib-9.5.25-alt1.x86_64, for example, /usr/bin/pg_archivecleanup (52 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 postgresql9.6-contrib-9.6.24-alt0.M90P.1.x86_64, for example, /usr/bin/pg_archivecleanup (52 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.; 
warn	postgresql11-perl-11.22-alt0.M90P.1.x86_64	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql10-perl-10.23-alt0.M90P.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.; There are file conflicts with the package postgresql12-perl-12.22-alt0.M90P.1.x86_64, for example, /usr/share/pgsql/extension/plperl--1.0.sql (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/lib64/pgsql/plperl.so conflicts with the package postgresql9.4-perl-9.4.26-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/lib64/pgsql/plperl.so conflicts with the package postgresql9.5-perl-9.5.25-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/lib64/pgsql/plperl.so conflicts with the package postgresql9.6-perl-9.6.24-alt0.M90P.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.; 
warn	postgresql11-pg_partman-4.2.0-alt1.x86_64	There are file conflicts with the package postgresql12-pg_partman-4.6.2-alt0.M90P.1.x86_64, for example, /usr/bin/check_unique_constraint.py (44 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.; 
warn	postgresql11-python-11.22-alt0.M90P.1.x86_64	File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql10-python-10.23-alt0.M90P.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.; There are file conflicts with the package postgresql12-python-12.22-alt0.M90P.1.x86_64, for example, /usr/share/pgsql/extension/plpython2u--1.0.sql (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/lib64/pgsql/plpython2.so conflicts with the package postgresql9.4-python-9.4.26-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/lib64/pgsql/plpython2.so conflicts with the package postgresql9.5-python-9.5.25-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/lib64/pgsql/plpython2.so conflicts with the package postgresql9.6-python-9.6.24-alt0.M90P.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.; 
warn	postgresql11-server-11.22-alt0.M90P.1.x86_64	There are file conflicts with the package postgresql10-server-10.23-alt0.M90P.1.x86_64, for example, /usr/bin/initdb (49 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 postgresql12-server-12.22-alt0.M90P.1.x86_64, for example, /usr/bin/initdb (70 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 postgresql9.4-server-9.4.26-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (253 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 postgresql9.5-server-9.5.25-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (193 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 postgresql9.6-server-9.6.24-alt0.M90P.1.x86_64, for example, /etc/rc.d/init.d/postgresql (158 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.; 
warn	postgresql11-tcl-11.22-alt0.M90P.1.x86_64	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql10-tcl-10.23-alt0.M90P.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.; There are file conflicts with the package postgresql12-tcl-12.22-alt0.M90P.1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (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/lib64/pgsql/pltcl.so conflicts with the package postgresql9.4-tcl-9.4.26-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/lib64/pgsql/pltcl.so conflicts with the package postgresql9.5-tcl-9.5.25-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/lib64/pgsql/pltcl.so conflicts with the package postgresql9.6-tcl-9.6.24-alt0.M90P.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.; 
warn	postgresql12-1C-contrib-12.20-alt0.M90P.3.x86_64	There are file conflicts with the package postgresql9.4-contrib-9.4.26-alt1.x86_64, for example, /usr/bin/oid2name (46 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.; 
warn	postgresql12-1C-perl-12.20-alt0.M90P.3.x86_64	There are file conflicts with the package postgresql9.4-perl-9.4.26-alt1.x86_64, for example, /usr/lib64/pgsql/plperl.so (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.; 
warn	postgresql12-1C-python-12.20-alt0.M90P.3.x86_64	There are file conflicts with the package postgresql9.4-python-9.4.26-alt1.x86_64, for example, /usr/lib64/pgsql/plpython2.so (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.; 
warn	postgresql12-1C-server-12.20-alt0.M90P.3.x86_64	There are file conflicts with the package postgresql9.4-server-9.4.26-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (257 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.; 
warn	postgresql12-1C-tcl-12.20-alt0.M90P.3.x86_64	There are file conflicts with the package postgresql9.4-tcl-9.4.26-alt1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (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.; 
warn	postgresql12-contrib-12.22-alt0.M90P.1.x86_64	There are file conflicts with the package postgresql10-contrib-10.23-alt0.M90P.1.x86_64, for example, /usr/bin/oid2name (38 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 postgresql11-contrib-11.22-alt0.M90P.1.x86_64, for example, /usr/bin/oid2name (31 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql9.4-contrib-9.4.26-alt1.x86_64, for example, /usr/bin/oid2name (46 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 postgresql9.5-contrib-9.5.25-alt1.x86_64, for example, /usr/bin/oid2name (51 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql9.6-contrib-9.6.24-alt0.M90P.1.x86_64, for example, /usr/bin/oid2name (49 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.; 
warn	postgresql12-perl-12.22-alt0.M90P.1.x86_64	There are file conflicts with the package postgresql10-perl-10.23-alt0.M90P.1.x86_64, for example, /usr/lib64/pgsql/plperl.so (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 postgresql11-perl-11.22-alt0.M90P.1.x86_64, for example, /usr/share/pgsql/extension/plperl--1.0.sql (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 postgresql9.4-perl-9.4.26-alt1.x86_64, for example, /usr/lib64/pgsql/plperl.so (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 postgresql9.5-perl-9.5.25-alt1.x86_64, for example, /usr/lib64/pgsql/plperl.so (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 postgresql9.6-perl-9.6.24-alt0.M90P.1.x86_64, for example, /usr/lib64/pgsql/plperl.so (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.; 
warn	postgresql12-pg_partman-4.6.2-alt0.M90P.1.x86_64	There are file conflicts with the package postgresql11-pg_partman-4.2.0-alt1.x86_64, for example, /usr/bin/check_unique_constraint.py (44 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.; 
warn	postgresql12-python-12.22-alt0.M90P.1.x86_64	There are file conflicts with the package postgresql10-python-10.23-alt0.M90P.1.x86_64, for example, /usr/lib64/pgsql/plpython2.so (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 postgresql11-python-11.22-alt0.M90P.1.x86_64, for example, /usr/share/pgsql/extension/plpython2u--1.0.sql (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 postgresql9.4-python-9.4.26-alt1.x86_64, for example, /usr/lib64/pgsql/plpython2.so (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 postgresql9.5-python-9.5.25-alt1.x86_64, for example, /usr/lib64/pgsql/plpython2.so (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 postgresql9.6-python-9.6.24-alt0.M90P.1.x86_64, for example, /usr/lib64/pgsql/plpython2.so (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.; 
warn	postgresql12-server-12.22-alt0.M90P.1.x86_64	There are file conflicts with the package postgresql10-server-10.23-alt0.M90P.1.x86_64, for example, /usr/bin/initdb (88 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 postgresql11-server-11.22-alt0.M90P.1.x86_64, for example, /usr/bin/initdb (70 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 postgresql9.4-server-9.4.26-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (271 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 postgresql9.5-server-9.5.25-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (212 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 postgresql9.6-server-9.6.24-alt0.M90P.1.x86_64, for example, /etc/rc.d/init.d/postgresql (183 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.; 
warn	postgresql12-tcl-12.22-alt0.M90P.1.x86_64	There are file conflicts with the package postgresql10-tcl-10.23-alt0.M90P.1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (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 postgresql11-tcl-11.22-alt0.M90P.1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (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 postgresql9.4-tcl-9.4.26-alt1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (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 postgresql9.5-tcl-9.5.25-alt1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (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 postgresql9.6-tcl-9.6.24-alt0.M90P.1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (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.; 
warn	postgresql9.4-contrib-9.4.26-alt1.x86_64	There are file conflicts with the package postgresql10-contrib-10.23-alt0.M90P.1.x86_64, for example, /usr/bin/oid2name (40 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 postgresql11-contrib-11.22-alt0.M90P.1.x86_64, for example, /usr/bin/oid2name (47 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 postgresql12-1C-contrib-12.20-alt0.M90P.3.x86_64, for example, /usr/bin/oid2name (46 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 postgresql12-contrib-12.22-alt0.M90P.1.x86_64, for example, /usr/bin/oid2name (46 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 postgresql9.5-contrib-9.5.25-alt1.x86_64, for example, /usr/bin/oid2name (32 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 postgresql9.6-contrib-9.6.24-alt0.M90P.1.x86_64, for example, /usr/bin/oid2name (37 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.; 
warn	postgresql9.4-perl-9.4.26-alt1.x86_64	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql10-perl-10.23-alt0.M90P.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql11-perl-11.22-alt0.M90P.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.; There are file conflicts with the package postgresql12-1C-perl-12.20-alt0.M90P.3.x86_64, for example, /usr/lib64/pgsql/plperl.so (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 postgresql12-perl-12.22-alt0.M90P.1.x86_64, for example, /usr/lib64/pgsql/plperl.so (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/lib64/pgsql/plperl.so conflicts with the package postgresql9.5-perl-9.5.25-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/lib64/pgsql/plperl.so conflicts with the package postgresql9.6-perl-9.6.24-alt0.M90P.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.; 
warn	postgresql9.4-python-9.4.26-alt1.x86_64	File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql10-python-10.23-alt0.M90P.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql11-python-11.22-alt0.M90P.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.; There are file conflicts with the package postgresql12-1C-python-12.20-alt0.M90P.3.x86_64, for example, /usr/lib64/pgsql/plpython2.so (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 postgresql12-python-12.22-alt0.M90P.1.x86_64, for example, /usr/lib64/pgsql/plpython2.so (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/lib64/pgsql/plpython2.so conflicts with the package postgresql9.5-python-9.5.25-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/lib64/pgsql/plpython2.so conflicts with the package postgresql9.6-python-9.6.24-alt0.M90P.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.; 
warn	postgresql9.4-server-9.4.26-alt1.x86_64	There are file conflicts with the package postgresql10-server-10.23-alt0.M90P.1.x86_64, for example, /etc/rc.d/init.d/postgresql (238 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 postgresql11-server-11.22-alt0.M90P.1.x86_64, for example, /etc/rc.d/init.d/postgresql (253 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 postgresql12-1C-server-12.20-alt0.M90P.3.x86_64, for example, /etc/rc.d/init.d/postgresql (257 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 postgresql12-server-12.22-alt0.M90P.1.x86_64, for example, /etc/rc.d/init.d/postgresql (271 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 postgresql9.5-server-9.5.25-alt1.x86_64, for example, /usr/bin/initdb (104 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 postgresql9.6-server-9.6.24-alt0.M90P.1.x86_64, for example, /usr/bin/initdb (145 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.; 
warn	postgresql9.4-tcl-9.4.26-alt1.x86_64	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql10-tcl-10.23-alt0.M90P.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql11-tcl-11.22-alt0.M90P.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.; There are file conflicts with the package postgresql12-1C-tcl-12.20-alt0.M90P.3.x86_64, for example, /usr/lib64/pgsql/pltcl.so (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 postgresql12-tcl-12.22-alt0.M90P.1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (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/lib64/pgsql/pltcl.so conflicts with the package postgresql9.6-tcl-9.6.24-alt0.M90P.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.; 
warn	postgresql9.5-contrib-9.5.25-alt1.x86_64	There are file conflicts with the package postgresql10-contrib-10.23-alt0.M90P.1.x86_64, for example, /usr/bin/pg_archivecleanup (43 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 postgresql11-contrib-11.22-alt0.M90P.1.x86_64, for example, /usr/bin/pg_archivecleanup (52 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 postgresql12-contrib-12.22-alt0.M90P.1.x86_64, for example, /usr/bin/oid2name (51 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql9.4-contrib-9.4.26-alt1.x86_64, for example, /usr/bin/oid2name (32 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 postgresql9.6-contrib-9.6.24-alt0.M90P.1.x86_64, for example, /usr/bin/pgbench (22 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.; 
warn	postgresql9.5-perl-9.5.25-alt1.x86_64	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql11-perl-11.22-alt0.M90P.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.; There are file conflicts with the package postgresql12-perl-12.22-alt0.M90P.1.x86_64, for example, /usr/lib64/pgsql/plperl.so (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/lib64/pgsql/plperl.so conflicts with the package postgresql9.4-perl-9.4.26-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/lib64/pgsql/plperl.so conflicts with the package postgresql9.6-perl-9.6.24-alt0.M90P.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.; 
warn	postgresql9.5-python-9.5.25-alt1.x86_64	File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql10-python-10.23-alt0.M90P.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql11-python-11.22-alt0.M90P.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.; There are file conflicts with the package postgresql12-python-12.22-alt0.M90P.1.x86_64, for example, /usr/lib64/pgsql/plpython2.so (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/lib64/pgsql/plpython2.so conflicts with the package postgresql9.4-python-9.4.26-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/lib64/pgsql/plpython2.so conflicts with the package postgresql9.6-python-9.6.24-alt0.M90P.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.; 
warn	postgresql9.5-server-9.5.25-alt1.x86_64	There are file conflicts with the package postgresql10-server-10.23-alt0.M90P.1.x86_64, for example, /etc/rc.d/init.d/postgresql (172 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 postgresql11-server-11.22-alt0.M90P.1.x86_64, for example, /etc/rc.d/init.d/postgresql (193 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 postgresql12-server-12.22-alt0.M90P.1.x86_64, for example, /etc/rc.d/init.d/postgresql (212 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 postgresql9.4-server-9.4.26-alt1.x86_64, for example, /usr/bin/initdb (104 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 postgresql9.6-server-9.6.24-alt0.M90P.1.x86_64, for example, /usr/bin/initdb (61 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.; 
warn	postgresql9.5-tcl-9.5.25-alt1.x86_64	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql10-tcl-10.23-alt0.M90P.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql11-tcl-11.22-alt0.M90P.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.; There are file conflicts with the package postgresql12-tcl-12.22-alt0.M90P.1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (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/lib64/pgsql/pltcl.so conflicts with the package postgresql9.6-tcl-9.6.24-alt0.M90P.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.; 
warn	postgresql9.6-contrib-9.6.24-alt0.M90P.1.x86_64	There are file conflicts with the package postgresql10-contrib-10.23-alt0.M90P.1.x86_64, for example, /usr/bin/pg_archivecleanup (38 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 postgresql11-contrib-11.22-alt0.M90P.1.x86_64, for example, /usr/bin/pg_archivecleanup (52 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 postgresql12-contrib-12.22-alt0.M90P.1.x86_64, for example, /usr/bin/oid2name (49 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 postgresql9.4-contrib-9.4.26-alt1.x86_64, for example, /usr/bin/oid2name (37 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 postgresql9.5-contrib-9.5.25-alt1.x86_64, for example, /usr/bin/pgbench (22 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.; 
warn	postgresql9.6-perl-9.6.24-alt0.M90P.1.x86_64	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql10-perl-10.23-alt0.M90P.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql11-perl-11.22-alt0.M90P.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.; There are file conflicts with the package postgresql12-perl-12.22-alt0.M90P.1.x86_64, for example, /usr/lib64/pgsql/plperl.so (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/lib64/pgsql/plperl.so conflicts with the package postgresql9.4-perl-9.4.26-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/lib64/pgsql/plperl.so conflicts with the package postgresql9.5-perl-9.5.25-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.; 
warn	postgresql9.6-python-9.6.24-alt0.M90P.1.x86_64	File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql10-python-10.23-alt0.M90P.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql11-python-11.22-alt0.M90P.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.; There are file conflicts with the package postgresql12-python-12.22-alt0.M90P.1.x86_64, for example, /usr/lib64/pgsql/plpython2.so (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/lib64/pgsql/plpython2.so conflicts with the package postgresql9.4-python-9.4.26-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/lib64/pgsql/plpython2.so conflicts with the package postgresql9.5-python-9.5.25-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.; 
warn	postgresql9.6-server-9.6.24-alt0.M90P.1.x86_64	There are file conflicts with the package postgresql10-server-10.23-alt0.M90P.1.x86_64, for example, /etc/rc.d/init.d/postgresql (134 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 postgresql11-server-11.22-alt0.M90P.1.x86_64, for example, /etc/rc.d/init.d/postgresql (158 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 postgresql12-server-12.22-alt0.M90P.1.x86_64, for example, /etc/rc.d/init.d/postgresql (183 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 postgresql9.4-server-9.4.26-alt1.x86_64, for example, /usr/bin/initdb (145 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 postgresql9.5-server-9.5.25-alt1.x86_64, for example, /usr/bin/initdb (61 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.; 
warn	postgresql9.6-tcl-9.6.24-alt0.M90P.1.x86_64	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql10-tcl-10.23-alt0.M90P.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql11-tcl-11.22-alt0.M90P.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.; There are file conflicts with the package postgresql12-tcl-12.22-alt0.M90P.1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (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/lib64/pgsql/pltcl.so conflicts with the package postgresql9.4-tcl-9.4.26-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/lib64/pgsql/pltcl.so conflicts with the package postgresql9.5-tcl-9.5.25-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.; 
warn	pve-http-server-3.1.1-alt5.x86_64	File /usr/share/javascript/jquery/jquery.min.js conflicts with the package javascript-jquery-1.7.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.; 
warn	pve-manager-6.3.3-alt5.x86_64	Files /usr/bin/vzdump /usr/share/man/man1/vzdump.1.xz conflict with the package vzdump-1.0-alt3.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.; 
warn	pve-qemu-common-5.1.0-alt6.x86_64	File /usr/share/qemu/skiboot.lid conflicts with the package opal-firmware-6.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/qemu/hppa-firmware.img conflicts with the package qemu-system-hppa-core-5.2.0-alt6.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/qemu/petalogix-ml605.dtb /usr/share/qemu/petalogix-s3adsp1800.dtb conflict with the package qemu-system-microblaze-core-5.2.0-alt6.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.; 
warn	pve-qemu-system-5.1.0-alt6.x86_64	File /usr/share/man/man1/qemu.1.xz conflicts with the package qemu-common-5.2.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/bin/qemu-system-aarch64 conflicts with the package qemu-system-aarch64-core-5.2.0-alt6.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/bin/qemu-system-x86_64 conflicts with the package qemu-system-x86-core-5.2.0-alt6.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.; 
warn	python-module-apiclient-1.0.3-alt1.noarch	Files /usr/lib/python2.7/site-packages/apiclient/__init__.py /usr/lib/python2.7/site-packages/apiclient/__init__.pyc /usr/lib/python2.7/site-packages/apiclient/__init__.pyo conflict with the package python-module-google-api-client-1.7.8-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	python-module-asterisk-ami-0.1.5-alt1.noarch	Files /usr/lib/python2.7/site-packages/asterisk/__init__.py /usr/lib/python2.7/site-packages/asterisk/__init__.pyc /usr/lib/python2.7/site-packages/asterisk/__init__.pyo conflict with the package python-module-pyst-0.6.50-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	python-module-commonmark-0.8.1-alt0.1.noarch	File /usr/bin/cmark conflicts with the package cmark-0.28.3-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.; 
warn	python-module-configobj-5.0.6-alt1.1.1.noarch	Files /usr/lib/python2.7/site-packages/configobj.py /usr/lib/python2.7/site-packages/validate.py conflict with the package dynagen-0.11.0-alt1.qa1.1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	python-module-cron_descriptor-1.2.8-alt1.noarch	Files /usr/lib/python2.7/site-packages/tests/__init__.py /usr/lib/python2.7/site-packages/tests/__init__.pyc /usr/lib/python2.7/site-packages/tests/__init__.pyo conflict with the package python-module-m2r-0.11-alt1.qa1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	python-module-dataflake-1.4-alt1.2.x86_64	Files /usr/lib64/python2.7/site-packages/dataflake/__init__.py /usr/lib64/python2.7/site-packages/dataflake/__init__.pyc /usr/lib64/python2.7/site-packages/dataflake/__init__.pyo conflict with the package python-module-dataflake.fakeldap-2.1-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.; 
warn	python-module-dataflake.fakeldap-2.1-alt2.x86_64	Files /usr/lib64/python2.7/site-packages/dataflake/__init__.py /usr/lib64/python2.7/site-packages/dataflake/__init__.pyc /usr/lib64/python2.7/site-packages/dataflake/__init__.pyo conflict with the package python-module-dataflake-1.4-alt1.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	python-module-django-cms-2.1.5-alt3.noarch	There are file conflicts with the package python-module-django-publisher-0.0.3-alt1.2.noarch, for example, /usr/lib/python2.7/site-packages/publisher/__init__.py (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.; 
warn	python-module-django-facebook-utils-1.0.4-alt1.git20130201.1.2.noarch	Files /usr/lib/python2.7/site-packages/facebook_utils/__init__.py /usr/lib/python2.7/site-packages/facebook_utils/__init__.pyc /usr/lib/python2.7/site-packages/facebook_utils/__init__.pyo conflict with the package python-module-facebook_utils-0.20.3-alt1.git20140717.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.; 
warn	python-module-django-publisher-0.0.3-alt1.2.noarch	There are file conflicts with the package python-module-django-cms-2.1.5-alt3.noarch, for example, /usr/lib/python2.7/site-packages/publisher/__init__.py (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.; 
warn	python-module-docker-registry-0.6.1-alt1.noarch	File /etc/docker-registry/config.yml conflicts with the package docker-registry-2.6.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.; 
warn	python-module-facebook-2.3.14-alt1.git20140409.1.2.noarch	There are file conflicts with the package python-module-facebook_api-0.1.4-alt1.2.noarch, for example, /usr/lib/python2.7/site-packages/facebook/__init__.py (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/lib/python2.7/site-packages/facebook/__init__.py /usr/lib/python2.7/site-packages/facebook/__init__.pyc /usr/lib/python2.7/site-packages/facebook/__init__.pyo conflict with the package python-module-tornado-facebook-sdk-0.1.0-alt1.git20121001.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.; 
warn	python-module-facebook-ads-api-0.3.0-alt1.noarch	Files /usr/lib/python2.7/site-packages/facebook.py /usr/lib/python2.7/site-packages/facebook.pyc /usr/lib/python2.7/site-packages/facebook.pyo conflict with the package python-module-geventhttpclient-facebook-0.4.4-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib/python2.7/site-packages/facebook.py /usr/lib/python2.7/site-packages/facebook.pyc /usr/lib/python2.7/site-packages/facebook.pyo conflict with the package python-module-requests-facebook-0.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.; 
warn	python-module-facebook-sdk-1.0.0-alt1.alpha.git20140828.2.noarch	Files /usr/lib/python2.7/site-packages/facebook/__init__.py /usr/lib/python2.7/site-packages/facebook/__init__.pyc /usr/lib/python2.7/site-packages/facebook/__init__.pyo conflict with the package python-module-facebook_api-0.1.4-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib/python2.7/site-packages/facebook/__init__.py /usr/lib/python2.7/site-packages/facebook/__init__.pyc /usr/lib/python2.7/site-packages/facebook/__init__.pyo conflict with the package python-module-tornado-facebook-sdk-0.1.0-alt1.git20121001.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.; 
warn	python-module-facebook_api-0.1.4-alt1.2.noarch	There are file conflicts with the package python-module-facebook-2.3.14-alt1.git20140409.1.2.noarch, for example, /usr/lib/python2.7/site-packages/facebook/__init__.py (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/lib/python2.7/site-packages/facebook/__init__.py /usr/lib/python2.7/site-packages/facebook/__init__.pyc /usr/lib/python2.7/site-packages/facebook/__init__.pyo conflict with the package python-module-facebook-sdk-1.0.0-alt1.alpha.git20140828.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/lib/python2.7/site-packages/facebook/__init__.py /usr/lib/python2.7/site-packages/facebook/__init__.pyc /usr/lib/python2.7/site-packages/facebook/__init__.pyo conflict with the package python-module-tornado-facebook-sdk-0.1.0-alt1.git20121001.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.; 
warn	python-module-facebook_utils-0.20.3-alt1.git20140717.2.noarch	Files /usr/lib/python2.7/site-packages/facebook_utils/__init__.py /usr/lib/python2.7/site-packages/facebook_utils/__init__.pyc /usr/lib/python2.7/site-packages/facebook_utils/__init__.pyo conflict with the package python-module-django-facebook-utils-1.0.4-alt1.git20130201.1.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.; 
warn	python-module-gearbox-0.1.1-alt2.1.noarch	File /usr/bin/gearbox conflicts with the package mesa-demos-8.4.0-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	python-module-geventhttpclient-facebook-0.4.4-alt1.2.noarch	Files /usr/lib/python2.7/site-packages/facebook.py /usr/lib/python2.7/site-packages/facebook.pyc /usr/lib/python2.7/site-packages/facebook.pyo conflict with the package python-module-facebook-ads-api-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.; Files /usr/lib/python2.7/site-packages/facebook.py /usr/lib/python2.7/site-packages/facebook.pyc /usr/lib/python2.7/site-packages/facebook.pyo conflict with the package python-module-requests-facebook-0.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.; 
warn	python-module-google-api-client-1.7.8-alt1.noarch	Files /usr/lib/python2.7/site-packages/apiclient/__init__.py /usr/lib/python2.7/site-packages/apiclient/__init__.pyc /usr/lib/python2.7/site-packages/apiclient/__init__.pyo conflict with the package python-module-apiclient-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.; 
warn	python-module-libarchive-3.1.2.1-alt4.1.x86_64	Files /usr/lib64/python2.7/site-packages/libarchive/__init__.py /usr/lib64/python2.7/site-packages/libarchive/__init__.pyc /usr/lib64/python2.7/site-packages/libarchive/__init__.pyo conflict with the package python-module-libarchive-c-2.8-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.; 
warn	python-module-libarchive-c-2.8-alt1.x86_64	Files /usr/lib64/python2.7/site-packages/libarchive/__init__.py /usr/lib64/python2.7/site-packages/libarchive/__init__.pyc /usr/lib64/python2.7/site-packages/libarchive/__init__.pyo conflict with the package python-module-libarchive-3.1.2.1-alt4.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.; 
warn	python-module-m2r-0.11-alt1.qa1.noarch	Files /usr/lib/python2.7/site-packages/tests/__init__.py /usr/lib/python2.7/site-packages/tests/__init__.pyc /usr/lib/python2.7/site-packages/tests/__init__.pyo conflict with the package python-module-cron_descriptor-1.2.8-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	python-module-phonon-2.0-alt1.noarch	File /usr/lib/python2.7/site-packages/test/__init__.py conflicts with the package python-module-sqlalchemy_monetdb-1.0.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	python-module-pisa-3.0.33-alt2.noarch	Files /usr/lib/python2.7/site-packages/sx/__init__.py /usr/lib/python2.7/site-packages/sx/__init__.pyc /usr/lib/python2.7/site-packages/sx/__init__.pyo conflict with the package libsx-2.17-alt1_9.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	python-module-ptest-1.7.4-alt1.1.noarch	File /usr/bin/ptest conflicts with the package parmetis-4.0.3-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.; 
warn	python-module-pybugz-0.9.0-alt1.rc1.1.noarch	Files /etc/bash_completion.d/bash-completion /usr/bin/bugz conflict with the package python3-module-pybugz-0.11.1-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	python-module-pyst-0.6.50-alt1.noarch	Files /usr/lib/python2.7/site-packages/asterisk/__init__.py /usr/lib/python2.7/site-packages/asterisk/__init__.pyc /usr/lib/python2.7/site-packages/asterisk/__init__.pyo conflict with the package python-module-asterisk-ami-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.; 
warn	python-module-radon-3.0.3-alt1.noarch	File /usr/bin/radon conflicts with the package nfft-3.2.3-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.; 
warn	python-module-requests-facebook-0.4.0-alt1.noarch	Files /usr/lib/python2.7/site-packages/facebook.py /usr/lib/python2.7/site-packages/facebook.pyc /usr/lib/python2.7/site-packages/facebook.pyo conflict with the package python-module-facebook-ads-api-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.; Files /usr/lib/python2.7/site-packages/facebook.py /usr/lib/python2.7/site-packages/facebook.pyc /usr/lib/python2.7/site-packages/facebook.pyo conflict with the package python-module-geventhttpclient-facebook-0.4.4-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.; 
warn	python-module-servicemanager-0.0.16-alt2.noarch	File /usr/bin/sm conflicts with the package screen-message-0.6-alt1.qa1.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.; 
warn	python-module-shiboken2-devel-5.12.6-alt1.1.p9.x86_64	Files /usr/include/shiboken2/sbkversion.h /usr/lib64/cmake/Shiboken2-5.12.6/Shiboken2Config.cmake /usr/lib64/cmake/Shiboken2-5.12.6/Shiboken2Targets-release.cmake conflict with the package python3-module-shiboken2-devel-5.12.6-alt0.2.p9.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.; 
warn	python-module-spec-1.4.0-alt1.1.noarch	File /usr/bin/spec conflicts with the package iceb-19.14-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.; 
warn	python-module-sqlalchemy_monetdb-1.0.0-alt1.1.noarch	File /usr/lib/python2.7/site-packages/test/__init__.py conflicts with the package python-module-phonon-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.; 
warn	python-module-tornado-facebook-sdk-0.1.0-alt1.git20121001.2.noarch	Files /usr/lib/python2.7/site-packages/facebook/__init__.py /usr/lib/python2.7/site-packages/facebook/__init__.pyc /usr/lib/python2.7/site-packages/facebook/__init__.pyo conflict with the package python-module-facebook-2.3.14-alt1.git20140409.1.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/lib/python2.7/site-packages/facebook/__init__.py /usr/lib/python2.7/site-packages/facebook/__init__.pyc /usr/lib/python2.7/site-packages/facebook/__init__.pyo conflict with the package python-module-facebook-sdk-1.0.0-alt1.alpha.git20140828.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/lib/python2.7/site-packages/facebook/__init__.py /usr/lib/python2.7/site-packages/facebook/__init__.pyc /usr/lib/python2.7/site-packages/facebook/__init__.pyo conflict with the package python-module-facebook_api-0.1.4-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.; 
warn	python-module-tpg-3.2.2-alt3.1.noarch	File /usr/bin/tpg conflicts with the package tpg-3.2.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	python-module-xstatic-1.0.1-alt2.1.noarch	File /usr/lib/python2.7/site-packages/xstatic/pkg/__init__.py conflicts with the package python-module-xstatic-html5shiv-3.6.1-alt3.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib/python2.7/site-packages/xstatic/pkg/__init__.py conflicts with the package python-module-xstatic-less-1.3.0.1-alt3.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib/python2.7/site-packages/xstatic/pkg/__init__.py conflicts with the package python-module-xstatic-socialshareprivacy-1.4.1-alt3.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	python-module-xstatic-html5shiv-3.6.1-alt3.1.noarch	File /usr/lib/python2.7/site-packages/xstatic/pkg/__init__.py conflicts with the package python-module-xstatic-1.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.; 
warn	python-module-xstatic-less-1.3.0.1-alt3.1.noarch	File /usr/lib/python2.7/site-packages/xstatic/pkg/__init__.py conflicts with the package python-module-xstatic-1.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.; 
warn	python-module-xstatic-socialshareprivacy-1.4.1-alt3.1.noarch	File /usr/lib/python2.7/site-packages/xstatic/pkg/__init__.py conflicts with the package python-module-xstatic-1.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.; 
warn	python3-module-apiclient-1.0.3-alt1.noarch	There are file conflicts with the package python3-module-google-api-client-1.7.8-alt1.noarch, for example, /usr/lib/python3/site-packages/apiclient/__init__.py (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.; 
warn	python3-module-dataflake-1.4-alt1.2.x86_64	There are file conflicts with the package python3-module-dataflake.fakeldap-2.1-alt2.x86_64, for example, /usr/lib64/python3/site-packages/dataflake/__init__.py (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.; 
warn	python3-module-dataflake.fakeldap-2.1-alt2.x86_64	There are file conflicts with the package python3-module-dataflake-1.4-alt1.2.x86_64, for example, /usr/lib64/python3/site-packages/dataflake/__init__.py (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.; 
warn	python3-module-django-facebook-utils-1.0.4-alt1.git20130201.1.2.noarch	There are file conflicts with the package python3-module-facebook_utils-0.20.3-alt1.git20140717.2.noarch, for example, /usr/lib/python3/site-packages/facebook_utils/__init__.py (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.; 
warn	python3-module-facebook-2.3.14-alt1.git20140409.1.2.noarch	There are file conflicts with the package python3-module-facebook_api-0.1.4-alt1.2.noarch, for example, /usr/lib/python3/site-packages/facebook/__init__.py (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 python3-module-tornado-facebook-sdk-0.1.0-alt1.git20121001.2.noarch, for example, /usr/lib/python3/site-packages/facebook/__init__.py (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.; 
warn	python3-module-facebook-ads-api-0.3.0-alt1.noarch	File /usr/lib/python3/site-packages/facebook.py conflicts with the package python3-module-geventhttpclient-facebook-0.4.4-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/lib/python3/site-packages/facebook.py conflicts with the package python3-module-requests-facebook-0.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.; 
warn	python3-module-facebook-sdk-1.0.0-alt1.alpha.git20140828.2.noarch	There are file conflicts with the package python3-module-facebook_api-0.1.4-alt1.2.noarch, for example, /usr/lib/python3/site-packages/facebook/__init__.py (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 python3-module-tornado-facebook-sdk-0.1.0-alt1.git20121001.2.noarch, for example, /usr/lib/python3/site-packages/facebook/__init__.py (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.; 
warn	python3-module-facebook_api-0.1.4-alt1.2.noarch	There are file conflicts with the package python3-module-facebook-2.3.14-alt1.git20140409.1.2.noarch, for example, /usr/lib/python3/site-packages/facebook/__init__.py (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 python3-module-facebook-sdk-1.0.0-alt1.alpha.git20140828.2.noarch, for example, /usr/lib/python3/site-packages/facebook/__init__.py (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 python3-module-tornado-facebook-sdk-0.1.0-alt1.git20121001.2.noarch, for example, /usr/lib/python3/site-packages/facebook/__init__.py (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.; 
warn	python3-module-facebook_utils-0.20.3-alt1.git20140717.2.noarch	There are file conflicts with the package python3-module-django-facebook-utils-1.0.4-alt1.git20130201.1.2.noarch, for example, /usr/lib/python3/site-packages/facebook_utils/__init__.py (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.; 
warn	python3-module-geventhttpclient-facebook-0.4.4-alt1.2.noarch	File /usr/lib/python3/site-packages/facebook.py conflicts with the package python3-module-facebook-ads-api-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.; There are file conflicts with the package python3-module-requests-facebook-0.4.0-alt1.noarch, for example, /usr/lib/python3/site-packages/__pycache__/facebook.cpython-37.opt-1.pyc (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.; 
warn	python3-module-google-api-client-1.7.8-alt1.noarch	There are file conflicts with the package python3-module-apiclient-1.0.3-alt1.noarch, for example, /usr/lib/python3/site-packages/apiclient/__init__.py (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.; 
warn	python3-module-js.jquery-1.9.1-alt1.1.1.1.1.x86_64	Files /usr/lib64/python3/site-packages/js/jquery/__pycache__/__init__.cpython-37.opt-1.pyc /usr/lib64/python3/site-packages/js/jquery/__pycache__/__init__.cpython-37.opt-2.pyc /usr/lib64/python3/site-packages/js/jquery/__pycache__/__init__.cpython-37.pyc conflict with the package python3-module-js.query-1.9.2-alt1.dev0.hg20130303.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	python3-module-js.query-1.9.2-alt1.dev0.hg20130303.2.x86_64	Files /usr/lib64/python3/site-packages/js/jquery/__pycache__/__init__.cpython-37.opt-1.pyc /usr/lib64/python3/site-packages/js/jquery/__pycache__/__init__.cpython-37.opt-2.pyc /usr/lib64/python3/site-packages/js/jquery/__pycache__/__init__.cpython-37.pyc conflict with the package python3-module-js.jquery-1.9.1-alt1.1.1.1.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.; 
warn	python3-module-libsass-0.20.1-alt1.x86_64	File /usr/bin/sassc conflicts with the package sassc-3.5.0-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	python3-module-m2r-0.11-alt1.qa1.noarch	Files /usr/lib/python3/site-packages/tests/__pycache__/__init__.cpython-37.opt-1.pyc /usr/lib/python3/site-packages/tests/__pycache__/__init__.cpython-37.opt-2.pyc /usr/lib/python3/site-packages/tests/__pycache__/__init__.cpython-37.pyc conflict with the package python3-module-pymta-tests-0.5.2-alt3.1.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.; 
warn	python3-module-phonon-2.0-alt1.noarch	There are file conflicts with the package python3-module-sqlalchemy_monetdb-1.0.0-alt1.1.noarch, for example, /usr/lib/python3/site-packages/test/__init__.py (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.; 
warn	python3-module-pybugz-0.11.1-alt1.2.noarch	Files /etc/bash_completion.d/bash-completion /usr/bin/bugz conflict with the package python-module-pybugz-0.9.0-alt1.rc1.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.; 
warn	python3-module-pymta-tests-0.5.2-alt3.1.2.noarch	Files /usr/lib/python3/site-packages/tests/__pycache__/__init__.cpython-37.opt-1.pyc /usr/lib/python3/site-packages/tests/__pycache__/__init__.cpython-37.opt-2.pyc /usr/lib/python3/site-packages/tests/__pycache__/__init__.cpython-37.pyc conflict with the package python3-module-m2r-0.11-alt1.qa1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	python3-module-rasterio-1.1.8-alt3.x86_64	File /usr/bin/rio conflicts with the package plan9-wm-1.0-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.; 
warn	python3-module-requests-facebook-0.4.0-alt1.noarch	File /usr/lib/python3/site-packages/facebook.py conflicts with the package python3-module-facebook-ads-api-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.; There are file conflicts with the package python3-module-geventhttpclient-facebook-0.4.4-alt1.2.noarch, for example, /usr/lib/python3/site-packages/__pycache__/facebook.cpython-37.opt-1.pyc (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.; 
warn	python3-module-shiboken2-devel-5.12.6-alt0.2.p9.x86_64	Files /usr/include/shiboken2/sbkversion.h /usr/lib64/cmake/Shiboken2-5.12.6/Shiboken2Config.cmake /usr/lib64/cmake/Shiboken2-5.12.6/Shiboken2Targets-release.cmake conflict with the package python-module-shiboken2-devel-5.12.6-alt1.1.p9.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.; 
warn	python3-module-sqlalchemy_monetdb-1.0.0-alt1.1.noarch	There are file conflicts with the package python3-module-phonon-2.0-alt1.noarch, for example, /usr/lib/python3/site-packages/test/__init__.py (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.; 
warn	python3-module-tornado-facebook-sdk-0.1.0-alt1.git20121001.2.noarch	There are file conflicts with the package python3-module-facebook-2.3.14-alt1.git20140409.1.2.noarch, for example, /usr/lib/python3/site-packages/facebook/__init__.py (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 python3-module-facebook-sdk-1.0.0-alt1.alpha.git20140828.2.noarch, for example, /usr/lib/python3/site-packages/facebook/__init__.py (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 python3-module-facebook_api-0.1.4-alt1.2.noarch, for example, /usr/lib/python3/site-packages/facebook/__init__.py (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.; 
warn	python3-module-xstatic-1.0.1-alt2.1.noarch	File /usr/lib/python3/site-packages/xstatic/pkg/__init__.py conflicts with the package python3-module-xstatic-html5shiv-3.6.1-alt3.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib/python3/site-packages/xstatic/pkg/__init__.py conflicts with the package python3-module-xstatic-less-1.3.0.1-alt3.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib/python3/site-packages/xstatic/pkg/__init__.py conflicts with the package python3-module-xstatic-socialshareprivacy-1.4.1-alt3.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	python3-module-xstatic-html5shiv-3.6.1-alt3.1.noarch	File /usr/lib/python3/site-packages/xstatic/pkg/__init__.py conflicts with the package python3-module-xstatic-1.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.; Files /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-37.opt-1.pyc /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-37.opt-2.pyc /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-37.pyc conflict with the package python3-module-xstatic-less-1.3.0.1-alt3.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-37.opt-1.pyc /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-37.opt-2.pyc /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-37.pyc conflict with the package python3-module-xstatic-socialshareprivacy-1.4.1-alt3.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	python3-module-xstatic-less-1.3.0.1-alt3.1.noarch	File /usr/lib/python3/site-packages/xstatic/pkg/__init__.py conflicts with the package python3-module-xstatic-1.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.; Files /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-37.opt-1.pyc /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-37.opt-2.pyc /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-37.pyc conflict with the package python3-module-xstatic-html5shiv-3.6.1-alt3.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-37.opt-1.pyc /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-37.opt-2.pyc /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-37.pyc conflict with the package python3-module-xstatic-socialshareprivacy-1.4.1-alt3.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	python3-module-xstatic-socialshareprivacy-1.4.1-alt3.1.noarch	File /usr/lib/python3/site-packages/xstatic/pkg/__init__.py conflicts with the package python3-module-xstatic-1.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.; Files /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-37.opt-1.pyc /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-37.opt-2.pyc /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-37.pyc conflict with the package python3-module-xstatic-html5shiv-3.6.1-alt3.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-37.opt-1.pyc /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-37.opt-2.pyc /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-37.pyc conflict with the package python3-module-xstatic-less-1.3.0.1-alt3.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	qemu-common-5.2.0-alt6.noarch	File /usr/share/man/man1/qemu.1.xz conflicts with the package pve-qemu-system-5.1.0-alt6.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.; 
warn	qemu-system-aarch64-core-5.2.0-alt6.x86_64	File /usr/bin/qemu-system-aarch64 conflicts with the package pve-qemu-system-5.1.0-alt6.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.; 
warn	qemu-system-hppa-core-5.2.0-alt6.x86_64	File /usr/share/qemu/hppa-firmware.img conflicts with the package pve-qemu-common-5.1.0-alt6.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.; 
warn	qemu-system-microblaze-core-5.2.0-alt6.x86_64	Files /usr/share/qemu/petalogix-ml605.dtb /usr/share/qemu/petalogix-s3adsp1800.dtb conflict with the package pve-qemu-common-5.1.0-alt6.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.; 
warn	qemu-system-ppc-core-5.2.0-alt6.x86_64	File /usr/share/qemu/skiboot.lid conflicts with the package opal-firmware-6.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.; 
warn	qemu-system-x86-core-5.2.0-alt6.x86_64	File /usr/bin/qemu-system-x86_64 conflicts with the package pve-qemu-system-5.1.0-alt6.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.; 
warn	qgis-devel-2.18.28-alt4.1.p9.x86_64	There are file conflicts with the package qgis3-devel-3.18.3-alt0.p9.1.x86_64, for example, /usr/include/qgis/Bezier3D.h (573 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.; 
warn	qgis-grass-2.18.28-alt4.1.p9.x86_64	There are file conflicts with the package qgis3-grass-3.18.3-alt0.p9.1.x86_64, for example, /usr/lib64/qgis/grass/bin/qgis.g.browser7 (666 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.; 
warn	qgis-python-2.18.28-alt4.1.p9.x86_64	There are file conflicts with the package qgis3-python-3.18.3-alt0.p9.1.x86_64, for example, /usr/share/qgis/python/console/__init__.py (1006 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.; 
warn	qgis-server-2.18.28-alt4.1.p9.x86_64	File /usr/libexec/qgis/qgis_mapserv.fcgi conflicts with the package qgis3-server-3.18.3-alt0.p9.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.; 
warn	qgis3-devel-3.18.3-alt0.p9.1.x86_64	There are file conflicts with the package qgis-devel-2.18.28-alt4.1.p9.x86_64, for example, /usr/include/qgis/Bezier3D.h (573 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.; 
warn	qgis3-grass-3.18.3-alt0.p9.1.x86_64	There are file conflicts with the package qgis-grass-2.18.28-alt4.1.p9.x86_64, for example, /usr/lib64/qgis/grass/bin/qgis.g.browser7 (666 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.; 
warn	qgis3-python-3.18.3-alt0.p9.1.x86_64	There are file conflicts with the package qgis-python-2.18.28-alt4.1.p9.x86_64, for example, /usr/share/qgis/python/console/__init__.py (1006 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.; 
warn	qgis3-server-3.18.3-alt0.p9.1.x86_64	File /usr/libexec/qgis/qgis_mapserv.fcgi conflicts with the package qgis-server-2.18.28-alt4.1.p9.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.; 
warn	quota-devel-4.05.0.3.f2eb-alt1.noarch	Files /usr/include/rpcsvc/rquota.h /usr/include/rpcsvc/rquota.x conflict with the package glibc-devel-2.27-alt14.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.; 
warn	racket-7.3-alt1.x86_64	File /usr/bin/slideshow conflicts with the package batik-slideshow-1.10-alt1_2jpp8.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	rr-1.3-alt1.qa1.x86_64	File /usr/bin/rr conflicts with the package rr-project-5.2.0-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.; 
warn	rr-project-5.2.0-alt2.x86_64	File /usr/bin/rr conflicts with the package rr-1.3-alt1.qa1.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.; 
warn	ruby-activemodel-serializers-xml-doc-1.0.2-alt1.noarch	File /usr/share/ri/site/ActiveRecord/cdesc-ActiveRecord.ri conflicts with the package ruby-activerecord-mysql2-adapter-doc-0.0.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/ActiveRecord/cdesc-ActiveRecord.ri conflicts with the package ruby-activerecord-session_store-doc-1.1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/ActiveModel/cdesc-ActiveModel.ri conflicts with the package ruby-draper-doc-3.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/ActiveRecord/cdesc-ActiveRecord.ri conflicts with the package ruby-friendly_id-doc-5.2.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/ActiveRecord/cdesc-ActiveRecord.ri conflicts with the package ruby-scoped-search-doc-4.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.; 
warn	ruby-activerecord-mysql2-adapter-doc-0.0.3-alt1.1.noarch	File /usr/share/ri/site/ActiveRecord/cdesc-ActiveRecord.ri conflicts with the package ruby-activemodel-serializers-xml-doc-1.0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/ActiveRecord/cdesc-ActiveRecord.ri conflicts with the package ruby-activerecord-session_store-doc-1.1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-em-synchrony-doc-1.0.6-alt1.1.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/ActiveRecord/cdesc-ActiveRecord.ri conflicts with the package ruby-friendly_id-doc-5.2.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/ActiveRecord/cdesc-ActiveRecord.ri conflicts with the package ruby-scoped-search-doc-4.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.; 
warn	ruby-activerecord-session_store-doc-1.1.1-alt1.noarch	File /usr/share/ri/site/ActiveRecord/cdesc-ActiveRecord.ri conflicts with the package ruby-activemodel-serializers-xml-doc-1.0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/ActiveRecord/cdesc-ActiveRecord.ri conflicts with the package ruby-activerecord-mysql2-adapter-doc-0.0.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/ActiveRecord/VERSION/cdesc-VERSION.ri /usr/share/ri/site/ActiveRecord/cdesc-ActiveRecord.ri conflict with the package ruby-em-synchrony-doc-1.0.6-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/ActiveRecord/VERSION/cdesc-VERSION.ri /usr/share/ri/site/ActiveRecord/cdesc-ActiveRecord.ri conflict with the package ruby-friendly_id-doc-5.2.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/ActionDispatch/cdesc-ActionDispatch.ri conflicts with the package ruby-oauth-doc-0.5.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/ActiveRecord/cdesc-ActiveRecord.ri conflicts with the package ruby-scoped-search-doc-4.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.; 
warn	ruby-algebrick-doc-0.7.5-alt1.1.noarch	File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-cfpropertylist-doc-3.0.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-fission-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-rr-doc-1.2.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-sfl-doc-2.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-amazon-ec2-doc-0.9.17-alt3.noarch	File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-cfpropertylist-doc-3.0.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-fission-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-fog-xenserver-doc-0.3.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/Hash/cdesc-Hash.ri conflicts with the package ruby-rr-doc-1.2.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-amq-protocol-doc-2.3.0-alt1.1.noarch	There are file conflicts with the package ruby-amqp-doc-1.8.0-alt1.1.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.; 
warn	ruby-amqp-doc-1.8.0-alt1.1.noarch	There are file conflicts with the package ruby-amq-protocol-doc-2.3.0-alt1.1.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-net-ping-doc-2.0.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/RbConfig/cdesc-RbConfig.ri conflicts with the package ruby-spoon-doc-0.0.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-sys-proctable-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.; 
warn	ruby-archive-tar-minitar-0.5.2-alt1.2.noarch	File /usr/lib/ruby/site_ruby/archive/tar/minitar.rb conflicts with the package ruby-minitar-0.6.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-archive-tar-minitar-doc-0.5.2-alt1.2.noarch	There are file conflicts with the package ruby-minitar-doc-0.6.1-alt1.noarch, for example, /usr/share/ri/site/Archive/Tar/Minitar/Input/cdesc-Input.ri (54 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.; 
warn	ruby-archive-zip-doc-0.11.0-alt1.noarch	File /usr/share/ri/site/Time/cdesc-Time.ri conflicts with the package gem-vpim-doc-13.11.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.; Files /usr/share/ri/site/Integer/cdesc-Integer.ri /usr/share/ri/site/Integer/ord-i.ri conflict with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Time/cdesc-Time.ri conflicts with the package ruby-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Archive/cdesc-Archive.ri conflicts with the package ruby-ffi-libarchive-doc-0.4.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Archive/cdesc-Archive.ri conflicts with the package ruby-minitar-doc-0.6.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-awesome-print-doc-1.8.0-alt1.1.noarch	File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-storage-doc-0.15.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-backports-doc-3.7.0-alt1.1.noarch, for example, /usr/share/ri/site/Kernel/cdesc-Kernel.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/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-em-synchrony-doc-1.0.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-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fission-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-java-doc-0.0.2-alt2.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/ri/site/String/cdesc-String.ri conflicts with the package ruby-kindlerb-doc-1.2.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-memoist-doc-0.16.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/Method/cdesc-Method.ri /usr/share/ri/site/UnboundMethod/cdesc-UnboundMethod.ri conflict with the package ruby-method_source-doc-0.9.0-alt1.noarch. Moreover, the packages have 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-oauth-doc-0.5.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-pedump-doc-0.5.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-polyglot-doc-0.3.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/ActionView/cdesc-ActionView.ri conflicts with the package ruby-rails-html-sanitizer-doc-1.0.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/Kernel/cdesc-Kernel.ri conflicts with the package ruby-retriable-doc-3.1.2-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-scrub_rb-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-sfl-doc-2.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-specinfra-doc-2.77.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-zhexdump-doc-0.0.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-azure-core-doc-0.1.14-alt2.1.noarch	File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-awesome-print-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Azure/cdesc-Azure.ri conflicts with the package ruby-azure-doc-0.7.10-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-azure-storage-doc-0.15.0-alt1.1.noarch, for example, /usr/share/ri/site/Azure/cdesc-Azure.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/String/cdesc-String.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fission-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/IPAddr/cdesc-IPAddr.ri conflicts with the package ruby-fog-ecloud-doc-0.3.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-kindlerb-doc-1.2.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-pedump-doc-0.5.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-scrub_rb-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-specinfra-doc-2.77.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-zhexdump-doc-0.0.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-azure-doc-0.7.10-alt2.1.noarch	File /usr/share/ri/site/Azure/cdesc-Azure.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-azure-storage-doc-0.15.0-alt1.1.noarch, for example, /usr/share/ri/site/Azure/Service/EnumerationResults/cdesc-EnumerationResults.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.; 
warn	ruby-azure-storage-doc-0.15.0-alt1.1.noarch	File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-awesome-print-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-azure-core-doc-0.1.14-alt2.1.noarch, for example, /usr/share/ri/site/Azure/cdesc-Azure.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.; There are file conflicts with the package ruby-azure-doc-0.7.10-alt2.1.noarch, for example, /usr/share/ri/site/Azure/Service/EnumerationResults/cdesc-EnumerationResults.ri (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fission-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/IPAddr/cdesc-IPAddr.ri conflicts with the package ruby-fog-ecloud-doc-0.3.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-kindlerb-doc-1.2.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-pedump-doc-0.5.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-scrub_rb-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-specinfra-doc-2.77.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-zhexdump-doc-0.0.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-backports-doc-3.7.0-alt1.1.noarch	File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-algebrick-doc-0.7.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/Hash/cdesc-Hash.ri conflicts with the package ruby-amazon-ec2-doc-0.9.17-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.; Files /usr/share/ri/site/Integer/cdesc-Integer.ri /usr/share/ri/site/Integer/ord-i.ri conflict with the package ruby-archive-zip-doc-0.11.0-alt1.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-awesome-print-doc-1.8.0-alt1.1.noarch, for example, /usr/share/ri/site/Kernel/cdesc-Kernel.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/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-storage-doc-0.15.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Enumerator/cdesc-Enumerator.ri /usr/share/ri/site/Hash/cdesc-Hash.ri conflict with the package ruby-cfpropertylist-doc-3.0.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-em-synchrony-doc-1.0.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/IO/cdesc-IO.ri conflicts with the package ruby-excon-doc-0.62.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-extlib-doc-0.9.16-alt1.1.noarch, for example, /usr/share/ri/site/Array/cdesc-Array.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.; There are file conflicts with the package ruby-fission-doc-0.5.0-alt1.1.noarch, for example, /usr/share/ri/site/Array/cdesc-Array.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/Hash/cdesc-Hash.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Hash/cdesc-Hash.ri /usr/share/ri/site/Hash/symbolize_keys%21-i.ri conflict with the package ruby-fog-xenserver-doc-0.3.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/IO/cdesc-IO.ri conflicts with the package ruby-io-like-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.; Files /usr/share/ri/site/Kernel/cdesc-Kernel.ri /usr/share/ri/site/Module/cdesc-Module.ri conflict with the package ruby-java-doc-0.0.2-alt2.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/ri/site/String/cdesc-String.ri conflicts with the package ruby-kindlerb-doc-1.2.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Kernel/cdesc-Kernel.ri /usr/share/ri/site/Kernel/singleton_class-i.ri conflict with the package ruby-memoist-doc-0.16.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/Method/cdesc-Method.ri /usr/share/ri/site/Proc/cdesc-Proc.ri /usr/share/ri/site/UnboundMethod/cdesc-UnboundMethod.ri conflict with the package ruby-method_source-doc-0.9.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Process/cdesc-Process.ri conflicts with the package ruby-mixlib-shellout-doc-2.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/Symbol/cdesc-Symbol.ri conflicts with the package ruby-mongo-doc-2.6.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-net-ping-doc-2.0.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-pedump-doc-0.5.2-alt1.1.noarch, for example, /usr/share/ri/site/File/cdesc-File.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-polyglot-doc-0.3.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/Process/cdesc-Process.ri conflicts with the package ruby-process-group-doc-1.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Process/cdesc-Process.ri conflicts with the package ruby-process-pipeline-doc-1.0.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-retriable-doc-3.1.2-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-rr-doc-1.2.1-alt1.1.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/String/cdesc-String.ri conflicts with the package ruby-scrub_rb-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Regexp/cdesc-Regexp.ri conflicts with the package ruby-serverspec-doc-2.41.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Kernel/cdesc-Kernel.ri /usr/share/ri/site/Process/cdesc-Process.ri conflict with the package ruby-sfl-doc-2.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-specinfra-doc-2.77.0-alt1.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/Numeric/cdesc-Numeric.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-temple-doc-0.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-zhexdump-doc-0.0.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-bundler-ext-doc-0.4.0-alt1.1.noarch	File /usr/share/ri/site/Gem/cdesc-Gem.ri conflicts with the package ruby-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Gem/cdesc-Gem.ri conflicts with the package ruby-json-schema-doc-2.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Gem/cdesc-Gem.ri conflicts with the package ruby-oauth-doc-0.5.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-cfpropertylist-doc-3.0.0-alt2.1.noarch	File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-algebrick-doc-0.7.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/Hash/cdesc-Hash.ri conflicts with the package ruby-amazon-ec2-doc-0.9.17-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.; Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Enumerator/cdesc-Enumerator.ri /usr/share/ri/site/Hash/cdesc-Hash.ri conflict with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Hash/cdesc-Hash.ri conflict with the package ruby-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Hash/cdesc-Hash.ri conflict with the package ruby-fission-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-fog-xenserver-doc-0.3.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.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-sfl-doc-2.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-chef-sugar-doc-3.4.0-alt1.1.noarch	File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-algebrick-doc-0.7.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-awesome-print-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-storage-doc-0.15.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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.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-cfpropertylist-doc-3.0.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/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-fission-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-kindlerb-doc-1.2.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-pedump-doc-0.5.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-rr-doc-1.2.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-scrub_rb-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-sfl-doc-2.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-specinfra-doc-2.77.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-zhexdump-doc-0.0.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-cleanroom-doc-1.0.0-alt1.1.noarch	File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-its-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/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-junit-formatter-doc-0.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/RSpec/cdesc-RSpec.ri conflicts with the package ruby-serverspec-doc-2.41.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-coffee-rails-doc-4.2.2-alt1.noarch	File /usr/share/ri/site/ActionView/cdesc-ActionView.ri conflicts with the package ruby-rails-html-sanitizer-doc-1.0.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.; 
warn	ruby-declarative-doc-0.0.10-alt1.1.noarch	File /usr/share/ri/site/Declarative/cdesc-Declarative.ri conflicts with the package ruby-declarative-option-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-declarative-option-doc-0.1.0-alt1.1.noarch	File /usr/share/ri/site/Declarative/cdesc-Declarative.ri conflicts with the package ruby-declarative-doc-0.0.10-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.; 
warn	ruby-draper-doc-3.0.1-alt1.noarch	File /usr/share/ri/site/ActiveModel/cdesc-ActiveModel.ri conflicts with the package ruby-activemodel-serializers-xml-doc-1.0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-em-synchrony-doc-1.0.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/ActionController/cdesc-ActionController.ri conflicts with the package ruby-oauth-doc-0.5.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-pundit-doc-2.0.1-alt1.noarch, for example, /usr/share/ri/site/Rspec/Generators/cdesc-Generators.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/Rails/cdesc-Rails.ri conflicts with the package ruby-rails-html-sanitizer-doc-1.0.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/Rails/cdesc-Rails.ri conflicts with the package ruby-request_store-doc-1.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.; Files /usr/share/ri/site/ActionController/cdesc-ActionController.ri /usr/share/ri/site/Rails/Generators/cdesc-Generators.ri /usr/share/ri/site/Rails/cdesc-Rails.ri conflict with the package ruby-responders-doc-2.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/ActionController/cdesc-ActionController.ri /usr/share/ri/site/Rails/cdesc-Rails.ri conflict with the package ruby-secure-headers-doc-6.0.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/ActionController/cdesc-ActionController.ri /usr/share/ri/site/Rails/cdesc-Rails.ri conflict with the package ruby-securer-headers-doc-6.0.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-sprockets-rails-doc-3.2.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/Rails/cdesc-Rails.ri conflicts with the package ruby-typhoeus-doc-1.3.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.; 
warn	ruby-em-hiredis-doc-0.3.1-alt1.1.noarch	File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-redis-doc-0.3.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/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-socksify-doc-0.3.2-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-em-synchrony-doc-1.0.6-alt1.1.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.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-faraday-doc-0.15.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-oauth-doc-0.5.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-em-http-request-doc-1.1.5-alt1.2.noarch	File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-awesome-print-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-storage-doc-0.15.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-hiredis-doc-0.3.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-redis-doc-0.3.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/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-socksify-doc-0.3.2-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.; 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.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-faraday-doc-0.15.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fission-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-kindlerb-doc-1.2.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/EventMachine/HttpClient/cdesc-HttpClient.ri /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflict with the package ruby-oauth-doc-0.5.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-pedump-doc-0.5.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-scrub_rb-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-specinfra-doc-2.77.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-zhexdump-doc-0.0.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-em-jack-doc-0.1.5-alt1.1.noarch	Files /usr/share/ri/site/EMJack/Connection/cdesc-Connection.ri /usr/share/ri/site/EMJack/Connection/use-i.ri /usr/share/ri/site/EMJack/cdesc-EMJack.ri conflict with the package ruby-em-synchrony-doc-1.0.6-alt1.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.; 
warn	ruby-em-redis-doc-0.3.0-alt1.1.noarch	File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-hiredis-doc-0.3.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-socksify-doc-0.3.2-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-em-synchrony-doc-1.0.6-alt1.1.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-faraday-doc-0.15.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-oauth-doc-0.5.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-em-socksify-doc-0.3.2-alt2.1.noarch	File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-hiredis-doc-0.3.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-redis-doc-0.3.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/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-synchrony-doc-1.0.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/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-faraday-doc-0.15.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-oauth-doc-0.5.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-em-synchrony-doc-1.0.6-alt1.1.noarch	There are file conflicts with the package ruby-activerecord-mysql2-adapter-doc-0.0.3-alt1.1.noarch, for example, /usr/share/ri/site/ActiveRecord/ConnectionAdapters/ConnectionPool/cdesc-ConnectionPool.ri (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/ActiveRecord/VERSION/cdesc-VERSION.ri /usr/share/ri/site/ActiveRecord/cdesc-ActiveRecord.ri conflict with the package ruby-activerecord-session_store-doc-1.1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-awesome-print-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-draper-doc-3.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-em-hiredis-doc-0.3.1-alt1.1.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.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/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.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-redis-doc-0.3.0-alt1.1.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-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/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-faraday-doc-0.15.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/ActiveRecord/VERSION/cdesc-VERSION.ri /usr/share/ri/site/ActiveRecord/cdesc-ActiveRecord.ri conflict with the package ruby-friendly_id-doc-5.2.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/Kernel/cdesc-Kernel.ri conflicts with the package ruby-java-doc-0.0.2-alt2.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/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-memoist-doc-0.16.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/Mongo/cdesc-Mongo.ri conflicts with the package ruby-mongo-doc-2.6.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/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-oauth-doc-0.5.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-polyglot-doc-0.3.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/Rails/cdesc-Rails.ri conflicts with the package ruby-rails-html-sanitizer-doc-1.0.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/Memcached/cdesc-Memcached.ri conflicts with the package ruby-remcached-doc-0.4.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-request_store-doc-1.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-responders-doc-2.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-retriable-doc-3.1.2-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/ActiveRecord/cdesc-ActiveRecord.ri conflicts with the package ruby-scoped-search-doc-4.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/Rails/cdesc-Rails.ri conflicts with the package ruby-secure-headers-doc-6.0.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-securer-headers-doc-6.0.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-sfl-doc-2.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-sprockets-rails-doc-3.2.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/Rails/cdesc-Rails.ri conflicts with the package ruby-typhoeus-doc-1.3.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.; 
warn	ruby-excon-doc-0.62.0-alt1.1.noarch	File /usr/share/ri/site/IO/cdesc-IO.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/URI/cdesc-URI.ri conflicts with the package ruby-globalid-doc-0.4.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/IO/cdesc-IO.ri conflicts with the package ruby-io-like-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/URI/cdesc-URI.ri conflicts with the package ruby-proxifier-doc-1.0.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-extlib-doc-0.9.16-alt1.1.noarch	File /usr/share/ri/site/Time/cdesc-Time.ri conflicts with the package gem-vpim-doc-13.11.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/Array/cdesc-Array.ri conflicts with the package ruby-algebrick-doc-0.7.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/Hash/cdesc-Hash.ri conflicts with the package ruby-amazon-ec2-doc-0.9.17-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Time/cdesc-Time.ri conflicts with the package ruby-archive-zip-doc-0.11.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-awesome-print-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-storage-doc-0.15.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-backports-doc-3.7.0-alt1.1.noarch, for example, /usr/share/ri/site/Array/cdesc-Array.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/Gem/cdesc-Gem.ri conflicts with the package ruby-bundler-ext-doc-0.4.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Hash/cdesc-Hash.ri conflict with the package ruby-cfpropertylist-doc-3.0.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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-chef-sugar-doc-3.4.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-fission-doc-0.5.0-alt1.1.noarch, for example, /usr/share/ri/site/Array/cdesc-Array.ri (12 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/Hash/cdesc-Hash.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-fog-xenserver-doc-0.3.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/Module/cdesc-Module.ri conflicts with the package ruby-java-doc-0.0.2-alt2.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.; Files /usr/share/ri/site/Gem/Specification/cdesc-Specification.ri /usr/share/ri/site/Gem/cdesc-Gem.ri conflict with the package ruby-json-schema-doc-2.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-kindlerb-doc-1.2.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package ruby-mongo-doc-2.6.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/Gem/cdesc-Gem.ri conflicts with the package ruby-oauth-doc-0.5.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/NilClass/cdesc-NilClass.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-pedump-doc-0.5.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-rr-doc-1.2.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-scrub_rb-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-sfl-doc-2.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Class/cdesc-Class.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-specinfra-doc-2.77.0-alt1.noarch. Moreover, the packages have 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-sucker-punch-doc-2.1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Numeric/cdesc-Numeric.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-temple-doc-0.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-zhexdump-doc-0.0.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-faraday-doc-0.15.2-alt1.1.noarch	File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-hiredis-doc-0.3.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-redis-doc-0.3.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/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-socksify-doc-0.3.2-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/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-synchrony-doc-1.0.6-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/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_middleware-doc-0.12.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-oauth-doc-0.5.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-typhoeus-doc-1.3.0-alt1.1.noarch, for example, /usr/share/ri/site/Faraday/Adapter/Typhoeus/call-i.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.; 
warn	ruby-faraday_middleware-doc-0.12.2-alt1.1.noarch	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.15.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Faraday/cdesc-Faraday.ri conflicts with the package ruby-typhoeus-doc-1.3.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.; 
warn	ruby-ffi-libarchive-doc-0.4.2-alt1.noarch	File /usr/share/ri/site/Archive/cdesc-Archive.ri conflicts with the package ruby-archive-zip-doc-0.11.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Archive/cdesc-Archive.ri conflicts with the package ruby-minitar-doc-0.6.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-fission-doc-0.5.0-alt1.1.noarch	File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-algebrick-doc-0.7.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/Hash/cdesc-Hash.ri conflicts with the package ruby-amazon-ec2-doc-0.9.17-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-awesome-print-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-storage-doc-0.15.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-backports-doc-3.7.0-alt1.1.noarch, for example, /usr/share/ri/site/Array/cdesc-Array.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/Array/cdesc-Array.ri /usr/share/ri/site/Hash/cdesc-Hash.ri conflict with the package ruby-cfpropertylist-doc-3.0.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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-chef-sugar-doc-3.4.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-extlib-doc-0.9.16-alt1.1.noarch, for example, /usr/share/ri/site/Array/cdesc-Array.ri (12 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/Hash/cdesc-Hash.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-fog-xenserver-doc-0.3.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-kindlerb-doc-1.2.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/File/cdesc-File.ri conflicts with the package ruby-net-ping-doc-2.0.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/File/cdesc-File.ri /usr/share/ri/site/NilClass/cdesc-NilClass.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-pedump-doc-0.5.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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.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-scrub_rb-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-sfl-doc-2.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Class/cdesc-Class.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-specinfra-doc-2.77.0-alt1.noarch. Moreover, the packages have 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-sucker-punch-doc-2.1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-zhexdump-doc-0.0.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-fog-aliyun-doc-0.3.2-alt1.1.noarch	Files /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-atmos-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-dynect-doc-0.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-ecloud-doc-0.3.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/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-internet-archive-doc-0.0.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-json-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.; Files /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-local-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-powerdns-doc-0.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.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-rackspace-doc-0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-radosgw-doc-0.0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-riakcs-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-sakuracloud-doc-1.7.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/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-serverlove-doc-0.1.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-storm_on_demand-doc-0.1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-terremark-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-vmfusion-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-voxel-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-xenserver-doc-0.3.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-xml-doc-0.1.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-fog-atmos-doc-0.1.0-alt1.1.noarch	Files /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-aliyun-doc-0.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-dynect-doc-0.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-ecloud-doc-0.3.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/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-internet-archive-doc-0.0.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-json-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.; Files /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-local-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-powerdns-doc-0.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.; Files /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-rackspace-doc-0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-radosgw-doc-0.0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-riakcs-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-sakuracloud-doc-1.7.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-serverlove-doc-0.1.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-storm_on_demand-doc-0.1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-terremark-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-vmfusion-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-voxel-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-xenserver-doc-0.3.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-xml-doc-0.1.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-fog-dynect-doc-0.0.3-alt1.noarch	File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-aliyun-doc-0.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-atmos-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-ecloud-doc-0.3.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-internet-archive-doc-0.0.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-json-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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-local-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/DNS/cdesc-DNS.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-powerdns-doc-0.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.; Files /usr/share/ri/site/Fog/DNS/cdesc-DNS.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-rackspace-doc-0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-radosgw-doc-0.0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-riakcs-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/DNS/cdesc-DNS.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-sakuracloud-doc-1.7.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-serverlove-doc-0.1.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/DNS/cdesc-DNS.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/DNS/cdesc-DNS.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-storm_on_demand-doc-0.1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-terremark-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-vmfusion-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-voxel-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-xenserver-doc-0.3.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-xml-doc-0.1.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-fog-ecloud-doc-0.3.0-alt1.1.noarch	File /usr/share/ri/site/IPAddr/cdesc-IPAddr.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/IPAddr/cdesc-IPAddr.ri conflicts with the package ruby-azure-storage-doc-0.15.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-aliyun-doc-0.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-atmos-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-dynect-doc-0.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-internet-archive-doc-0.0.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-json-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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-local-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-powerdns-doc-0.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.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-rackspace-doc-0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-radosgw-doc-0.0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-riakcs-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-sakuracloud-doc-1.7.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/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-serverlove-doc-0.1.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-storm_on_demand-doc-0.1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-terremark-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-vmfusion-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-voxel-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-xenserver-doc-0.3.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-xml-doc-0.1.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-fog-internet-archive-doc-0.0.1-alt1.1.noarch	Files /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-aliyun-doc-0.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-atmos-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-dynect-doc-0.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-ecloud-doc-0.3.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-json-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.; Files /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-local-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-powerdns-doc-0.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.; Files /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-rackspace-doc-0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-radosgw-doc-0.0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-riakcs-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-sakuracloud-doc-1.7.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-serverlove-doc-0.1.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-storm_on_demand-doc-0.1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Parsers/cdesc-Parsers.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-terremark-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-vmfusion-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Parsers/cdesc-Parsers.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-voxel-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Parsers/cdesc-Parsers.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-xenserver-doc-0.3.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/Fog/Parsers/cdesc-Parsers.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-xml-doc-0.1.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-fog-json-doc-1.2.0-alt1.1.noarch	File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-aliyun-doc-0.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-atmos-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-dynect-doc-0.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-ecloud-doc-0.3.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-internet-archive-doc-0.0.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-local-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-powerdns-doc-0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-rackspace-doc-0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-radosgw-doc-0.0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-riakcs-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-sakuracloud-doc-1.7.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-serverlove-doc-0.1.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-storm_on_demand-doc-0.1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-terremark-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-vmfusion-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-voxel-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-xenserver-doc-0.3.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-xml-doc-0.1.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-fog-local-doc-0.5.0-alt1.1.noarch	Files /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-aliyun-doc-0.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-atmos-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-dynect-doc-0.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-ecloud-doc-0.3.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/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-internet-archive-doc-0.0.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-json-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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-powerdns-doc-0.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.; Files /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-rackspace-doc-0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-radosgw-doc-0.0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-riakcs-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-sakuracloud-doc-1.7.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-serverlove-doc-0.1.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-storm_on_demand-doc-0.1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-terremark-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-vmfusion-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-voxel-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-xenserver-doc-0.3.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-xml-doc-0.1.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-fog-powerdns-doc-0.2.0-alt1.1.noarch	File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-aliyun-doc-0.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-atmos-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/DNS/cdesc-DNS.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-dynect-doc-0.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-ecloud-doc-0.3.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-internet-archive-doc-0.0.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-json-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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-local-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/DNS/cdesc-DNS.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-rackspace-doc-0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-radosgw-doc-0.0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-riakcs-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/DNS/cdesc-DNS.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-sakuracloud-doc-1.7.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-serverlove-doc-0.1.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/DNS/cdesc-DNS.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/DNS/cdesc-DNS.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-storm_on_demand-doc-0.1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-terremark-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-vmfusion-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-voxel-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-xenserver-doc-0.3.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-xml-doc-0.1.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-fog-rackspace-doc-0.1.5-alt1.1.noarch	Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-aliyun-doc-0.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-atmos-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/DNS/cdesc-DNS.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-dynect-doc-0.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-ecloud-doc-0.3.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/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-internet-archive-doc-0.0.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-json-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.; Files /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-local-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/DNS/cdesc-DNS.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-powerdns-doc-0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-radosgw-doc-0.0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-riakcs-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/DNS/cdesc-DNS.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-sakuracloud-doc-1.7.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/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-serverlove-doc-0.1.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch, for example, /usr/share/ri/site/Fog/Compute/cdesc-Compute.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.; There are file conflicts with the package ruby-fog-storm_on_demand-doc-0.1.1-alt1.1.noarch, for example, /usr/share/ri/site/Fog/Compute/cdesc-Compute.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/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-terremark-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-vmfusion-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-voxel-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-xenserver-doc-0.3.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-xml-doc-0.1.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-fog-radosgw-doc-0.0.5-alt1.noarch	File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-aliyun-doc-0.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-atmos-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-dynect-doc-0.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-ecloud-doc-0.3.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-internet-archive-doc-0.0.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-json-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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-local-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-powerdns-doc-0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-rackspace-doc-0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-riakcs-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-sakuracloud-doc-1.7.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-serverlove-doc-0.1.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-storm_on_demand-doc-0.1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-terremark-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-vmfusion-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-voxel-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-xenserver-doc-0.3.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-xml-doc-0.1.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-fog-riakcs-doc-0.1.0-alt1.1.noarch	File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-aliyun-doc-0.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-atmos-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-dynect-doc-0.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-ecloud-doc-0.3.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-internet-archive-doc-0.0.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-json-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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-local-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-powerdns-doc-0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-rackspace-doc-0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-radosgw-doc-0.0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-sakuracloud-doc-1.7.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-serverlove-doc-0.1.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-storm_on_demand-doc-0.1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-terremark-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-vmfusion-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-voxel-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-xenserver-doc-0.3.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-xml-doc-0.1.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-fog-sakuracloud-doc-1.7.5-alt1.1.noarch	Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-aliyun-doc-0.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-atmos-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/DNS/cdesc-DNS.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-dynect-doc-0.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-ecloud-doc-0.3.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-internet-archive-doc-0.0.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-json-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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-local-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/DNS/cdesc-DNS.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-powerdns-doc-0.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.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/DNS/cdesc-DNS.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-rackspace-doc-0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-radosgw-doc-0.0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-riakcs-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-serverlove-doc-0.1.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch, for example, /usr/share/ri/site/Fog/Compute/cdesc-Compute.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.; There are file conflicts with the package ruby-fog-storm_on_demand-doc-0.1.1-alt1.1.noarch, for example, /usr/share/ri/site/Fog/Compute/cdesc-Compute.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/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-terremark-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-vmfusion-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-voxel-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-xenserver-doc-0.3.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-xml-doc-0.1.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-fog-serverlove-doc-0.1.2-alt1.1.noarch	Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-aliyun-doc-0.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-atmos-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-dynect-doc-0.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-ecloud-doc-0.3.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-internet-archive-doc-0.0.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-json-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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-local-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-powerdns-doc-0.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.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-rackspace-doc-0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-radosgw-doc-0.0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-riakcs-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-sakuracloud-doc-1.7.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/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-storm_on_demand-doc-0.1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-terremark-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-vmfusion-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-voxel-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-xenserver-doc-0.3.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-xml-doc-0.1.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch	File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-amazon-ec2-doc-0.9.17-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-awesome-print-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-storage-doc-0.15.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Hash/cdesc-Hash.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-cfpropertylist-doc-3.0.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Hash/cdesc-Hash.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Hash/cdesc-Hash.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-fission-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-aliyun-doc-0.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-atmos-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/DNS/cdesc-DNS.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-dynect-doc-0.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-ecloud-doc-0.3.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/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-internet-archive-doc-0.0.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-json-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.; Files /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-local-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/DNS/cdesc-DNS.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-powerdns-doc-0.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.; There are file conflicts with the package ruby-fog-rackspace-doc-0.1.5-alt1.1.noarch, for example, /usr/share/ri/site/Fog/Compute/cdesc-Compute.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-radosgw-doc-0.0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-riakcs-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-fog-sakuracloud-doc-1.7.5-alt1.1.noarch, for example, /usr/share/ri/site/Fog/Compute/cdesc-Compute.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/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-serverlove-doc-0.1.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-fog-storm_on_demand-doc-0.1.1-alt1.1.noarch, for example, /usr/share/ri/site/Fog/Account/cdesc-Account.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/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-terremark-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-vmfusion-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-voxel-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri /usr/share/ri/site/Hash/cdesc-Hash.ri conflict with the package ruby-fog-xenserver-doc-0.3.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-xml-doc-0.1.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-kindlerb-doc-1.2.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-pedump-doc-0.5.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-rr-doc-1.2.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-scrub_rb-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-specinfra-doc-2.77.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-zhexdump-doc-0.0.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-fog-storm_on_demand-doc-0.1.1-alt1.1.noarch	Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-aliyun-doc-0.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-atmos-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/DNS/cdesc-DNS.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-dynect-doc-0.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-ecloud-doc-0.3.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/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-internet-archive-doc-0.0.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-json-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.; Files /usr/share/ri/site/Fog/Storage/cdesc-Storage.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-local-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/DNS/cdesc-DNS.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-powerdns-doc-0.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.; There are file conflicts with the package ruby-fog-rackspace-doc-0.1.5-alt1.1.noarch, for example, /usr/share/ri/site/Fog/Compute/cdesc-Compute.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-radosgw-doc-0.0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-riakcs-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-fog-sakuracloud-doc-1.7.5-alt1.1.noarch, for example, /usr/share/ri/site/Fog/Compute/cdesc-Compute.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/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-serverlove-doc-0.1.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch, for example, /usr/share/ri/site/Fog/Account/cdesc-Account.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/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-terremark-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-vmfusion-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-voxel-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-xenserver-doc-0.3.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-xml-doc-0.1.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-fog-terremark-doc-0.1.0-alt1.1.noarch	Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-aliyun-doc-0.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-atmos-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-dynect-doc-0.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-ecloud-doc-0.3.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/Fog/Parsers/cdesc-Parsers.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-internet-archive-doc-0.0.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-json-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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-local-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-powerdns-doc-0.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.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-rackspace-doc-0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-radosgw-doc-0.0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-riakcs-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-sakuracloud-doc-1.7.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/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-serverlove-doc-0.1.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-storm_on_demand-doc-0.1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-vmfusion-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/Parsers/cdesc-Parsers.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-voxel-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/Parsers/cdesc-Parsers.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-xenserver-doc-0.3.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/Fog/Parsers/cdesc-Parsers.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-xml-doc-0.1.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-fog-vmfusion-doc-0.1.0-alt1.1.noarch	Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-aliyun-doc-0.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-atmos-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-dynect-doc-0.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-ecloud-doc-0.3.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-internet-archive-doc-0.0.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-json-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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-local-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-powerdns-doc-0.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.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-rackspace-doc-0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-radosgw-doc-0.0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-riakcs-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-sakuracloud-doc-1.7.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/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-serverlove-doc-0.1.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-storm_on_demand-doc-0.1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-terremark-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-voxel-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-xenserver-doc-0.3.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-xml-doc-0.1.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-fog-voxel-doc-0.1.0-alt1.1.noarch	Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-aliyun-doc-0.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-atmos-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-dynect-doc-0.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-ecloud-doc-0.3.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/Fog/Parsers/cdesc-Parsers.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-internet-archive-doc-0.0.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-json-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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-local-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-powerdns-doc-0.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.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-rackspace-doc-0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-radosgw-doc-0.0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-riakcs-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-sakuracloud-doc-1.7.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/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-serverlove-doc-0.1.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-storm_on_demand-doc-0.1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/Parsers/cdesc-Parsers.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-terremark-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-vmfusion-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/Parsers/cdesc-Parsers.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-xenserver-doc-0.3.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/Fog/Parsers/cdesc-Parsers.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-xml-doc-0.1.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-fog-xenserver-doc-0.3.0-alt1.1.noarch	File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-amazon-ec2-doc-0.9.17-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.; Files /usr/share/ri/site/Hash/cdesc-Hash.ri /usr/share/ri/site/Hash/symbolize_keys%21-i.ri conflict with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-cfpropertylist-doc-3.0.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-fission-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-aliyun-doc-0.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-atmos-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-dynect-doc-0.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-ecloud-doc-0.3.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/Fog/Parsers/cdesc-Parsers.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-internet-archive-doc-0.0.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-json-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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-local-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-powerdns-doc-0.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.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-rackspace-doc-0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-radosgw-doc-0.0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-riakcs-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-sakuracloud-doc-1.7.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/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-serverlove-doc-0.1.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri /usr/share/ri/site/Hash/cdesc-Hash.ri conflict with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-storm_on_demand-doc-0.1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/Parsers/cdesc-Parsers.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-terremark-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-vmfusion-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Compute/cdesc-Compute.ri /usr/share/ri/site/Fog/Parsers/cdesc-Parsers.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-voxel-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Parsers/cdesc-Parsers.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-xml-doc-0.1.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-rr-doc-1.2.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-fog-xml-doc-0.1.3-alt1.1.noarch	File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-aliyun-doc-0.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-atmos-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-dynect-doc-0.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-ecloud-doc-0.3.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/Fog/Parsers/cdesc-Parsers.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-internet-archive-doc-0.0.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-json-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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-local-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-powerdns-doc-0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-rackspace-doc-0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-radosgw-doc-0.0.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-riakcs-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-sakuracloud-doc-1.7.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/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-serverlove-doc-0.1.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-storm_on_demand-doc-0.1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Parsers/cdesc-Parsers.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-terremark-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Fog/cdesc-Fog.ri conflicts with the package ruby-fog-vmfusion-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Parsers/cdesc-Parsers.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-voxel-doc-0.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Fog/Parsers/cdesc-Parsers.ri /usr/share/ri/site/Fog/cdesc-Fog.ri conflict with the package ruby-fog-xenserver-doc-0.3.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.; 
warn	ruby-friendly_id-doc-5.2.4-alt1.noarch	File /usr/share/ri/site/ActiveRecord/cdesc-ActiveRecord.ri conflicts with the package ruby-activemodel-serializers-xml-doc-1.0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/ActiveRecord/cdesc-ActiveRecord.ri conflicts with the package ruby-activerecord-mysql2-adapter-doc-0.0.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/ActiveRecord/VERSION/cdesc-VERSION.ri /usr/share/ri/site/ActiveRecord/cdesc-ActiveRecord.ri conflict with the package ruby-activerecord-session_store-doc-1.1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/ActiveRecord/VERSION/cdesc-VERSION.ri /usr/share/ri/site/ActiveRecord/cdesc-ActiveRecord.ri conflict with the package ruby-em-synchrony-doc-1.0.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/ActiveRecord/cdesc-ActiveRecord.ri conflicts with the package ruby-scoped-search-doc-4.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.; 
warn	ruby-globalid-doc-0.4.1-alt1.1.noarch	File /usr/share/ri/site/URI/cdesc-URI.ri conflicts with the package ruby-excon-doc-0.62.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/URI/cdesc-URI.ri conflicts with the package ruby-proxifier-doc-1.0.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-hashie-doc-3.6.0-alt1.noarch	Files /usr/share/ri/site/Hashie/Mash/cdesc-Mash.ri /usr/share/ri/site/Hashie/cdesc-Hashie.ri conflict with the package ruby-rash-doc-0.4.7-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.; 
warn	ruby-hirb-doc-0.7.3-alt1.1.noarch	File /usr/share/ri/site/Hirb/cdesc-Hirb.ri conflicts with the package ruby-hirb-unicode-steakknife-doc-0.0.8-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.; 
warn	ruby-hirb-unicode-steakknife-doc-0.0.8-alt1.1.noarch	File /usr/share/ri/site/Hirb/cdesc-Hirb.ri conflicts with the package ruby-hirb-doc-0.7.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-io-like-doc-0.3.0-alt1.noarch	File /usr/share/ri/site/IO/cdesc-IO.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/IO/cdesc-IO.ri conflicts with the package ruby-excon-doc-0.62.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-java-doc-0.0.2-alt2.S1.noarch	File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-awesome-print-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Kernel/cdesc-Kernel.ri /usr/share/ri/site/Module/cdesc-Module.ri conflict with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-em-synchrony-doc-1.0.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/Module/cdesc-Module.ri conflicts with the package ruby-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-memoist-doc-0.16.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/Kernel/cdesc-Kernel.ri conflicts with the package ruby-polyglot-doc-0.3.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/Kernel/cdesc-Kernel.ri conflicts with the package ruby-retriable-doc-3.1.2-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-sfl-doc-2.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-json-schema-doc-2.8.0-alt1.1.noarch	File /usr/share/ri/site/Gem/cdesc-Gem.ri conflicts with the package ruby-bundler-ext-doc-0.4.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Gem/Specification/cdesc-Specification.ri /usr/share/ri/site/Gem/cdesc-Gem.ri conflict with the package ruby-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Gem/cdesc-Gem.ri conflicts with the package ruby-oauth-doc-0.5.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-kindlerb-doc-1.2.0-alt1.noarch	File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-awesome-print-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-storage-doc-0.15.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fission-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-pedump-doc-0.5.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-scrub_rb-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-specinfra-doc-2.77.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-zhexdump-doc-0.0.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-makeconf-doc-0.3.0-alt2.svn20130509.noarch	File /usr/share/ri/site/Test/cdesc-Test.ri conflicts with the package ruby-structured-warnings-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.; 
warn	ruby-memoist-doc-0.16.0-alt1.1.noarch	File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-awesome-print-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Kernel/cdesc-Kernel.ri /usr/share/ri/site/Kernel/singleton_class-i.ri conflict with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-em-synchrony-doc-1.0.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/Kernel/cdesc-Kernel.ri conflicts with the package ruby-java-doc-0.0.2-alt2.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/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-polyglot-doc-0.3.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/Kernel/cdesc-Kernel.ri conflicts with the package ruby-retriable-doc-3.1.2-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-sfl-doc-2.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-method_source-doc-0.9.0-alt1.noarch	Files /usr/share/ri/site/Method/cdesc-Method.ri /usr/share/ri/site/UnboundMethod/cdesc-UnboundMethod.ri conflict with the package ruby-awesome-print-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Method/cdesc-Method.ri /usr/share/ri/site/Proc/cdesc-Proc.ri /usr/share/ri/site/UnboundMethod/cdesc-UnboundMethod.ri conflict with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-minitar-0.6.1-alt1.noarch	File /usr/lib/ruby/site_ruby/archive/tar/minitar.rb conflicts with the package ruby-archive-tar-minitar-0.5.2-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.; 
warn	ruby-minitar-doc-0.6.1-alt1.noarch	There are file conflicts with the package ruby-archive-tar-minitar-doc-0.5.2-alt1.2.noarch, for example, /usr/share/ri/site/Archive/Tar/Minitar/Input/cdesc-Input.ri (54 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/Archive/cdesc-Archive.ri conflicts with the package ruby-archive-zip-doc-0.11.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Archive/cdesc-Archive.ri conflicts with the package ruby-ffi-libarchive-doc-0.4.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-mixlib-archive-doc-0.4.18-alt1.noarch	File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-authentication-doc-2.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/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-config-doc-2.2.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/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-log-doc-2.0.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/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-shellout-doc-2.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.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.; 
warn	ruby-mixlib-authentication-doc-2.1.4-alt1.noarch	File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-archive-doc-0.4.18-alt1.noarch. Moreover, the packages have 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.2.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/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-log-doc-2.0.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/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-shellout-doc-2.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.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.; 
warn	ruby-mixlib-config-doc-2.2.14-alt1.noarch	File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-archive-doc-0.4.18-alt1.noarch. Moreover, the packages have 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-authentication-doc-2.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/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-log-doc-2.0.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/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-shellout-doc-2.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.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.; 
warn	ruby-mixlib-log-doc-2.0.7-alt1.noarch	File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-archive-doc-0.4.18-alt1.noarch. Moreover, the packages have 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-authentication-doc-2.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/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-config-doc-2.2.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/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-shellout-doc-2.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.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.; 
warn	ruby-mixlib-shellout-doc-2.4.0-alt1.noarch	File /usr/share/ri/site/Process/cdesc-Process.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-archive-doc-0.4.18-alt1.noarch. Moreover, the packages have 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-authentication-doc-2.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/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-config-doc-2.2.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/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-log-doc-2.0.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/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-versioning-doc-1.2.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/Process/cdesc-Process.ri conflicts with the package ruby-process-group-doc-1.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Process/cdesc-Process.ri conflicts with the package ruby-process-pipeline-doc-1.0.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Process/cdesc-Process.ri conflicts with the package ruby-sfl-doc-2.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-mixlib-versioning-doc-1.2.6-alt1.noarch	File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-archive-doc-0.4.18-alt1.noarch. Moreover, the packages have 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-authentication-doc-2.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/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-config-doc-2.2.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/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-log-doc-2.0.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/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-shellout-doc-2.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.; 
warn	ruby-mongo-doc-2.6.2-alt1.noarch	File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Mongo/cdesc-Mongo.ri conflicts with the package ruby-em-synchrony-doc-1.0.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/Symbol/cdesc-Symbol.ri conflicts with the package ruby-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-multipart-post-doc-2.0.0-alt1.1.noarch	File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-dhcp-doc-1.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-ping-doc-2.0.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/Net/cdesc-Net.ri conflicts with the package ruby-net-telnet-doc-0.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/Net/cdesc-Net.ri conflicts with the package ruby-oauth-doc-0.5.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-net-dhcp-doc-1.3.2-alt1.1.noarch	File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-multipart-post-doc-2.0.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-ping-doc-2.0.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/Net/cdesc-Net.ri conflicts with the package ruby-net-telnet-doc-0.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/Net/cdesc-Net.ri conflicts with the package ruby-oauth-doc-0.5.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-net-ping-doc-2.0.5-alt1.noarch	File /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri conflicts with the package ruby-amqp-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/File/cdesc-File.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/File/cdesc-File.ri conflicts with the package ruby-fission-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-multipart-post-doc-2.0.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-dhcp-doc-1.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-telnet-doc-0.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/Net/cdesc-Net.ri conflicts with the package ruby-oauth-doc-0.5.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/File/cdesc-File.ri conflicts with the package ruby-pedump-doc-0.5.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri conflicts with the package ruby-spoon-doc-0.0.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-sys-proctable-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.; 
warn	ruby-net-telnet-doc-0.2.0-alt1.noarch	File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-multipart-post-doc-2.0.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-dhcp-doc-1.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-ping-doc-2.0.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/Net/cdesc-Net.ri conflicts with the package ruby-oauth-doc-0.5.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-oauth-doc-0.5.4-alt1.noarch	Files /usr/share/ri/site/cache.ri /usr/share/ri/site/created.rid conflict with the package gem-olddoc-doc-1.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/ActionDispatch/cdesc-ActionDispatch.ri conflicts with the package ruby-activerecord-session_store-doc-1.1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/ActiveSupport/cdesc-ActiveSupport.ri conflicts with the package ruby-awesome-print-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Gem/cdesc-Gem.ri conflicts with the package ruby-bundler-ext-doc-0.4.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/ActionController/cdesc-ActionController.ri conflicts with the package ruby-draper-doc-3.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/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-hiredis-doc-0.3.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/EventMachine/HttpClient/cdesc-HttpClient.ri /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflict with the package ruby-em-http-request-doc-1.1.5-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-redis-doc-0.3.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/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-socksify-doc-0.3.2-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/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-synchrony-doc-1.0.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/Gem/cdesc-Gem.ri conflicts with the package ruby-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-faraday-doc-0.15.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Gem/cdesc-Gem.ri conflicts with the package ruby-json-schema-doc-2.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-multipart-post-doc-2.0.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-dhcp-doc-1.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-ping-doc-2.0.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/Net/cdesc-Net.ri conflicts with the package ruby-net-telnet-doc-0.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.; Files /usr/share/ri/site/cache.ri /usr/share/ri/site/created.rid conflict with the package ruby-parseconfig-doc-0.5-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/cache.ri /usr/share/ri/site/created.rid conflict with the package ruby-rails-i18n-doc-5.1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/ActionController/cdesc-ActionController.ri conflicts with the package ruby-responders-doc-2.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/ActionController/Base/cdesc-Base.ri /usr/share/ri/site/ActionController/cdesc-ActionController.ri conflict with the package ruby-secure-headers-doc-6.0.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/ActionController/Base/cdesc-Base.ri /usr/share/ri/site/ActionController/cdesc-ActionController.ri conflict with the package ruby-securer-headers-doc-6.0.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-omniauth-doc-1.9.0-alt1.noarch	Files /usr/share/ri/site/OmniAuth/Strategies/cdesc-Strategies.ri /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflict with the package ruby-omniauth-github-doc-1.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/OmniAuth/Strategies/cdesc-Strategies.ri /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflict with the package ruby-omniauth-gitlab-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.; Files /usr/share/ri/site/OmniAuth/Strategies/cdesc-Strategies.ri /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflict with the package ruby-omniauth-google-oauth2-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/OmniAuth/Strategies/cdesc-Strategies.ri /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflict with the package ruby-omniauth-oauth2-doc-1.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/OmniAuth/Strategies/cdesc-Strategies.ri /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflict with the package ruby-omniauth-openid-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.; 
warn	ruby-omniauth-github-doc-1.3.0-alt1.noarch	Files /usr/share/ri/site/OmniAuth/Strategies/cdesc-Strategies.ri /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflict with the package ruby-omniauth-doc-1.9.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflicts with the package ruby-omniauth-gitlab-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.; Files /usr/share/ri/site/OmniAuth/Strategies/cdesc-Strategies.ri /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflict with the package ruby-omniauth-google-oauth2-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/OmniAuth/Strategies/cdesc-Strategies.ri /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflict with the package ruby-omniauth-openid-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.; 
warn	ruby-omniauth-gitlab-doc-2.0.0-alt1.noarch	Files /usr/share/ri/site/OmniAuth/Strategies/cdesc-Strategies.ri /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflict with the package ruby-omniauth-doc-1.9.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflicts with the package ruby-omniauth-github-doc-1.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/OmniAuth/Strategies/cdesc-Strategies.ri /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflict with the package ruby-omniauth-google-oauth2-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/OmniAuth/cdesc-OmniAuth.ri conflicts with the package ruby-omniauth-oauth2-doc-1.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/OmniAuth/Strategies/cdesc-Strategies.ri /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflict with the package ruby-omniauth-openid-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.; 
warn	ruby-omniauth-google-oauth2-doc-0.6.0-alt1.noarch	Files /usr/share/ri/site/OmniAuth/Strategies/cdesc-Strategies.ri /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflict with the package ruby-omniauth-doc-1.9.0-alt1.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/OmniAuth/Strategies/cdesc-Strategies.ri /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflict with the package ruby-omniauth-github-doc-1.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/OmniAuth/Strategies/cdesc-Strategies.ri /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflict with the package ruby-omniauth-gitlab-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.; Files /usr/share/ri/site/OmniAuth/Strategies/cdesc-Strategies.ri /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflict with the package ruby-omniauth-oauth2-doc-1.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/OmniAuth/Strategies/cdesc-Strategies.ri /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflict with the package ruby-omniauth-openid-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.; 
warn	ruby-omniauth-oauth2-doc-1.6.0-alt1.noarch	Files /usr/share/ri/site/OmniAuth/Strategies/cdesc-Strategies.ri /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflict with the package ruby-omniauth-doc-1.9.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflicts with the package ruby-omniauth-gitlab-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.; Files /usr/share/ri/site/OmniAuth/Strategies/cdesc-Strategies.ri /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflict with the package ruby-omniauth-google-oauth2-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/OmniAuth/Strategies/cdesc-Strategies.ri /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflict with the package ruby-omniauth-openid-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.; 
warn	ruby-omniauth-openid-doc-2.0.0-alt1.noarch	Files /usr/share/ri/site/OmniAuth/Strategies/cdesc-Strategies.ri /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflict with the package ruby-omniauth-doc-1.9.0-alt1.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/OmniAuth/Strategies/cdesc-Strategies.ri /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflict with the package ruby-omniauth-github-doc-1.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/OmniAuth/Strategies/cdesc-Strategies.ri /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflict with the package ruby-omniauth-gitlab-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.; Files /usr/share/ri/site/OmniAuth/Strategies/cdesc-Strategies.ri /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflict with the package ruby-omniauth-google-oauth2-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/OmniAuth/Strategies/cdesc-Strategies.ri /usr/share/ri/site/OmniAuth/cdesc-OmniAuth.ri conflict with the package ruby-omniauth-oauth2-doc-1.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.; 
warn	ruby-parseconfig-doc-0.5-alt1.1.noarch	Files /usr/share/ri/site/cache.ri /usr/share/ri/site/created.rid conflict with the package gem-olddoc-doc-1.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/cache.ri /usr/share/ri/site/created.rid conflict with the package ruby-oauth-doc-0.5.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/cache.ri /usr/share/ri/site/created.rid conflict with the package ruby-rails-i18n-doc-5.1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-pedump-0.5.2-alt1.1.noarch	File /usr/bin/pedump conflicts with the package mono-devel-6.12.0.206-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.; 
warn	ruby-pedump-doc-0.5.2-alt1.1.noarch	File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-awesome-print-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-storage-doc-0.15.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-backports-doc-3.7.0-alt1.1.noarch, for example, /usr/share/ri/site/File/cdesc-File.ri (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/NilClass/cdesc-NilClass.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/File/cdesc-File.ri /usr/share/ri/site/NilClass/cdesc-NilClass.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-fission-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-kindlerb-doc-1.2.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/File/cdesc-File.ri conflicts with the package ruby-net-ping-doc-2.0.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-scrub_rb-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Logger/cdesc-Logger.ri conflicts with the package ruby-serverengine-doc-2.0.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/String/cdesc-String.ri conflicts with the package ruby-specinfra-doc-2.77.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Logger/cdesc-Logger.ri conflicts with the package ruby-syslog-logger-doc-1.6.8-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-temple-doc-0.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-zhexdump-doc-0.0.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-polyglot-doc-0.3.5-alt1.1.noarch	File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-awesome-print-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-em-synchrony-doc-1.0.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/Kernel/cdesc-Kernel.ri conflicts with the package ruby-java-doc-0.0.2-alt2.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/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-memoist-doc-0.16.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/Kernel/cdesc-Kernel.ri conflicts with the package ruby-retriable-doc-3.1.2-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-sfl-doc-2.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-process-group-doc-1.1.0-alt1.1.noarch	File /usr/share/ri/site/Process/cdesc-Process.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Process/cdesc-Process.ri conflicts with the package ruby-mixlib-shellout-doc-2.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/Process/cdesc-Process.ri conflicts with the package ruby-process-pipeline-doc-1.0.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Process/cdesc-Process.ri conflicts with the package ruby-sfl-doc-2.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-process-pipeline-doc-1.0.1-alt1.1.noarch	File /usr/share/ri/site/Process/cdesc-Process.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Process/cdesc-Process.ri conflicts with the package ruby-mixlib-shellout-doc-2.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/Process/cdesc-Process.ri conflicts with the package ruby-process-group-doc-1.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Process/cdesc-Process.ri conflicts with the package ruby-sfl-doc-2.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-proxifier-doc-1.0.3-alt1.1.noarch	File /usr/share/ri/site/URI/cdesc-URI.ri conflicts with the package ruby-excon-doc-0.62.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/URI/cdesc-URI.ri conflicts with the package ruby-globalid-doc-0.4.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-pundit-doc-2.0.1-alt1.noarch	There are file conflicts with the package ruby-draper-doc-3.0.1-alt1.noarch, for example, /usr/share/ri/site/Rspec/Generators/cdesc-Generators.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.; 
warn	ruby-rack-accept-doc-0.4.5-alt1.noarch	File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package gem-rack-mount-doc-0.8.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-rack-cache-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-rack-jsonp-doc-1.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-rack-openid-doc-1.4.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-typhoeus-doc-1.3.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.; 
warn	ruby-rack-cache-doc-1.8.0-alt1.1.noarch	File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package gem-rack-mount-doc-0.8.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-rack-accept-doc-0.4.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-rack-jsonp-doc-1.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-rack-openid-doc-1.4.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-typhoeus-doc-1.3.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.; 
warn	ruby-rack-jsonp-doc-1.3.2-alt1.1.noarch	File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package gem-rack-mount-doc-0.8.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-rack-accept-doc-0.4.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-rack-cache-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-rack-openid-doc-1.4.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-typhoeus-doc-1.3.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.; 
warn	ruby-rack-openid-doc-1.4.2-alt1.1.noarch	File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package gem-rack-mount-doc-0.8.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-rack-accept-doc-0.4.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-rack-cache-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-rack-jsonp-doc-1.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-typhoeus-doc-1.3.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.; 
warn	ruby-rails-html-sanitizer-doc-1.0.4-alt1.1.noarch	File /usr/share/ri/site/ActionView/cdesc-ActionView.ri conflicts with the package ruby-awesome-print-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/ActionView/cdesc-ActionView.ri conflicts with the package ruby-coffee-rails-doc-4.2.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/Rails/cdesc-Rails.ri conflicts with the package ruby-draper-doc-3.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.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-request_store-doc-1.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-responders-doc-2.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/Rails/cdesc-Rails.ri conflicts with the package ruby-secure-headers-doc-6.0.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-securer-headers-doc-6.0.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-sprockets-rails-doc-3.2.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/Rails/cdesc-Rails.ri conflicts with the package ruby-typhoeus-doc-1.3.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.; 
warn	ruby-rails-i18n-doc-5.1.1-alt1.noarch	Files /usr/share/ri/site/cache.ri /usr/share/ri/site/created.rid conflict with the package gem-olddoc-doc-1.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/cache.ri /usr/share/ri/site/created.rid conflict with the package ruby-oauth-doc-0.5.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/cache.ri /usr/share/ri/site/created.rid conflict with the package ruby-parseconfig-doc-0.5-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-rash-doc-0.4.7-alt1.1.noarch	Files /usr/share/ri/site/Hashie/Mash/cdesc-Mash.ri /usr/share/ri/site/Hashie/cdesc-Hashie.ri conflict with the package ruby-hashie-doc-3.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.; 
warn	ruby-rbnacl-doc-5.0.0-alt1.1.noarch	File /usr/share/ri/site/RbNaCl/cdesc-RbNaCl.ri conflicts with the package ruby-rbnacl-libsodium-doc-1.0.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-rbnacl-libsodium-doc-1.0.16-alt1.1.noarch	File /usr/share/ri/site/RbNaCl/cdesc-RbNaCl.ri conflicts with the package ruby-rbnacl-doc-5.0.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-remcached-doc-0.4.1-alt1.1.noarch	File /usr/share/ri/site/Memcached/cdesc-Memcached.ri conflicts with the package ruby-em-synchrony-doc-1.0.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.; 
warn	ruby-request_store-doc-1.4.1-alt1.noarch	File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-draper-doc-3.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.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-rails-html-sanitizer-doc-1.0.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/Rails/cdesc-Rails.ri conflicts with the package ruby-responders-doc-2.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/Rails/cdesc-Rails.ri conflicts with the package ruby-secure-headers-doc-6.0.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-securer-headers-doc-6.0.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-sprockets-rails-doc-3.2.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/Rails/cdesc-Rails.ri conflicts with the package ruby-typhoeus-doc-1.3.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.; 
warn	ruby-responders-doc-2.4.0-alt1.noarch	Files /usr/share/ri/site/ActionController/cdesc-ActionController.ri /usr/share/ri/site/Rails/Generators/cdesc-Generators.ri /usr/share/ri/site/Rails/cdesc-Rails.ri conflict with the package ruby-draper-doc-3.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.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/ActionController/cdesc-ActionController.ri conflicts with the package ruby-oauth-doc-0.5.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-rails-html-sanitizer-doc-1.0.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/Rails/cdesc-Rails.ri conflicts with the package ruby-request_store-doc-1.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.; Files /usr/share/ri/site/ActionController/cdesc-ActionController.ri /usr/share/ri/site/Rails/cdesc-Rails.ri conflict with the package ruby-secure-headers-doc-6.0.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/ActionController/cdesc-ActionController.ri /usr/share/ri/site/Rails/cdesc-Rails.ri conflict with the package ruby-securer-headers-doc-6.0.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-sprockets-rails-doc-3.2.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/Rails/cdesc-Rails.ri conflicts with the package ruby-typhoeus-doc-1.3.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.; 
warn	ruby-retriable-doc-3.1.2-alt3.noarch	File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-awesome-print-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-em-synchrony-doc-1.0.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/Kernel/cdesc-Kernel.ri conflicts with the package ruby-java-doc-0.0.2-alt2.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/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-memoist-doc-0.16.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/Kernel/cdesc-Kernel.ri conflicts with the package ruby-polyglot-doc-0.3.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/Kernel/cdesc-Kernel.ri conflicts with the package ruby-sfl-doc-2.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-rr-doc-1.2.1-alt1.1.noarch	File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-algebrick-doc-0.7.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/Hash/cdesc-Hash.ri conflicts with the package ruby-amazon-ec2-doc-0.9.17-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.1.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.; Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Hash/cdesc-Hash.ri conflict with the package ruby-cfpropertylist-doc-3.0.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Hash/cdesc-Hash.ri conflict with the package ruby-fission-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-fog-xenserver-doc-0.3.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/Regexp/cdesc-Regexp.ri conflicts with the package ruby-serverspec-doc-2.41.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-sfl-doc-2.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-rspec-its-doc-1.2.0-alt1.1.noarch	File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-cleanroom-doc-1.0.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-junit-formatter-doc-0.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/RSpec/cdesc-RSpec.ri conflicts with the package ruby-serverspec-doc-2.41.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-rspec-junit-formatter-doc-0.2.3-alt1.noarch	File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-cleanroom-doc-1.0.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-its-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.; Files /usr/share/ri/site/RSpec/Core/cdesc-Core.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-serverspec-doc-2.41.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-sass-rails-doc-5.0.7-alt1.1.noarch	File /usr/share/ri/site/Sprockets/cdesc-Sprockets.ri conflicts with the package ruby-sprockets-rails-doc-3.2.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/Sprockets/cdesc-Sprockets.ri conflicts with the package sprockets-doc-3.7.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.; 
warn	ruby-scoped-search-doc-4.1.5-alt1.noarch	File /usr/share/ri/site/ActiveRecord/cdesc-ActiveRecord.ri conflicts with the package ruby-activemodel-serializers-xml-doc-1.0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/ActiveRecord/cdesc-ActiveRecord.ri conflicts with the package ruby-activerecord-mysql2-adapter-doc-0.0.3-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/ActiveRecord/cdesc-ActiveRecord.ri conflicts with the package ruby-activerecord-session_store-doc-1.1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/ActiveRecord/cdesc-ActiveRecord.ri conflicts with the package ruby-em-synchrony-doc-1.0.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/ActiveRecord/cdesc-ActiveRecord.ri conflicts with the package ruby-friendly_id-doc-5.2.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.; 
warn	ruby-scrub_rb-doc-1.0.1-alt1.noarch	File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-awesome-print-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-storage-doc-0.15.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fission-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-kindlerb-doc-1.2.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-pedump-doc-0.5.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-specinfra-doc-2.77.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-zhexdump-doc-0.0.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-secure-headers-doc-6.0.0-alt2.noarch	Files /usr/share/ri/site/ActionController/cdesc-ActionController.ri /usr/share/ri/site/Rails/cdesc-Rails.ri conflict with the package ruby-draper-doc-3.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.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/ActionController/Base/cdesc-Base.ri /usr/share/ri/site/ActionController/cdesc-ActionController.ri conflict with the package ruby-oauth-doc-0.5.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-rails-html-sanitizer-doc-1.0.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/Rails/cdesc-Rails.ri conflicts with the package ruby-request_store-doc-1.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.; Files /usr/share/ri/site/ActionController/cdesc-ActionController.ri /usr/share/ri/site/Rails/cdesc-Rails.ri conflict with the package ruby-responders-doc-2.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/Rails/cdesc-Rails.ri conflicts with the package ruby-sprockets-rails-doc-3.2.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/Rails/cdesc-Rails.ri conflicts with the package ruby-typhoeus-doc-1.3.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.; 
warn	ruby-securer-headers-doc-6.0.0-alt1.1.noarch	Files /usr/share/ri/site/ActionController/cdesc-ActionController.ri /usr/share/ri/site/Rails/cdesc-Rails.ri conflict with the package ruby-draper-doc-3.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.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/ActionController/Base/cdesc-Base.ri /usr/share/ri/site/ActionController/cdesc-ActionController.ri conflict with the package ruby-oauth-doc-0.5.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-rails-html-sanitizer-doc-1.0.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/Rails/cdesc-Rails.ri conflicts with the package ruby-request_store-doc-1.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.; Files /usr/share/ri/site/ActionController/cdesc-ActionController.ri /usr/share/ri/site/Rails/cdesc-Rails.ri conflict with the package ruby-responders-doc-2.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/Rails/cdesc-Rails.ri conflicts with the package ruby-sprockets-rails-doc-3.2.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/Rails/cdesc-Rails.ri conflicts with the package ruby-typhoeus-doc-1.3.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.; 
warn	ruby-serverengine-doc-2.0.7-alt1.noarch	File /usr/share/ri/site/Logger/cdesc-Logger.ri conflicts with the package ruby-pedump-doc-0.5.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Logger/cdesc-Logger.ri conflicts with the package ruby-syslog-logger-doc-1.6.8-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.; 
warn	ruby-serverspec-doc-2.41.3-alt1.1.noarch	File /usr/share/ri/site/Regexp/cdesc-Regexp.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-cleanroom-doc-1.0.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Regexp/cdesc-Regexp.ri conflicts with the package ruby-rr-doc-1.2.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-its-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.; Files /usr/share/ri/site/RSpec/Core/cdesc-Core.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-junit-formatter-doc-0.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.; 
warn	ruby-sfl-doc-2.1-alt1.1.noarch	File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-algebrick-doc-0.7.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/Kernel/cdesc-Kernel.ri conflicts with the package ruby-awesome-print-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Kernel/cdesc-Kernel.ri /usr/share/ri/site/Process/cdesc-Process.ri conflict with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-cfpropertylist-doc-3.0.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-em-synchrony-doc-1.0.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/Array/cdesc-Array.ri conflicts with the package ruby-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-fission-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-java-doc-0.0.2-alt2.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/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-memoist-doc-0.16.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/Process/cdesc-Process.ri conflicts with the package ruby-mixlib-shellout-doc-2.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-polyglot-doc-0.3.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/Process/cdesc-Process.ri conflicts with the package ruby-process-group-doc-1.1.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Process/cdesc-Process.ri conflicts with the package ruby-process-pipeline-doc-1.0.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-retriable-doc-3.1.2-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-rr-doc-1.2.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-specinfra-doc-2.77.0-alt1.noarch	File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-awesome-print-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-storage-doc-0.15.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Class/cdesc-Class.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Class/cdesc-Class.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-fission-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-kindlerb-doc-1.2.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-pedump-doc-0.5.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-scrub_rb-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Class/cdesc-Class.ri conflicts with the package ruby-sucker-punch-doc-2.1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-zhexdump-doc-0.0.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-spoon-doc-0.0.6-alt1.1.noarch	File /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri conflicts with the package ruby-amqp-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri conflicts with the package ruby-net-ping-doc-2.0.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/RbConfig/cdesc-RbConfig.ri conflicts with the package ruby-sys-proctable-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.; 
warn	ruby-sprockets-rails-doc-3.2.1-alt2.1.noarch	File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-draper-doc-3.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.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-rails-html-sanitizer-doc-1.0.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/Rails/cdesc-Rails.ri conflicts with the package ruby-request_store-doc-1.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-responders-doc-2.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/Sprockets/cdesc-Sprockets.ri conflicts with the package ruby-sass-rails-doc-5.0.7-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-secure-headers-doc-6.0.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-securer-headers-doc-6.0.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-typhoeus-doc-1.3.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/Sprockets/Cache/cdesc-Cache.ri /usr/share/ri/site/Sprockets/cdesc-Sprockets.ri conflict with the package sprockets-doc-3.7.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.; 
warn	ruby-structured-warnings-doc-0.3.0-alt1.noarch	File /usr/share/ri/site/Test/cdesc-Test.ri conflicts with the package ruby-makeconf-doc-0.3.0-alt2.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.; 
warn	ruby-sucker-punch-doc-2.1.1-alt1.noarch	File /usr/share/ri/site/Class/cdesc-Class.ri conflicts with the package ruby-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Class/cdesc-Class.ri conflicts with the package ruby-fission-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Class/cdesc-Class.ri conflicts with the package ruby-specinfra-doc-2.77.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-sys-proctable-doc-1.2.1-alt1.noarch	File /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri conflicts with the package ruby-amqp-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri conflicts with the package ruby-net-ping-doc-2.0.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/RbConfig/cdesc-RbConfig.ri conflicts with the package ruby-spoon-doc-0.0.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.; 
warn	ruby-syslog-logger-doc-1.6.8-alt1.1.noarch	File /usr/share/ri/site/Logger/cdesc-Logger.ri conflicts with the package ruby-pedump-doc-0.5.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Logger/cdesc-Logger.ri conflicts with the package ruby-serverengine-doc-2.0.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.; 
warn	ruby-temple-doc-0.8.0-alt1.1.noarch	File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-awesome-print-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-storage-doc-0.15.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Numeric/cdesc-Numeric.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Numeric/cdesc-Numeric.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fission-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-kindlerb-doc-1.2.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-pedump-doc-0.5.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-scrub_rb-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-specinfra-doc-2.77.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-zhexdump-doc-0.0.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-typhoeus-doc-1.3.0-alt1.1.noarch	File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package gem-rack-mount-doc-0.8.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-draper-doc-3.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.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-faraday-doc-0.15.2-alt1.1.noarch, for example, /usr/share/ri/site/Faraday/Adapter/Typhoeus/call-i.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/Faraday/cdesc-Faraday.ri conflicts with the package ruby-faraday_middleware-doc-0.12.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-rack-accept-doc-0.4.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-rack-cache-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-rack-jsonp-doc-1.3.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-rack-openid-doc-1.4.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-rails-html-sanitizer-doc-1.0.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/Rails/cdesc-Rails.ri conflicts with the package ruby-request_store-doc-1.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-responders-doc-2.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/Rails/cdesc-Rails.ri conflicts with the package ruby-secure-headers-doc-6.0.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-securer-headers-doc-6.0.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-sprockets-rails-doc-3.2.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.; 
warn	ruby-tzinfo-data-doc-1.2018.5-alt1.noarch	File /usr/share/ri/site/TZInfo/cdesc-TZInfo.ri conflicts with the package ruby-tzinfo-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.; 
warn	ruby-tzinfo-doc-1.2.5-alt1.noarch	File /usr/share/ri/site/TZInfo/cdesc-TZInfo.ri conflicts with the package ruby-tzinfo-data-doc-1.2018.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.; 
warn	ruby-zhexdump-doc-0.0.2-alt1.1.noarch	File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-awesome-print-doc-1.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-storage-doc-0.15.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-extlib-doc-0.9.16-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fission-doc-0.5.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fog-softlayer-doc-1.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-kindlerb-doc-1.2.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-pedump-doc-0.5.2-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-scrub_rb-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-specinfra-doc-2.77.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	samba-client-4.14.10-alt2.x86_64	File /usr/bin/mdfind conflicts with the package gnustep-gworkspace-0.9.2-alt4.svn20131218.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.; 
warn	sassc-3.5.0-alt1.x86_64	File /usr/bin/sassc conflicts with the package python3-module-libsass-0.20.1-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	scim-fcitx-tools-3.1.1-alt1.1.qa1.x86_64	Files /usr/bin/createPYMB /usr/bin/mb2txt /usr/bin/txt2mb conflict with the package fcitx-4.2.9.8-alt2_1.p9.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.; 
warn	screen-message-0.6-alt1.qa1.x86_64	File /usr/bin/sm conflicts with the package python-module-servicemanager-0.0.16-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.; 
warn	secure_delete-3.1-alt1.x86_64	Files /usr/bin/srm /usr/share/man/man1/srm.1.gz conflict with the package srm-1.2.14-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.; 
warn	shared-color-profiles-0.1.5-alt1.noarch	File /usr/share/color/icc/bluish.icc conflicts with the package xcalib-0.8-alt3.qa1.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.; 
warn	sprockets-doc-3.7.2-alt1.noarch	File /usr/share/ri/site/Sprockets/cdesc-Sprockets.ri conflicts with the package ruby-sass-rails-doc-5.0.7-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/Sprockets/Cache/cdesc-Cache.ri /usr/share/ri/site/Sprockets/cdesc-Sprockets.ri conflict with the package ruby-sprockets-rails-doc-3.2.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.; 
warn	srm-1.2.14-alt1.x86_64	Files /usr/bin/srm /usr/share/man/man1/srm.1.gz conflict with the package secure_delete-3.1-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	stress-1.0.4-alt2.x86_64	File /usr/bin/stress conflicts with the package golang-tools-0-alt7.git24acc66e.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.; 
warn	sysconfig-network-1.0-alt2.noarch	File /etc/sysconfig/network conflicts with the package etcnet-0.9.19.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.; 
warn	syslinux-4.04-alt15.x86_64	File /usr/share/man/man1/extlinux.1.xz conflicts with the package extlinux-6.04.pre1-alt1.5e426532.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/bin/lss16toppm /usr/bin/ppmtolss16 /usr/bin/syslinux conflict with the package syslinux1-1.62-alt4.1.qa1.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.; 
warn	syslinux1-1.62-alt4.1.qa1.x86_64	Files /usr/bin/lss16toppm /usr/bin/ppmtolss16 /usr/bin/syslinux conflict with the package syslinux-4.04-alt15.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.; 
warn	systemd-services-247.13-alt1.x86_64	File /usr/share/bash-completion/completions/loginctl conflicts with the package bash-completion-elogind-241.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.; 
warn	task-core-2.5.1-alt2.x86_64	File /usr/bin/task conflicts with the package go-task-2.4.0-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	tatham-puzzles-20180227-alt1.x86_64	Files /usr/share/icons/hicolor/16x16/apps/blackbox.png /usr/share/icons/hicolor/32x32/apps/blackbox.png /usr/share/icons/hicolor/48x48/apps/blackbox.png conflict with the package blackbox-0.74-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.; 
warn	terminfo-extra-6.1.20180407-alt2.noarch	File /usr/share/terminfo/f/fbterm conflicts with the package fbterm-1.7-alt3.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.; 
warn	texlive-collection-basic-2018-alt1_5.noarch	File /usr/share/man/man1/mmafm.1.xz conflicts with the package lcdf-typetools-2.108-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.; 
warn	tklib-0.6-alt1.noarch	File /usr/bin/dia conflicts with the package dia-0.97.4-alt0.7.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.; 
warn	tpg-3.2.2-alt1.1.noarch	File /usr/bin/tpg conflicts with the package python-module-tpg-3.2.2-alt3.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	volumes-profile-alt-workstation-0.1-alt1.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.13-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-server-0.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/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-education-9.2-alt1.p9.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-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-kdesktop-0.9.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-lite-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/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.; 
warn	volumes-profile-centaurus-0.13-alt1.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-workstation-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-cliff-server-0.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/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-education-9.2-alt1.p9.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-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-kdesktop-0.9.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-lite-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/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.; 
warn	volumes-profile-cliff-server-0.17-alt1.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-workstation-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-centaurus-0.13-alt1.noarch. Moreover, the 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-education-9.2-alt1.p9.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-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-kdesktop-0.9.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-lite-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/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.; 
warn	volumes-profile-education-9.2-alt1.p9.1.x86_64	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-workstation-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-centaurus-0.13-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-server-0.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/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-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-kdesktop-0.9.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-lite-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/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.; 
warn	volumes-profile-jeos-0.2-alt1.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-workstation-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-centaurus-0.13-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-server-0.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/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-education-9.2-alt1.p9.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-kdesktop-0.9.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-lite-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/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.; 
warn	volumes-profile-kdesktop-0.9.0-alt2.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-workstation-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-centaurus-0.13-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-server-0.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/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-education-9.2-alt1.p9.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-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-lite-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/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.; 
warn	volumes-profile-lite-0.4.1-alt1.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-workstation-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-centaurus-0.13-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-server-0.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/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-education-9.2-alt1.p9.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-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-kdesktop-0.9.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/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.; 
warn	volumes-profile-master-0.2-alt1.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-workstation-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-centaurus-0.13-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-server-0.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/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-education-9.2-alt1.p9.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-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-kdesktop-0.9.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-lite-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/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.; 
warn	volumes-profile-regular-0.4-alt1.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-workstation-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-centaurus-0.13-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-server-0.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/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-education-9.2-alt1.p9.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-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-kdesktop-0.9.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-lite-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/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.; 
warn	vzdump-1.0-alt3.x86_64	Files /usr/bin/vzdump /usr/share/man/man1/vzdump.1.xz conflict with the package pve-manager-6.3.3-alt5.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.; 
warn	wildfly-as-10.1.0-alt3.noarch	File /usr/bin/jboss-cli conflicts with the package jboss-as-vanilla-7.1.1-alt14.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	xcalib-0.8-alt3.qa1.x86_64	File /usr/share/color/icc/bluish.icc conflicts with the package shared-color-profiles-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.; 
warn	xfce-settings-lite-1.0-alt7.noarch	Files /etc/skel/.config/xfce4/desktop/icons.screen0.rc /etc/skel/.config/xfce4/helpers.rc conflict with the package branding-alt-education-xfce-settings-9.2-alt4.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.; 
warn	xfce-settings-lite-network-1.0-alt7.noarch	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.; 
warn	xfce-settings-lite-office-lite-1.0-alt7.noarch	File /etc/skel/.config/xfce4/panel/launcher-11888137035.rc conflicts with the package branding-altlinux-desktop-xfce-settings-5.9.9-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/skel/.config/xfce4/panel/launcher-11888137035.rc conflicts with the package branding-altlinux-lite-xfce-settings-5.9.9-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.config/xfce4/panel/launcher-11888137035.rc conflicts with the package branding-school-lite-xfce-settings-5.9.9-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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.; 
warn	xfce-settings-lite-office-superlite-1.0-alt7.noarch	File /etc/skel/.config/xfce4/panel/launcher-12888137035.rc conflicts with the package xfce-settings-lite-school-office-superlite-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.; 
warn	xfce-settings-lite-school-0.6-alt2.noarch	Files /etc/skel/.config/xfce4/desktop/icons.screen0.rc /etc/skel/.config/xfce4/helpers.rc conflict with the package branding-alt-education-xfce-settings-9.2-alt4.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 /etc/skel/.config/xfce4/desktop/icons.screen0.rc /etc/skel/.config/xfce4/helpers.rc conflict with the package branding-alt-tonk-xfce-settings-9.0-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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 branding-altlinux-desktop-xfce-settings-5.9.9-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.; 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 branding-altlinux-lite-xfce-settings-5.9.9-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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 branding-school-lite-xfce-settings-5.9.9-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.config/xfce4/helpers.rc conflicts with the package branding-simply-linux-xfce-settings-9.1-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.; 
warn	xfce-settings-lite-school-network-0.6-alt2.noarch	File /etc/skel/.config/xfce4/panel/launcher-10.rc conflicts with the package branding-altlinux-desktop-xfce-settings-5.9.9-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/skel/.config/xfce4/panel/launcher-10.rc conflicts with the package branding-altlinux-lite-xfce-settings-5.9.9-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.config/xfce4/panel/launcher-10.rc conflicts with the package branding-school-lite-xfce-settings-5.9.9-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.config/xfce4/panel/launcher-10.rc conflicts with the package xfce-settings-lite-network-1.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	xfce-settings-lite-school-office-lite-0.6-alt2.noarch	File /etc/skel/.config/xfce4/panel/launcher-11888137035.rc conflicts with the package branding-altlinux-desktop-xfce-settings-5.9.9-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/skel/.config/xfce4/panel/launcher-11888137035.rc conflicts with the package branding-altlinux-lite-xfce-settings-5.9.9-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.config/xfce4/panel/launcher-11888137035.rc conflicts with the package branding-school-lite-xfce-settings-5.9.9-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.config/xfce4/panel/launcher-11888137035.rc conflicts with the package xfce-settings-lite-office-lite-1.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	xfce-settings-lite-school-office-superlite-0.6-alt2.noarch	File /etc/skel/.config/xfce4/panel/launcher-12888137035.rc conflicts with the package xfce-settings-lite-office-superlite-1.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.;