warn	3proxy-0.6.1-alt1.qa1.x86_64	File /usr/bin/proxy conflicts with the package libproxy-tools-0.4.14-alt0.M80P.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	OCE-draw-0.18.3-alt0.M80P.1.x86_64	File /usr/bin/DRAWEXE conflicts with the package opencascade-6.8.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	SNNS-4.3-alt1.1.1.1.x86_64	File /usr/bin/analyze conflicts with the package hunspell-utils-1.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	Wcalc-1.1-alt2.1.x86_64	File /usr/bin/wcalc conflicts with the package wcalc-2.4-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	abinit-6.0.4-alt1.qa1.x86_64	File /usr/bin/aim conflicts with the package marsyas-0.6.0-alt1.alpha.git20150301.x86_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	abuse-data-0.8-alt2.noarch	Files /usr/share/games/abuse/abuse.bmp /usr/share/games/abuse/abuse.lsp /usr/share/games/abuse/abuse.png conflict with the package abuse_sdl-fRaBs-0.7.1-alt2.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	abuse_sdl-fRaBs-0.7.1-alt2.qa1.noarch	Files /usr/share/games/abuse/abuse.bmp /usr/share/games/abuse/abuse.lsp /usr/share/games/abuse/abuse.png conflict with the package abuse-data-0.8-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	accounts-qt5-devel-1.15-alt1.M80P.1.x86_64	There are file conflicts with the package libaccounts-qt5-devel-1.13-alt1_11.x86_64, for example, /usr/include/accounts-qt5/Accounts/account-service.h (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	alsa-bat-1.1.0-alt1.1.x86_64	File /usr/bin/bat conflicts with the package bacula7-bat-7.4.7-alt3.M80P.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/bin/bat conflicts with the package bacula9-bat-9.4.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	alt-license-junior-0.1-alt2.x86_64	Files /usr/share/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-office-server-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/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-server-0.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	alt-license-junior-sj-0.1-alt2.x86_64	Files /usr/share/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-office-server-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/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-server-0.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	alt-license-junior-sl-0.1-alt2.x86_64	Files /usr/share/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-office-server-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/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-server-0.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	alt-license-junior-sm-0.1-alt2.x86_64	Files /usr/share/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-office-server-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/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-server-0.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	alt-license-junior-st-0.1-alt2.x86_64	Files /usr/share/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-office-server-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/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-server-0.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	alt-license-office-server-0.1-alt1.noarch	Files /usr/share/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-junior-0.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.; Files /usr/share/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-junior-sj-0.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.; Files /usr/share/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-junior-sl-0.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.; Files /usr/share/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-junior-sm-0.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.; Files /usr/share/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-junior-st-0.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.; Files /usr/share/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-server-0.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	alt-license-server-0.1-alt2.noarch	Files /usr/share/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-junior-0.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.; Files /usr/share/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-junior-sj-0.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.; Files /usr/share/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-junior-sl-0.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.; Files /usr/share/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-junior-sm-0.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.; Files /usr/share/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-junior-st-0.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.; Files /usr/share/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-office-server-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	alt-notes-children-0.1-alt1.noarch	There are file conflicts with the package alt-notes-junior-0.2-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 alt-notes-junior-sj-0.2-alt4.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 alt-notes-junior-sm-0.2-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.; Files /usr/share/alt-notes/license.all.html /usr/share/alt-notes/release-notes.all.html /usr/share/alt-notes/release-notes.ru.html conflict with the package alt-notes-server-lite-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 branding-alt-education-notes-8.2-alt0.M80P.2.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-alt-tonk-notes-8.3-alt0.M80P.3.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	alt-notes-junior-0.2-alt1.noarch	There are file conflicts with the package alt-notes-children-0.1-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 alt-notes-server-lite-0.1-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-alt-education-notes-8.2-alt0.M80P.2.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-alt-tonk-notes-8.3-alt0.M80P.3.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	alt-notes-junior-sj-0.2-alt4.noarch	There are file conflicts with the package alt-notes-children-0.1-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 alt-notes-server-lite-0.1-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-alt-education-notes-8.2-alt0.M80P.2.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-alt-tonk-notes-8.3-alt0.M80P.3.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	alt-notes-junior-sm-0.2-alt3.noarch	There are file conflicts with the package alt-notes-children-0.1-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 alt-notes-server-lite-0.1-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-alt-education-notes-8.2-alt0.M80P.2.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-alt-tonk-notes-8.3-alt0.M80P.3.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	alt-notes-school-server-4.1-alt3.noarch	There are file conflicts with the package branding-alt-education-notes-8.2-alt0.M80P.2.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.; Files /usr/share/alt-notes/release-notes.all.html /usr/share/alt-notes/release-notes.ru.html conflict with the package branding-alt-server-notes-8.2-alt0.M80P.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.; There are file conflicts with the package branding-alt-spserver-notes-8.0-alt0.M80P.2.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-alt-spworkstation-notes-8.0-alt0.M80P.2.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-alt-tonk-notes-8.3-alt0.M80P.3.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.; Files /usr/share/alt-notes/release-notes.all.html /usr/share/alt-notes/release-notes.ru.html conflict with the package branding-alt-workstation-notes-8.2-alt0.M80P.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 branding-school-master-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-school-teacher-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.; 
warn	alt-notes-server-lite-0.1-alt1.noarch	Files /usr/share/alt-notes/license.all.html /usr/share/alt-notes/release-notes.all.html /usr/share/alt-notes/release-notes.ru.html conflict with the package alt-notes-children-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 alt-notes-junior-0.2-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 alt-notes-junior-sj-0.2-alt4.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 alt-notes-junior-sm-0.2-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-alt-education-notes-8.2-alt0.M80P.2.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-alt-tonk-notes-8.3-alt0.M80P.3.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	altlinux-release-icarus-20160328-alt1.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package altlinux-release-sisyphus-20081222-alt1.noarch. 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-alt-education-release-8.2-alt0.M80P.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 /etc/altlinux-release conflicts with the package branding-alt-sisyphus-release-20161130-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-alt-spserver-release-8.0-alt0.M80P.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 /etc/altlinux-release conflicts with the package branding-alt-spworkstation-release-8.0-alt0.M80P.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 /etc/altlinux-release conflicts with the package branding-alt-starterkit-release-p8-alt0.M80P.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.; File /etc/altlinux-release conflicts with the package branding-alt-tonk-release-8.3-alt0.M80P.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /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-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.; 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-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.; File /etc/altlinux-release conflicts with the package branding-altlinux-sisyphus-release-20160315-alt1.noarch. 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-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-alt46.noarch. 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-junior-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-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-school-master-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-school-server-release-7.0.5-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-school-teacher-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-sisyphus-server-light-release-1.9.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-xalt-kworkstation-release-8.3.0-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.; 
warn	altlinux-release-p8-20160414-alt1.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-alt-spserver-release-8.0-alt0.M80P.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 /etc/altlinux-release conflicts with the package branding-alt-spworkstation-release-8.0-alt0.M80P.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 /etc/altlinux-release conflicts with the package branding-alt-starterkit-release-p8-alt0.M80P.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.; File /etc/altlinux-release conflicts with the package branding-alt-tonk-release-8.3-alt0.M80P.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /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-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.; 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-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.; File /etc/altlinux-release conflicts 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-alt46.noarch. 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-junior-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-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-school-master-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-school-server-release-7.0.5-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-school-teacher-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-sisyphus-server-light-release-1.9.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-xalt-kworkstation-release-8.3.0-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.; 
warn	altlinux-release-sisyphus-20081222-alt1.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-alt-education-release-8.2-alt0.M80P.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 /etc/altlinux-release conflicts with the package branding-alt-tonk-release-8.3-alt0.M80P.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	apache-common-1.3.42rusPL30.24-alt8.1.x86_64	Files /usr/bin/htpasswd /usr/share/man/man1/htpasswd.1.gz conflict with the package mini_httpd-htpasswd-1.19-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	apache-suexec-1.3.42rusPL30.24-alt8.1.x86_64	File /usr/sbin/suexec conflicts with the package apache2-suexec-2.4.43-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	apache2-htpasswd-2.4.43-alt1.x86_64	File /usr/bin/htpasswd conflicts with the package mini_httpd-htpasswd-1.19-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	apache2-suexec-2.4.43-alt1.x86_64	File /usr/sbin/suexec conflicts with the package apache-suexec-1.3.42rusPL30.24-alt8.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	asciidoctor-doc-1.5.6.1-alt0.M80P.1.noarch	Files /usr/share/ri/site/String/cdesc-String.ri /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflict with the package chef-doc-12.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/Hash/cdesc-Hash.ri conflicts with the package ruby-amazon-ec2-doc-0.9.17-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch, for example, /usr/share/ri/site/Array/cdesc-Array.ri (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.; 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.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-deep_merge-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.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/IO/cdesc-IO.ri conflicts with the package ruby-eventmachine-doc-1.2.5-alt0.M80P.4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-alt1.M80P.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.M80P.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/IO/cdesc-IO.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.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/IO/cdesc-IO.ri conflicts with the package ruby-io-extra-doc-1.2.7-alt1.1.M80P.4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Regexp/cdesc-Regexp.ri /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflict with the package ruby-json-pure-doc-2.1.0-alt0.M80P.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.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-mail-doc-2.6.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/Symbol/cdesc-Symbol.ri conflicts with the package ruby-msgpack-doc-1.1.0-alt0.M80P.5.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.5.0-alt1.1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-puppet-lint-doc-1.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-rgen-doc-0.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Hash/cdesc-Hash.ri /usr/share/ri/site/Regexp/cdesc-Regexp.ri conflict with the package ruby-rr-doc-1.1.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch, for example, /usr/share/ri/site/Array/cdesc-Array.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-treetop-doc-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.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-core-sounds-fr-alaw-1.5-alt1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.alaw conflicts with the package asterisk-extra-sounds-fr-alaw-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	asterisk-core-sounds-fr-g722-1.5-alt1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.g722 conflicts with the package asterisk-extra-sounds-fr-g722-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	asterisk-core-sounds-fr-g729-1.5-alt1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.g729 conflicts with the package asterisk-extra-sounds-fr-g729-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	asterisk-core-sounds-fr-gsm-1.5-alt1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.gsm conflicts with the package asterisk-extra-sounds-fr-gsm-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	asterisk-core-sounds-fr-siren14-1.5-alt1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.siren14 conflicts with the package asterisk-extra-sounds-fr-siren14-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	asterisk-core-sounds-fr-siren7-1.5-alt1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.siren7 conflicts with the package asterisk-extra-sounds-fr-siren7-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	asterisk-core-sounds-fr-sln16-1.5-alt1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.sln16 conflicts with the package asterisk-extra-sounds-fr-sln16-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	asterisk-core-sounds-fr-ulaw-1.5-alt1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.ulaw conflicts with the package asterisk-extra-sounds-fr-ulaw-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	asterisk-core-sounds-fr-wav-1.5-alt1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.wav conflicts with the package asterisk-extra-sounds-fr-wav-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	asterisk-extra-sounds-fr-alaw-1.5-alt1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.alaw conflicts with the package asterisk-core-sounds-fr-alaw-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	asterisk-extra-sounds-fr-g722-1.5-alt1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.g722 conflicts with the package asterisk-core-sounds-fr-g722-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	asterisk-extra-sounds-fr-g729-1.5-alt1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.g729 conflicts with the package asterisk-core-sounds-fr-g729-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	asterisk-extra-sounds-fr-gsm-1.5-alt1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.gsm conflicts with the package asterisk-core-sounds-fr-gsm-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	asterisk-extra-sounds-fr-siren14-1.5-alt1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.siren14 conflicts with the package asterisk-core-sounds-fr-siren14-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	asterisk-extra-sounds-fr-siren7-1.5-alt1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.siren7 conflicts with the package asterisk-core-sounds-fr-siren7-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	asterisk-extra-sounds-fr-sln16-1.5-alt1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.sln16 conflicts with the package asterisk-core-sounds-fr-sln16-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	asterisk-extra-sounds-fr-ulaw-1.5-alt1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.ulaw conflicts with the package asterisk-core-sounds-fr-ulaw-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	asterisk-extra-sounds-fr-wav-1.5-alt1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.wav conflicts with the package asterisk-core-sounds-fr-wav-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	atril-gtk-1.16.1-alt1.x86_64	File /usr/share/thumbnailers/atril.thumbnailer conflicts with the package mate-document-viewer-thumbnailer-1.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.; 
warn	atril-gtk-dvi-1.16.1-alt1.x86_64	Files /usr/lib64/atril/3/backends/dvidocument.atril-backend /usr/lib64/atril/3/backends/libdvidocument.so conflict with the package mate-document-viewer-dvi-1.12.2-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	audiofile-0.3.6-alt1.qa1.x86_64	File /usr/bin/sfinfo conflicts with the package marsyas-0.6.0-alt1.alpha.git20150301.x86_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	bacula-director-mysql-5.2.13-alt9.M80P.1.x86_64	File /etc/rc.d/init.d/bacula-dir conflicts with the package bacula7-director-postgresql-7.4.7-alt3.M80P.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 /etc/rc.d/init.d/bacula-dir conflicts with the package bacula7-director-sqlite3-7.4.7-alt3.M80P.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 /etc/rc.d/init.d/bacula-dir conflicts with the package bacula9-director-common-9.4.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	bacula-director-postgresql-5.2.13-alt9.M80P.1.x86_64	File /etc/rc.d/init.d/bacula-dir conflicts with the package bacula7-director-mysql-7.4.7-alt3.M80P.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 /etc/rc.d/init.d/bacula-dir conflicts with the package bacula7-director-sqlite3-7.4.7-alt3.M80P.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 /etc/rc.d/init.d/bacula-dir conflicts with the package bacula9-director-common-9.4.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	bacula-director-sqlite3-5.2.13-alt9.M80P.1.x86_64	File /etc/rc.d/init.d/bacula-dir conflicts with the package bacula7-director-mysql-7.4.7-alt3.M80P.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 /etc/rc.d/init.d/bacula-dir conflicts with the package bacula7-director-postgresql-7.4.7-alt3.M80P.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 /etc/rc.d/init.d/bacula-dir conflicts with the package bacula9-director-common-9.4.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	bacula-tray-monitor-5.2.13-alt9.M80P.1.x86_64	Files /usr/share/applications/bacula-tray-monitor.desktop /usr/share/man/man1/bacula-tray-monitor.1.xz conflict with the package bacula9-traymonitor-9.4.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	bacula7-bat-7.4.7-alt3.M80P.1.x86_64	File /usr/bin/bat conflicts with the package alsa-bat-1.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	bacula7-director-mysql-7.4.7-alt3.M80P.1.x86_64	File /etc/rc.d/init.d/bacula-dir conflicts with the package bacula-director-postgresql-5.2.13-alt9.M80P.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 /etc/rc.d/init.d/bacula-dir conflicts with the package bacula-director-sqlite3-5.2.13-alt9.M80P.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	bacula7-director-postgresql-7.4.7-alt3.M80P.1.x86_64	File /etc/rc.d/init.d/bacula-dir conflicts with the package bacula-director-mysql-5.2.13-alt9.M80P.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 /etc/rc.d/init.d/bacula-dir conflicts with the package bacula-director-sqlite3-5.2.13-alt9.M80P.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	bacula7-director-sqlite3-7.4.7-alt3.M80P.1.x86_64	File /etc/rc.d/init.d/bacula-dir conflicts with the package bacula-director-mysql-5.2.13-alt9.M80P.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 /etc/rc.d/init.d/bacula-dir conflicts with the package bacula-director-postgresql-5.2.13-alt9.M80P.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	bacula9-bat-9.4.2-alt2.x86_64	File /usr/bin/bat conflicts with the package alsa-bat-1.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	bacula9-director-common-9.4.2-alt2.x86_64	File /etc/rc.d/init.d/bacula-dir conflicts with the package bacula-director-mysql-5.2.13-alt9.M80P.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 /etc/rc.d/init.d/bacula-dir conflicts with the package bacula-director-postgresql-5.2.13-alt9.M80P.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 /etc/rc.d/init.d/bacula-dir conflicts with the package bacula-director-sqlite3-5.2.13-alt9.M80P.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	bacula9-traymonitor-9.4.2-alt2.x86_64	Files /usr/share/applications/bacula-tray-monitor.desktop /usr/share/man/man1/bacula-tray-monitor.1.xz conflict with the package bacula-tray-monitor-5.2.13-alt9.M80P.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	bash-devel-3.2.57-alt1.x86_64	There are file conflicts with the package bash4-devel-4.2.50-alt1.1.x86_64, for example, /usr/include/bash/alias.h (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	bash4-devel-4.2.50-alt1.1.x86_64	There are file conflicts with the package bash-devel-3.2.57-alt1.x86_64, for example, /usr/include/bash/alias.h (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	batik-slideshow-1.8-alt2_2jpp8.noarch	File /usr/bin/slideshow conflicts with the package racket-6.0.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	berkeley_upc-docs-2.20.0-alt1.noarch	Files /usr/share/doc/gasnet/README-extref /usr/share/doc/gasnet/README-release conflict with the package gasnet-doc-1.22.4-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	blackbox-0.70.1-alt3.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-10286-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	br2684ctl-20040226-alt1.qa1.x86_64	Files /usr/sbin/br2684ctl /usr/share/man/man8/br2684ctl.8.gz conflict with the package linux-atm-2.5.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.; 
warn	branding-alt-education-alterator-8.2-alt0.M80P.2.noarch	There are file conflicts with the package branding-alt-sisyphus-alterator-20161130-alt2.noarch, for example, /usr/share/alterator/design/images/attention.gif (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-alt-education-indexhtml-8.2-alt0.M80P.2.noarch	There are file conflicts with the package branding-alt-sisyphus-indexhtml-20161130-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.; File /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-school-master-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.; 
warn	branding-alt-education-kde-settings-8.2-alt0.M80P.2.noarch	File /etc/skel/.kde4/share/config/default-apps conflicts with the package branding-alt-sisyphus-kde4-settings-20161130-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-education-mate-settings-8.2-alt0.M80P.2.noarch	File /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflicts with the package branding-alt-spserver-mate-settings-8.0-alt0.M80P.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/glib-2.0/schemas/60_mate-theme.gschema.override conflicts with the package branding-alt-spworkstation-mate-settings-8.0-alt0.M80P.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	branding-alt-education-notes-8.2-alt0.M80P.2.noarch	There are file conflicts with the package alt-notes-children-0.1-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 alt-notes-junior-0.2-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 alt-notes-junior-sj-0.2-alt4.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 alt-notes-junior-sm-0.2-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 alt-notes-school-server-4.1-alt3.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package alt-notes-server-lite-0.1-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-alt-sisyphus-notes-20161130-alt2.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-alt-education-release-8.2-alt0.M80P.2.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package altlinux-release-sisyphus-20081222-alt1.noarch. 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-sisyphus-release-20161130-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-education-xfce-settings-8.2-alt0.M80P.2.noarch	There are file conflicts with the package branding-alt-sisyphus-xfce-settings-20161130-alt2.noarch, for example, /etc/skel/.config/xfce4/desktop/icons.screen0.rc (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 /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/gtk-3.0/settings.ini /etc/skel/.gtkrc-2.0 conflict with the package branding-xalt-kworkstation-graphics-8.3.0-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.; 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.; There are file conflicts with the package xfce-settings-simple-1.0-alt6.noarch, for example, /etc/skel/.config/xfce4/Xcursor.xrdb (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	branding-alt-server-alterator-8.2-alt0.M80P.5.noarch	There are file conflicts with the package branding-alt-sisyphus-alterator-20161130-alt2.noarch, for example, /usr/share/alterator/design/images/attention.gif (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-alt-server-indexhtml-8.2-alt0.M80P.5.noarch	File /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-school-master-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.; 
warn	branding-alt-server-mate-settings-8.2-alt0.M80P.5.noarch	File /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflicts with the package branding-alt-spserver-mate-settings-8.0-alt0.M80P.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/glib-2.0/schemas/60_mate-theme.gschema.override conflicts with the package branding-alt-spworkstation-mate-settings-8.0-alt0.M80P.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	branding-alt-server-notes-8.2-alt0.M80P.5.noarch	Files /usr/share/alt-notes/release-notes.all.html /usr/share/alt-notes/release-notes.ru.html conflict with the package alt-notes-school-server-4.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.; Files /usr/share/alt-notes/release-notes.all.html /usr/share/alt-notes/release-notes.ru.html conflict with the package branding-alt-sisyphus-notes-20161130-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-sisyphus-alterator-20161130-alt2.noarch	There are file conflicts with the package branding-alt-education-alterator-8.2-alt0.M80P.2.noarch, for example, /usr/share/alterator/design/images/attention.gif (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-alt-server-alterator-8.2-alt0.M80P.5.noarch, for example, /usr/share/alterator/design/images/attention.gif (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.; File /usr/share/alterator/design/images/steps/notes-license.png conflicts with the package branding-alt-starterkit-alterator-p8-alt0.M80P.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.; There are file conflicts with the package branding-alt-tonk-alterator-8.3-alt0.M80P.3.noarch, for example, /usr/share/alterator/design/images/attention.gif (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-alt-workstation-alterator-8.2-alt0.M80P.2.noarch, for example, /usr/share/alterator/design/images/attention.gif (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-backup-server-alterator-6.0.0-alt3.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (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 branding-altlinux-desktop-alterator-5.9.9-alt3.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/clock-face.png (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-altlinux-tablet-alterator-6.0.0-alt3.noarch, for example, /usr/share/alterator/design/images/clock-face.png (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-school-teacher-alterator-7.0.5-alt1.noarch, for example, /usr/share/alterator/design/images/attention.gif (16 file conflicts in 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-alt-sisyphus-indexhtml-20161130-alt2.noarch	There are file conflicts with the package branding-alt-education-indexhtml-8.2-alt0.M80P.2.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-alt-tonk-indexhtml-8.3-alt0.M80P.3.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-alt-sisyphus-kde4-settings-20161130-alt2.noarch	File /etc/skel/.kde4/share/config/default-apps conflicts with the package branding-alt-education-kde-settings-8.2-alt0.M80P.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 /etc/skel/.kde4/share/config/default-apps conflicts with the package branding-alt-tonk-kde4-settings-8.3-alt0.M80P.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /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/kde4/xdg/menus/applications-merged/desktop.menu conflicts with the package branding-altlinux-desktop-kde4-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/.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.; File /etc/skel/.kde4/share/config/default-apps conflicts with the package branding-school-teacher-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.; 
warn	branding-alt-sisyphus-notes-20161130-alt2.noarch	There are file conflicts with the package branding-alt-education-notes-8.2-alt0.M80P.2.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.; Files /usr/share/alt-notes/release-notes.all.html /usr/share/alt-notes/release-notes.ru.html conflict with the package branding-alt-server-notes-8.2-alt0.M80P.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.; There are file conflicts with the package branding-alt-starterkit-notes-p8-alt0.M80P.5.noarch, for example, /usr/share/alt-notes/index-en.html (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-alt-tonk-notes-8.3-alt0.M80P.3.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.; Files /usr/share/alt-notes/release-notes.all.html /usr/share/alt-notes/release-notes.ru.html conflict with the package branding-alt-workstation-notes-8.2-alt0.M80P.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 branding-altlinux-backup-server-notes-6.0.0-alt3.noarch, for example, /usr/share/alt-notes/index-en.html (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-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-desktop-notes-5.9.9-alt3.noarch, for example, /usr/share/alt-notes/index-en.html (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-notes-6.0.0-alt7.noarch, for example, /usr/share/alt-notes/index-en.html (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-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 (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-teacher-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.; 
warn	branding-alt-sisyphus-release-20161130-alt2.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /etc/altlinux-release /etc/os-release conflict with the package branding-alt-education-release-8.2-alt0.M80P.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 /etc/altlinux-release /etc/os-release conflict with the package branding-alt-tonk-release-8.3-alt0.M80P.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-alt-sisyphus-xfce-settings-20161130-alt2.noarch	There are file conflicts with the package branding-alt-education-xfce-settings-8.2-alt0.M80P.2.noarch, for example, /etc/skel/.config/xfce4/desktop/icons.screen0.rc (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/xfce4/backdrops/default.png /usr/share/xfce4/backdrops/xdm.png conflict with the package branding-alt-starterkit-xfce-settings-p8-alt0.M80P.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.; There are file conflicts with the package branding-alt-tonk-xfce-settings-8.3-alt0.M80P.3.noarch, for example, /etc/skel/.config/xfce4/desktop/icons.screen0.rc (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/xfce4/backdrops/default.png /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.; There are file conflicts with the package branding-school-teacher-xfce-settings-7.0.5-alt1.noarch, for example, /etc/skel/.config/xfce4/desktop/icons.screen0.rc (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 /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.; There are file conflicts with the package xfce-settings-simple-1.0-alt6.noarch, for example, /etc/skel/.Xdefaults (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-alt-spserver-alterator-8.0-alt0.M80P.2.noarch	There are file conflicts with the package branding-altlinux-office-server-alterator-5.9.9-alt1.noarch, for example, /usr/share/alterator/design/images/attention.gif (20 file conflicts in 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-alt-spserver-indexhtml-8.0-alt0.M80P.2.noarch	There are file conflicts with the package branding-alt-tonk-indexhtml-8.3-alt0.M80P.3.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.; File /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-school-master-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.; There are file conflicts with the package branding-sisyphus-server-light-indexhtml-1.9.3-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.; 
warn	branding-alt-spserver-mate-settings-8.0-alt0.M80P.2.noarch	File /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflicts with the package branding-alt-education-mate-settings-8.2-alt0.M80P.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/glib-2.0/schemas/60_mate-theme.gschema.override conflicts with the package branding-alt-server-mate-settings-8.2-alt0.M80P.5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/glib-2.0/schemas/50_mate-background.gschema.override /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflict with the package branding-altlinux-centaurus-mate-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.; Files /usr/share/glib-2.0/schemas/50_mate-background.gschema.override /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflict with the package branding-altlinux-spt-mate-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.; Files /usr/share/glib-2.0/schemas/50_mate-background.gschema.override /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflict with the package branding-school-junior-mate-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.; Files /usr/share/glib-2.0/schemas/50_mate-background.gschema.override /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflict with the package branding-school-master-mate-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.; Files /usr/share/glib-2.0/schemas/50_mate-background.gschema.override /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflict with the package branding-school-server-mate-settings-7.0.5-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/glib-2.0/schemas/50_mate-background.gschema.override /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflict with the package branding-school-teacher-mate-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.; 
warn	branding-alt-spserver-menu-8.0-alt0.M80P.2.noarch	Files /usr/share/slinux-style/applications/alt-alt_linux.desktop /usr/share/slinux-style/applications/alt-docs-main.desktop conflict with the package branding-alt-tonk-menu-8.3-alt0.M80P.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/slinux-style/applications/dropbox.desktop conflicts with the package branding-school-junior-menu-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 /usr/share/slinux-style/applications/dropbox.desktop conflicts with the package branding-school-master-menu-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 /usr/share/slinux-style/applications/dropbox.desktop conflicts with the package branding-school-teacher-menu-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-simply-linux-menu-8.2.0-alt1.noarch, for example, /usr/share/slinux-style/applications/Ri-li.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-alt-spserver-notes-8.0-alt0.M80P.2.noarch	There are file conflicts with the package alt-notes-school-server-4.1-alt3.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-alt-tonk-notes-8.3-alt0.M80P.3.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-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-sisyphus-server-light-notes-1.9.3-alt1.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-alt-spserver-release-8.0-alt0.M80P.2.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /etc/altlinux-release /etc/os-release conflict with the package branding-alt-tonk-release-8.3-alt0.M80P.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /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-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.; File /etc/altlinux-release conflicts with the package branding-sisyphus-server-light-release-1.9.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-alt-spworkstation-alterator-8.0-alt0.M80P.2.noarch	There are file conflicts with the package branding-altlinux-office-server-alterator-5.9.9-alt1.noarch, for example, /usr/share/alterator/design/images/attention.gif (20 file conflicts in 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-alt-spworkstation-indexhtml-8.0-alt0.M80P.2.noarch	There are file conflicts with the package branding-alt-tonk-indexhtml-8.3-alt0.M80P.3.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.; File /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-school-master-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.; There are file conflicts with the package branding-sisyphus-server-light-indexhtml-1.9.3-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.; 
warn	branding-alt-spworkstation-mate-settings-8.0-alt0.M80P.2.noarch	File /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflicts with the package branding-alt-education-mate-settings-8.2-alt0.M80P.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/glib-2.0/schemas/60_mate-theme.gschema.override conflicts with the package branding-alt-server-mate-settings-8.2-alt0.M80P.5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/glib-2.0/schemas/50_mate-background.gschema.override /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflict with the package branding-altlinux-centaurus-mate-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.; Files /usr/share/glib-2.0/schemas/50_mate-background.gschema.override /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflict with the package branding-altlinux-spt-mate-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.; Files /usr/share/glib-2.0/schemas/50_mate-background.gschema.override /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflict with the package branding-school-junior-mate-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.; Files /usr/share/glib-2.0/schemas/50_mate-background.gschema.override /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflict with the package branding-school-master-mate-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.; Files /usr/share/glib-2.0/schemas/50_mate-background.gschema.override /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflict with the package branding-school-server-mate-settings-7.0.5-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/glib-2.0/schemas/50_mate-background.gschema.override /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflict with the package branding-school-teacher-mate-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.; 
warn	branding-alt-spworkstation-menu-8.0-alt0.M80P.2.noarch	Files /usr/share/slinux-style/applications/alt-alt_linux.desktop /usr/share/slinux-style/applications/alt-docs-main.desktop conflict with the package branding-alt-tonk-menu-8.3-alt0.M80P.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/slinux-style/applications/dropbox.desktop conflicts with the package branding-school-junior-menu-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 /usr/share/slinux-style/applications/dropbox.desktop conflicts with the package branding-school-master-menu-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 /usr/share/slinux-style/applications/dropbox.desktop conflicts with the package branding-school-teacher-menu-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-simply-linux-menu-8.2.0-alt1.noarch, for example, /usr/share/slinux-style/applications/Ri-li.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-alt-spworkstation-notes-8.0-alt0.M80P.2.noarch	There are file conflicts with the package alt-notes-school-server-4.1-alt3.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-alt-tonk-notes-8.3-alt0.M80P.3.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-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-sisyphus-server-light-notes-1.9.3-alt1.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-alt-spworkstation-release-8.0-alt0.M80P.2.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /etc/altlinux-release /etc/os-release conflict with the package branding-alt-tonk-release-8.3-alt0.M80P.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /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-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.; File /etc/altlinux-release conflicts with the package branding-sisyphus-server-light-release-1.9.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-alt-starterkit-alterator-p8-alt0.M80P.5.noarch	File /usr/share/alterator/design/images/steps/notes-license.png conflicts with the package branding-alt-sisyphus-alterator-20161130-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-backup-server-alterator-6.0.0-alt3.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (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 branding-altlinux-centaurus-alterator-7.0.5-alt1.noarch, for example, /usr/share/alterator/design/images/attention.gif (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-alterator-5.9.9-alt3.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lxdesktop-alterator-6.0.0-alt7.noarch, for example, /usr/share/alterator/design/images/clock-face.png (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-altlinux-spt-alterator-7.0.0-alt1.noarch, for example, /usr/share/alterator/design/images/attention.gif (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-alterator-6.0.0-alt3.noarch, for example, /usr/share/alterator/design/images/clock-face.png (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-school-teacher-alterator-7.0.5-alt1.noarch, for example, /usr/share/alterator/design/images/attention.gif (16 file conflicts in 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-alt-starterkit-indexhtml-p8-alt0.M80P.5.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 (4 file conflicts in total). Moreover, the packages have no explicit conflicts 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 (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lxdesktop-indexhtml-6.0.0-alt7.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-office-server-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-spt-indexhtml-7.0.0-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-tablet-indexhtml-6.0.0-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-informika-schoolmaster-indexhtml-6.0.0-alt46.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-junior-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-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-school-master-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-school-teacher-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-simply-linux-indexhtml-8.2.0-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-alt-starterkit-kde4-settings-p8-alt0.M80P.5.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/kde4/xdg/menus/applications-merged/desktop.menu conflicts with the package branding-altlinux-desktop-kde4-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/.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.; File /etc/skel/.kde4/share/config/default-apps conflicts with the package branding-school-teacher-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.; 
warn	branding-alt-starterkit-notes-p8-alt0.M80P.5.noarch	There are file conflicts with the package branding-alt-sisyphus-notes-20161130-alt2.noarch, for example, /usr/share/alt-notes/index-en.html (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-backup-server-notes-6.0.0-alt3.noarch, for example, /usr/share/alt-notes/index-en.html (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-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-desktop-notes-5.9.9-alt3.noarch, for example, /usr/share/alt-notes/index-en.html (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-notes-6.0.0-alt7.noarch, for example, /usr/share/alt-notes/index-en.html (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-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 (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-teacher-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.; 
warn	branding-alt-starterkit-release-p8-alt0.M80P.5.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-altlinux-backup-server-release-6.0.0-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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.; 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/os-release conflicts with the package branding-school-teacher-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.; 
warn	branding-alt-starterkit-xfce-settings-p8-alt0.M80P.5.noarch	Files /usr/share/xfce4/backdrops/default.png /usr/share/xfce4/backdrops/xdm.png conflict with the package branding-alt-sisyphus-xfce-settings-20161130-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/xfce4/backdrops/default.png /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.; There are file conflicts with the package branding-school-teacher-xfce-settings-7.0.5-alt1.noarch, for example, /etc/skel/.config/xfce4/desktop/icons.screen0.rc (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 /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.; There are file conflicts with the package xfce-settings-simple-1.0-alt6.noarch, for example, /etc/skel/.Xdefaults (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-alt-tonk-alterator-8.3-alt0.M80P.3.noarch	There are file conflicts with the package branding-alt-sisyphus-alterator-20161130-alt2.noarch, for example, /usr/share/alterator/design/images/attention.gif (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-alt-tonk-indexhtml-8.3-alt0.M80P.3.noarch	There are file conflicts with the package branding-alt-sisyphus-indexhtml-20161130-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-alt-spserver-indexhtml-8.0-alt0.M80P.2.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-alt-spworkstation-indexhtml-8.0-alt0.M80P.2.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.; File /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-school-master-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.; 
warn	branding-alt-tonk-kde4-settings-8.3-alt0.M80P.3.noarch	File /etc/skel/.kde4/share/config/default-apps conflicts with the package branding-alt-sisyphus-kde4-settings-20161130-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-tonk-menu-8.3-alt0.M80P.3.noarch	Files /usr/share/slinux-style/applications/alt-alt_linux.desktop /usr/share/slinux-style/applications/alt-docs-main.desktop conflict with the package branding-alt-spserver-menu-8.0-alt0.M80P.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/slinux-style/applications/alt-alt_linux.desktop /usr/share/slinux-style/applications/alt-docs-main.desktop conflict with the package branding-alt-spworkstation-menu-8.0-alt0.M80P.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	branding-alt-tonk-notes-8.3-alt0.M80P.3.noarch	There are file conflicts with the package alt-notes-children-0.1-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 alt-notes-junior-0.2-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 alt-notes-junior-sj-0.2-alt4.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 alt-notes-junior-sm-0.2-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 alt-notes-school-server-4.1-alt3.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package alt-notes-server-lite-0.1-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-alt-sisyphus-notes-20161130-alt2.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-alt-spserver-notes-8.0-alt0.M80P.2.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-alt-spworkstation-notes-8.0-alt0.M80P.2.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-alt-tonk-release-8.3-alt0.M80P.3.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package altlinux-release-sisyphus-20081222-alt1.noarch. 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-sisyphus-release-20161130-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-spserver-release-8.0-alt0.M80P.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 /etc/altlinux-release /etc/os-release conflict with the package branding-alt-spworkstation-release-8.0-alt0.M80P.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	branding-alt-tonk-xfce-settings-8.3-alt0.M80P.3.noarch	There are file conflicts with the package branding-alt-sisyphus-xfce-settings-20161130-alt2.noarch, for example, /etc/skel/.config/xfce4/desktop/icons.screen0.rc (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 /etc/skel/.gconf/apps/%gconf.xml conflicts with the package livecd-gnome-nowarn-space-0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /etc/skel/.config/xfce4/desktop/icons.screen0.rc /etc/skel/.config/xfce4/helpers.rc conflict with the package xfce-settings-lite-school-0.6-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package xfce-settings-simple-1.0-alt6.noarch, for example, /etc/skel/.config/xfce4/Xcursor.xrdb (8 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-alt-workstation-alterator-8.2-alt0.M80P.2.noarch	There are file conflicts with the package branding-alt-sisyphus-alterator-20161130-alt2.noarch, for example, /usr/share/alterator/design/images/attention.gif (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-alt-workstation-indexhtml-8.2-alt0.M80P.2.noarch	File /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-school-master-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.; 
warn	branding-alt-workstation-notes-8.2-alt0.M80P.2.noarch	Files /usr/share/alt-notes/release-notes.all.html /usr/share/alt-notes/release-notes.ru.html conflict with the package alt-notes-school-server-4.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.; Files /usr/share/alt-notes/release-notes.all.html /usr/share/alt-notes/release-notes.ru.html conflict with the package branding-alt-sisyphus-notes-20161130-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-backup-server-alterator-6.0.0-alt3.noarch	There are file conflicts with the package branding-alt-sisyphus-alterator-20161130-alt2.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (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 branding-alt-starterkit-alterator-p8-alt0.M80P.5.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (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 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-sisyphus-alterator-20160315-alt1.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (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 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-alt46.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-sisyphus-server-light-alterator-1.9.3-alt1.noarch, for example, /usr/share/alterator/design/images/groups/datetime.png (31 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-xalt-kworkstation-alterator-8.3.0-alt4.noarch, for example, /usr/share/alterator/design/images/clock-face.png (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-alt-starterkit-indexhtml-p8-alt0.M80P.5.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 (4 file conflicts in total). Moreover, the packages have no explicit conflicts 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-alt46.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-sisyphus-server-light-indexhtml-1.9.3-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-xalt-kworkstation-indexhtml-8.3.0-alt4.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-backup-server-notes-6.0.0-alt3.noarch	There are file conflicts with the package branding-alt-sisyphus-notes-20161130-alt2.noarch, for example, /usr/share/alt-notes/index-en.html (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-alt-spserver-notes-8.0-alt0.M80P.2.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-alt-spworkstation-notes-8.0-alt0.M80P.2.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-alt-starterkit-notes-p8-alt0.M80P.5.noarch, for example, /usr/share/alt-notes/index-en.html (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-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-sisyphus-notes-20160315-alt1.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-alt46.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-sisyphus-server-light-notes-1.9.3-alt1.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-xalt-kworkstation-notes-8.3.0-alt4.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-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-alt-spserver-release-8.0-alt0.M80P.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 /etc/altlinux-release conflicts with the package branding-alt-spworkstation-release-8.0-alt0.M80P.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 /etc/altlinux-release conflicts with the package branding-alt-starterkit-release-p8-alt0.M80P.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.; 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-alt46.noarch. 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-sisyphus-server-light-release-1.9.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-xalt-kworkstation-release-8.3.0-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.; 
warn	branding-altlinux-centaurus-alterator-7.0.5-alt1.noarch	There are file conflicts with the package branding-alt-starterkit-alterator-p8-alt0.M80P.5.noarch, for example, /usr/share/alterator/design/images/attention.gif (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-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-alt46.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-sisyphus-server-light-alterator-1.9.3-alt1.noarch, for example, /usr/share/alterator/design/images/attention.gif (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-xalt-kworkstation-alterator-8.3.0-alt4.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.; 
warn	branding-altlinux-centaurus-indexhtml-7.0.5-alt1.noarch	There are file conflicts with the package branding-alt-starterkit-indexhtml-p8-alt0.M80P.5.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-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-alt46.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-8.2.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-sisyphus-server-light-indexhtml-1.9.3-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-8.3.0-alt4.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-centaurus-kde4-settings-7.0.5-alt1.noarch	File /etc/skel/.kde4/share/config/default-apps conflicts with the package branding-alt-sisyphus-kde4-settings-20161130-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/.kde4/share/config/default-apps conflicts with the package branding-alt-starterkit-kde4-settings-p8-alt0.M80P.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.; File /etc/skel/.kde4/share/config/default-apps conflicts with the package branding-xalt-kworkstation-kde4-settings-8.3.0-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.; 
warn	branding-altlinux-centaurus-mate-settings-7.0.5-alt1.noarch	Files /usr/share/glib-2.0/schemas/50_mate-background.gschema.override /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflict with the package branding-alt-spserver-mate-settings-8.0-alt0.M80P.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/glib-2.0/schemas/50_mate-background.gschema.override /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflict with the package branding-alt-spworkstation-mate-settings-8.0-alt0.M80P.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	branding-altlinux-centaurus-notes-7.0.5-alt1.noarch	There are file conflicts with the package branding-alt-sisyphus-notes-20161130-alt2.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-alt-starterkit-notes-p8-alt0.M80P.5.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-8.3.0-alt4.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	File /etc/altlinux-release conflicts with the package altlinux-release-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /etc/altlinux-release /etc/os-release conflict with the package branding-alt-starterkit-release-p8-alt0.M80P.5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /etc/altlinux-release /etc/os-release conflict with the package branding-xalt-kworkstation-release-8.3.0-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.; 
warn	branding-altlinux-desktop-alterator-5.9.9-alt3.noarch	There are file conflicts with the package branding-alt-sisyphus-alterator-20161130-alt2.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-alt-starterkit-alterator-p8-alt0.M80P.5.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (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-sisyphus-alterator-20160315-alt1.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.; 
warn	branding-altlinux-desktop-indexhtml-5.9.9-alt3.noarch	There are file conflicts with the package branding-alt-starterkit-indexhtml-p8-alt0.M80P.5.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-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-alt46.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-ivk-chainmail-indexhtml-3.0-alt2.noarch, for example, /usr/share/applications/indexhtml.desktop (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-school-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-simply-linux-indexhtml-8.2.0-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-sisyphus-server-light-indexhtml-1.9.3-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-altlinux-desktop-kde4-settings-5.9.9-alt3.noarch	File /etc/kde4/xdg/menus/applications-merged/desktop.menu conflicts with the package branding-alt-sisyphus-kde4-settings-20161130-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/kde4/xdg/menus/applications-merged/desktop.menu conflicts with the package branding-alt-starterkit-kde4-settings-p8-alt0.M80P.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.; File /etc/kde4/xdg/menus/applications-merged/desktop.menu conflicts with the package branding-altlinux-sisyphus-kde4-settings-20160315-alt1.noarch. 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-notes-5.9.9-alt3.noarch	There are file conflicts with the package branding-alt-sisyphus-notes-20161130-alt2.noarch, for example, /usr/share/alt-notes/index-en.html (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-alt-starterkit-notes-p8-alt0.M80P.5.noarch, for example, /usr/share/alt-notes/index-en.html (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-sisyphus-notes-20160315-alt1.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-desktop-release-5.9.9-alt3.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-alt-starterkit-release-p8-alt0.M80P.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	branding-altlinux-desktop-xfce-settings-5.9.9-alt3.noarch	Files /usr/share/xfce4/backdrops/default.png /usr/share/xfce4/backdrops/xdm.png conflict with the package branding-alt-sisyphus-xfce-settings-20161130-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/xfce4/backdrops/default.png /usr/share/xfce4/backdrops/xdm.png conflict with the package branding-alt-starterkit-xfce-settings-p8-alt0.M80P.5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/xfce4/backdrops/default.png /usr/share/xfce4/backdrops/xdm.png conflict with the package branding-altlinux-sisyphus-xfce-settings-20160315-alt1.noarch. 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.; 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.; There are file conflicts with the package xfce-settings-simple-1.0-alt6.noarch, for example, /etc/skel/.Xdefaults (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-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-alt46.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/gtk-3.0/settings.ini /etc/skel/.gtkrc-2.0 conflict with the package branding-alt-education-xfce-settings-8.2-alt0.M80P.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 /etc/skel/.gtkrc-2.0 conflicts with the package branding-simply-linux-xfce-settings-8.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	branding-altlinux-kdesktop-indexhtml-8.0.0-alt0.6.noarch	There are file conflicts with the package branding-alt-starterkit-indexhtml-p8-alt0.M80P.5.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-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-alt46.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.; File /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-school-master-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.; There are file conflicts with the package branding-simply-linux-indexhtml-8.2.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-sisyphus-server-light-indexhtml-1.9.3-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.; 
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	File /etc/altlinux-release conflicts with the package altlinux-release-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-altlinux-backup-server-release-6.0.0-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-altlinux-lxdesktop-release-6.0.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-altlinux-tablet-release-6.0.0-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-altlinux-lite-indexhtml-5.9.9-alt1.noarch	There are file conflicts with the package branding-alt-starterkit-indexhtml-p8-alt0.M80P.5.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-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-alt46.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-ivk-chainmail-indexhtml-3.0-alt2.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-school-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-simply-linux-indexhtml-8.2.0-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-sisyphus-server-light-indexhtml-1.9.3-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.; 
warn	branding-altlinux-lite-release-5.9.9-alt1.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
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.; There are file conflicts with the package xfce-settings-simple-1.0-alt6.noarch, for example, /etc/skel/.Xdefaults (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-alterator-6.0.0-alt7.noarch	There are file conflicts with the package branding-alt-sisyphus-alterator-20161130-alt2.noarch, for example, /usr/share/alterator/design/images/clock-face.png (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-alt-starterkit-alterator-p8-alt0.M80P.5.noarch, for example, /usr/share/alterator/design/images/clock-face.png (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-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-sisyphus-alterator-20160315-alt1.noarch, for example, /usr/share/alterator/design/images/clock-face.png (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-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-alt46.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-sisyphus-server-light-alterator-1.9.3-alt1.noarch, for example, /usr/share/alterator/design/images/groups/datetime.png (31 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-xalt-kworkstation-alterator-8.3.0-alt4.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (34 file conflicts in 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-alt-starterkit-indexhtml-p8-alt0.M80P.5.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-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-alt46.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-8.2.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-sisyphus-server-light-indexhtml-1.9.3-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-8.3.0-alt4.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.; 
warn	branding-altlinux-lxdesktop-notes-6.0.0-alt7.noarch	There are file conflicts with the package branding-alt-sisyphus-notes-20161130-alt2.noarch, for example, /usr/share/alt-notes/index-en.html (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-alt-starterkit-notes-p8-alt0.M80P.5.noarch, for example, /usr/share/alt-notes/index-en.html (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-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-sisyphus-notes-20160315-alt1.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-alt46.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-sisyphus-server-light-notes-1.9.3-alt1.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-xalt-kworkstation-notes-8.3.0-alt4.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-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-alt-starterkit-release-p8-alt0.M80P.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.; 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-alt46.noarch. 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-sisyphus-server-light-release-1.9.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-xalt-kworkstation-release-8.3.0-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.; 
warn	branding-altlinux-office-server-alterator-5.9.9-alt1.noarch	There are file conflicts with the package branding-alt-spserver-alterator-8.0-alt0.M80P.2.noarch, for example, /usr/share/alterator/design/images/attention.gif (20 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-alt-spworkstation-alterator-8.0-alt0.M80P.2.noarch, for example, /usr/share/alterator/design/images/attention.gif (20 file conflicts in 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-indexhtml-5.9.9-alt1.noarch	There are file conflicts with the package branding-alt-spserver-indexhtml-8.0-alt0.M80P.2.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-alt-spworkstation-indexhtml-8.0-alt0.M80P.2.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-alt-starterkit-indexhtml-p8-alt0.M80P.5.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-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-alt46.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-ivk-chainmail-indexhtml-3.0-alt2.noarch, for example, /usr/share/applications/indexhtml.desktop (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-school-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-simply-linux-indexhtml-8.2.0-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-sisyphus-server-light-indexhtml-1.9.3-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-altlinux-office-server-release-5.9.9-alt1.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-alt-spserver-release-8.0-alt0.M80P.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 /etc/altlinux-release conflicts with the package branding-alt-spworkstation-release-8.0-alt0.M80P.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	branding-altlinux-sisyphus-alterator-20160315-alt1.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/close-dialog-button.png (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 branding-altlinux-desktop-alterator-5.9.9-alt3.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/clock-face.png (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-altlinux-tablet-alterator-6.0.0-alt3.noarch, for example, /usr/share/alterator/design/images/clock-face.png (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-altlinux-sisyphus-kde4-settings-20160315-alt1.noarch	File /etc/kde4/xdg/menus/applications-merged/desktop.menu conflicts with the package branding-altlinux-desktop-kde4-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/.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-sisyphus-notes-20160315-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/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-desktop-notes-5.9.9-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-sisyphus-release-20160315-alt1.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-altlinux-sisyphus-xfce-settings-20160315-alt1.noarch	Files /usr/share/xfce4/backdrops/default.png /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.; 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.; There are file conflicts with the package xfce-settings-simple-1.0-alt6.noarch, for example, /etc/skel/.Xdefaults (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-spt-alterator-7.0.0-alt1.noarch	There are file conflicts with the package branding-alt-starterkit-alterator-p8-alt0.M80P.5.noarch, for example, /usr/share/alterator/design/images/attention.gif (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-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-alt46.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-sisyphus-server-light-alterator-1.9.3-alt1.noarch, for example, /usr/share/alterator/design/images/attention.gif (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-xalt-kworkstation-alterator-8.3.0-alt4.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.; 
warn	branding-altlinux-spt-indexhtml-7.0.0-alt1.noarch	There are file conflicts with the package branding-alt-starterkit-indexhtml-p8-alt0.M80P.5.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-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-alt46.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-8.2.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-sisyphus-server-light-indexhtml-1.9.3-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-8.3.0-alt4.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-spt-kde4-settings-7.0.0-alt1.noarch	File /etc/skel/.kde4/share/config/default-apps conflicts with the package branding-alt-sisyphus-kde4-settings-20161130-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/.kde4/share/config/default-apps conflicts with the package branding-alt-starterkit-kde4-settings-p8-alt0.M80P.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.; File /etc/skel/.kde4/share/config/default-apps conflicts with the package branding-xalt-kworkstation-kde4-settings-8.3.0-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.; 
warn	branding-altlinux-spt-mate-settings-7.0.0-alt1.noarch	Files /usr/share/glib-2.0/schemas/50_mate-background.gschema.override /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflict with the package branding-alt-spserver-mate-settings-8.0-alt0.M80P.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/glib-2.0/schemas/50_mate-background.gschema.override /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflict with the package branding-alt-spworkstation-mate-settings-8.0-alt0.M80P.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	branding-altlinux-spt-notes-7.0.0-alt1.noarch	There are file conflicts with the package branding-alt-sisyphus-notes-20161130-alt2.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-alt-starterkit-notes-p8-alt0.M80P.5.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-8.3.0-alt4.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	File /etc/altlinux-release conflicts with the package altlinux-release-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /etc/altlinux-release /etc/os-release conflict with the package branding-alt-starterkit-release-p8-alt0.M80P.5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /etc/altlinux-release /etc/os-release conflict with the package branding-xalt-kworkstation-release-8.3.0-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.; 
warn	branding-altlinux-tablet-alterator-6.0.0-alt3.noarch	There are file conflicts with the package branding-alt-sisyphus-alterator-20161130-alt2.noarch, for example, /usr/share/alterator/design/images/clock-face.png (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-alt-starterkit-alterator-p8-alt0.M80P.5.noarch, for example, /usr/share/alterator/design/images/clock-face.png (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-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-altlinux-sisyphus-alterator-20160315-alt1.noarch, for example, /usr/share/alterator/design/images/clock-face.png (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-informika-schoolmaster-alterator-6.0.0-alt46.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-sisyphus-server-light-alterator-1.9.3-alt1.noarch, for example, /usr/share/alterator/design/images/groups/datetime.png (31 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-xalt-kworkstation-alterator-8.3.0-alt4.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (30 file conflicts in 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-alt-starterkit-indexhtml-p8-alt0.M80P.5.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-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-alt46.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-8.2.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-sisyphus-server-light-indexhtml-1.9.3-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-8.3.0-alt4.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.; 
warn	branding-altlinux-tablet-kde4-settings-6.0.0-alt3.noarch	File /etc/skel/.kde4/share/config/default-apps conflicts with the package branding-alt-sisyphus-kde4-settings-20161130-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/.kde4/share/config/default-apps conflicts with the package branding-alt-starterkit-kde4-settings-p8-alt0.M80P.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.; 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-altlinux-sisyphus-kde4-settings-20160315-alt1.noarch. 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-alt46.noarch. 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-8.3.0-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.; 
warn	branding-altlinux-tablet-notes-6.0.0-alt3.noarch	There are file conflicts with the package branding-alt-sisyphus-notes-20161130-alt2.noarch, for example, /usr/share/alt-notes/index-en.html (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-alt-starterkit-notes-p8-alt0.M80P.5.noarch, for example, /usr/share/alt-notes/index-en.html (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-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-altlinux-sisyphus-notes-20160315-alt1.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-alt46.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-sisyphus-server-light-notes-1.9.3-alt1.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-xalt-kworkstation-notes-8.3.0-alt4.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-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-alt-starterkit-release-p8-alt0.M80P.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.; 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-alt46.noarch. 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-sisyphus-server-light-release-1.9.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-xalt-kworkstation-release-8.3.0-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.; 
warn	branding-informika-schoolmaster-alterator-6.0.0-alt46.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-sisyphus-server-light-alterator-1.9.3-alt1.noarch, for example, /usr/share/alterator/design/images/groups/datetime.png (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-xalt-kworkstation-alterator-8.3.0-alt4.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (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-informika-schoolmaster-indexhtml-6.0.0-alt46.noarch	There are file conflicts with the package branding-alt-starterkit-indexhtml-p8-alt0.M80P.5.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-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.; File /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-school-master-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.; There are file conflicts with the package branding-simply-linux-indexhtml-8.2.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-sisyphus-server-light-indexhtml-1.9.3-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-8.3.0-alt4.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.; 
warn	branding-informika-schoolmaster-kde4-settings-6.0.0-alt46.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-alt46.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-sisyphus-server-light-notes-1.9.3-alt1.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-xalt-kworkstation-notes-8.3.0-alt4.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-alt46.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-altlinux-backup-server-release-6.0.0-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-altlinux-lxdesktop-release-6.0.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-altlinux-tablet-release-6.0.0-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-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-sisyphus-server-light-release-1.9.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-xalt-kworkstation-release-8.3.0-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.; 
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-alt46.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-sisyphus-server-light-alterator-1.9.3-alt1.noarch, for example, /usr/share/alterator/design/images/groups/datetime.png (31 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-xalt-kworkstation-alterator-8.3.0-alt4.noarch, for example, /usr/share/alterator/design/images/clock-face.png (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-alt-starterkit-indexhtml-p8-alt0.M80P.5.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-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-alt46.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-8.2.0-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-sisyphus-server-light-indexhtml-1.9.3-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-xalt-kworkstation-indexhtml-8.3.0-alt4.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-ivk-chainmail-notes-3.0-alt2.noarch	There are file conflicts with the package branding-xalt-kworkstation-notes-8.3.0-alt4.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-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-xalt-kworkstation-release-8.3.0-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.; 
warn	branding-school-junior-indexhtml-7.0.5-alt1.noarch	There are file conflicts with the package branding-alt-starterkit-indexhtml-p8-alt0.M80P.5.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.; File /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-school-master-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.; 
warn	branding-school-junior-mate-settings-7.0.5-alt1.noarch	Files /usr/share/glib-2.0/schemas/50_mate-background.gschema.override /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflict with the package branding-alt-spserver-mate-settings-8.0-alt0.M80P.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/glib-2.0/schemas/50_mate-background.gschema.override /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflict with the package branding-alt-spworkstation-mate-settings-8.0-alt0.M80P.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	branding-school-junior-menu-7.0.5-alt1.noarch	File /usr/share/slinux-style/applications/dropbox.desktop conflicts with the package branding-alt-spserver-menu-8.0-alt0.M80P.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/slinux-style/applications/dropbox.desktop conflicts with the package branding-alt-spworkstation-menu-8.0-alt0.M80P.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/slinux-style/applications/dropbox.desktop conflicts with the package branding-school-server-menu-7.0.5-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-simply-linux-menu-8.2.0-alt1.noarch, for example, /usr/share/slinux-style/applications/Ri-li.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-school-junior-release-7.0.5-alt1.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-school-junior-xfce-settings-7.0.5-alt1.noarch	File /etc/skel/.gconf/apps/%gconf.xml conflicts with the package livecd-gnome-nowarn-space-0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /etc/skel/.config/xfce4/desktop/icons.screen0.rc /etc/skel/.config/xfce4/helpers.rc conflict with the package xfce-settings-lite-school-0.6-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package xfce-settings-simple-1.0-alt6.noarch, for example, /etc/skel/.config/xfce4/Xcursor.xrdb (8 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-school-lite-indexhtml-5.9.9-alt1.noarch	There are file conflicts with the package branding-alt-starterkit-indexhtml-p8-alt0.M80P.5.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-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-alt46.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-ivk-chainmail-indexhtml-3.0-alt2.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-simply-linux-indexhtml-8.2.0-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-sisyphus-server-light-indexhtml-1.9.3-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
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-alt46.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-sisyphus-server-light-notes-1.9.3-alt1.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-school-lite-release-5.9.9-alt1.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-altlinux-backup-server-release-6.0.0-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-altlinux-lxdesktop-release-6.0.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-altlinux-tablet-release-6.0.0-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-informika-schoolmaster-release-6.0.0-alt46.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-sisyphus-server-light-release-1.9.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
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.; File /etc/skel/.Xdefaults conflicts with the package xfce-settings-simple-1.0-alt6.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-school-master-indexhtml-7.0.5-alt1.noarch	There are file conflicts with the package branding-alt-starterkit-indexhtml-p8-alt0.M80P.5.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-master-kde4-settings-7.0.5-alt1.noarch	File /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-alt-education-indexhtml-8.2-alt0.M80P.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/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-alt-server-indexhtml-8.2-alt0.M80P.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.; File /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-alt-spserver-indexhtml-8.0-alt0.M80P.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/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-alt-spworkstation-indexhtml-8.0-alt0.M80P.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/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-alt-tonk-indexhtml-8.3-alt0.M80P.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-alt-workstation-indexhtml-8.2-alt0.M80P.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/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-altlinux-kdesktop-indexhtml-8.0.0-alt0.6.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-informika-schoolmaster-indexhtml-6.0.0-alt46.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-school-junior-indexhtml-7.0.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-school-teacher-indexhtml-7.0.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-xalt-kworkstation-indexhtml-8.3.0-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.; 
warn	branding-school-master-mate-settings-7.0.5-alt1.noarch	Files /usr/share/glib-2.0/schemas/50_mate-background.gschema.override /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflict with the package branding-alt-spserver-mate-settings-8.0-alt0.M80P.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/glib-2.0/schemas/50_mate-background.gschema.override /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflict with the package branding-alt-spworkstation-mate-settings-8.0-alt0.M80P.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	branding-school-master-menu-7.0.5-alt1.noarch	File /usr/share/slinux-style/applications/dropbox.desktop conflicts with the package branding-alt-spserver-menu-8.0-alt0.M80P.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/slinux-style/applications/dropbox.desktop conflicts with the package branding-alt-spworkstation-menu-8.0-alt0.M80P.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/slinux-style/applications/dropbox.desktop conflicts with the package branding-school-server-menu-7.0.5-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-simply-linux-menu-8.2.0-alt1.noarch, for example, /usr/share/slinux-style/applications/Ri-li.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-school-master-notes-7.0.5-alt1.noarch	There are file conflicts with the package alt-notes-school-server-4.1-alt3.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-school-master-release-7.0.5-alt1.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-school-master-xfce-settings-7.0.5-alt1.noarch	File /etc/skel/.gconf/apps/%gconf.xml conflicts with the package livecd-gnome-nowarn-space-0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /etc/skel/.config/xfce4/desktop/icons.screen0.rc /etc/skel/.config/xfce4/helpers.rc conflict with the package xfce-settings-lite-school-0.6-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package xfce-settings-simple-1.0-alt6.noarch, for example, /etc/skel/.config/xfce4/Xcursor.xrdb (8 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-school-server-mate-settings-7.0.5-alt2.noarch	Files /usr/share/glib-2.0/schemas/50_mate-background.gschema.override /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflict with the package branding-alt-spserver-mate-settings-8.0-alt0.M80P.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/glib-2.0/schemas/50_mate-background.gschema.override /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflict with the package branding-alt-spworkstation-mate-settings-8.0-alt0.M80P.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	branding-school-server-menu-7.0.5-alt2.noarch	File /usr/share/slinux-style/applications/dropbox.desktop conflicts with the package branding-school-junior-menu-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 /usr/share/slinux-style/applications/dropbox.desktop conflicts with the package branding-school-master-menu-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 /usr/share/slinux-style/applications/dropbox.desktop conflicts with the package branding-school-teacher-menu-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-simply-linux-menu-8.2.0-alt1.noarch, for example, /usr/share/slinux-style/applications/Ri-li.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-school-server-release-7.0.5-alt2.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-school-server-xfce-settings-7.0.5-alt2.noarch	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.; 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.; There are file conflicts with the package xfce-settings-lite-school-0.6-alt2.noarch, for example, /etc/skel/.config/xfce4/desktop/icons.screen0.rc (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/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.; There are file conflicts with the package xfce-settings-simple-1.0-alt6.noarch, for example, /etc/skel/.config/xfce4/Xcursor.xrdb (8 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-school-teacher-alterator-7.0.5-alt1.noarch	There are file conflicts with the package branding-alt-sisyphus-alterator-20161130-alt2.noarch, for example, /usr/share/alterator/design/images/attention.gif (16 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-alt-starterkit-alterator-p8-alt0.M80P.5.noarch, for example, /usr/share/alterator/design/images/attention.gif (16 file conflicts in 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-teacher-indexhtml-7.0.5-alt1.noarch	There are file conflicts with the package branding-alt-starterkit-indexhtml-p8-alt0.M80P.5.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.; File /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-school-master-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.; 
warn	branding-school-teacher-kde4-settings-7.0.5-alt1.noarch	File /etc/skel/.kde4/share/config/default-apps conflicts with the package branding-alt-sisyphus-kde4-settings-20161130-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/.kde4/share/config/default-apps conflicts with the package branding-alt-starterkit-kde4-settings-p8-alt0.M80P.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	branding-school-teacher-mate-settings-7.0.5-alt1.noarch	Files /usr/share/glib-2.0/schemas/50_mate-background.gschema.override /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflict with the package branding-alt-spserver-mate-settings-8.0-alt0.M80P.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/glib-2.0/schemas/50_mate-background.gschema.override /usr/share/glib-2.0/schemas/60_mate-theme.gschema.override conflict with the package branding-alt-spworkstation-mate-settings-8.0-alt0.M80P.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	branding-school-teacher-menu-7.0.5-alt1.noarch	File /usr/share/slinux-style/applications/dropbox.desktop conflicts with the package branding-alt-spserver-menu-8.0-alt0.M80P.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/slinux-style/applications/dropbox.desktop conflicts with the package branding-alt-spworkstation-menu-8.0-alt0.M80P.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/slinux-style/applications/dropbox.desktop conflicts with the package branding-school-server-menu-7.0.5-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-simply-linux-menu-8.2.0-alt1.noarch, for example, /usr/share/slinux-style/applications/Ri-li.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-school-teacher-notes-7.0.5-alt1.noarch	There are file conflicts with the package alt-notes-school-server-4.1-alt3.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-alt-sisyphus-notes-20161130-alt2.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-alt-starterkit-notes-p8-alt0.M80P.5.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-teacher-release-7.0.5-alt1.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/os-release conflicts with the package branding-alt-starterkit-release-p8-alt0.M80P.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	branding-school-teacher-xfce-settings-7.0.5-alt1.noarch	There are file conflicts with the package branding-alt-sisyphus-xfce-settings-20161130-alt2.noarch, for example, /etc/skel/.config/xfce4/desktop/icons.screen0.rc (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-alt-starterkit-xfce-settings-p8-alt0.M80P.5.noarch, for example, /etc/skel/.config/xfce4/desktop/icons.screen0.rc (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 /etc/skel/.gconf/apps/%gconf.xml conflicts with the package livecd-gnome-nowarn-space-0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /etc/skel/.config/xfce4/desktop/icons.screen0.rc /etc/skel/.config/xfce4/helpers.rc conflict with the package xfce-settings-lite-school-0.6-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package xfce-settings-simple-1.0-alt6.noarch, for example, /etc/skel/.config/xfce4/Xcursor.xrdb (8 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-simply-linux-indexhtml-8.2.0-alt1.noarch	There are file conflicts with the package branding-alt-starterkit-indexhtml-p8-alt0.M80P.5.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-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-alt46.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-sisyphus-server-light-indexhtml-1.9.3-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-8.3.0-alt4.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-simply-linux-menu-8.2.0-alt1.noarch	There are file conflicts with the package branding-alt-spserver-menu-8.0-alt0.M80P.2.noarch, for example, /usr/share/slinux-style/applications/Ri-li.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-alt-spworkstation-menu-8.0-alt0.M80P.2.noarch, for example, /usr/share/slinux-style/applications/Ri-li.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-school-junior-menu-7.0.5-alt1.noarch, for example, /usr/share/slinux-style/applications/Ri-li.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-school-master-menu-7.0.5-alt1.noarch, for example, /usr/share/slinux-style/applications/Ri-li.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-school-server-menu-7.0.5-alt2.noarch, for example, /usr/share/slinux-style/applications/Ri-li.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-school-teacher-menu-7.0.5-alt1.noarch, for example, /usr/share/slinux-style/applications/Ri-li.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-simply-linux-xfce-settings-8.2.0-alt1.noarch	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-8.3.0-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.; 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.; There are file conflicts with the package xfce-settings-simple-1.0-alt6.noarch, for example, /etc/skel/.config/xfce4/Xcursor.xrdb (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	branding-sisyphus-server-light-alterator-1.9.3-alt1.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/groups/datetime.png (31 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-centaurus-alterator-7.0.5-alt1.noarch, for example, /usr/share/alterator/design/images/attention.gif (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lxdesktop-alterator-6.0.0-alt7.noarch, for example, /usr/share/alterator/design/images/groups/datetime.png (31 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-spt-alterator-7.0.0-alt1.noarch, for example, /usr/share/alterator/design/images/attention.gif (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-tablet-alterator-6.0.0-alt3.noarch, for example, /usr/share/alterator/design/images/groups/datetime.png (31 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-informika-schoolmaster-alterator-6.0.0-alt46.noarch, for example, /usr/share/alterator/design/images/groups/datetime.png (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-ivk-chainmail-alterator-3.0-alt2.noarch, for example, /usr/share/alterator/design/images/groups/datetime.png (31 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-sisyphus-server-light-indexhtml-1.9.3-alt1.noarch	There are file conflicts with the package branding-alt-spserver-indexhtml-8.0-alt0.M80P.2.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-alt-spworkstation-indexhtml-8.0-alt0.M80P.2.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-backup-server-indexhtml-6.0.0-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-centaurus-indexhtml-7.0.5-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-desktop-indexhtml-5.9.9-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-kdesktop-indexhtml-8.0.0-alt0.6.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-lxdesktop-indexhtml-6.0.0-alt7.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-office-server-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-spt-indexhtml-7.0.0-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-tablet-indexhtml-6.0.0-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-informika-schoolmaster-indexhtml-6.0.0-alt46.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-ivk-chainmail-indexhtml-3.0-alt2.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-school-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-simply-linux-indexhtml-8.2.0-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-sisyphus-server-light-notes-1.9.3-alt1.noarch	There are file conflicts with the package branding-alt-spserver-notes-8.0-alt0.M80P.2.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-alt-spworkstation-notes-8.0-alt0.M80P.2.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-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-alt46.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-school-lite-notes-5.9.9-alt1.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-sisyphus-server-light-release-1.9.3-alt1.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-alt-spserver-release-8.0-alt0.M80P.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 /etc/altlinux-release conflicts with the package branding-alt-spworkstation-release-8.0-alt0.M80P.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 /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-alt46.noarch. 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.; 
warn	branding-xalt-kworkstation-alterator-8.3.0-alt4.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 (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/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 (34 file conflicts in total). Moreover, the packages have no explicit conflicts 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 (30 file conflicts in total). Moreover, the packages have no explicit conflicts 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-alt46.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (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-ivk-chainmail-alterator-3.0-alt2.noarch, for example, /usr/share/alterator/design/images/clock-face.png (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-8.3.0-alt4.noarch	Files /etc/skel/.config/gtk-3.0/settings.ini /etc/skel/.gtkrc-2.0 conflict with the package branding-alt-education-xfce-settings-8.2-alt0.M80P.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 /etc/skel/.gtkrc-2.0 conflicts with the package branding-simply-linux-xfce-settings-8.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	branding-xalt-kworkstation-indexhtml-8.3.0-alt4.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-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 (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-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-alt46.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.; File /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-school-master-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.; There are file conflicts with the package branding-simply-linux-indexhtml-8.2.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.; 
warn	branding-xalt-kworkstation-kde4-settings-8.3.0-alt4.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-8.3.0-alt4.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-alt46.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-8.3.0-alt4.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-altlinux-backup-server-release-6.0.0-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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-alt46.noarch. 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	buzztrax-data-0.8.0-alt1.git20140805.noarch	File /usr/share/applications/mimeinfo.cache conflicts with the package cssed-common-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.; 
warn	chef-doc-12.6.0-alt1.noarch	Files /usr/share/ri/site/String/cdesc-String.ri /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflict with the package asciidoctor-doc-1.5.6.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Chef/cdesc-Chef.ri /usr/share/ri/site/Mash/cdesc-Mash.ri conflict with the package ohai-doc-8.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/String/cdesc-String.ri /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflict with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Gem/cdesc-Gem.ri /usr/share/ri/site/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package ruby-bundler-doc-1.16.2-alt2.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-chef-sugar-doc-3.1.0-alt1.noarch, for example, /usr/share/ri/site/Chef/Node/cdesc-Node.ri (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-cleanroom-doc-1.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.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/Win32/cdesc-Win32.ri conflicts with the package ruby-facter-doc-2.0.1-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-alt1.M80P.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/FFI/Pointer/cdesc-Pointer.ri /usr/share/ri/site/FFI/cdesc-FFI.ri conflict with the package ruby-ffi-doc-1.9.18-alt1.M80P.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.; There are file conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch, for example, /usr/share/ri/site/FalseClass/cdesc-FalseClass.ri (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.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/Symbol/cdesc-Symbol.ri conflicts with the package ruby-json-pure-doc-2.1.0-alt0.M80P.5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Net/cdesc-Net.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-mail-doc-2.6.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/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package ruby-mechanize-doc-0.9.3-alt1.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package ruby-mini_portile2-doc-2.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-msgpack-doc-1.1.0-alt0.M80P.5.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package ruby-multipart-post-doc-2.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-dhcp-doc-1.3.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-http-pipeline-doc-1.0.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/SSH/cdesc-SSH.ri conflicts with the package ruby-net-ssh-doc-4.2.0-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-net-ssh-multi-doc-1.2.0-alt1.noarch, for example, /usr/share/ri/site/Net/SSH/Multi/Server/busy%3f-i.ri (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.5.0-alt1.1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-puppet-lint-doc-1.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/ri/site/RSpec/Core/cdesc-Core.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-core-doc-3.6.0-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-expectations-doc-3.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/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-mocks-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-puppet-doc-0.1.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-support-doc-3.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.; There are file conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch, for example, /usr/share/ri/site/FalseClass/cdesc-FalseClass.ri (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Gem/cdesc-Gem.ri /usr/share/ri/site/RSpec/Core/cdesc-Core.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-spec_helper-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-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.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	chicken-4.1.0-alt2.1.x86_64	File /usr/bin/csc conflicts with the package mono-core-5.20.1.19-alt0.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/bin/csi conflicts with the package mono-devel-5.20.1.19-alt0.M80P.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	clang-analyzer-3.8.0-alt0.M80P.1.x86_64	File /usr/share/man/man1/scan-build.1.xz conflicts with the package clang4.0-analyzer-4.0.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	clang-devel-3.8.0-alt0.M80P.1.x86_64	There are file conflicts with the package clang4.0-devel-4.0.1-alt0.M80P.1.x86_64, for example, /usr/include/clang-c/Index.h (269 file conflicts in 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	clang-devel-static-3.8.0-alt0.M80P.1.x86_64	There are file conflicts with the package clang4.0-devel-static-4.0.1-alt0.M80P.1.x86_64, for example, /usr/lib64/libclangARCMigrate.a (24 file conflicts in 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	clang4.0-analyzer-4.0.1-alt0.M80P.1.noarch	File /usr/share/man/man1/scan-build.1.xz conflicts with the package clang-analyzer-3.8.0-alt0.M80P.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	clang4.0-devel-4.0.1-alt0.M80P.1.x86_64	There are file conflicts with the package clang-devel-3.8.0-alt0.M80P.1.x86_64, for example, /usr/include/clang-c/Index.h (269 file conflicts in 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	clang4.0-devel-static-4.0.1-alt0.M80P.1.x86_64	There are file conflicts with the package clang-devel-static-3.8.0-alt0.M80P.1.x86_64, for example, /usr/lib64/libclangARCMigrate.a (24 file conflicts in 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	cmdtest-0.16-alt1.noarch	File /usr/bin/yarn conflicts with the package hadoop-yarn-2.4.1-alt2_14jpp8.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	courier-imap-4.10.0-alt0.2.x86_64	File /etc/pam.d/imap conflicts with the package cyrus-imapd-2.5.17-alt0.M80P.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	cssed-common-0.4.1-alt1.noarch	File /usr/share/applications/mimeinfo.cache conflicts with the package buzztrax-data-0.8.0-alt1.git20140805.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	custom-libgccjit7-devel-7.3.1-alt8.M80P.1.x86_64	Files /usr/include/libgccjit++.h /usr/include/libgccjit.h conflict with the package libgccjit5-devel-5.3.1-alt3.M80P.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	cyrus-imapd-2.5.17-alt0.M80P.2.x86_64	File /etc/pam.d/imap conflicts with the package courier-imap-4.10.0-alt0.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	dap-devel-3.10-alt1.1.x86_64	File /usr/include/ps.h conflicts with the package python-module-gist-2.2.0-alt2.git20130422.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	dapl2-utils-2.0.30-alt2.1.x86_64	File /usr/share/man/man5/dat.conf.5.gz conflicts with the package libdapl-1.2.16-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	db4.7-utils-4.7.25-alt8.x86_64	There are file conflicts with the package pks-db-0.9.6-alt1.qa1.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-alt1.x86_64	There are file conflicts with the package pks-db-0.9.6-alt1.qa1.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-alt1.x86_64	There are file conflicts with the package pks-db-0.9.6-alt1.qa1.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.x86_64	File /usr/bin/dcadec conflicts with the package dcadec-0.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	dcadec-0.2.0-alt1.x86_64	File /usr/bin/dcadec conflicts with the package dca-apps-0.0.5-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	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	eGroupWare-addressbook-1.8-alt6.noarch	There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/addressbook/doc/README (80 file conflicts in 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	eGroupWare-bookmarks-1.8-alt6.noarch	There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/bookmarks/glist.wml (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	eGroupWare-calendar-1.8-alt6.noarch	There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/calendar/egroupware.org/accept_holiday.php (92 file conflicts in 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	eGroupWare-core-1.8-alt6.noarch	There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/about.php (702 file conflicts in 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	eGroupWare-developer_tools-1.8-alt6.noarch	There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/developer_tools/doc/copyright.gpl (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	eGroupWare-emailadmin-1.8-alt6.noarch	There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/emailadmin/inc/class.dbmaildbmailuser.inc.php (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	eGroupWare-filemanager-1.8-alt6.noarch	There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/filemanager/cli.php (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	eGroupWare-importexport-1.8-alt6.noarch	There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/importexport/doc/README_developers.txt (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	eGroupWare-infolog-1.8-alt6.noarch	There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/infolog/inc/class.infolog_bo.inc.php (57 file conflicts in 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	eGroupWare-manual-1.8-alt6.noarch	There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/manual/inc/class.uimanual.inc.php (19 file conflicts in 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	eGroupWare-news_admin-1.8-alt6.noarch	There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/news_admin/doc/copyright.gpl (55 file conflicts in 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	eGroupWare-notifications-1.8-alt6.noarch	There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/notifications/inc/class.notifications.inc.php (30 file conflicts in 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	eGroupWare-phpbrain-1.8-alt6.noarch	There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/phpbrain/inc/class.bokb.inc.php (57 file conflicts in 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	eGroupWare-projectmanager-1.8-alt6.noarch	There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/projectmanager/inc/class.datasource.inc.php (62 file conflicts in 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	eGroupWare-registration-1.8-alt6.noarch	There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/registration/doc/README (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	eGroupWare-resources-1.8-alt6.noarch	There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/resources/inc/class.bo_acl.inc.php (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.; 
warn	eGroupWare-sambaadmin-1.8-alt6.noarch	There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/sambaadmin/inc/class.bosambaadmin.inc.php (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.; 
warn	eGroupWare-sitemgr-1.8-alt6.noarch	There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/sitemgr/inc/class.ACL_BO.inc.php (268 file conflicts in 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	eGroupWare-timesheet-1.8-alt6.noarch	There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/timesheet/inc/class.timesheet_bo.inc.php (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.; 
warn	eGroupWare-tracker-1.8-alt6.noarch	There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/tracker/inc/class.botracker.inc.php (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	eGroupWare-wiki-1.8-alt6.noarch	There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/wiki/action/admin.php (82 file conflicts in 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	efl-libs-devel-1.20.5-alt0.M80P.1.x86_64	File /usr/lib64/pkgconfig/eo.pc conflicts with the package libeo-devel-1.3.1-alt1.qa3.x86_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	egroupware-epl-14.2-alt1.noarch	There are file conflicts with the package eGroupWare-addressbook-1.8-alt6.noarch, for example, /usr/share/egroupware/addressbook/doc/README (80 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package eGroupWare-bookmarks-1.8-alt6.noarch, for example, /usr/share/egroupware/bookmarks/glist.wml (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.; There are file conflicts with the package eGroupWare-calendar-1.8-alt6.noarch, for example, /usr/share/egroupware/calendar/egroupware.org/accept_holiday.php (92 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package eGroupWare-core-1.8-alt6.noarch, for example, /usr/share/egroupware/about.php (702 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package eGroupWare-developer_tools-1.8-alt6.noarch, for example, /usr/share/egroupware/developer_tools/doc/copyright.gpl (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 eGroupWare-emailadmin-1.8-alt6.noarch, for example, /usr/share/egroupware/emailadmin/inc/class.dbmaildbmailuser.inc.php (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 eGroupWare-filemanager-1.8-alt6.noarch, for example, /usr/share/egroupware/filemanager/cli.php (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 eGroupWare-importexport-1.8-alt6.noarch, for example, /usr/share/egroupware/importexport/doc/README_developers.txt (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 eGroupWare-infolog-1.8-alt6.noarch, for example, /usr/share/egroupware/infolog/inc/class.infolog_bo.inc.php (57 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package eGroupWare-manual-1.8-alt6.noarch, for example, /usr/share/egroupware/manual/inc/class.uimanual.inc.php (19 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package eGroupWare-news_admin-1.8-alt6.noarch, for example, /usr/share/egroupware/news_admin/doc/copyright.gpl (55 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package eGroupWare-notifications-1.8-alt6.noarch, for example, /usr/share/egroupware/notifications/inc/class.notifications.inc.php (30 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package eGroupWare-phpbrain-1.8-alt6.noarch, for example, /usr/share/egroupware/phpbrain/inc/class.bokb.inc.php (57 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package eGroupWare-projectmanager-1.8-alt6.noarch, for example, /usr/share/egroupware/projectmanager/inc/class.datasource.inc.php (62 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package eGroupWare-registration-1.8-alt6.noarch, for example, /usr/share/egroupware/registration/doc/README (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 eGroupWare-resources-1.8-alt6.noarch, for example, /usr/share/egroupware/resources/inc/class.bo_acl.inc.php (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 eGroupWare-sambaadmin-1.8-alt6.noarch, for example, /usr/share/egroupware/sambaadmin/inc/class.bosambaadmin.inc.php (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 eGroupWare-sitemgr-1.8-alt6.noarch, for example, /usr/share/egroupware/sitemgr/inc/class.ACL_BO.inc.php (268 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package eGroupWare-timesheet-1.8-alt6.noarch, for example, /usr/share/egroupware/timesheet/inc/class.timesheet_bo.inc.php (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 eGroupWare-tracker-1.8-alt6.noarch, for example, /usr/share/egroupware/tracker/inc/class.botracker.inc.php (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 eGroupWare-wiki-1.8-alt6.noarch, for example, /usr/share/egroupware/wiki/action/admin.php (82 file conflicts in 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	erubis-doc-2.7.0-alt2.noarch	File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-bundler-doc-1.16.2-alt2.M80P.1.noarch. Moreover, the packages have 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.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/ActionView/cdesc-ActionView.ri /usr/share/ri/site/ERB/cdesc-ERB.ri conflict with the package ruby-escape_utils-doc-1.2.1-alt0.M80P.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.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-hpricot-doc-0.8.6-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-json-pure-doc-2.1.0-alt0.M80P.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.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-polyglot-doc-0.3.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package yajl-ruby-doc-1.3.0-alt0.M80P.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	fcitx-4.2.7-alt2.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	flamegraph-20160128-alt1.noarch	File /usr/bin/flamegraph.pl conflicts with the package perl-Devel-NYTProf-6.03-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	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.0.M80P.3.x86_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	gasnet-doc-1.22.4-alt2.noarch	Files /usr/share/doc/gasnet/README-extref /usr/share/doc/gasnet/README-release conflict with the package berkeley_upc-docs-2.20.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	gd2-utils-2.0.35-alt6.x86_64	There are file conflicts with the package gd3-utils-2.2.5-alt2.M80P.1.x86_64, for example, /usr/bin/annotate (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.; File /usr/bin/bdftogd conflicts with the package perl-GD-2.56-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	gd3-utils-2.2.5-alt2.M80P.1.x86_64	There are file conflicts with the package gd2-utils-2.0.35-alt6.x86_64, for example, /usr/bin/annotate (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.; File /usr/bin/bdftogd conflicts with the package perl-GD-2.56-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	gdm-data-3.24.3-alt0.M80P.1.noarch	File /usr/share/pixmaps/nobody.png conflicts with the package mint-display-manager-1.0.8-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	geda-xgsch2pcb-0.1.3-alt1.noarch	Files /usr/lib/python2.7/site-packages/config.py /usr/lib/python2.7/site-packages/config.pyc /usr/lib/python2.7/site-packages/config.pyo conflict with the package python-module-config-0.3.7-alt2.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	glibc-devel-2.23-alt3.M80P.2.x86_64	Files /usr/include/rpcsvc/rquota.h /usr/include/rpcsvc/rquota.x conflict with the package quota-devel-4.03-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	glusterfs3-geo-replication-3.12.15-alt0.M80P.1.x86_64	There are file conflicts with the package glusterfs6-georeplication-6.3-alt2.M80P.3.x86_64, for example, /usr/lib/glusterfs/gsyncd (18 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	glusterfs6-georeplication-6.3-alt2.M80P.3.x86_64	There are file conflicts with the package glusterfs3-geo-replication-3.12.15-alt0.M80P.1.x86_64, for example, /usr/lib/glusterfs/gsyncd (18 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package glusterfs7-georeplication-7.4-alt0.M80P.1.x86_64, for example, /usr/lib/glusterfs/gverify.sh (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.; 
warn	glusterfs7-georeplication-7.4-alt0.M80P.1.x86_64	There are file conflicts with the package glusterfs6-georeplication-6.3-alt2.M80P.3.x86_64, for example, /usr/lib/glusterfs/gverify.sh (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.; 
warn	gnome-themes-accessibility-2.32.1-alt1.noarch	File /usr/share/themes/HighContrast/index.theme conflicts with the package gnome-themes-standard-data-3.22.3-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	gnome-themes-standard-data-3.22.3-alt0.M80P.1.noarch	File /usr/share/themes/HighContrast/index.theme conflicts with the package gnome-themes-accessibility-2.32.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/themes/HighContrast/gtk-2.0/gtkrc conflicts with the package gtk2-themes-accessibility-2.32.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/icons/HighContrast/index.theme conflicts with the package icon-themes-accessibility-2.32.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	gnu-efi-3.0r-3.0r-alt2.x86_64	There are file conflicts with the package gnu-efi-3.0u-3.0u-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	gnu-efi-3.0u-3.0u-alt3.x86_64	There are file conflicts with the package gnu-efi-3.0r-3.0r-alt2.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-quartzcore-0.1-alt3.svn20121018.x86_64	File /usr/bin/hello conflicts with the package hello-2.10-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	golang-tools-0-alt5.git78926538.x86_64	File /usr/bin/stress conflicts with the package stress-1.0.4-alt1.qa1.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	gperftools-2.6.3-alt1.x86_64	File /usr/bin/pprof conflicts with the package tau-2.23-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	gtk2-themes-accessibility-2.32.1-alt1.noarch	File /usr/share/themes/HighContrast/gtk-2.0/gtkrc conflicts with the package gnome-themes-standard-data-3.22.3-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	hadoop-yarn-2.4.1-alt2_14jpp8.noarch	File /usr/bin/yarn conflicts with the package cmdtest-0.16-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	hello-2.10-alt1.1.x86_64	File /usr/bin/hello conflicts with the package gnustep-quartzcore-0.1-alt3.svn20121018.x86_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	ht-2.0.22-alt1.1.x86_64	File /usr/bin/ht conflicts with the package tex4ht-1.0.2009_06_11_1038-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	hunspell-utils-1.6.2-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	icon-themes-accessibility-2.32.1-alt1.noarch	File /usr/share/icons/HighContrast/index.theme conflicts with the package gnome-themes-standard-data-3.22.3-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	inn-2.4.5-alt6.1.1.x86_64	File /usr/bin/sm conflicts with the package python-module-servicemanager-0.0.16-alt1.git20141007.1.noarch. Moreover, 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/sm /usr/share/man/man1/sm.1.gz conflict 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	installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch	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-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-backup-server-stage2-6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-centaurus-stage2-8.2-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit 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/preinstall.d/80-setup-user-groups conflict with the package installer-distro-cliff-stage2-8.0-alt0.M80P.1.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-desktop-stage2-5.0-alt23.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-junior-stage2-8.1-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit 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/installer-steps conflict with the package installer-distro-office-server-stage2-5.0-alt28.noarch. Moreover, the 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-8.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps /usr/share/install2/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-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-workbench-stage2-5.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-office-desktop-stage2-5.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-server-lite-stage2-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-server-stage2-0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch	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-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-backup-server-stage2-6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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-8.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 (4 file conflicts in 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.0-alt0.M80P.1.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-desktop-stage2-5.0-alt23.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-junior-stage2-8.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-lxdesktop-stage2-6.0-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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-office-server-stage2-5.0-alt28.noarch. Moreover, the 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-8.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-tablet-stage2-6.0-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-workbench-stage2-5.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-office-desktop-stage2-5.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-server-lite-stage2-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-server-stage2-0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-altlinux-server-stage2-7.0.2-alt1.noarch	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-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-backup-server-stage2-6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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-8.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 (4 file conflicts in 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-cliff-stage2-8.0-alt0.M80P.1.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-desktop-stage2-5.0-alt23.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-junior-stage2-8.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-lxdesktop-stage2-6.0-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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-office-server-stage2-5.0-alt28.noarch. Moreover, the 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-8.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-tablet-stage2-6.0-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-workbench-stage2-5.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/initinstall.d/05-vm-profile /usr/share/install2/installer-steps conflict with the package installer-office-desktop-stage2-5.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-server-lite-stage2-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/initinstall.d/05-vm-profile /usr/share/install2/installer-steps conflict with the package installer-server-stage2-0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-backup-server-stage2-6.0-alt1.noarch	Files /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-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-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-server-stage2-7.0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/20-alterator-menu.sh conflict with the package installer-distro-centaurus-stage2-8.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-chainmail-stage2-3.0.0-alt8.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/20-alterator-menu.sh conflict with the package installer-distro-cliff-stage2-8.0-alt0.M80P.1.noarch. Moreover, the 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-desktop-stage2-5.0-alt23.noarch. Moreover, the 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-junior-stage2-8.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/20-alterator-menu.sh conflict with the package installer-distro-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.; There are file conflicts with the package installer-distro-office-server-stage2-5.0-alt28.noarch, for example, /usr/share/install2/alterator-menu/module-order-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/20-alterator-menu.sh conflict with the package installer-distro-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.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/99-services.sh conflict with the package installer-distro-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/installer-steps conflicts with the package installer-distro-simply-linux-stage2-8.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/20-alterator-menu.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.; Files /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-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/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-workbench-stage2-5.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-office-desktop-stage2-5.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-server-lite-stage2-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-server-stage2-0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-centaurus-stage2-8.2-alt1.noarch	There are file conflicts with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-server-stage2-7.0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/20-alterator-menu.sh conflict with the package installer-distro-backup-server-stage2-6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-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/installer-steps /usr/share/install2/systemd-enabled conflict with the package installer-distro-cliff-stage2-8.0-alt0.M80P.1.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-desktop-stage2-5.0-alt23.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-junior-stage2-8.1-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-lxdesktop-stage2-6.0-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-office-server-stage2-5.0-alt28.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-school-server-stage2-7.0-alt9.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-server-light-stage2-8.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-simply-linux-stage2-8.3-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-tablet-stage2-6.0-alt3.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-workbench-stage2-5.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-office-desktop-stage2-5.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-server-lite-stage2-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-server-stage2-0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-chainmail-stage2-3.0.0-alt8.noarch	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.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-backup-server-stage2-6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-centaurus-stage2-8.2-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.0-alt0.M80P.1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-desktop-stage2-5.0-alt23.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-junior-stage2-8.1-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-lxdesktop-stage2-6.0-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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-office-server-stage2-5.0-alt28.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 (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-8.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-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-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-workbench-stage2-5.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-office-desktop-stage2-5.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-server-lite-stage2-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-server-stage2-0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-cliff-stage2-8.0-alt0.M80P.1.noarch	Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list conflict with the package installer-distro-altlinux-server-stage2-7.0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/20-alterator-menu.sh conflict with the package installer-distro-backup-server-stage2-6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/systemd-enabled conflict with the package installer-distro-centaurus-stage2-8.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.; There are file conflicts with the package installer-distro-desktop-stage2-5.0-alt23.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-junior-stage2-8.1-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-lxdesktop-stage2-6.0-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-office-server-stage2-5.0-alt28.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-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.; There are file conflicts with the package installer-distro-simply-linux-stage2-8.3-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-tablet-stage2-6.0-alt3.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-workbench-stage2-5.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-office-desktop-stage2-5.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-server-lite-stage2-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-server-stage2-0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-desktop-5.0-alt23.noarch	File /usr/share/install2/help/ru_RU/license.html conflicts with the package installer-server-0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/help/ru_RU/license.html conflicts with the package installer-server-lite-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-desktop-stage2-5.0-alt23.noarch	There are file conflicts with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-altlinux-server-stage2-7.0.2-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-backup-server-stage2-6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-centaurus-stage2-8.2-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-chainmail-stage2-3.0.0-alt8.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-cliff-stage2-8.0-alt0.M80P.1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-junior-stage2-8.1-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-lxdesktop-stage2-6.0-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-order-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-office-server-stage2-5.0-alt28.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-school-server-stage2-7.0-alt9.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-server-light-stage2-8.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-simply-linux-stage2-8.3-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-tablet-stage2-6.0-alt3.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/initinstall.d/05-vm-profile /usr/share/install2/installer-steps conflict with the package installer-distro-workbench-stage2-5.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-office-desktop-stage2-5.0-alt7.noarch, for example, /usr/share/install2/initinstall.d/05-vm-profile (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-server-lite-stage2-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/initinstall.d/05-vm-profile /usr/share/install2/installer-steps conflict with the package installer-server-stage2-0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-junior-8.1-alt1.noarch	File /usr/share/install2/help/ru_RU/license.html conflicts with the package installer-server-0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/help/ru_RU/license.html conflicts with the package installer-server-lite-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-junior-stage2-8.1-alt1.noarch	There are file conflicts with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-server-stage2-7.0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-backup-server-stage2-6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-centaurus-stage2-8.2-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-chainmail-stage2-3.0.0-alt8.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-cliff-stage2-8.0-alt0.M80P.1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-desktop-stage2-5.0-alt23.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-lxdesktop-stage2-6.0-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-office-server-stage2-5.0-alt28.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-school-server-stage2-7.0-alt9.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-server-light-stage2-8.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-simply-linux-stage2-8.3-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-tablet-stage2-6.0-alt3.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-workbench-stage2-5.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/postinstall.d/01-remove-installer-desktop-pkgs.sh /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-office-desktop-stage2-5.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-server-lite-stage2-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-server-stage2-0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-lxdesktop-6.0-alt5.noarch	File /usr/share/install2/help/ru_RU/license.html conflicts with the package installer-server-0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/help/ru_RU/license.html conflicts with the package installer-server-lite-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-lxdesktop-stage2-6.0-alt5.noarch	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.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/20-alterator-menu.sh conflict with the package installer-distro-backup-server-stage2-6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-centaurus-stage2-8.2-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; There are file conflicts with the package installer-distro-cliff-stage2-8.0-alt0.M80P.1.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-desktop-stage2-5.0-alt23.noarch, for example, /usr/share/install2/alterator-menu/module-order-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-junior-stage2-8.1-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-office-server-stage2-5.0-alt28.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-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-8.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-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-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-workbench-stage2-5.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-order-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-office-desktop-stage2-5.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-server-lite-stage2-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-server-stage2-0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-office-server-stage2-5.0-alt28.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-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.; There are file conflicts with the package installer-distro-backup-server-stage2-6.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-order-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-centaurus-stage2-8.2-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-chainmail-stage2-3.0.0-alt8.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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-cliff-stage2-8.0-alt0.M80P.1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-desktop-stage2-5.0-alt23.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-junior-stage2-8.1-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit 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 (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.; 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-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.; 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.; 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-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-workbench-stage2-5.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-office-desktop-stage2-5.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-server-lite-stage2-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-server-stage2-0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-school-server-stage2-7.0-alt9.noarch	Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list conflict with the package installer-distro-altlinux-server-stage2-7.0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/20-alterator-menu.sh conflict with the package installer-distro-backup-server-stage2-6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-centaurus-stage2-8.2-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-chainmail-stage2-3.0.0-alt8.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-cliff-stage2-8.0-alt0.M80P.1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-desktop-stage2-5.0-alt23.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-junior-stage2-8.1-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-lxdesktop-stage2-6.0-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-office-server-stage2-5.0-alt28.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-server-light-stage2-8.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-simply-linux-stage2-8.3-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-tablet-stage2-6.0-alt3.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-workbench-stage2-5.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-office-desktop-stage2-5.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-server-lite-stage2-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-server-stage2-0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-server-light-stage2-8.0-alt1.noarch	File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-server-stage2-7.0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/99-services.sh conflict with the package installer-distro-backup-server-stage2-6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-centaurus-stage2-8.2-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-chainmail-stage2-3.0.0-alt8.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-cliff-stage2-8.0-alt0.M80P.1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-desktop-stage2-5.0-alt23.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-junior-stage2-8.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-lxdesktop-stage2-6.0-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-office-server-stage2-5.0-alt28.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-school-server-stage2-7.0-alt9.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-simply-linux-stage2-8.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-distro-tablet-stage2-6.0-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-workbench-stage2-5.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-office-desktop-stage2-5.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-server-lite-stage2-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-server-stage2-0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-simply-linux-stage2-8.3-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-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.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-backup-server-stage2-6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-centaurus-stage2-8.2-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-chainmail-stage2-3.0.0-alt8.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-cliff-stage2-8.0-alt0.M80P.1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-desktop-stage2-5.0-alt23.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-junior-stage2-8.1-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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-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-skip-list /usr/share/install2/installer-steps conflict with the package installer-distro-office-server-stage2-5.0-alt28.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-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 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-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-workbench-stage2-5.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-desktop-pkgs.sh /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-office-desktop-stage2-5.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-server-lite-stage2-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-server-stage2-0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-tablet-stage2-6.0-alt3.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-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.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/20-alterator-menu.sh conflict with the package installer-distro-backup-server-stage2-6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-centaurus-stage2-8.2-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; There are file conflicts with the package installer-distro-cliff-stage2-8.0-alt0.M80P.1.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-desktop-stage2-5.0-alt23.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-junior-stage2-8.1-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-lxdesktop-stage2-6.0-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-office-server-stage2-5.0-alt28.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-school-server-stage2-7.0-alt9.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/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-8.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-token-desktop-stage2-0.1.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-workbench-stage2-5.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-office-desktop-stage2-5.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-server-lite-stage2-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-server-stage2-0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-token-desktop-live-0.1.1-alt2.noarch	File /usr/share/livecd-install/alterator-menu/module-expert-list conflicts with the package installer-feature-simply-livecd-0.8.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.; 
warn	installer-distro-token-desktop-stage2-0.1.1-alt2.noarch	File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-server-stage2-7.0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-backup-server-stage2-6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-centaurus-stage2-8.2-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-chainmail-stage2-3.0.0-alt8.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-cliff-stage2-8.0-alt0.M80P.1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-desktop-stage2-5.0-alt23.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-junior-stage2-8.1-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit 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/installer-steps conflict with the package installer-distro-office-server-stage2-5.0-alt28.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-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-8.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps /usr/share/install2/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.; There are file conflicts with the package installer-distro-workbench-stage2-5.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-office-desktop-stage2-5.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-server-lite-stage2-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-server-stage2-0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-workbench-5.0-alt2.noarch	File /usr/share/install2/help/ru_RU/license.html conflicts with the package installer-server-0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/help/ru_RU/license.html conflicts with the package installer-server-lite-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-workbench-stage2-5.0-alt2.noarch	There are file conflicts with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-altlinux-server-stage2-7.0.2-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-backup-server-stage2-6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-centaurus-stage2-8.2-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-chainmail-stage2-3.0.0-alt8.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-cliff-stage2-8.0-alt0.M80P.1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/initinstall.d/05-vm-profile /usr/share/install2/installer-steps conflict with the package installer-distro-desktop-stage2-5.0-alt23.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-junior-stage2-8.1-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-lxdesktop-stage2-6.0-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-order-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-office-server-stage2-5.0-alt28.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-school-server-stage2-7.0-alt9.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-server-light-stage2-8.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-simply-linux-stage2-8.3-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-tablet-stage2-6.0-alt3.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/initinstall.d/05-vm-profile /usr/share/install2/installer-steps conflict with the package installer-office-desktop-stage2-5.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-server-lite-stage2-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/initinstall.d/05-vm-profile /usr/share/install2/installer-steps conflict with the package installer-server-stage2-0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
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.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-powerbutton-stage3-0.2.1-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-0.8.11-alt1.noarch	File /usr/share/livecd-install/alterator-menu/module-expert-list conflicts with the package installer-distro-token-desktop-live-0.1.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
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-office-desktop-5.0-alt7.noarch	File /usr/share/install2/help/ru_RU/license.html conflicts with the package installer-server-0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/help/ru_RU/license.html conflicts with the package installer-server-lite-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-office-desktop-stage2-5.0-alt7.noarch	Files /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.; 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/initinstall.d/05-vm-profile /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.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-backup-server-stage2-6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-centaurus-stage2-8.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/installer-steps conflicts with the package installer-distro-chainmail-stage2-3.0.0-alt8.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-cliff-stage2-8.0-alt0.M80P.1.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-desktop-stage2-5.0-alt23.noarch, for example, /usr/share/install2/initinstall.d/05-vm-profile (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/postinstall.d/01-remove-installer-desktop-pkgs.sh /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-junior-stage2-8.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /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/installer-steps conflicts with the package installer-distro-office-server-stage2-5.0-alt28.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-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/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-desktop-pkgs.sh /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-simply-linux-stage2-8.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/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/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-token-desktop-stage2-0.1.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/initinstall.d/05-vm-profile /usr/share/install2/installer-steps conflict with the package installer-distro-workbench-stage2-5.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-server-lite-stage2-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/initinstall.d/05-vm-profile /usr/share/install2/installer-steps conflict with the package installer-server-stage2-0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-server-0.2-alt2.x86_64	File /usr/share/install2/help/ru_RU/license.html conflicts with the package installer-distro-desktop-5.0-alt23.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/help/ru_RU/license.html conflicts with the package installer-distro-junior-8.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/help/ru_RU/license.html conflicts with the package installer-distro-lxdesktop-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/help/ru_RU/license.html conflicts with the package installer-distro-workbench-5.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/help/ru_RU/license.html conflicts with the package installer-office-desktop-5.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/locale/ru/LC_MESSAGES/alterator-server.mo conflicts with the package installer-server-lite-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-server-lite-0.2-alt1.x86_64	File /usr/share/install2/help/ru_RU/license.html conflicts with the package installer-distro-desktop-5.0-alt23.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/help/ru_RU/license.html conflicts with the package installer-distro-junior-8.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/help/ru_RU/license.html conflicts with the package installer-distro-lxdesktop-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/help/ru_RU/license.html conflicts with the package installer-distro-workbench-5.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/help/ru_RU/license.html conflicts with the package installer-office-desktop-5.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/locale/ru/LC_MESSAGES/alterator-server.mo conflicts with the package installer-server-0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-server-lite-stage2-0.2-alt1.x86_64	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.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-backup-server-stage2-6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-distro-centaurus-stage2-8.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/installer-steps conflicts with the package installer-distro-chainmail-stage2-3.0.0-alt8.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-distro-cliff-stage2-8.0-alt0.M80P.1.noarch. Moreover, the 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-desktop-stage2-5.0-alt23.noarch. Moreover, the 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-junior-stage2-8.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts 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/installer-steps conflicts with the package installer-distro-office-server-stage2-5.0-alt28.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-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.; Files /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.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-simply-linux-stage2-8.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-distro-tablet-stage2-6.0-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-workbench-stage2-5.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-office-desktop-stage2-5.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-server-stage2-0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-server-lite-stage3-0.2-alt1.x86_64	File /usr/share/alterator/ui/server/finish.scm conflicts with the package installer-server-stage3-0.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-server-stage2-0.2-alt2.x86_64	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.; Files /usr/share/install2/initinstall.d/05-vm-profile /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.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-backup-server-stage2-6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-distro-centaurus-stage2-8.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/installer-steps conflicts with the package installer-distro-chainmail-stage2-3.0.0-alt8.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-distro-cliff-stage2-8.0-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/initinstall.d/05-vm-profile /usr/share/install2/installer-steps conflict with the package installer-distro-desktop-stage2-5.0-alt23.noarch. Moreover, the 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-junior-stage2-8.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts 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/installer-steps conflicts with the package installer-distro-office-server-stage2-5.0-alt28.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-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.; Files /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.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-simply-linux-stage2-8.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-distro-tablet-stage2-6.0-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/initinstall.d/05-vm-profile /usr/share/install2/installer-steps conflict with the package installer-distro-workbench-stage2-5.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/initinstall.d/05-vm-profile /usr/share/install2/installer-steps conflict with the package installer-office-desktop-stage2-5.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-server-lite-stage2-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-server-stage3-0.2-alt2.x86_64	File /usr/share/alterator/ui/server/finish.scm conflicts with the package installer-server-lite-stage3-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	ipset-6.32-alt1.M80P.1.x86_64	File /sbin/ipset conflicts with the package ipset6-6.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	ipset6-6.8-alt2.x86_64	File /sbin/ipset conflicts with the package ipset-6.32-alt1.M80P.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	jboss-as-vanilla-7.1.1-alt14.noarch	File /usr/bin/jboss-cli conflicts with the package wildfly-as-10.1.0-alt2.M80P.1.noarch. 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-1.3.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	js-1.7.0-alt7.x86_64	File /usr/bin/js conflicts with the package libmozjs38-tools-38.2.1-alt2.M80P.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	k3b-i18n-1.0.5-alt1.1.noarch	There are file conflicts with the package kde5-k3b-18.04.3-alt1.M80P.1.x86_64, for example, /usr/share/locale/ar/LC_MESSAGES/k3b.mo (119 file conflicts in 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	kde4edu-blinken-15.12.3-alt2.x86_64	There are file conflicts with the package kdeedu-blinken-3.5.13.2-alt2.1.1.x86_64, for example, /usr/bin/blinken (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	kde4edu-kalzium-15.12.3-alt2.x86_64	There are file conflicts with the package kdeedu-kalzium-3.5.13.2-alt2.1.1.x86_64, for example, /usr/bin/kalzium (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	kde4edu-kanagram-15.12.3-alt2.x86_64	There are file conflicts with the package kdeedu-kanagram-3.5.13.2-alt2.1.1.x86_64, for example, /usr/bin/kanagram (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	kde4edu-kbruch-15.12.3-alt2.x86_64	There are file conflicts with the package kdeedu-kbruch-3.5.13.2-alt2.1.1.x86_64, for example, /usr/bin/kbruch (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	kde4edu-kgeography-15.12.3-alt2.x86_64	There are file conflicts with the package kdeedu-kgeography-3.5.13.2-alt2.1.1.x86_64, for example, /usr/bin/kgeography (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	kde4edu-khangman-15.12.3-alt2.x86_64	There are file conflicts with the package kdeedu-khangman-3.5.13.2-alt2.1.1.x86_64, for example, /usr/bin/khangman (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	kde4edu-kig-15.12.3-alt2.x86_64	There are file conflicts with the package kdeedu-kig-3.5.13.2-alt2.1.1.x86_64, for example, /usr/bin/kig (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	kde4edu-kiten-15.12.3-alt2.x86_64	There are file conflicts with the package kdeedu-kiten-3.5.13.2-alt2.1.1.x86_64, for example, /usr/bin/kiten (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	kde4edu-klettres-15.12.3-alt2.x86_64	There are file conflicts with the package kdeedu-klettres-3.5.13.2-alt2.1.1.x86_64, for example, /usr/bin/klettres (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	kde4edu-kmplot-15.12.3-alt2.x86_64	There are file conflicts with the package kdeedu-kmplot-3.5.13.2-alt2.1.1.x86_64, for example, /usr/bin/kmplot (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	kde4edu-kstars-15.12.3-alt2.x86_64	There are file conflicts with the package kdeedu-kstars-3.5.13.2-alt2.1.1.x86_64, for example, /usr/bin/kstars (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	kde4edu-ktouch-15.12.3-alt2.x86_64	There are file conflicts with the package kdeedu-ktouch-3.5.13.2-alt2.1.1.x86_64, for example, /usr/bin/ktouch (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	kde4edu-kturtle-15.12.3-alt2.x86_64	Files /usr/bin/kturtle /usr/share/icons/hicolor/16x16/apps/kturtle.png /usr/share/icons/hicolor/32x32/apps/kturtle.png conflict with the package kdeedu-kturtle-3.5.13.2-alt2.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	kde4edu-kwordquiz-15.12.3-alt2.x86_64	There are file conflicts with the package kdeedu-kwordquiz-3.5.13.2-alt2.1.1.x86_64, for example, /usr/bin/kwordquiz (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	kde4games-devel-15.4.3-alt1.x86_64	Files /usr/lib64/libpala/pala-targets-release.cmake /usr/lib64/libpala/pala-targets.cmake conflict with the package kde5-palapeli-devel-18.04.3-alt1.M80P.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	kde4sdk-kapptemplate-15.12.2-alt1.x86_64	File /usr/share/kde4/apps/kdevappwizard/templates/qmake_qt4guiapp.tar.bz2 conflicts with the package kdevelop-qmake-1.6.60-alt1.git.x86_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	kde5-k3b-18.04.3-alt1.M80P.1.x86_64	There are file conflicts with the package k3b-i18n-1.0.5-alt1.1.noarch, for example, /usr/share/locale/ar/LC_MESSAGES/k3b.mo (119 file conflicts in 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	kde5-palapeli-devel-18.04.3-alt1.M80P.1.x86_64	Files /usr/lib64/libpala/pala-targets-release.cmake /usr/lib64/libpala/pala-targets.cmake conflict with the package kde4games-devel-15.4.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	kdeedu-blinken-3.5.13.2-alt2.1.1.x86_64	There are file conflicts with the package kde4edu-blinken-15.12.3-alt2.x86_64, for example, /usr/bin/blinken (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	kdeedu-kalzium-3.5.13.2-alt2.1.1.x86_64	There are file conflicts with the package kde4edu-kalzium-15.12.3-alt2.x86_64, for example, /usr/bin/kalzium (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	kdeedu-kanagram-3.5.13.2-alt2.1.1.x86_64	There are file conflicts with the package kde4edu-kanagram-15.12.3-alt2.x86_64, for example, /usr/bin/kanagram (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	kdeedu-kbruch-3.5.13.2-alt2.1.1.x86_64	There are file conflicts with the package kde4edu-kbruch-15.12.3-alt2.x86_64, for example, /usr/bin/kbruch (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	kdeedu-kgeography-3.5.13.2-alt2.1.1.x86_64	There are file conflicts with the package kde4edu-kgeography-15.12.3-alt2.x86_64, for example, /usr/bin/kgeography (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	kdeedu-khangman-3.5.13.2-alt2.1.1.x86_64	There are file conflicts with the package kde4edu-khangman-15.12.3-alt2.x86_64, for example, /usr/bin/khangman (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	kdeedu-kig-3.5.13.2-alt2.1.1.x86_64	There are file conflicts with the package kde4edu-kig-15.12.3-alt2.x86_64, for example, /usr/bin/kig (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	kdeedu-kiten-3.5.13.2-alt2.1.1.x86_64	There are file conflicts with the package kde4edu-kiten-15.12.3-alt2.x86_64, for example, /usr/bin/kiten (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	kdeedu-klettres-3.5.13.2-alt2.1.1.x86_64	There are file conflicts with the package kde4edu-klettres-15.12.3-alt2.x86_64, for example, /usr/bin/klettres (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	kdeedu-kmplot-3.5.13.2-alt2.1.1.x86_64	There are file conflicts with the package kde4edu-kmplot-15.12.3-alt2.x86_64, for example, /usr/bin/kmplot (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	kdeedu-kstars-3.5.13.2-alt2.1.1.x86_64	There are file conflicts with the package kde4edu-kstars-15.12.3-alt2.x86_64, for example, /usr/bin/kstars (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	kdeedu-ktouch-3.5.13.2-alt2.1.1.x86_64	There are file conflicts with the package kde4edu-ktouch-15.12.3-alt2.x86_64, for example, /usr/bin/ktouch (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	kdeedu-kturtle-3.5.13.2-alt2.1.1.x86_64	Files /usr/bin/kturtle /usr/share/icons/hicolor/16x16/apps/kturtle.png /usr/share/icons/hicolor/32x32/apps/kturtle.png conflict with the package kde4edu-kturtle-15.12.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	kdeedu-kwordquiz-3.5.13.2-alt2.1.1.x86_64	There are file conflicts with the package kde4edu-kwordquiz-15.12.3-alt2.x86_64, for example, /usr/bin/kwordquiz (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	kdenetwork-kopete-3.5.13.2-alt4.2.x86_64	File /usr/lib64/libkopete_videodevice.so.0.0.0 conflicts with the package libkopete_videodevice0-18.04.3-alt1.M80P.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	kdevelop-qmake-1.6.60-alt1.git.x86_64	File /usr/share/kde4/apps/kdevappwizard/templates/qmake_qt4guiapp.tar.bz2 conflicts with the package kde4sdk-kapptemplate-15.12.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-man-el-def-2.6.32-alt25.noarch	There are file conflicts with the package kernel-man-el7-def-3.10.0-alt9.noarch, for example, /usr/share/man/man9l/GetPortFacts.9.gz (1386 file conflicts in 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	kernel-man-el7-def-3.10.0-alt9.noarch	There are file conflicts with the package kernel-man-el-def-2.6.32-alt25.noarch, for example, /usr/share/man/man9l/GetPortFacts.9.gz (1386 file conflicts in 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	kernel-source-rtl8723de-4.10down-5.1.1.8-alt1.M80P.1.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.M80P.1.noarch. 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.M80P.1.noarch	File /usr/src/kernel/sources/kernel-source-rtl8723de-5.1.1.8.tar.bz2 conflicts with the package kernel-source-rtl8723de-4.10down-5.1.1.8-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libaccounts-qt5-devel-1.13-alt1_11.x86_64	There are file conflicts with the package accounts-qt5-devel-1.15-alt1.M80P.1.x86_64, for example, /usr/include/accounts-qt5/Accounts/account-service.h (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	libbobpp-devel-0.2.0-alt1.1.x86_64	File /usr/include/config.h conflicts with the package libpicosat-devel-960-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.; File /usr/include/config.h conflicts with the package openquicktime-devel-2.0.0-alt6.a1.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	libcdio++-0.94-alt0.M80P.1.x86_64	Files /usr/lib64/libcdio++.so.0.0.2 /usr/lib64/libiso9660++.so.0.0.0 conflict with the package libcdio12++-0.82-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	libcdio12++-0.82-alt3.x86_64	Files /usr/lib64/libcdio++.so.0.0.2 /usr/lib64/libiso9660++.so.0.0.0 conflict with the package libcdio++-0.94-alt0.M80P.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	libclipper-devel-6.2.1-alt1.x86_64	File /usr/include/polyclipping/clipper.hpp conflicts with the package libpolyclipping-devel-6.1.3a-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	libcpufreq-devel-008-alt1.1.x86_64	File /usr/include/cpufreq.h conflicts with the package libcpupower-devel-4.19-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libcpupower-devel-4.19-alt2.x86_64	File /usr/include/cpufreq.h conflicts with the package libcpufreq-devel-008-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	libdapl-1.2.16-alt2.x86_64	File /usr/share/man/man5/dat.conf.5.gz conflicts with the package dapl2-utils-2.0.30-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	libdbus-qt-devel-0.62-alt9.1.1.qa2.x86_64	There are file conflicts with the package libdbus-tqt-devel-3.5.13.2-alt1.1.x86_64, for example, /usr/include/dbus-1.0/dbus/connection.h (4 file conflicts in 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	libdbus-tqt-devel-3.5.13.2-alt1.1.x86_64	There are file conflicts with the package libdbus-qt-devel-0.62-alt9.1.1.qa2.x86_64, for example, /usr/include/dbus-1.0/dbus/connection.h (4 file conflicts in 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	libdispatch-objc2-devel-1.2-alt3.git20140226.x86_64	File /usr/share/man/man3/dispatch.3.gz conflicts with the package libnetcdf7-seq-doc-4.3.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libeo-devel-1.3.1-alt1.qa3.x86_64	File /usr/lib64/pkgconfig/eo.pc conflicts with the package efl-libs-devel-1.20.5-alt0.M80P.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	libfox-devel-1.6.46-alt3.qa1.x86_64	There are file conflicts with the package libfox1.7-devel-1.7.49-alt1.x86_64, for example, /usr/bin/fox-config (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	libfox-examples-1.6.46-alt3.qa1.x86_64	There are file conflicts with the package libfox1.7-examples-1.7.49-alt1.x86_64, for example, /usr/bin/PathFinder (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	libfox1.7-devel-1.7.49-alt1.x86_64	There are file conflicts with the package libfox-devel-1.6.46-alt3.qa1.x86_64, for example, /usr/bin/fox-config (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	libfox1.7-examples-1.7.49-alt1.x86_64	There are file conflicts with the package libfox-examples-1.6.46-alt3.qa1.x86_64, for example, /usr/bin/PathFinder (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	libftdi-docs-0.20-alt2.noarch	There are file conflicts with the package libftdi1-docs-1.0-alt1.noarch, for example, /usr/share/man/man3/Ftdi.3.gz (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	libftdi1-docs-1.0-alt1.noarch	There are file conflicts with the package libftdi-docs-0.20-alt2.noarch, for example, /usr/share/man/man3/Ftdi.3.gz (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	libgccjit5-devel-5.3.1-alt3.M80P.1.x86_64	Files /usr/include/libgccjit++.h /usr/include/libgccjit.h conflict with the package custom-libgccjit7-devel-7.3.1-alt8.M80P.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	libgnustep-gdl2-devel-0.12.0-alt5.svn20130819.1.x86_64	There are file conflicts with the package libsope-devel-3.2.10-alt1.M80P.1.x86_64, for example, /usr/include/EOControl/EOArrayDataSource.h (15 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
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	libgtest-devel-1.8.0-alt4.M80P.1.x86_64	File /usr/include/gtest/gtest.h conflicts with the package trilinos10-headers-11.12.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	libimlxx-devel-1.2a-alt2.noarch	File /usr/include/gmres.h conflicts with the package trilinos10-headers-11.12.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	libjpeg-utils-1.3.1-alt0.1.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	libjs-devel-1.7.0-alt7.x86_64	There are file conflicts with the package libmozjs-devel-1.8.5-alt2.x86_64, for example, /usr/include/js/js.msg (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	libkopete_videodevice0-18.04.3-alt1.M80P.1.x86_64	File /usr/lib64/libkopete_videodevice.so.0.0.0 conflicts with the package kdenetwork-kopete-3.5.13.2-alt4.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	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-alt1.git20150807.1.noarch	File /usr/share/man/man3/config.h.3.xz conflicts with the package libpgf-devel-6.14.12-alt1_5.x86_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	libm17n-db-1.6.2-alt1.noarch	There are file conflicts with the package m17n-db-1.3.3-alt0.1.noarch, for example, /usr/bin/m17n-db (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/m17n/am-sera.mim conflicts with the package m17n-db-amharic-1.3.3-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.; File /usr/share/m17n/ar-kbd.mim conflicts with the package m17n-db-arabic-1.3.3-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.; File /usr/share/m17n/hy-kbd.mim conflicts with the package m17n-db-armenian-1.3.3-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.; File /usr/share/m17n/as-itrans.mim conflicts with the package m17n-db-assamese-1.3.3-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.; File /usr/share/m17n/bn-itrans.mim conflicts with the package m17n-db-bengali-1.3.3-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.; There are file conflicts with the package m17n-db-chinese-1.3.3-alt0.1.noarch, for example, /usr/share/m17n/zh-cangjie.mim (10 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/m17n/cjk-util.mim conflicts with the package m17n-db-common-cjk-1.3.3-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.; File /usr/share/m17n/hr-kbd.mim conflicts with the package m17n-db-croatian-1.3.3-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.; There are file conflicts with the package m17n-db-datafiles-1.3.3-alt0.1.noarch, for example, /usr/share/m17n/ARAB-OTF-NO-GPOS.flt (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/m17n/dv-phonetic.mim conflicts with the package m17n-db-dhivehi-1.3.3-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.; File /usr/share/m17n/fa-isiri.mim conflicts with the package m17n-db-farsi-1.3.3-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.; Files /usr/share/m17n/rfc1345.mim /usr/share/m17n/unicode.mim conflict with the package m17n-db-generic-1.3.3-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.; File /usr/share/m17n/ka-kbd.mim conflicts with the package m17n-db-georgian-1.3.3-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.; File /usr/share/m17n/el-kbd.mim conflicts with the package m17n-db-greek-1.3.3-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.; File /usr/share/m17n/gu-itrans.mim conflicts with the package m17n-db-gujarati-1.3.3-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.; File /usr/share/m17n/he-kbd.mim conflicts with the package m17n-db-hebrew-1.3.3-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.; Files /usr/share/m17n/hi-itrans.mim /usr/share/m17n/hi-typewriter.mim /usr/share/m17n/icons/hi-typewriter.png conflict with the package m17n-db-hindi-1.3.3-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.; File /usr/share/m17n/ja-tcode.mim conflicts with the package m17n-db-japanese-1.3.3-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.; File /usr/share/m17n/kn-itrans.mim conflicts with the package m17n-db-kannada-1.3.3-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.; Files /usr/share/m17n/kk-arabic.mim /usr/share/m17n/kk-kbd.mim conflict with the package m17n-db-kazakh-1.3.3-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.; File /usr/share/m17n/km-yannis.mim conflicts with the package m17n-db-khmer-1.3.3-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.; Files /usr/share/m17n/ko-han2.mim /usr/share/m17n/ko-romaja.mim conflict with the package m17n-db-korean-1.3.3-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.; Files /usr/share/m17n/lo-kbd.mim /usr/share/m17n/lo-lrt.mim conflict with the package m17n-db-lao-1.3.3-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.; Files /usr/share/m17n/latn-post.mim /usr/share/m17n/latn-pre.mim conflict with the package m17n-db-latin-1.3.3-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.; File /usr/share/m17n/ml-itrans.mim conflicts with the package m17n-db-malayalam-1.3.3-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.; File /usr/share/m17n/my-kbd.mim conflicts with the package m17n-db-myanmar-1.3.3-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.; File /usr/share/m17n/or-itrans.mim conflicts with the package m17n-db-oriya-1.3.3-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.; File /usr/share/m17n/pa-itrans.mim conflicts with the package m17n-db-punjabi-1.3.3-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.; Files /usr/share/m17n/ru-kbd.mim /usr/share/m17n/ru-yawerty.mim conflict with the package m17n-db-russian-1.3.3-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.; File /usr/share/m17n/sr-kbd.mim conflicts with the package m17n-db-serbian-1.3.3-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.; There are file conflicts with the package m17n-db-sinhala-1.3.3-alt0.1.noarch, for example, /usr/share/m17n/icons/si-samanala.png (4 file conflicts in 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/m17n/sk-kbd.mim conflicts with the package m17n-db-slovak-1.3.3-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.; File /usr/share/m17n/sv-post.mim conflicts with the package m17n-db-swedish-1.3.3-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.; File /usr/share/m17n/syrc-phonetic.mim conflicts with the package m17n-db-syriac-1.3.3-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.; File /usr/share/m17n/ta-itrans.mim conflicts with the package m17n-db-tamil-1.3.3-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.; File /usr/share/m17n/te-itrans.mim conflicts with the package m17n-db-telugu-1.3.3-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.; File /usr/share/m17n/th-kesmanee.mim conflicts with the package m17n-db-thai-1.3.3-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.; File /usr/share/m17n/bo-wylie.mim conflicts with the package m17n-db-tibetan-1.3.3-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.; Files /usr/share/m17n/vi-telex.mim /usr/share/m17n/vi-viqr.mim /usr/share/m17n/vi-vni.mim conflict with the package m17n-db-vietnamese-1.3.3-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	libmozjs-devel-1.8.5-alt2.x86_64	There are file conflicts with the package libjs-devel-1.7.0-alt7.x86_64, for example, /usr/include/js/js.msg (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	libmozjs-tools-1.8.5-alt2.x86_64	File /usr/bin/js-config conflicts with the package libmozjs38-tools-38.2.1-alt2.M80P.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	libmozjs38-tools-38.2.1-alt2.M80P.1.x86_64	File /usr/bin/js conflicts with the package js-1.7.0-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.; File /usr/bin/js-config conflicts with the package libmozjs-tools-1.8.5-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	libmysqlclient-devel-10.1.48-alt1.x86_64	There are file conflicts with the package libmysqlclient20-devel-5.7.28-alt1.x86_64, for example, /usr/bin/mysql_config (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	libmysqlclient20-devel-5.7.28-alt1.x86_64	There are file conflicts with the package libmysqlclient-devel-10.1.48-alt1.x86_64, for example, /usr/bin/mysql_config (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	libnetcdf7-seq-doc-4.3.2-alt1.noarch	File /usr/share/man/man3/dispatch.3.gz conflicts with the package libdispatch-objc2-devel-1.2-alt3.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.; File /usr/share/man/man3/deprecated.3.gz conflicts with the package libqwt-devel-5.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	libnnti-devel-2.0-alt1.git20150304.x86_64	There are file conflicts with the package trilinos10-headers-11.12.1-alt2.x86_64, for example, /usr/include/Trios_config.h (4 file conflicts in 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	libnss-devel-static-3.45.0-alt0.M80P.1.x86_64	File /usr/lib64/libssl.a conflicts with the package libssl-devel-static-1.0.2u-alt0.M80P.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	libpgf-devel-6.14.12-alt1_5.x86_64	File /usr/share/man/man3/config.h.3.xz conflicts with the package liblog4cplus-devel-docs-2.0.0-alt1.git20150807.1.noarch. 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-960-alt2.1.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.; File /usr/include/config.h conflicts with the package openquicktime-devel-2.0.0-alt6.a1.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	libpolyclipping-devel-6.1.3a-alt1_2.x86_64	File /usr/include/polyclipping/clipper.hpp conflicts with the package libclipper-devel-6.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	libproxy-tools-0.4.14-alt0.M80P.1.x86_64	File /usr/bin/proxy conflicts with the package 3proxy-0.6.1-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	libqalculate-devel-0.9.7-alt2.2.x86_64	There are file conflicts with the package libqalculate4-devel-0.9.6-alt3.1.qa1.x86_64, for example, /usr/include/libqalculate/BuiltinFunctions.h (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	libqalculate4-devel-0.9.6-alt3.1.qa1.x86_64	There are file conflicts with the package libqalculate-devel-0.9.7-alt2.2.x86_64, for example, /usr/include/libqalculate/BuiltinFunctions.h (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	libquvi-devel-0.4.1-alt2.x86_64	File /usr/share/man/man3/libquvi.3.gz conflicts with the package libquvi0.9-devel-0.9.4-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libquvi0.9-devel-0.9.4-alt2.x86_64	File /usr/share/man/man3/libquvi.3.gz conflicts with the package libquvi-devel-0.4.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	libqwt-devel-5.2.3-alt1.x86_64	File /usr/share/man/man3/deprecated.3.gz conflicts with the package libnetcdf7-seq-doc-4.3.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libreadline-devel-6.3.8-alt2.x86_64	There are file conflicts with the package libreadline5-devel-5.2.14-alt5.1.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-6.3.8-alt2.x86_64	Files /usr/lib64/libhistory.a /usr/lib64/libreadline.a conflict with the package libreadline5-devel-static-5.2.14-alt5.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	libreadline5-devel-5.2.14-alt5.1.x86_64	There are file conflicts with the package libreadline-devel-6.3.8-alt2.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-alt5.1.x86_64	Files /usr/lib64/libhistory.a /usr/lib64/libreadline.a conflict with the package libreadline-devel-static-6.3.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	libshape-1.3.0b2-alt1.qa1.x86_64	File /usr/bin/dbfdump conflicts with the package perl-DBD-XBase-1.06-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	libsmbclient-devel-4.9.18-alt1.x86_64	File /usr/include/samba-4.0/libsmbclient.h conflicts with the package samba-DC-devel-4.9.18-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	libsope-devel-3.2.10-alt1.M80P.1.x86_64	There are file conflicts with the package libgnustep-gdl2-devel-0.12.0-alt5.svn20130819.1.x86_64, for example, /usr/include/EOControl/EOArrayDataSource.h (15 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
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	libssl-devel-static-1.0.2u-alt0.M80P.1.x86_64	File /usr/lib64/libssl.a conflicts with the package libnss-devel-static-3.45.0-alt0.M80P.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	libsx-2.17-alt1_4.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	libtau-common-2.23-alt2.x86_64	File /usr/include/opari2/pomp2_lib.h conflicts with the package opari2-devel-1.1.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	libtorque-devel-4.2.1-alt1.x86_64	File /usr/include/uthash.h conflicts with the package libuthash-devel-1.9.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	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	libuthash-devel-1.9.8-alt1.noarch	File /usr/include/uthash.h conflicts with the package libtorque-devel-4.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	libwps-tools-0.4.2-alt1.x86_64	Files /usr/bin/wks2raw /usr/bin/wks2text /usr/bin/wps2raw conflict with the package libwps3-tools-0.3.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	libwps3-tools-0.3.0-alt2.x86_64	Files /usr/bin/wks2raw /usr/bin/wks2text /usr/bin/wps2raw conflict with the package libwps-tools-0.4.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	libwxBase3.0-devel-3.0.4-alt2.M80P.3.x86_64	File /usr/share/aclocal/wxwin.m4 conflicts with the package libwxGTK3.1-gtk2-devel-3.1.0-alt1.20160229.x86_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	libwxGTK3.1-gtk2-devel-3.1.0-alt1.20160229.x86_64	File /usr/share/aclocal/wxwin.m4 conflicts with the package libwxBase3.0-devel-3.0.4-alt2.M80P.3.x86_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	libxcbutil-proto-1.12-alt1.noarch	File /usr/share/pkgconfig/xcb-proto.pc conflicts with the package xorg-xcbproto-devel-1.12-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	lightsquid-1.8-alt1.noarch	There are file conflicts with the package lightsquid-admin-1.8.0.1-alt2.13.noarch, for example, /etc/cron.d/lightsquid (45 file conflicts in 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	lightsquid-admin-1.8.0.1-alt2.13.noarch	There are file conflicts with the package lightsquid-1.8-alt1.noarch, for example, /etc/cron.d/lightsquid (45 file conflicts in 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	lightsquid-admin-apache-1.8.0.1-alt2.13.noarch	File /etc/httpd/conf/addon-modules.d/lightsquid.conf conflicts with the package lightsquid-apache-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	lightsquid-apache-1.8-alt1.noarch	File /etc/httpd/conf/addon-modules.d/lightsquid.conf conflicts with the package lightsquid-admin-apache-1.8.0.1-alt2.13.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	linux-atm-2.5.1-alt4.x86_64	Files /usr/sbin/br2684ctl /usr/share/man/man8/br2684ctl.8.gz conflict with the package br2684ctl-20040226-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	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-8.2-alt0.M80P.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 /etc/skel/.gconf/apps/%gconf.xml conflicts with the package branding-alt-tonk-xfce-settings-8.3-alt0.M80P.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.gconf/apps/%gconf.xml conflicts with the package branding-school-junior-xfce-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/.gconf/apps/%gconf.xml conflicts with the package branding-school-master-xfce-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/.gconf/apps/%gconf.xml conflicts with the package branding-school-server-xfce-settings-7.0.5-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.gconf/apps/%gconf.xml conflicts with the package branding-school-teacher-xfce-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.; 
warn	llvm-devel-3.8.0-alt0.M80P.1.x86_64	There are file conflicts with the package llvm4.0-devel-4.0.1-alt0.M80P.1.x86_64, for example, /usr/bin/llvm-config (598 file conflicts in 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	llvm-devel-static-3.8.0-alt0.M80P.1.x86_64	There are file conflicts with the package llvm4.0-devel-static-4.0.1-alt0.M80P.1.x86_64, for example, /usr/lib64/libLLVMAMDGPUAsmParser.a (53 file conflicts in 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	llvm4.0-devel-4.0.1-alt0.M80P.1.x86_64	There are file conflicts with the package llvm-devel-3.8.0-alt0.M80P.1.x86_64, for example, /usr/bin/llvm-config (598 file conflicts in 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	llvm4.0-devel-static-4.0.1-alt0.M80P.1.x86_64	There are file conflicts with the package llvm-devel-static-3.8.0-alt0.M80P.1.x86_64, for example, /usr/lib64/libLLVMAMDGPUAsmParser.a (53 file conflicts in 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	llvm4.0-libs-4.0.1-alt0.M80P.1.x86_64	File /usr/lib64/LLVMgold.so conflicts with the package llvm6.0-devel-6.0.0-alt0.6.M80P.1.rel.x86_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	llvm6.0-devel-6.0.0-alt0.6.M80P.1.rel.x86_64	File /usr/lib64/LLVMgold.so conflicts with the package llvm4.0-libs-4.0.1-alt0.M80P.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	m17n-db-1.3.3-alt0.1.noarch	There are file conflicts with the package libm17n-db-1.6.2-alt1.noarch, for example, /usr/bin/m17n-db (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	m17n-db-amharic-1.3.3-alt0.1.noarch	File /usr/share/m17n/am-sera.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-arabic-1.3.3-alt0.1.noarch	File /usr/share/m17n/ar-kbd.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-armenian-1.3.3-alt0.1.noarch	File /usr/share/m17n/hy-kbd.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-assamese-1.3.3-alt0.1.noarch	File /usr/share/m17n/as-itrans.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-bengali-1.3.3-alt0.1.noarch	File /usr/share/m17n/bn-itrans.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-chinese-1.3.3-alt0.1.noarch	There are file conflicts with the package libm17n-db-1.6.2-alt1.noarch, for example, /usr/share/m17n/zh-cangjie.mim (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	m17n-db-common-cjk-1.3.3-alt0.1.noarch	File /usr/share/m17n/cjk-util.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-croatian-1.3.3-alt0.1.noarch	File /usr/share/m17n/hr-kbd.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-datafiles-1.3.3-alt0.1.noarch	There are file conflicts with the package libm17n-db-1.6.2-alt1.noarch, for example, /usr/share/m17n/ARAB-OTF-NO-GPOS.flt (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	m17n-db-dhivehi-1.3.3-alt0.1.noarch	File /usr/share/m17n/dv-phonetic.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-farsi-1.3.3-alt0.1.noarch	File /usr/share/m17n/fa-isiri.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-generic-1.3.3-alt0.1.noarch	Files /usr/share/m17n/rfc1345.mim /usr/share/m17n/unicode.mim conflict with the package libm17n-db-1.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.; 
warn	m17n-db-georgian-1.3.3-alt0.1.noarch	File /usr/share/m17n/ka-kbd.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-greek-1.3.3-alt0.1.noarch	File /usr/share/m17n/el-kbd.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-gujarati-1.3.3-alt0.1.noarch	File /usr/share/m17n/gu-itrans.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-hebrew-1.3.3-alt0.1.noarch	File /usr/share/m17n/he-kbd.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-hindi-1.3.3-alt0.1.noarch	Files /usr/share/m17n/hi-itrans.mim /usr/share/m17n/hi-typewriter.mim /usr/share/m17n/icons/hi-typewriter.png conflict with the package libm17n-db-1.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.; 
warn	m17n-db-japanese-1.3.3-alt0.1.noarch	File /usr/share/m17n/ja-tcode.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-kannada-1.3.3-alt0.1.noarch	File /usr/share/m17n/kn-itrans.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-kazakh-1.3.3-alt0.1.noarch	Files /usr/share/m17n/kk-arabic.mim /usr/share/m17n/kk-kbd.mim conflict with the package libm17n-db-1.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.; 
warn	m17n-db-khmer-1.3.3-alt0.1.noarch	File /usr/share/m17n/km-yannis.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-korean-1.3.3-alt0.1.noarch	Files /usr/share/m17n/ko-han2.mim /usr/share/m17n/ko-romaja.mim conflict with the package libm17n-db-1.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.; 
warn	m17n-db-lao-1.3.3-alt0.1.noarch	Files /usr/share/m17n/lo-kbd.mim /usr/share/m17n/lo-lrt.mim conflict with the package libm17n-db-1.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.; 
warn	m17n-db-latin-1.3.3-alt0.1.noarch	Files /usr/share/m17n/latn-post.mim /usr/share/m17n/latn-pre.mim conflict with the package libm17n-db-1.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.; 
warn	m17n-db-malayalam-1.3.3-alt0.1.noarch	File /usr/share/m17n/ml-itrans.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-myanmar-1.3.3-alt0.1.noarch	File /usr/share/m17n/my-kbd.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-oriya-1.3.3-alt0.1.noarch	File /usr/share/m17n/or-itrans.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-punjabi-1.3.3-alt0.1.noarch	File /usr/share/m17n/pa-itrans.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-russian-1.3.3-alt0.1.noarch	Files /usr/share/m17n/ru-kbd.mim /usr/share/m17n/ru-yawerty.mim conflict with the package libm17n-db-1.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.; 
warn	m17n-db-serbian-1.3.3-alt0.1.noarch	File /usr/share/m17n/sr-kbd.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-sinhala-1.3.3-alt0.1.noarch	There are file conflicts with the package libm17n-db-1.6.2-alt1.noarch, for example, /usr/share/m17n/icons/si-samanala.png (4 file conflicts in 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	m17n-db-slovak-1.3.3-alt0.1.noarch	File /usr/share/m17n/sk-kbd.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-swedish-1.3.3-alt0.1.noarch	File /usr/share/m17n/sv-post.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-syriac-1.3.3-alt0.1.noarch	File /usr/share/m17n/syrc-phonetic.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-tamil-1.3.3-alt0.1.noarch	File /usr/share/m17n/ta-itrans.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-telugu-1.3.3-alt0.1.noarch	File /usr/share/m17n/te-itrans.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-thai-1.3.3-alt0.1.noarch	File /usr/share/m17n/th-kesmanee.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-tibetan-1.3.3-alt0.1.noarch	File /usr/share/m17n/bo-wylie.mim conflicts with the package libm17n-db-1.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.; 
warn	m17n-db-vietnamese-1.3.3-alt0.1.noarch	Files /usr/share/m17n/vi-telex.mim /usr/share/m17n/vi-viqr.mim /usr/share/m17n/vi-vni.mim conflict with the package libm17n-db-1.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.; 
warn	marsyas-0.6.0-alt1.alpha.git20150301.x86_64	File /usr/bin/aim conflicts with the package abinit-6.0.4-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.; File /usr/bin/sfinfo conflicts with the package audiofile-0.3.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.; File /usr/bin/record conflicts with the package xawtv4-common-4.0-alt3.git20081014.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	mate-document-viewer-dvi-1.12.2-alt1_1.x86_64	Files /usr/lib64/atril/3/backends/dvidocument.atril-backend /usr/lib64/atril/3/backends/libdvidocument.so conflict with the package atril-gtk-dvi-1.16.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	mate-document-viewer-thumbnailer-1.12.2-alt1_1.noarch	File /usr/share/thumbnailers/atril.thumbnailer conflicts with the package atril-gtk-1.16.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	maui-3.3-alt1.1.x86_64	File /usr/bin/mclient conflicts with the package monetdb-client-11.19.7-alt1.qa2.M80P.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/bin/mprof conflicts with the package python-module-memory_profiler-0.41-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	mediawiki-common-1.23.11-alt3.noarch	There are file conflicts with the package mediawiki-extensions-PdfHandler-1.23-alt1.noarch, for example, /usr/share/mediawiki/extensions/PdfHandler/PdfHandler.php (105 file conflicts in 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	mediawiki-extensions-Math-texvc-1.24-alt1.x86_64	Files /usr/bin/texvc /usr/bin/texvc_test /usr/bin/texvc_tex conflict with the package texvc-1.14.0-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	mediawiki-extensions-PdfHandler-1.23-alt1.noarch	There are file conflicts with the package mediawiki-common-1.23.11-alt3.noarch, for example, /usr/share/mediawiki/extensions/PdfHandler/PdfHandler.php (105 file conflicts in 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	mingw32-iconv-1.12-alt2.noarch	Files /usr/i586-pc-mingw32/sys-root/mingw/include/iconv.h /usr/i586-pc-mingw32/sys-root/mingw/lib/libiconv.dll.a conflict with the package mingw32-win-iconv-0.0.3-alt1_4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	mingw32-iconv-static-1.12-alt2.noarch	File /usr/i586-pc-mingw32/sys-root/mingw/lib/libiconv.a conflicts with the package mingw32-win-iconv-static-0.0.3-alt1_4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	mingw32-win-iconv-0.0.3-alt1_4.noarch	Files /usr/i586-pc-mingw32/sys-root/mingw/include/iconv.h /usr/i586-pc-mingw32/sys-root/mingw/lib/libiconv.dll.a conflict with the package mingw32-iconv-1.12-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	mingw32-win-iconv-static-0.0.3-alt1_4.noarch	File /usr/i586-pc-mingw32/sys-root/mingw/lib/libiconv.a conflicts with the package mingw32-iconv-static-1.12-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	mini_httpd-htpasswd-1.19-alt2.x86_64	Files /usr/bin/htpasswd /usr/share/man/man1/htpasswd.1.gz conflict with the package apache-common-1.3.42rusPL30.24-alt8.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/bin/htpasswd conflicts with the package apache2-htpasswd-2.4.43-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	mint-display-manager-1.0.8-alt1.2.x86_64	File /usr/share/pixmaps/nobody.png conflicts with the package gdm-data-3.24.3-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	monetdb-client-11.19.7-alt1.qa2.M80P.1.x86_64	File /usr/bin/mclient conflicts with the package maui-3.3-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	mono-core-5.20.1.19-alt0.M80P.2.x86_64	File /usr/bin/csc conflicts with the package chicken-4.1.0-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	mono-devel-5.20.1.19-alt0.M80P.2.x86_64	File /usr/bin/csi conflicts with the package chicken-4.1.0-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	moodle-apache2-1.9.19.20130513-alt1.noarch	File /etc/httpd2/conf/include/Directory_moodle_default.conf conflicts with the package moodle3.3-apache2-3.3.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	moodle-auth-pam-1.9.19.2007101592.05.0.20130513-alt1.noarch	File /var/www/webapps/moodle/auth/pam/auth.php conflicts with the package moodle3.3-auth-pam-3.3.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	moodle-base-1.9.19.20130513-alt1.noarch	There are file conflicts with the package moodle3.3-base-3.3.1-alt0.M80P.1.noarch, for example, /var/www/webapps/moodle/COPYING.txt (1427 file conflicts in 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	moodle2.0-apache2-2.0.10.20120706-alt3.noarch	File /etc/httpd2/conf/include/Directory_moodle_default.conf conflicts with the package moodle3.3-apache2-3.3.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	moodle2.0-auth-pam-2.0.0.2009112400.0.20120706-alt3.noarch	There are file conflicts with the package moodle3.3-auth-pam-3.3.1-alt0.M80P.1.noarch, for example, /var/www/webapps/moodle/auth/pam/auth.php (4 file conflicts in 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	moodle2.0-mod-book-2.0.0.20111008-alt3.noarch	There are file conflicts with the package moodle3.3-base-3.3.1-alt0.M80P.1.noarch, for example, /var/www/webapps/moodle/mod/book/backup/moodle1/lib.php (24 file conflicts in 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	moodle2.1-apache2-2.1.10.20130114-alt2.noarch	File /etc/httpd2/conf/include/Directory_moodle_default.conf conflicts with the package moodle3.3-apache2-3.3.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	moodle2.1-auth-pam-2.1.0.2009112400.0.20130114-alt2.noarch	There are file conflicts with the package moodle3.3-auth-pam-3.3.1-alt0.M80P.1.noarch, for example, /var/www/webapps/moodle/auth/pam/auth.php (4 file conflicts in 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	moodle2.1-mod-book-2.1.0.20111105-alt2.noarch	There are file conflicts with the package moodle3.3-base-3.3.1-alt0.M80P.1.noarch, for example, /var/www/webapps/moodle/mod/book/README.md (58 file conflicts in 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	moodle2.2-apache2-2.2.10.20130704-alt1.noarch	File /etc/httpd2/conf/include/Directory_moodle_default.conf conflicts with the package moodle3.3-apache2-3.3.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	moodle2.2-auth-pam-2.2.0.2011112900.0.20130704-alt1.noarch	There are file conflicts with the package moodle3.3-auth-pam-3.3.1-alt0.M80P.1.noarch, for example, /var/www/webapps/moodle/auth/pam/auth.php (4 file conflicts in 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	moodle2.4-apache2-2.4.11.20140714-alt1.noarch	File /etc/httpd2/conf/include/Directory_moodle_default.conf conflicts with the package moodle3.3-apache2-3.3.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	moodle2.4-auth-pam-2.4.0.2012112900.0.20140714-alt1.noarch	Files /var/www/webapps/moodle/auth/pam/auth.php /var/www/webapps/moodle/auth/pam/lang/en/auth_pam.php /var/www/webapps/moodle/auth/pam/version.php conflict with the package moodle3.3-auth-pam-3.3.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	moodle2.5-apache2-2.5.9.20141110-alt1.noarch	File /etc/httpd2/conf/include/Directory_moodle_default.conf conflicts with the package moodle3.3-apache2-3.3.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	moodle2.5-auth-pam-2.5.0.2013050100.0.20141110-alt1.noarch	Files /var/www/webapps/moodle/auth/pam/auth.php /var/www/webapps/moodle/auth/pam/lang/en/auth_pam.php conflict with the package moodle3.3-auth-pam-3.3.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	moodle3.3-apache2-3.3.1-alt0.M80P.1.noarch	File /etc/httpd2/conf/include/Directory_moodle_default.conf conflicts with the package moodle-apache2-1.9.19.20130513-alt1.noarch. 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/httpd2/conf/include/Directory_moodle_default.conf conflicts with the package moodle2.0-apache2-2.0.10.20120706-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/httpd2/conf/include/Directory_moodle_default.conf conflicts with the package moodle2.1-apache2-2.1.10.20130114-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/httpd2/conf/include/Directory_moodle_default.conf conflicts with the package moodle2.2-apache2-2.2.10.20130704-alt1.noarch. 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/httpd2/conf/include/Directory_moodle_default.conf conflicts with the package moodle2.4-apache2-2.4.11.20140714-alt1.noarch. 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/httpd2/conf/include/Directory_moodle_default.conf conflicts with the package moodle2.5-apache2-2.5.9.20141110-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	moodle3.3-auth-pam-3.3.1-alt0.M80P.1.noarch	File /var/www/webapps/moodle/auth/pam/auth.php conflicts with the package moodle-auth-pam-1.9.19.2007101592.05.0.20130513-alt1.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 moodle2.0-auth-pam-2.0.0.2009112400.0.20120706-alt3.noarch, for example, /var/www/webapps/moodle/auth/pam/auth.php (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package moodle2.1-auth-pam-2.1.0.2009112400.0.20130114-alt2.noarch, for example, /var/www/webapps/moodle/auth/pam/auth.php (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package moodle2.2-auth-pam-2.2.0.2011112900.0.20130704-alt1.noarch, for example, /var/www/webapps/moodle/auth/pam/auth.php (4 file conflicts in 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 /var/www/webapps/moodle/auth/pam/auth.php /var/www/webapps/moodle/auth/pam/lang/en/auth_pam.php /var/www/webapps/moodle/auth/pam/version.php conflict with the package moodle2.4-auth-pam-2.4.0.2012112900.0.20140714-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /var/www/webapps/moodle/auth/pam/auth.php /var/www/webapps/moodle/auth/pam/lang/en/auth_pam.php conflict with the package moodle2.5-auth-pam-2.5.0.2013050100.0.20141110-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	moodle3.3-base-3.3.1-alt0.M80P.1.noarch	There are file conflicts with the package moodle-base-1.9.19.20130513-alt1.noarch, for example, /var/www/webapps/moodle/COPYING.txt (1427 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package moodle2.0-mod-book-2.0.0.20111008-alt3.noarch, for example, /var/www/webapps/moodle/mod/book/backup/moodle1/lib.php (24 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package moodle2.1-mod-book-2.1.0.20111105-alt2.noarch, for example, /var/www/webapps/moodle/mod/book/README.md (58 file conflicts in 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	msv-xmlgen-2013.6.1-alt1_7jpp8.noarch	File /usr/bin/xmlgen conflicts with the package openpdt-3.17-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	mysql-utilities-1.6.1-alt1.noarch	File /usr/bin/mysqldiff conflicts with the package mysqldiff-0.43-alt1.noarch. 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.43-alt1.noarch	File /usr/bin/mysqldiff conflicts with the package mysql-utilities-1.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	nx-3.5.1-alt16.M80P.1.x86_64	Files /etc/nxagent/nxagent.keyboard /usr/bin/nxagent conflict with the package nxagent-3.5.2.31-alt6.M80P.8.x86_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	nxagent-3.5.2.31-alt6.M80P.8.x86_64	Files /etc/nxagent/nxagent.keyboard /usr/bin/nxagent conflict with the package nx-3.5.1-alt16.M80P.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	obexftp-0.24.2-alt2.0.M80P.3.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	ohai-doc-8.7.0-alt1.noarch	Files /usr/share/ri/site/Chef/cdesc-Chef.ri /usr/share/ri/site/Mash/cdesc-Mash.ri conflict with the package chef-doc-12.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/Chef/cdesc-Chef.ri conflicts with the package ruby-chef-sugar-doc-3.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri conflicts with the package ruby-dalli-doc-2.7.6-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Plist/cdesc-Plist.ri /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri conflict with the package ruby-facter-doc-2.0.1-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Plist/cdesc-Plist.ri conflicts with the package ruby-plist-doc-3.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Sigar/cdesc-Sigar.ri conflicts with the package ruby-sigar-doc-0.7.3-alt1.2.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri conflicts with the package ruby-spoon-doc-0.0.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	opari2-devel-1.1.2-alt1.x86_64	File /usr/include/opari2/pomp2_lib.h conflicts with the package libtau-common-2.23-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	opencascade-6.8.0-alt1.x86_64	File /usr/bin/DRAWEXE conflicts with the package OCE-draw-0.18.3-alt0.M80P.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	openpdt-3.17-alt2.x86_64	File /usr/bin/xmlgen conflicts with the package msv-xmlgen-2013.6.1-alt1_7jpp8.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	openquicktime-devel-2.0.0-alt6.a1.1.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.; File /usr/include/config.h conflicts with the package libpicosat-devel-960-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.; File /usr/include/plugin.h conflicts with the package python-module-gist-2.2.0-alt2.git20130422.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	owncloud-3rdparty-7.0.4-alt1.noarch	There are file conflicts with the package owncloud8-3rdparty-8.0.9-alt1.noarch, for example, /var/www/webapps/owncloud/3rdparty/composer.json (362 file conflicts in 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	owncloud-apps-7.0.4-alt1.noarch	There are file conflicts with the package owncloud8-apps-8.0.9-alt1.noarch, for example, /var/www/webapps/owncloud/apps/external/ajax/setsites.php (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	owncloud8-3rdparty-8.0.9-alt1.noarch	There are file conflicts with the package owncloud-3rdparty-7.0.4-alt1.noarch, for example, /var/www/webapps/owncloud/3rdparty/composer.json (362 file conflicts in 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	owncloud8-apps-8.0.9-alt1.noarch	There are file conflicts with the package owncloud-apps-7.0.4-alt1.noarch, for example, /var/www/webapps/owncloud/apps/external/ajax/setsites.php (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	parmetis-4.0.3-alt1.x86_64	File /usr/bin/mtest conflicts with the package pine-4.64L-alt8.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/bin/ptest conflicts with the package python-module-ptest-1.3.0-alt1.git20150813.1.noarch. 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	pear-XML_Util-1.2.3-alt1.noarch	File /usr/share/php/pear/XML/Util.php conflicts with the package pear-core-1.10.1-alt0.M80P.1.noarch. 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-core-1.10.1-alt0.M80P.1.noarch	File /usr/share/php/pear/XML/Util.php conflicts with the package pear-XML_Util-1.2.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	perl-DBD-XBase-1.06-alt1.x86_64	File /usr/bin/dbfdump conflicts with the package libshape-1.3.0b2-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	perl-Devel-NYTProf-6.03-alt1.x86_64	File /usr/bin/flamegraph.pl conflicts with the package flamegraph-20160128-alt1.noarch. 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-GD-2.56-alt1.1.x86_64	File /usr/bin/bdftogd conflicts with the package gd2-utils-2.0.35-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/bdftogd conflicts with the package gd3-utils-2.2.5-alt2.M80P.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-Primality-scripts-0.08-alt2.noarch	File /usr/bin/primes.pl conflicts with the package perl-Math-Prime-Util-scripts-0.57-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	perl-Math-Prime-Util-scripts-0.57-alt1.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-Module-Release-scripts-2.122-alt1.noarch	File /usr/bin/release conflicts with the package python-module-zest.releaser-3.55-alt1.dev0.git20141229.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	perl-pip-1.19-alt1.noarch	File /usr/bin/pip conflicts with the package python-module-pip-10.0.1-alt1.M80P.1.noarch. 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-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	pine-4.64L-alt8.2.x86_64	File /usr/bin/mtest conflicts with the package parmetis-4.0.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	pks-db-0.9.6-alt1.qa1.x86_64	There are file conflicts with the package db4.7-utils-4.7.25-alt8.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-alt1.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-alt1.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-alt1.qa1.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 python-module-rasterio-0.26.0-alt1.git20150811.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	postgre-etersoft9.6-9.6.1.2-alt1.M80P.2.x86_64	There are file conflicts with the package postgresql10-10.17-alt0.M80P.1.x86_64, for example, /usr/bin/clusterdb (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 postgresql11-11.12-alt0.M80P.1.x86_64, for example, /usr/bin/clusterdb (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 postgresql11-1C-11.12-alt0.M80P.1.x86_64, for example, /usr/bin/clusterdb (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 postgresql12-12.7-alt0.M80P.1.x86_64, for example, /usr/bin/clusterdb (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 postgresql9.1-9.1.24-alt0.M80P.3.x86_64, for example, /usr/bin/clusterdb (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 postgresql9.3-9.3.25-alt0.M80P.2.x86_64, for example, /usr/bin/clusterdb (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 postgresql9.4-9.4.26-alt0.M80P.1.x86_64, for example, /usr/bin/clusterdb (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 postgresql9.5-9.5.25-alt0.M80P.1.x86_64, for example, /usr/bin/clusterdb (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 postgresql9.6-9.6.22-alt0.M80P.1.x86_64, for example, /usr/bin/clusterdb (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	postgre-etersoft9.6-contrib-9.6.1.2-alt1.M80P.2.x86_64	Files /usr/bin/oid2name /usr/bin/pgbench /usr/bin/vacuumlo conflict with the package postgresql10-contrib-10.17-alt0.M80P.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/bin/oid2name /usr/bin/pgbench /usr/bin/vacuumlo conflict with the package postgresql11-1C-contrib-11.12-alt0.M80P.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/bin/oid2name /usr/bin/pgbench /usr/bin/vacuumlo conflict with the package postgresql11-contrib-11.12-alt0.M80P.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/bin/oid2name /usr/bin/pgbench /usr/bin/vacuumlo conflict with the package postgresql12-contrib-12.7-alt0.M80P.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/bin/oid2name /usr/bin/pgbench /usr/bin/vacuumlo conflict with the package postgresql9.1-contrib-9.1.24-alt0.M80P.3.x86_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/oid2name /usr/bin/pgbench /usr/bin/vacuumlo conflict with the package postgresql9.3-contrib-9.3.25-alt0.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/bin/oid2name /usr/bin/pgbench /usr/bin/vacuumlo conflict with the package postgresql9.4-contrib-9.4.26-alt0.M80P.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/bin/oid2name /usr/bin/pgbench /usr/bin/vacuumlo conflict with the package postgresql9.5-contrib-9.5.25-alt0.M80P.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/bin/oid2name /usr/bin/vacuumlo conflict with the package postgresql9.6-contrib-9.6.22-alt0.M80P.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	postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.2.x86_64	File /etc/sysconfig/postgresql conflicts with the package postgresql-common-1.0-alt8.noarch. Moreover, 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/pg_isready /usr/bin/pg_recvlogical /usr/bin/pg_test_timing conflict with the package postgresql10-10.17-alt0.M80P.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/bin/pg_archivecleanup /usr/bin/pg_standby conflict with the package postgresql10-contrib-10.17-alt0.M80P.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 postgresql10-server-10.17-alt0.M80P.1.x86_64, for example, /etc/rc.d/init.d/postgresql (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.; Files /usr/bin/pg_isready /usr/bin/pg_recvlogical /usr/bin/pg_test_timing conflict with the package postgresql11-11.12-alt0.M80P.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/bin/pg_isready /usr/bin/pg_recvlogical /usr/bin/pg_test_timing conflict with the package postgresql11-1C-11.12-alt0.M80P.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/bin/pg_archivecleanup /usr/bin/pg_standby conflict with the package postgresql11-1C-contrib-11.12-alt0.M80P.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 postgresql11-1C-server-11.12-alt0.M80P.1.x86_64, for example, /etc/rc.d/init.d/postgresql (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/bin/pg_archivecleanup /usr/bin/pg_standby conflict with the package postgresql11-contrib-11.12-alt0.M80P.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 postgresql11-server-11.12-alt0.M80P.1.x86_64, for example, /etc/rc.d/init.d/postgresql (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/bin/pg_isready /usr/bin/pg_recvlogical /usr/bin/pg_test_timing conflict with the package postgresql12-12.7-alt0.M80P.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/bin/pg_archivecleanup /usr/bin/pg_standby conflict with the package postgresql12-contrib-12.7-alt0.M80P.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-server-12.7-alt0.M80P.1.x86_64, for example, /etc/rc.d/init.d/postgresql (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/bin/pg_archivecleanup /usr/bin/pg_standby conflict with the package postgresql9.1-contrib-9.1.24-alt0.M80P.3.x86_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 postgresql9.1-server-9.1.24-alt0.M80P.3.x86_64, for example, /etc/rc.d/init.d/postgresql (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/bin/pg_isready /usr/bin/pg_test_timing conflict with the package postgresql9.3-9.3.25-alt0.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/bin/pg_archivecleanup /usr/bin/pg_standby /usr/bin/pg_xlogdump conflict with the package postgresql9.3-contrib-9.3.25-alt0.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql9.3-server-9.3.25-alt0.M80P.2.x86_64, for example, /etc/rc.d/init.d/postgresql (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.; Files /usr/bin/pg_isready /usr/bin/pg_recvlogical conflict with the package postgresql9.4-9.4.26-alt0.M80P.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/bin/pg_archivecleanup /usr/bin/pg_standby /usr/bin/pg_xlogdump conflict with the package postgresql9.4-contrib-9.4.26-alt0.M80P.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 postgresql9.4-server-9.4.26-alt0.M80P.1.x86_64, for example, /etc/rc.d/init.d/postgresql (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.; Files /usr/bin/pg_isready /usr/bin/pg_recvlogical conflict with the package postgresql9.5-9.5.25-alt0.M80P.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/bin/pg_standby /usr/bin/pg_xlogdump conflict with the package postgresql9.5-contrib-9.5.25-alt0.M80P.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 postgresql9.5-server-9.5.25-alt0.M80P.1.x86_64, for example, /etc/rc.d/init.d/postgresql (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.; Files /usr/bin/pg_isready /usr/bin/pg_recvlogical conflict with the package postgresql9.6-9.6.22-alt0.M80P.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/bin/pg_standby conflicts with the package postgresql9.6-contrib-9.6.22-alt0.M80P.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 postgresql9.6-server-9.6.22-alt0.M80P.1.x86_64, for example, /etc/rc.d/init.d/postgresql (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	postgresql-common-1.0-alt8.noarch	File /etc/sysconfig/postgresql conflicts with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.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	postgresql10-10.17-alt0.M80P.1.x86_64	There are file conflicts with the package postgre-etersoft9.6-9.6.1.2-alt1.M80P.2.x86_64, for example, /usr/bin/clusterdb (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.; Files /usr/bin/pg_isready /usr/bin/pg_recvlogical /usr/bin/pg_test_timing conflict with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.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	postgresql10-contrib-10.17-alt0.M80P.1.x86_64	Files /usr/bin/oid2name /usr/bin/pgbench /usr/bin/vacuumlo conflict with the package postgre-etersoft9.6-contrib-9.6.1.2-alt1.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/bin/pg_archivecleanup /usr/bin/pg_standby conflict with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql11-1C-contrib-11.12-alt0.M80P.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.; File /usr/lib64/pgsql/ltree_plpython2.so conflicts with the package postgresql11-1C-python-11.12-alt0.M80P.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 postgresql11-contrib-11.12-alt0.M80P.1.x86_64, for example, /usr/bin/pgbench (28 file conflicts in total). Moreover, the packages have no explicit 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.7-alt0.M80P.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.1-contrib-9.1.24-alt0.M80P.3.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.3-contrib-9.3.25-alt0.M80P.2.x86_64, for example, /usr/bin/oid2name (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 postgresql9.4-contrib-9.4.26-alt0.M80P.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.; There are file conflicts with the package postgresql9.5-contrib-9.5.25-alt0.M80P.1.x86_64, for example, /usr/bin/pg_archivecleanup (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.6-contrib-9.6.22-alt0.M80P.1.x86_64, for example, /usr/bin/pg_archivecleanup (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.; 
warn	postgresql10-perl-10.17-alt0.M80P.1.x86_64	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql11-1C-perl-11.12-alt0.M80P.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.12-alt0.M80P.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 postgresql12-perl-12.7-alt0.M80P.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 postgresql9.1-perl-9.1.24-alt0.M80P.3.x86_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.3-perl-9.3.25-alt0.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.4-perl-9.4.26-alt0.M80P.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 postgresql9.5-perl-9.5.25-alt0.M80P.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 postgresql9.6-perl-9.6.22-alt0.M80P.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.17-alt0.M80P.1.x86_64	File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql11-1C-python-11.12-alt0.M80P.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.12-alt0.M80P.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 postgresql12-python-12.7-alt0.M80P.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 postgresql9.1-python-9.1.24-alt0.M80P.3.x86_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.3-python-9.3.25-alt0.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.4-python-9.4.26-alt0.M80P.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 postgresql9.5-python-9.5.25-alt0.M80P.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 postgresql9.6-python-9.6.22-alt0.M80P.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.17-alt0.M80P.1.x86_64	There are file conflicts with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.2.x86_64, for example, /etc/rc.d/init.d/postgresql (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	postgresql10-tcl-10.17-alt0.M80P.1.x86_64	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql11-1C-tcl-11.12-alt0.M80P.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.12-alt0.M80P.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 postgresql12-tcl-12.7-alt0.M80P.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 postgresql9.1-tcl-9.1.24-alt0.M80P.3.x86_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.3-tcl-9.3.25-alt0.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.4-tcl-9.4.26-alt0.M80P.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 postgresql9.5-tcl-9.5.25-alt0.M80P.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 postgresql9.6-tcl-9.6.22-alt0.M80P.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-11.12-alt0.M80P.1.x86_64	There are file conflicts with the package postgre-etersoft9.6-9.6.1.2-alt1.M80P.2.x86_64, for example, /usr/bin/clusterdb (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.; Files /usr/bin/pg_isready /usr/bin/pg_recvlogical /usr/bin/pg_test_timing conflict with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.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	postgresql11-1C-11.12-alt0.M80P.1.x86_64	There are file conflicts with the package postgre-etersoft9.6-9.6.1.2-alt1.M80P.2.x86_64, for example, /usr/bin/clusterdb (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.; Files /usr/bin/pg_isready /usr/bin/pg_recvlogical /usr/bin/pg_test_timing conflict with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.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	postgresql11-1C-contrib-11.12-alt0.M80P.1.x86_64	Files /usr/bin/oid2name /usr/bin/pgbench /usr/bin/vacuumlo conflict with the package postgre-etersoft9.6-contrib-9.6.1.2-alt1.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/bin/pg_archivecleanup /usr/bin/pg_standby conflict with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql10-contrib-10.17-alt0.M80P.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.7-alt0.M80P.1.x86_64, for example, /usr/bin/oid2name (28 file conflicts in total). Moreover, the packages have no explicit 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.1-contrib-9.1.24-alt0.M80P.3.x86_64, for example, /usr/bin/oid2name (34 file conflicts in total). Moreover, the packages have no explicit 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.3-contrib-9.3.25-alt0.M80P.2.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.4-contrib-9.4.26-alt0.M80P.1.x86_64, for example, /usr/bin/oid2name (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 postgresql9.5-contrib-9.5.25-alt0.M80P.1.x86_64, for example, /usr/bin/pg_archivecleanup (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 postgresql9.6-contrib-9.6.22-alt0.M80P.1.x86_64, for example, /usr/bin/pg_archivecleanup (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-1C-perl-11.12-alt0.M80P.1.x86_64	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql10-perl-10.17-alt0.M80P.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 postgresql9.1-perl-9.1.24-alt0.M80P.3.x86_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.3-perl-9.3.25-alt0.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.4-perl-9.4.26-alt0.M80P.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/hstore_plperl.so conflicts with the package postgresql9.5-contrib-9.5.25-alt0.M80P.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 postgresql9.5-perl-9.5.25-alt0.M80P.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/hstore_plperl.so conflicts with the package postgresql9.6-contrib-9.6.22-alt0.M80P.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 postgresql9.6-perl-9.6.22-alt0.M80P.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-1C-python-11.12-alt0.M80P.1.x86_64	File /usr/lib64/pgsql/ltree_plpython2.so conflicts with the package postgresql10-contrib-10.17-alt0.M80P.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 postgresql10-python-10.17-alt0.M80P.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 postgresql12-python-12.7-alt0.M80P.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 postgresql9.1-python-9.1.24-alt0.M80P.3.x86_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.3-python-9.3.25-alt0.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.4-python-9.4.26-alt0.M80P.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/lib64/pgsql/hstore_plpython2.so /usr/lib64/pgsql/ltree_plpython2.so conflict with the package postgresql9.5-contrib-9.5.25-alt0.M80P.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 postgresql9.5-python-9.5.25-alt0.M80P.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/lib64/pgsql/hstore_plpython2.so /usr/lib64/pgsql/ltree_plpython2.so conflict with the package postgresql9.6-contrib-9.6.22-alt0.M80P.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 postgresql9.6-python-9.6.22-alt0.M80P.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-1C-server-11.12-alt0.M80P.1.x86_64	There are file conflicts with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.2.x86_64, for example, /etc/rc.d/init.d/postgresql (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	postgresql11-1C-tcl-11.12-alt0.M80P.1.x86_64	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql10-tcl-10.17-alt0.M80P.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 postgresql9.1-tcl-9.1.24-alt0.M80P.3.x86_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.3-tcl-9.3.25-alt0.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.4-tcl-9.4.26-alt0.M80P.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 postgresql9.5-tcl-9.5.25-alt0.M80P.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 postgresql9.6-tcl-9.6.22-alt0.M80P.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.12-alt0.M80P.1.x86_64	Files /usr/bin/oid2name /usr/bin/pgbench /usr/bin/vacuumlo conflict with the package postgre-etersoft9.6-contrib-9.6.1.2-alt1.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/bin/pg_archivecleanup /usr/bin/pg_standby conflict with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql10-contrib-10.17-alt0.M80P.1.x86_64, for example, /usr/bin/pgbench (28 file conflicts in total). Moreover, the packages have no explicit 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.7-alt0.M80P.1.x86_64, for example, /usr/bin/oid2name (28 file conflicts in total). Moreover, the packages have no explicit 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.1-contrib-9.1.24-alt0.M80P.3.x86_64, for example, /usr/bin/oid2name (34 file conflicts in total). Moreover, the packages have no explicit 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.3-contrib-9.3.25-alt0.M80P.2.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.4-contrib-9.4.26-alt0.M80P.1.x86_64, for example, /usr/bin/oid2name (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 postgresql9.5-contrib-9.5.25-alt0.M80P.1.x86_64, for example, /usr/bin/pg_archivecleanup (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.6-contrib-9.6.22-alt0.M80P.1.x86_64, for example, /usr/bin/pg_archivecleanup (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.; 
warn	postgresql11-perl-11.12-alt0.M80P.1.x86_64	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql10-perl-10.17-alt0.M80P.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 postgresql9.1-perl-9.1.24-alt0.M80P.3.x86_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.3-perl-9.3.25-alt0.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.4-perl-9.4.26-alt0.M80P.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 postgresql9.5-perl-9.5.25-alt0.M80P.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 postgresql9.6-perl-9.6.22-alt0.M80P.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-python-11.12-alt0.M80P.1.x86_64	File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql10-python-10.17-alt0.M80P.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 postgresql12-python-12.7-alt0.M80P.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 postgresql9.1-python-9.1.24-alt0.M80P.3.x86_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.3-python-9.3.25-alt0.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.4-python-9.4.26-alt0.M80P.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 postgresql9.5-python-9.5.25-alt0.M80P.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 postgresql9.6-python-9.6.22-alt0.M80P.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.12-alt0.M80P.1.x86_64	There are file conflicts with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.2.x86_64, for example, /etc/rc.d/init.d/postgresql (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	postgresql11-tcl-11.12-alt0.M80P.1.x86_64	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql10-tcl-10.17-alt0.M80P.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 postgresql9.1-tcl-9.1.24-alt0.M80P.3.x86_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.3-tcl-9.3.25-alt0.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.4-tcl-9.4.26-alt0.M80P.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 postgresql9.5-tcl-9.5.25-alt0.M80P.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 postgresql9.6-tcl-9.6.22-alt0.M80P.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-12.7-alt0.M80P.1.x86_64	There are file conflicts with the package postgre-etersoft9.6-9.6.1.2-alt1.M80P.2.x86_64, for example, /usr/bin/clusterdb (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.; Files /usr/bin/pg_isready /usr/bin/pg_recvlogical /usr/bin/pg_test_timing conflict with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.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	postgresql12-contrib-12.7-alt0.M80P.1.x86_64	Files /usr/bin/oid2name /usr/bin/pgbench /usr/bin/vacuumlo conflict with the package postgre-etersoft9.6-contrib-9.6.1.2-alt1.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/bin/pg_archivecleanup /usr/bin/pg_standby conflict with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql10-contrib-10.17-alt0.M80P.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-1C-contrib-11.12-alt0.M80P.1.x86_64, for example, /usr/bin/oid2name (28 file conflicts in total). Moreover, the packages have no explicit 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.12-alt0.M80P.1.x86_64, for example, /usr/bin/oid2name (28 file conflicts in total). Moreover, the packages have no explicit 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.1-contrib-9.1.24-alt0.M80P.3.x86_64, for example, /usr/bin/oid2name (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 postgresql9.3-contrib-9.3.25-alt0.M80P.2.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.4-contrib-9.4.26-alt0.M80P.1.x86_64, for example, /usr/bin/oid2name (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 postgresql9.5-contrib-9.5.25-alt0.M80P.1.x86_64, for example, /usr/bin/oid2name (45 file conflicts in total). Moreover, the packages have no explicit 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.22-alt0.M80P.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.; 
warn	postgresql12-perl-12.7-alt0.M80P.1.x86_64	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql10-perl-10.17-alt0.M80P.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 postgresql9.1-perl-9.1.24-alt0.M80P.3.x86_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.3-perl-9.3.25-alt0.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.4-perl-9.4.26-alt0.M80P.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 postgresql9.5-perl-9.5.25-alt0.M80P.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 postgresql9.6-perl-9.6.22-alt0.M80P.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-python-12.7-alt0.M80P.1.x86_64	File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql10-python-10.17-alt0.M80P.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-1C-python-11.12-alt0.M80P.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.12-alt0.M80P.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 postgresql9.1-python-9.1.24-alt0.M80P.3.x86_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.3-python-9.3.25-alt0.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.4-python-9.4.26-alt0.M80P.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 postgresql9.5-python-9.5.25-alt0.M80P.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 postgresql9.6-python-9.6.22-alt0.M80P.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-server-12.7-alt0.M80P.1.x86_64	There are file conflicts with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.2.x86_64, for example, /etc/rc.d/init.d/postgresql (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	postgresql12-tcl-12.7-alt0.M80P.1.x86_64	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql10-tcl-10.17-alt0.M80P.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 postgresql9.1-tcl-9.1.24-alt0.M80P.3.x86_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.3-tcl-9.3.25-alt0.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.4-tcl-9.4.26-alt0.M80P.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 postgresql9.5-tcl-9.5.25-alt0.M80P.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 postgresql9.6-tcl-9.6.22-alt0.M80P.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.1-9.1.24-alt0.M80P.3.x86_64	There are file conflicts with the package postgre-etersoft9.6-9.6.1.2-alt1.M80P.2.x86_64, for example, /usr/bin/clusterdb (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.; 
warn	postgresql9.1-contrib-9.1.24-alt0.M80P.3.x86_64	Files /usr/bin/oid2name /usr/bin/pgbench /usr/bin/vacuumlo conflict with the package postgre-etersoft9.6-contrib-9.6.1.2-alt1.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/bin/pg_archivecleanup /usr/bin/pg_standby conflict with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql10-contrib-10.17-alt0.M80P.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 postgresql11-1C-contrib-11.12-alt0.M80P.1.x86_64, for example, /usr/bin/oid2name (34 file conflicts in total). Moreover, the packages have no explicit 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.12-alt0.M80P.1.x86_64, for example, /usr/bin/oid2name (34 file conflicts in total). Moreover, the packages have no explicit 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.7-alt0.M80P.1.x86_64, for example, /usr/bin/oid2name (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 postgresql9.3-contrib-9.3.25-alt0.M80P.2.x86_64, for example, /usr/bin/pg_archivecleanup (19 file conflicts in total). Moreover, the packages have no explicit 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-alt0.M80P.1.x86_64, for example, /usr/bin/oid2name (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 postgresql9.5-contrib-9.5.25-alt0.M80P.1.x86_64, for example, /usr/bin/oid2name (29 file conflicts in total). Moreover, the packages have no explicit 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.22-alt0.M80P.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.; 
warn	postgresql9.1-perl-9.1.24-alt0.M80P.3.x86_64	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql10-perl-10.17-alt0.M80P.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-1C-perl-11.12-alt0.M80P.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.12-alt0.M80P.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 postgresql12-perl-12.7-alt0.M80P.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 postgresql9.3-perl-9.3.25-alt0.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.4-perl-9.4.26-alt0.M80P.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 postgresql9.5-perl-9.5.25-alt0.M80P.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 postgresql9.6-perl-9.6.22-alt0.M80P.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.1-python-9.1.24-alt0.M80P.3.x86_64	File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql10-python-10.17-alt0.M80P.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-1C-python-11.12-alt0.M80P.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.12-alt0.M80P.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 postgresql12-python-12.7-alt0.M80P.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 postgresql9.3-python-9.3.25-alt0.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.4-python-9.4.26-alt0.M80P.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 postgresql9.5-python-9.5.25-alt0.M80P.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 postgresql9.6-python-9.6.22-alt0.M80P.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.1-server-9.1.24-alt0.M80P.3.x86_64	There are file conflicts with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.2.x86_64, for example, /etc/rc.d/init.d/postgresql (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	postgresql9.1-tcl-9.1.24-alt0.M80P.3.x86_64	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql10-tcl-10.17-alt0.M80P.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-1C-tcl-11.12-alt0.M80P.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.12-alt0.M80P.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 postgresql12-tcl-12.7-alt0.M80P.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/bin/pltcl_listmod /usr/bin/pltcl_loadmod conflict with the package postgresql9.4-tcl-9.4.26-alt0.M80P.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/bin/pltcl_listmod /usr/bin/pltcl_loadmod conflict with the package postgresql9.5-tcl-9.5.25-alt0.M80P.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/bin/pltcl_listmod /usr/bin/pltcl_loadmod /usr/lib64/pgsql/pltcl.so conflict with the package postgresql9.6-tcl-9.6.22-alt0.M80P.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.3-9.3.25-alt0.M80P.2.x86_64	There are file conflicts with the package postgre-etersoft9.6-9.6.1.2-alt1.M80P.2.x86_64, for example, /usr/bin/clusterdb (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.; Files /usr/bin/pg_isready /usr/bin/pg_test_timing conflict with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.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	postgresql9.3-contrib-9.3.25-alt0.M80P.2.x86_64	Files /usr/bin/oid2name /usr/bin/pgbench /usr/bin/vacuumlo conflict with the package postgre-etersoft9.6-contrib-9.6.1.2-alt1.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/bin/pg_archivecleanup /usr/bin/pg_standby /usr/bin/pg_xlogdump conflict with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql10-contrib-10.17-alt0.M80P.1.x86_64, for example, /usr/bin/oid2name (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 postgresql11-1C-contrib-11.12-alt0.M80P.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.12-alt0.M80P.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 postgresql12-contrib-12.7-alt0.M80P.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 postgresql9.1-contrib-9.1.24-alt0.M80P.3.x86_64, for example, /usr/bin/pg_archivecleanup (19 file conflicts in total). Moreover, the packages have no explicit 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-alt0.M80P.1.x86_64, for example, /usr/bin/oid2name (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 postgresql9.5-contrib-9.5.25-alt0.M80P.1.x86_64, for example, /usr/bin/oid2name (28 file conflicts in total). Moreover, the packages have no explicit 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.22-alt0.M80P.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.; 
warn	postgresql9.3-perl-9.3.25-alt0.M80P.2.x86_64	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql10-perl-10.17-alt0.M80P.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-1C-perl-11.12-alt0.M80P.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.12-alt0.M80P.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 postgresql12-perl-12.7-alt0.M80P.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 postgresql9.1-perl-9.1.24-alt0.M80P.3.x86_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-alt0.M80P.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 postgresql9.6-perl-9.6.22-alt0.M80P.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.3-python-9.3.25-alt0.M80P.2.x86_64	File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql10-python-10.17-alt0.M80P.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-1C-python-11.12-alt0.M80P.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.12-alt0.M80P.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 postgresql12-python-12.7-alt0.M80P.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 postgresql9.1-python-9.1.24-alt0.M80P.3.x86_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-alt0.M80P.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 postgresql9.6-python-9.6.22-alt0.M80P.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.3-server-9.3.25-alt0.M80P.2.x86_64	There are file conflicts with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.2.x86_64, for example, /etc/rc.d/init.d/postgresql (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	postgresql9.3-tcl-9.3.25-alt0.M80P.2.x86_64	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql10-tcl-10.17-alt0.M80P.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-1C-tcl-11.12-alt0.M80P.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.12-alt0.M80P.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 postgresql12-tcl-12.7-alt0.M80P.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/bin/pltcl_listmod /usr/bin/pltcl_loadmod conflict with the package postgresql9.4-tcl-9.4.26-alt0.M80P.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/bin/pltcl_listmod /usr/bin/pltcl_loadmod conflict with the package postgresql9.5-tcl-9.5.25-alt0.M80P.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/bin/pltcl_listmod /usr/bin/pltcl_loadmod /usr/lib64/pgsql/pltcl.so conflict with the package postgresql9.6-tcl-9.6.22-alt0.M80P.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-9.4.26-alt0.M80P.1.x86_64	There are file conflicts with the package postgre-etersoft9.6-9.6.1.2-alt1.M80P.2.x86_64, for example, /usr/bin/clusterdb (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.; Files /usr/bin/pg_isready /usr/bin/pg_recvlogical conflict with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.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	postgresql9.4-contrib-9.4.26-alt0.M80P.1.x86_64	Files /usr/bin/oid2name /usr/bin/pgbench /usr/bin/vacuumlo conflict with the package postgre-etersoft9.6-contrib-9.6.1.2-alt1.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/bin/pg_archivecleanup /usr/bin/pg_standby /usr/bin/pg_xlogdump conflict with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql10-contrib-10.17-alt0.M80P.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.; There are file conflicts with the package postgresql11-1C-contrib-11.12-alt0.M80P.1.x86_64, for example, /usr/bin/oid2name (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 postgresql11-contrib-11.12-alt0.M80P.1.x86_64, for example, /usr/bin/oid2name (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 postgresql12-contrib-12.7-alt0.M80P.1.x86_64, for example, /usr/bin/oid2name (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 postgresql9.1-contrib-9.1.24-alt0.M80P.3.x86_64, for example, /usr/bin/oid2name (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 postgresql9.3-contrib-9.3.25-alt0.M80P.2.x86_64, for example, /usr/bin/oid2name (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 postgresql9.5-contrib-9.5.25-alt0.M80P.1.x86_64, for example, /usr/bin/oid2name (28 file conflicts in total). Moreover, the packages have no explicit 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.22-alt0.M80P.1.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.; 
warn	postgresql9.4-perl-9.4.26-alt0.M80P.1.x86_64	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql10-perl-10.17-alt0.M80P.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-1C-perl-11.12-alt0.M80P.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.12-alt0.M80P.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 postgresql12-perl-12.7-alt0.M80P.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 postgresql9.1-perl-9.1.24-alt0.M80P.3.x86_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-alt0.M80P.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 postgresql9.6-perl-9.6.22-alt0.M80P.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-alt0.M80P.1.x86_64	File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql10-python-10.17-alt0.M80P.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-1C-python-11.12-alt0.M80P.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.12-alt0.M80P.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 postgresql12-python-12.7-alt0.M80P.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 postgresql9.1-python-9.1.24-alt0.M80P.3.x86_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-alt0.M80P.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 postgresql9.6-python-9.6.22-alt0.M80P.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-alt0.M80P.1.x86_64	There are file conflicts with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.2.x86_64, for example, /etc/rc.d/init.d/postgresql (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	postgresql9.4-tcl-9.4.26-alt0.M80P.1.x86_64	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql10-tcl-10.17-alt0.M80P.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-1C-tcl-11.12-alt0.M80P.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.12-alt0.M80P.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 postgresql12-tcl-12.7-alt0.M80P.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/bin/pltcl_listmod /usr/bin/pltcl_loadmod conflict with the package postgresql9.1-tcl-9.1.24-alt0.M80P.3.x86_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/pltcl_listmod /usr/bin/pltcl_loadmod conflict with the package postgresql9.3-tcl-9.3.25-alt0.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.6-tcl-9.6.22-alt0.M80P.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-9.5.25-alt0.M80P.1.x86_64	There are file conflicts with the package postgre-etersoft9.6-9.6.1.2-alt1.M80P.2.x86_64, for example, /usr/bin/clusterdb (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.; Files /usr/bin/pg_isready /usr/bin/pg_recvlogical conflict with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.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	postgresql9.5-contrib-9.5.25-alt0.M80P.1.x86_64	Files /usr/bin/oid2name /usr/bin/pgbench /usr/bin/vacuumlo conflict with the package postgre-etersoft9.6-contrib-9.6.1.2-alt1.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/bin/pg_standby /usr/bin/pg_xlogdump conflict with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql10-contrib-10.17-alt0.M80P.1.x86_64, for example, /usr/bin/pg_archivecleanup (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 postgresql11-1C-contrib-11.12-alt0.M80P.1.x86_64, for example, /usr/bin/pg_archivecleanup (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.; File /usr/lib64/pgsql/hstore_plperl.so conflicts with the package postgresql11-1C-perl-11.12-alt0.M80P.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/lib64/pgsql/hstore_plpython2.so /usr/lib64/pgsql/ltree_plpython2.so conflict with the package postgresql11-1C-python-11.12-alt0.M80P.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 postgresql11-contrib-11.12-alt0.M80P.1.x86_64, for example, /usr/bin/pg_archivecleanup (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-contrib-12.7-alt0.M80P.1.x86_64, for example, /usr/bin/oid2name (45 file conflicts in total). Moreover, the packages have no explicit 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.1-contrib-9.1.24-alt0.M80P.3.x86_64, for example, /usr/bin/oid2name (29 file conflicts in total). Moreover, the packages have no explicit 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.3-contrib-9.3.25-alt0.M80P.2.x86_64, for example, /usr/bin/oid2name (28 file conflicts in total). Moreover, the packages have no explicit 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-alt0.M80P.1.x86_64, for example, /usr/bin/oid2name (28 file conflicts in total). Moreover, the packages have no explicit 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.22-alt0.M80P.1.x86_64, for example, /usr/bin/pg_xlogdump (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.; 
warn	postgresql9.5-perl-9.5.25-alt0.M80P.1.x86_64	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql10-perl-10.17-alt0.M80P.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-1C-perl-11.12-alt0.M80P.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.12-alt0.M80P.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 postgresql12-perl-12.7-alt0.M80P.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 postgresql9.1-perl-9.1.24-alt0.M80P.3.x86_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.3-perl-9.3.25-alt0.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.4-perl-9.4.26-alt0.M80P.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-alt0.M80P.1.x86_64	File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql10-python-10.17-alt0.M80P.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-1C-python-11.12-alt0.M80P.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.12-alt0.M80P.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 postgresql12-python-12.7-alt0.M80P.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 postgresql9.1-python-9.1.24-alt0.M80P.3.x86_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.3-python-9.3.25-alt0.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.4-python-9.4.26-alt0.M80P.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 postgresql9.6-python-9.6.22-alt0.M80P.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-alt0.M80P.1.x86_64	There are file conflicts with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.2.x86_64, for example, /etc/rc.d/init.d/postgresql (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	postgresql9.5-tcl-9.5.25-alt0.M80P.1.x86_64	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql10-tcl-10.17-alt0.M80P.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-1C-tcl-11.12-alt0.M80P.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.12-alt0.M80P.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 postgresql12-tcl-12.7-alt0.M80P.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/bin/pltcl_listmod /usr/bin/pltcl_loadmod conflict with the package postgresql9.1-tcl-9.1.24-alt0.M80P.3.x86_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/pltcl_listmod /usr/bin/pltcl_loadmod conflict with the package postgresql9.3-tcl-9.3.25-alt0.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.6-tcl-9.6.22-alt0.M80P.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-9.6.22-alt0.M80P.1.x86_64	There are file conflicts with the package postgre-etersoft9.6-9.6.1.2-alt1.M80P.2.x86_64, for example, /usr/bin/clusterdb (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.; Files /usr/bin/pg_isready /usr/bin/pg_recvlogical conflict with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.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	postgresql9.6-contrib-9.6.22-alt0.M80P.1.x86_64	Files /usr/bin/oid2name /usr/bin/vacuumlo conflict with the package postgre-etersoft9.6-contrib-9.6.1.2-alt1.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/bin/pg_standby conflicts with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql10-contrib-10.17-alt0.M80P.1.x86_64, for example, /usr/bin/pg_archivecleanup (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 postgresql11-1C-contrib-11.12-alt0.M80P.1.x86_64, for example, /usr/bin/pg_archivecleanup (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.; File /usr/lib64/pgsql/hstore_plperl.so conflicts with the package postgresql11-1C-perl-11.12-alt0.M80P.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/lib64/pgsql/hstore_plpython2.so /usr/lib64/pgsql/ltree_plpython2.so conflict with the package postgresql11-1C-python-11.12-alt0.M80P.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 postgresql11-contrib-11.12-alt0.M80P.1.x86_64, for example, /usr/bin/pg_archivecleanup (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-contrib-12.7-alt0.M80P.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.1-contrib-9.1.24-alt0.M80P.3.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.3-contrib-9.3.25-alt0.M80P.2.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-alt0.M80P.1.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.5-contrib-9.5.25-alt0.M80P.1.x86_64, for example, /usr/bin/pg_xlogdump (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.; 
warn	postgresql9.6-perl-9.6.22-alt0.M80P.1.x86_64	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql10-perl-10.17-alt0.M80P.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-1C-perl-11.12-alt0.M80P.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.12-alt0.M80P.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 postgresql12-perl-12.7-alt0.M80P.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 postgresql9.1-perl-9.1.24-alt0.M80P.3.x86_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.3-perl-9.3.25-alt0.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.4-perl-9.4.26-alt0.M80P.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-python-9.6.22-alt0.M80P.1.x86_64	File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql10-python-10.17-alt0.M80P.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-1C-python-11.12-alt0.M80P.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.12-alt0.M80P.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 postgresql12-python-12.7-alt0.M80P.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 postgresql9.1-python-9.1.24-alt0.M80P.3.x86_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.3-python-9.3.25-alt0.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.4-python-9.4.26-alt0.M80P.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 postgresql9.5-python-9.5.25-alt0.M80P.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-server-9.6.22-alt0.M80P.1.x86_64	There are file conflicts with the package postgre-etersoft9.6-server-9.6.1.2-alt1.M80P.2.x86_64, for example, /etc/rc.d/init.d/postgresql (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	postgresql9.6-tcl-9.6.22-alt0.M80P.1.x86_64	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql10-tcl-10.17-alt0.M80P.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-1C-tcl-11.12-alt0.M80P.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.12-alt0.M80P.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 postgresql12-tcl-12.7-alt0.M80P.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/bin/pltcl_listmod /usr/bin/pltcl_loadmod /usr/lib64/pgsql/pltcl.so conflict with the package postgresql9.1-tcl-9.1.24-alt0.M80P.3.x86_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/pltcl_listmod /usr/bin/pltcl_loadmod /usr/lib64/pgsql/pltcl.so conflict with the package postgresql9.3-tcl-9.3.25-alt0.M80P.2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.4-tcl-9.4.26-alt0.M80P.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 postgresql9.5-tcl-9.5.25-alt0.M80P.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	pssh-2.3.1-alt1.noarch	There are file conflicts with the package xCAT-client-2.5.1-alt0.4.noarch, for example, /usr/bin/prsync (4 file conflicts in 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	putty-0.68-alt1.x86_64	File /usr/bin/pscp conflicts with the package xCAT-client-2.5.1-alt0.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	pve-manager-5.2.3-alt8.1.x86_64	File /usr/bin/vzdump conflicts with the package vzdump-1.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.; 
warn	pve-qemu-common-2.12.1-alt1.x86_64	File /usr/share/man/man1/qemu-img.1.xz conflicts with the package qemu-img-2.11.0-alt0.M80P.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/qemu/skiboot.lid /usr/share/qemu/slof.bin conflict with the package qemu-system-ppc-core-2.11.0-alt0.M80P.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	pve-qemu-system-2.12.1-alt1.x86_64	File /usr/bin/qemu-system-aarch64 conflicts with the package qemu-system-aarch64-core-2.11.0-alt0.M80P.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/bin/qemu-kvm /usr/bin/qemu-system-x86_64 conflict with the package qemu-system-x86-core-2.11.0-alt0.M80P.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	python-module-apiclient-1.0.2-alt2.1.1.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.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	python-module-cherrypy-tests-3.5.1-alt1.hg20140627.1.1.noarch	There are file conflicts with the package python-module-cherrypy2-2.3.0-alt2.1.1.noarch, for example, /usr/lib/python2.7/site-packages/cherrypy/test/__init__.py (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	python-module-cherrypy2-2.3.0-alt2.1.1.noarch	There are file conflicts with the package python-module-cherrypy-tests-3.5.1-alt1.hg20140627.1.1.noarch, for example, /usr/lib/python2.7/site-packages/cherrypy/test/__init__.py (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	python-module-config-0.3.7-alt2.1.1.noarch	Files /usr/lib/python2.7/site-packages/config.py /usr/lib/python2.7/site-packages/config.pyc /usr/lib/python2.7/site-packages/config.pyo conflict with the package geda-xgsch2pcb-0.1.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-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.; File /usr/lib/python2.7/site-packages/_version.py conflicts with the package python-module-flask-cors-1.9.0-alt1.git20141028.1.noarch. 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-alt0.M80P.1.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-alt0.M80P.1.noarch. 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-cms3.0-3.0.5-alt1.git20140820.1.noarch, for example, /usr/lib/python2.7/site-packages/cms/__init__.py (442 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package python-module-django-publisher-0.0.3-alt1.1.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-cms2.3-2.3.5-alt3.noarch	There are file conflicts with the package python-module-django-cms3.0-3.0.5-alt1.git20140820.1.noarch, for example, /usr/lib/python2.7/site-packages/cms/__init__.py (513 file conflicts in 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-cms3.0-3.0.5-alt1.git20140820.1.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/cms/__init__.py (442 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package python-module-django-cms2.3-2.3.5-alt3.noarch, for example, /usr/lib/python2.7/site-packages/cms/__init__.py (513 file conflicts in 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.1.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.1.noarch. 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.1.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-facebook-2.3.14-alt1.git20140409.1.1.noarch	There are file conflicts with the package python-module-facebook_api-0.1.4-alt1.1.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.1.noarch. 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.1.52-alt1.git20141125.1.1.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.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.; 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.2.1-alt1.git20140225.1.noarch. 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-scribe-2.0-alt1.git20130530.1.noarch	File /usr/lib/python2.7/site-packages/fb303/FacebookService.py conflicts with the package python-module-fb303-0.9.1-alt1_16.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	python-module-facebook-sdk-1.0.0-alt1.alpha.git20140828.1.1.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.1.noarch. Moreover, 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.1.noarch. 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.1.noarch	There are file conflicts with the package python-module-facebook-2.3.14-alt1.git20140409.1.1.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.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.; 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.1.noarch. 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.1.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.1.noarch. 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-fb303-0.9.1-alt1_16.4.x86_64	File /usr/lib/python2.7/site-packages/fb303/FacebookService.py conflicts with the package python-module-facebook-scribe-2.0-alt1.git20130530.1.noarch. 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-flask-cors-1.9.0-alt1.git20141028.1.noarch	File /usr/lib/python2.7/site-packages/_version.py conflicts 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	python-module-geventhttpclient-facebook-0.4.4-alt1.1.1.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.1.52-alt1.git20141125.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.; 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.2.1-alt1.git20140225.1.noarch. 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-gist-2.2.0-alt2.git20130422.1.1.x86_64	File /usr/include/ps.h conflicts with the package dap-devel-3.10-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.; File /usr/include/plugin.h conflicts with the package openquicktime-devel-2.0.0-alt6.a1.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-google-api-client-1.6.5-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.2-alt2.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-libtorrent-rasterbar-0.16.19-alt1.1.x86_64	File /usr/lib64/python2.7/site-packages/libtorrent.so conflicts with the package python-module-libtorrent-rasterbar9-1.1.4-alt0.M80P.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-libtorrent-rasterbar9-1.1.4-alt0.M80P.1.x86_64	File /usr/lib64/python2.7/site-packages/libtorrent.so conflicts with the package python-module-libtorrent-rasterbar-0.16.19-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	python-module-m2r-0.11-alt0.M80P.1.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-alt0.M80P.1.noarch. 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-manhole-1.0.0-alt2.git20150419.1.1.noarch	File /usr/bin/manhole conflicts with the package python-module-twisted-core-15.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	python-module-memory_profiler-0.41-alt1.noarch	File /usr/bin/mprof conflicts with the package maui-3.3-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	python-module-pip-10.0.1-alt1.M80P.1.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	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_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	python-module-ptest-1.3.0-alt1.git20150813.1.noarch	File /usr/bin/ptest conflicts with the package parmetis-4.0.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-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.1.noarch. 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-rasterio-0.26.0-alt1.git20150811.1.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	python-module-requests-facebook-0.2.1-alt1.git20140225.1.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.1.52-alt1.git20141125.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.; 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.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-scikits-0.2-alt2.dev.r803.1.1.x86_64	File /usr/lib64/python2.7/site-packages/scikits/__init__.py conflicts with the package python-module-scikits.eartho-0.2.1-alt2.git20141231.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	python-module-scikits.eartho-0.2.1-alt2.git20141231.1.1.x86_64	File /usr/lib64/python2.7/site-packages/scikits/__init__.py conflicts with the package python-module-scikits-0.2-alt2.dev.r803.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	python-module-servicemanager-0.0.16-alt1.git20141007.1.noarch	File /usr/bin/sm conflicts with the package inn-2.4.5-alt6.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.; 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-sphinx-readable-theme-1.1.0-alt1.git20140325.noarch	File /usr/lib/python2.7/site-packages/sphinx_readable_theme/readable/static/readable.css_t conflicts with the package python-module-sphinx_readable_theme-1.3.0-alt1.git20150327.1.noarch. 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-sphinx_readable_theme-1.3.0-alt1.git20150327.1.noarch	File /usr/lib/python2.7/site-packages/sphinx_readable_theme/readable/static/readable.css_t conflicts with the package python-module-sphinx-readable-theme-1.1.0-alt1.git20140325.noarch. 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-sqlbridge-0.1.68-alt2.git20141218.noarch	File /usr/bin/sqlcmd conflicts with the package python-module-sqlcmd-0.7.1-alt1.git20110314.1.noarch. 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-sqlcmd-0.7.1-alt1.git20110314.1.noarch	File /usr/bin/sqlcmd conflicts with the package python-module-sqlbridge-0.1.68-alt2.git20141218.noarch. 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.1.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.1.noarch. Moreover, 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.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.; 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.1.noarch. 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-alt1.1.noarch	Files /usr/bin/tpg /usr/lib/python2.7/site-packages/tpg.pyc /usr/lib/python2.7/site-packages/tpg.pyo conflict with the package tpg-3.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	python-module-twisted-core-15.3.0-alt1.x86_64	File /usr/bin/manhole conflicts with the package python-module-manhole-1.0.0-alt2.git20150419.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-zc-zookeeper-static-3.4.4.1-alt1.git20120925.x86_64	File /usr/lib64/python2.7/site-packages/zookeeper.so conflicts with the package python-module-zookeeper-3.4.6-alt1_15jpp8.x86_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-zest.pocompile-1.5-alt1.dev0.git20130705.1.1.x86_64	File /usr/bin/pocompile conflicts with the package translate-toolkit-1.13.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	python-module-zest.releaser-3.55-alt1.dev0.git20141229.1.1.x86_64	File /usr/bin/release conflicts with the package perl-Module-Release-scripts-2.122-alt1.noarch. 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-zookeeper-3.4.6-alt1_15jpp8.x86_64	File /usr/lib64/python2.7/site-packages/zookeeper.so conflicts with the package python-module-zc-zookeeper-static-3.4.4.1-alt1.git20120925.x86_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-apiclient-1.0.2-alt2.1.1.noarch	File /usr/lib/python3/site-packages/apiclient/__init__.py conflicts with the package python3-module-google-api-client-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	python3-module-bcrypt-2.0.0-alt1.1.x86_64	There are file conflicts with the package python3-module-py3k-bcrypt-0.3-alt1.git20120906.1.x86_64, for example, /usr/lib64/python3/site-packages/bcrypt/__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-configobj-5.0.6-alt1.1.1.noarch	File /usr/lib/python3/site-packages/_version.py conflicts with the package python3-module-flask-cors-1.9.0-alt1.git20141028.1.noarch. 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.1.noarch	File /usr/lib/python3/site-packages/facebook_utils/__init__.py conflicts with the package python3-module-facebook_utils-0.20.3-alt1.git20140717.1.noarch. 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.1.noarch	There are file conflicts with the package python3-module-facebook_api-0.1.4-alt1.1.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.; File /usr/lib/python3/site-packages/facebook/__init__.py conflicts with the package python3-module-tornado-facebook-sdk-0.1.0-alt1.git20121001.1.noarch. 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.1.52-alt1.git20141125.1.1.noarch	Files /usr/lib/python3/site-packages/__pycache__/facebook.cpython-33.pyc /usr/lib/python3/site-packages/__pycache__/facebook.cpython-33.pyo /usr/lib/python3/site-packages/facebook.py conflict with the package python3-module-geventhttpclient-facebook-0.4.4-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.; Files /usr/lib/python3/site-packages/__pycache__/facebook.cpython-33.pyc /usr/lib/python3/site-packages/__pycache__/facebook.cpython-33.pyo /usr/lib/python3/site-packages/facebook.py conflict with the package python3-module-requests-facebook-0.2.1-alt1.git20140225.1.noarch. 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.1.1.noarch	File /usr/lib/python3/site-packages/facebook/__init__.py conflicts with the package python3-module-facebook_api-0.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib/python3/site-packages/facebook/__init__.py conflicts with the package python3-module-tornado-facebook-sdk-0.1.0-alt1.git20121001.1.noarch. 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.1.noarch	There are file conflicts with the package python3-module-facebook-2.3.14-alt1.git20140409.1.1.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.; File /usr/lib/python3/site-packages/facebook/__init__.py conflicts with the package python3-module-facebook-sdk-1.0.0-alt1.alpha.git20140828.1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib/python3/site-packages/facebook/__init__.py conflicts with the package python3-module-tornado-facebook-sdk-0.1.0-alt1.git20121001.1.noarch. 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.1.noarch	File /usr/lib/python3/site-packages/facebook_utils/__init__.py conflicts with the package python3-module-django-facebook-utils-1.0.4-alt1.git20130201.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	python3-module-flask-cors-1.9.0-alt1.git20141028.1.noarch	File /usr/lib/python3/site-packages/_version.py conflicts with the package python3-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	python3-module-geventhttpclient-facebook-0.4.4-alt1.1.1.noarch	Files /usr/lib/python3/site-packages/__pycache__/facebook.cpython-33.pyc /usr/lib/python3/site-packages/__pycache__/facebook.cpython-33.pyo /usr/lib/python3/site-packages/facebook.py conflict with the package python3-module-facebook-ads-api-0.1.52-alt1.git20141125.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.; Files /usr/lib/python3/site-packages/__pycache__/facebook.cpython-33.pyc /usr/lib/python3/site-packages/__pycache__/facebook.cpython-33.pyo /usr/lib/python3/site-packages/facebook.py conflict with the package python3-module-requests-facebook-0.2.1-alt1.git20140225.1.noarch. 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.6.5-alt1.noarch	File /usr/lib/python3/site-packages/apiclient/__init__.py conflicts with the package python3-module-apiclient-1.0.2-alt2.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	python3-module-py3k-bcrypt-0.3-alt1.git20120906.1.x86_64	There are file conflicts with the package python3-module-bcrypt-2.0.0-alt1.1.x86_64, for example, /usr/lib64/python3/site-packages/bcrypt/__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.1.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-requests-facebook-0.2.1-alt1.git20140225.1.noarch	Files /usr/lib/python3/site-packages/__pycache__/facebook.cpython-33.pyc /usr/lib/python3/site-packages/__pycache__/facebook.cpython-33.pyo /usr/lib/python3/site-packages/facebook.py conflict with the package python3-module-facebook-ads-api-0.1.52-alt1.git20141125.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.; Files /usr/lib/python3/site-packages/__pycache__/facebook.cpython-33.pyc /usr/lib/python3/site-packages/__pycache__/facebook.cpython-33.pyo /usr/lib/python3/site-packages/facebook.py conflict with the package python3-module-geventhttpclient-facebook-0.4.4-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	python3-module-samba-4.9.18-alt1.x86_64	There are file conflicts with the package python3-module-samba-DC-4.9.18-alt1.x86_64, for example, /usr/lib64/python3/site-packages/samba/__pycache__/__init__.cpython-35.opt-1.pyc (241 file conflicts in 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-samba-DC-4.9.18-alt1.x86_64	There are file conflicts with the package python3-module-samba-4.9.18-alt1.x86_64, for example, /usr/lib64/python3/site-packages/samba/__pycache__/__init__.cpython-35.opt-1.pyc (241 file conflicts in 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-samba-DC-devel-4.9.18-alt1.x86_64	File /usr/lib64/pkgconfig/samba-policy.cpython-35m.pc conflicts with the package python3-module-samba-devel-4.9.18-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-samba-devel-4.9.18-alt1.x86_64	File /usr/lib64/pkgconfig/samba-policy.cpython-35m.pc conflicts with the package python3-module-samba-DC-devel-4.9.18-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-scikits-0.2-alt2.dev.r803.1.1.x86_64	There are file conflicts with the package python3-module-scikits.eartho-0.2.1-alt2.git20141231.1.1.x86_64, for example, /usr/lib64/python3/site-packages/scikits/__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-scikits.eartho-0.2.1-alt2.git20141231.1.1.x86_64	There are file conflicts with the package python3-module-scikits-0.2-alt2.dev.r803.1.1.x86_64, for example, /usr/lib64/python3/site-packages/scikits/__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.1.noarch	File /usr/lib/python3/site-packages/facebook/__init__.py conflicts with the package python3-module-facebook-2.3.14-alt1.git20140409.1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib/python3/site-packages/facebook/__init__.py conflicts with the package python3-module-facebook-sdk-1.0.0-alt1.alpha.git20140828.1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib/python3/site-packages/facebook/__init__.py conflicts with the package python3-module-facebook_api-0.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	qemu-img-2.11.0-alt0.M80P.4.x86_64	File /usr/share/man/man1/qemu-img.1.xz conflicts with the package pve-qemu-common-2.12.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	qemu-system-aarch64-core-2.11.0-alt0.M80P.4.x86_64	File /usr/bin/qemu-system-aarch64 conflicts with the package pve-qemu-system-2.12.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	qemu-system-ppc-core-2.11.0-alt0.M80P.4.x86_64	Files /usr/share/qemu/skiboot.lid /usr/share/qemu/slof.bin conflict with the package pve-qemu-common-2.12.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	qemu-system-x86-core-2.11.0-alt0.M80P.4.x86_64	Files /usr/bin/qemu-kvm /usr/bin/qemu-system-x86_64 conflict with the package pve-qemu-system-2.12.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	quota-devel-4.03-alt1.noarch	Files /usr/include/rpcsvc/rquota.h /usr/include/rpcsvc/rquota.x conflict with the package glibc-devel-2.23-alt3.M80P.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	racket-6.0.1-alt2.x86_64	File /usr/bin/slideshow conflicts with the package batik-slideshow-1.8-alt2_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	ruby-activerecord-mysql2-adapter-doc-0.0.3-alt1.noarch	There are file conflicts with the package ruby-em-synchrony-doc-1.0.5-alt1.noarch, for example, /usr/share/ri/site/ActiveRecord/ConnectionAdapters/ConnectionPool/cdesc-ConnectionPool.ri (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/ActiveRecord/cdesc-ActiveRecord.ri /usr/share/ri/site/Mysql2/cdesc-Mysql2.ri conflict with the package ruby-mysql2-doc-0.4.9-alt0.M80P.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	ruby-addressable-doc-2.4.0-alt1.noarch	Files /usr/share/ri/site/Addressable/URI/cdesc-URI.ri /usr/share/ri/site/Addressable/URI/normalized_query-i.ri /usr/share/ri/site/Addressable/cdesc-Addressable.ri conflict with the package ruby-faraday_middleware-doc-0.12.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-amazon-ec2-doc-0.9.17-alt1.noarch	File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-deep_merge-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch. Moreover, the packages have 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.1.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/Hash/cdesc-Hash.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-aws-sdk-doc-2.10.113-alt1.noarch	File /usr/share/ri/site/Aws/cdesc-Aws.ri conflicts with the package ruby-aws-sigv4-doc-1.0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-aws-sigv4-doc-1.0.2-alt1.noarch	File /usr/share/ri/site/Aws/cdesc-Aws.ri conflicts with the package ruby-aws-sdk-doc-2.10.113-alt1.noarch. 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-alt1.noarch	File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package chef-doc-12.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/Azure/cdesc-Azure.ri conflicts with the package ruby-azure-doc-0.7.10-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-alt1.M80P.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.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/String/cdesc-String.ri conflicts with the package ruby-mail-doc-2.6.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.5.0-alt1.1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-puppet-lint-doc-1.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-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.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-azure-doc-0.7.10-alt1.noarch	File /usr/share/ri/site/Azure/cdesc-Azure.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-backports-doc-3.7.0-alt1.noarch	There are file conflicts with the package asciidoctor-doc-1.5.6.1-alt0.M80P.1.noarch, for example, /usr/share/ri/site/Array/cdesc-Array.ri (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.; Files /usr/share/ri/site/String/cdesc-String.ri /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflict with the package chef-doc-12.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/Kernel/cdesc-Kernel.ri conflicts with the package erubis-doc-2.7.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/Hash/cdesc-Hash.ri conflicts with the package ruby-amazon-ec2-doc-0.9.17-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-bundler-doc-1.16.2-alt2.M80P.1.noarch. Moreover, the packages have 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.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-deep_merge-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-em-synchrony-doc-1.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/IO/cdesc-IO.ri conflicts with the package ruby-eventmachine-doc-1.2.5-alt0.M80P.4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-alt1.M80P.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch, for example, /usr/share/ri/site/Array/cdesc-Array.ri (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/IO/cdesc-IO.ri /usr/share/ri/site/Kernel/cdesc-Kernel.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-hpricot-doc-0.8.6-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.2.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Enumerable/cdesc-Enumerable.ri /usr/share/ri/site/File/cdesc-File.ri conflict with the package ruby-idn-doc-0.1.0-alt2.M80P.4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/IO/cdesc-IO.ri conflicts with the package ruby-io-extra-doc-1.2.7-alt1.1.M80P.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.; There are file conflicts with the package ruby-json-pure-doc-2.1.0-alt0.M80P.5.noarch, for example, /usr/share/ri/site/Complex/cdesc-Complex.ri (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/String/cdesc-String.ri /usr/share/ri/site/String/constantize-i.ri conflict with the package ruby-mail-doc-2.6.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/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.8.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/Symbol/cdesc-Symbol.ri conflicts with the package ruby-msgpack-doc-1.1.0-alt0.M80P.5.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.5.0-alt1.1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-polyglot-doc-0.3.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Process/cdesc-Process.ri conflicts with the package ruby-process-group-doc-1.1.0-alt0.M80P.1.noarch. Moreover, the packages have 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-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/String/cdesc-String.ri /usr/share/ri/site/String/prepend-i.ri conflict with the package ruby-puppet-lint-doc-1.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-rgen-doc-0.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-rr-doc-1.1.2-alt1.noarch, for example, /usr/share/ri/site/Array/cdesc-Array.ri (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/BasicObject/cdesc-BasicObject.ri conflicts with the package ruby-rspec-expectations-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/BasicObject/cdesc-BasicObject.ri conflicts with the package ruby-rspec-mocks-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/File/cdesc-File.ri conflicts with the package ruby-rspec-support-doc-3.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.; There are file conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch, for example, /usr/share/ri/site/Array/cdesc-Array.ri (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/Enumerable/cdesc-Enumerable.ri /usr/share/ri/site/File/cdesc-File.ri conflict with the package ruby-sigar-doc-0.7.3-alt1.2.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/File/cdesc-File.ri conflicts with the package ruby-spec_helper-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-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.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package yajl-ruby-doc-1.3.0-alt0.M80P.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	ruby-benchmark-ips-doc-1.2.0-alt1.gite47e416.noarch	File /usr/share/ri/site/Benchmark/cdesc-Benchmark.ri conflicts with the package ruby-benchmark_suite-doc-1.0.0-alt1.git5bded6.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-benchmark_suite-doc-1.0.0-alt1.git5bded6.noarch	File /usr/share/ri/site/Benchmark/cdesc-Benchmark.ri conflicts with the package ruby-benchmark-ips-doc-1.2.0-alt1.gite47e416.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-builder-doc-3.0.0-alt1.1.noarch	Files /usr/share/ri/site/Builder/XmlBase/_escape-i.ri /usr/share/ri/site/Builder/XmlBase/cdesc-XmlBase.ri /usr/share/ri/site/Builder/cdesc-Builder.ri conflict with the package ruby-escape_utils-doc-1.2.1-alt0.M80P.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	ruby-bundler-doc-1.16.2-alt2.M80P.1.noarch	Files /usr/share/ri/site/Gem/cdesc-Gem.ri /usr/share/ri/site/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package chef-doc-12.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/Kernel/cdesc-Kernel.ri conflicts with the package erubis-doc-2.7.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/Kernel/cdesc-Kernel.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Capistrano/cdesc-Capistrano.ri conflicts with the package ruby-capistrano-doc-2.5.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.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-em-synchrony-doc-1.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-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-hpricot-doc-0.8.6-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-json-pure-doc-2.1.0-alt0.M80P.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.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mail-doc-2.6.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/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package ruby-mechanize-doc-0.9.3-alt1.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package ruby-mini_portile2-doc-2.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/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package ruby-multipart-post-doc-2.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-dhcp-doc-1.3.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-http-pipeline-doc-1.0.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-ssh-multi-doc-1.2.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-polyglot-doc-0.3.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Gem/cdesc-Gem.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Gem/cdesc-Gem.ri /usr/share/ri/site/Rake/cdesc-Rake.ri conflict with the package ruby-spec_helper-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Object/namespace-i.ri /usr/share/ri/site/Object/rake_namespace-i.ri /usr/share/ri/site/Object/task-i.ri conflict with the package ruby-thor-doc-0.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.; Files /usr/share/ri/site/Object/namespace-i.ri /usr/share/ri/site/Object/rake_namespace-i.ri /usr/share/ri/site/Object/task-i.ri conflict with the package thor-doc-0.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.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package yajl-ruby-doc-1.3.0-alt0.M80P.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	ruby-capistrano-doc-2.5.10-alt1.1.noarch	File /usr/share/ri/site/Capistrano/cdesc-Capistrano.ri conflicts with the package ruby-bundler-doc-1.16.2-alt2.M80P.1.noarch. 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.1.0-alt1.noarch	Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package asciidoctor-doc-1.5.6.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package chef-doc-12.6.0-alt1.noarch, for example, /usr/share/ri/site/Chef/Node/cdesc-Node.ri (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Chef/cdesc-Chef.ri conflicts with the package ohai-doc-8.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-alt1.M80P.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.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/String/cdesc-String.ri conflicts with the package ruby-mail-doc-2.6.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.5.0-alt1.1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-puppet-lint-doc-1.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-rgen-doc-0.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-rr-doc-1.1.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Object/blank%3f-i.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-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.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-cleanroom-doc-1.0.0-alt1.noarch	File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package chef-doc-12.6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-core-doc-3.6.0-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-expectations-doc-3.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/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-mocks-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-puppet-doc-0.1.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-support-doc-3.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/RSpec/cdesc-RSpec.ri conflicts with the package ruby-spec_helper-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-dalli-doc-2.7.6-alt1.1.noarch	File /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri conflicts with the package ohai-doc-8.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-em-synchrony-doc-1.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/Rack/cdesc-Rack.ri conflicts with the package ruby-escape_utils-doc-1.2.1-alt0.M80P.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.; File /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri conflicts with the package ruby-facter-doc-2.0.1-alt1.M80P.1.noarch. Moreover, the packages have 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-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Rack/Session/cdesc-Session.ri /usr/share/ri/site/Rack/cdesc-Rack.ri conflict with the package ruby-rack-doc-1.6.8-alt1.0.M80P.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/Rack/cdesc-Rack.ri conflicts with the package ruby-rack-test-doc-0.6.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-simplecov-doc-0.12.0-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri conflicts with the package ruby-spoon-doc-0.0.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-deep_merge-doc-1.0.1-alt1.noarch	File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-amazon-ec2-doc-0.9.17-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch. Moreover, the packages have 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.1.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/Hash/cdesc-Hash.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-diff-lcs-doc-1.2.5-alt1.noarch	File /usr/share/ri/site/Diff/cdesc-Diff.ri conflicts with the package taskjuggler-3.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-em-http-request-doc-1.1.3-alt1.noarch	File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package chef-doc-12.6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-socksify-doc-0.3.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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.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/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-eventmachine-doc-1.2.5-alt0.M80P.4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-faraday-doc-0.12.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-alt1.M80P.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.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/String/cdesc-String.ri conflicts with the package ruby-mail-doc-2.6.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.5.0-alt1.1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-puppet-lint-doc-1.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-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.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-em-socksify-doc-0.3.1-alt1.noarch	File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-http-request-doc-1.1.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/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-synchrony-doc-1.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/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-eventmachine-doc-1.2.5-alt0.M80P.4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-faraday-doc-0.12.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-em-synchrony-doc-1.0.5-alt1.noarch	File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package erubis-doc-2.7.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-activerecord-mysql2-adapter-doc-0.0.3-alt1.noarch, for example, /usr/share/ri/site/ActiveRecord/ConnectionAdapters/ConnectionPool/cdesc-ConnectionPool.ri (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-bundler-doc-1.16.2-alt2.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-dalli-doc-2.7.6-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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.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/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-socksify-doc-0.3.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-eventmachine-doc-1.2.5-alt0.M80P.4.noarch, for example, /usr/share/ri/site/EM/cdesc-EM.ri (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-faraday-doc-0.12.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-hpricot-doc-0.8.6-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-json-pure-doc-2.1.0-alt0.M80P.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.; There are file conflicts with the package ruby-mysql2-doc-0.4.9-alt0.M80P.4.noarch, for example, /usr/share/ri/site/ActiveRecord/cdesc-ActiveRecord.ri (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-polyglot-doc-0.3.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-simplecov-doc-0.12.0-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package yajl-ruby-doc-1.3.0-alt0.M80P.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	ruby-escape_utils-doc-1.2.1-alt0.M80P.5.noarch	Files /usr/share/ri/site/ActionView/cdesc-ActionView.ri /usr/share/ri/site/ERB/cdesc-ERB.ri conflict with the package erubis-doc-2.7.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/Builder/XmlBase/_escape-i.ri /usr/share/ri/site/Builder/XmlBase/cdesc-XmlBase.ri /usr/share/ri/site/Builder/cdesc-Builder.ri conflict with the package ruby-builder-doc-3.0.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-dalli-doc-2.7.6-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/URI/cdesc-URI.ri conflicts with the package ruby-httpclient-doc-2.8.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/URI/cdesc-URI.ri conflicts with the package ruby-proxifier-doc-1.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-rack-doc-1.6.8-alt1.0.M80P.2.noarch, for example, /usr/share/ri/site/Rack/Utils/cdesc-Utils.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/Rack/cdesc-Rack.ri conflicts with the package ruby-rack-test-doc-0.6.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-eventmachine-doc-1.2.5-alt0.M80P.4.noarch	File /usr/share/ri/site/IO/cdesc-IO.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/IO/cdesc-IO.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-http-request-doc-1.1.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/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-socksify-doc-0.3.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-em-synchrony-doc-1.0.5-alt1.noarch, for example, /usr/share/ri/site/EM/cdesc-EM.ri (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-faraday-doc-0.12.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/IO/cdesc-IO.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/IO/cdesc-IO.ri conflicts with the package ruby-io-extra-doc-1.2.7-alt1.1.M80P.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	ruby-facter-doc-2.0.1-alt1.M80P.1.noarch	File /usr/share/ri/site/Win32/cdesc-Win32.ri conflicts with the package chef-doc-12.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/Plist/cdesc-Plist.ri /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri conflict with the package ohai-doc-8.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri conflicts with the package ruby-dalli-doc-2.7.6-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-plist-doc-3.1.0-alt1.noarch, for example, /usr/share/ri/site/Plist/Emit/cdesc-Emit.ri (51 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Puppet/cdesc-Puppet.ri conflicts with the package ruby-spec_helper-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri conflicts with the package ruby-spoon-doc-0.0.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-faraday-doc-0.12.1-alt1.noarch	File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-http-request-doc-1.1.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/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-socksify-doc-0.3.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-em-synchrony-doc-1.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/EventMachine/cdesc-EventMachine.ri conflicts with the package ruby-eventmachine-doc-1.2.5-alt0.M80P.4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/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.noarch. 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.noarch	Files /usr/share/ri/site/Addressable/URI/cdesc-URI.ri /usr/share/ri/site/Addressable/URI/normalized_query-i.ri /usr/share/ri/site/Addressable/cdesc-Addressable.ri conflict with the package ruby-addressable-doc-2.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/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.12.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-fast_gettext-doc-1.1.0-alt1.M80P.2.noarch	File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package chef-doc-12.6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.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/String/cdesc-String.ri conflicts with the package ruby-mail-doc-2.6.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.5.0-alt1.1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/String/%25-i.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-puppet-lint-doc-1.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-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.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-ffi-doc-1.9.18-alt1.M80P.4.noarch	Files /usr/share/ri/site/FFI/Pointer/cdesc-Pointer.ri /usr/share/ri/site/FFI/cdesc-FFI.ri conflict with the package chef-doc-12.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-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch	There are file conflicts with the package asciidoctor-doc-1.5.6.1-alt0.M80P.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.; There are file conflicts with the package chef-doc-12.6.0-alt1.noarch, for example, /usr/share/ri/site/FalseClass/cdesc-FalseClass.ri (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-amazon-ec2-doc-0.9.17-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch, for example, /usr/share/ri/site/Array/cdesc-Array.ri (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-bundler-doc-1.16.2-alt2.M80P.1.noarch. Moreover, the packages have 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.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/ActiveSupport/cdesc-ActiveSupport.ri conflicts with the package ruby-dalli-doc-2.7.6-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-deep_merge-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-alt1.M80P.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/String/cdesc-String.ri /usr/share/ri/site/StringIO/cdesc-StringIO.ri conflict with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.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.; There are file conflicts with the package ruby-json-pure-doc-2.1.0-alt0.M80P.5.noarch, for example, /usr/share/ri/site/Date/cdesc-Date.ri (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Net/cdesc-Net.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-mail-doc-2.6.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/Net/cdesc-Net.ri conflicts with the package ruby-mechanize-doc-0.9.3-alt1.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mini_portile2-doc-2.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-msgpack-doc-1.1.0-alt0.M80P.5.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-dhcp-doc-1.3.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-http-pipeline-doc-1.0.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-ssh-multi-doc-1.2.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.5.0-alt1.1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-puppet-lint-doc-1.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-rgen-doc-0.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Hash/cdesc-Hash.ri conflict with the package ruby-rr-doc-1.1.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch, for example, /usr/share/ri/site/Array/cdesc-Array.ri (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-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.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Yajl/cdesc-Yajl.ri conflicts with the package yajl-ruby-doc-1.3.0-alt0.M80P.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	ruby-hashie-doc-3.5.7-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.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-hiera-doc-3.2.0-alt1.noarch	Files /usr/share/ri/site/Hiera/Backend/cdesc-Backend.ri /usr/share/ri/site/Hiera/cdesc-Hiera.ri conflict with the package ruby-hiera-eyaml-doc-2.1.0-alt0.M80P.1.noarch. 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-hiera-eyaml-doc-2.1.0-alt0.M80P.1.noarch	Files /usr/share/ri/site/Hiera/Backend/cdesc-Backend.ri /usr/share/ri/site/Hiera/cdesc-Hiera.ri conflict with the package ruby-hiera-doc-3.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	ruby-highline-doc-1.7.5-alt1.noarch	Files /usr/share/ri/site/IO/cdesc-IO.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package asciidoctor-doc-1.5.6.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package chef-doc-12.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/Kernel/cdesc-Kernel.ri conflicts with the package erubis-doc-2.7.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/IO/cdesc-IO.ri /usr/share/ri/site/Kernel/cdesc-Kernel.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-bundler-doc-1.16.2-alt2.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add 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.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-em-synchrony-doc-1.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/IO/cdesc-IO.ri conflicts with the package ruby-eventmachine-doc-1.2.5-alt0.M80P.4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-alt1.M80P.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/String/cdesc-String.ri /usr/share/ri/site/StringIO/cdesc-StringIO.ri conflict with the package ruby-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch. Moreover, the packages have 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-hpricot-doc-0.8.6-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.2.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/IO/cdesc-IO.ri conflicts with the package ruby-io-extra-doc-1.2.7-alt1.1.M80P.4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-json-pure-doc-2.1.0-alt0.M80P.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.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-mail-doc-2.6.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.5.0-alt1.1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-polyglot-doc-0.3.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-puppet-lint-doc-1.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-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.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package yajl-ruby-doc-1.3.0-alt0.M80P.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	ruby-hpricot-doc-0.8.6-alt1.M80P.1.noarch	File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package erubis-doc-2.7.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/Kernel/cdesc-Kernel.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-bundler-doc-1.16.2-alt2.M80P.1.noarch. Moreover, the packages have 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.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-json-pure-doc-2.1.0-alt0.M80P.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.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-polyglot-doc-0.3.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package yajl-ruby-doc-1.3.0-alt0.M80P.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	ruby-http_parser.rb-doc-0.6.0-alt2.M80P.4.noarch	File /usr/share/ri/site/HTTP/cdesc-HTTP.ri conflicts with the package ruby-httpclient-doc-2.8.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/HTTP/cdesc-HTTP.ri conflicts with the package ruby-net-http-pipeline-doc-1.0.1-alt0.M80P.1.noarch. 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-httpclient-doc-2.8.2.4-alt1.noarch	File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package chef-doc-12.6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.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/URI/cdesc-URI.ri conflicts with the package ruby-escape_utils-doc-1.2.1-alt0.M80P.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.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-alt1.M80P.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/HTTP/cdesc-HTTP.ri conflicts with the package ruby-http_parser.rb-doc-0.6.0-alt2.M80P.4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/cache.ri /usr/share/ri/site/created.rid conflict with the package ruby-iconv-1.0.4-alt1.M80P.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-mail-doc-2.6.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-makeconf-doc-0.3.0-alt1.svn20130509.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/HTTP/cdesc-HTTP.ri conflicts with the package ruby-net-http-pipeline-doc-1.0.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.5.0-alt1.1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/cache.ri /usr/share/ri/site/created.rid conflict with the package ruby-parseconfig-doc-0.5-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/URI/cdesc-URI.ri conflicts with the package ruby-proxifier-doc-1.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-puppet-lint-doc-1.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-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.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-iconv-1.0.4-alt1.M80P.4.x86_64	Files /usr/share/ri/site/cache.ri /usr/share/ri/site/created.rid conflict with the package ruby-httpclient-doc-2.8.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.; Files /usr/share/ri/site/cache.ri /usr/share/ri/site/created.rid conflict with the package ruby-makeconf-doc-0.3.0-alt1.svn20130509.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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-idn-doc-0.1.0-alt2.M80P.4.noarch	Files /usr/share/ri/site/Enumerable/cdesc-Enumerable.ri /usr/share/ri/site/File/cdesc-File.ri conflict with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Installer/cdesc-Installer.ri /usr/share/ri/site/Installer/new-c.ri conflict with the package ruby-makeconf-doc-0.3.0-alt1.svn20130509.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Enumerable/cdesc-Enumerable.ri conflicts with the package ruby-rr-doc-1.1.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-rspec-support-doc-3.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.; There are file conflicts with the package ruby-sigar-doc-0.7.3-alt1.2.M80P.1.noarch, for example, /usr/share/ri/site/page-LICENSE.ri (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/File/cdesc-File.ri conflicts with the package ruby-spec_helper-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-io-extra-doc-1.2.7-alt1.1.M80P.4.noarch	File /usr/share/ri/site/IO/cdesc-IO.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/IO/cdesc-IO.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/IO/cdesc-IO.ri conflicts with the package ruby-eventmachine-doc-1.2.5-alt0.M80P.4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/IO/cdesc-IO.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-json-pure-doc-2.1.0-alt0.M80P.5.noarch	Files /usr/share/ri/site/Regexp/cdesc-Regexp.ri /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflict with the package asciidoctor-doc-1.5.6.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package chef-doc-12.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/Kernel/cdesc-Kernel.ri conflicts with the package erubis-doc-2.7.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch, for example, /usr/share/ri/site/Complex/cdesc-Complex.ri (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-bundler-doc-1.16.2-alt2.M80P.1.noarch. Moreover, the packages have 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.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-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch, for example, /usr/share/ri/site/Date/cdesc-Date.ri (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-hpricot-doc-0.8.6-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package ruby-msgpack-doc-1.1.0-alt0.M80P.5.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-oj-doc-3.5.0-alt1.1.M80P.1.noarch, for example, /usr/share/ri/site/JSON/Ext/cdesc-Ext.ri (18 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-polyglot-doc-0.3.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Range/cdesc-Range.ri /usr/share/ri/site/Regexp/cdesc-Regexp.ri conflict with the package ruby-rr-doc-1.1.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/Class/cdesc-Class.ri conflicts with the package ruby-rspec-mocks-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Range/cdesc-Range.ri /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflict with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package yajl-ruby-doc-1.3.0-alt0.M80P.4.noarch, for example, /usr/share/ri/site/JSON/GeneratorError/cdesc-GeneratorError.ri (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-mail-doc-2.6.4-alt1.noarch	File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Net/cdesc-Net.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package chef-doc-12.6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/String/cdesc-String.ri /usr/share/ri/site/String/constantize-i.ri conflict with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-bundler-doc-1.16.2-alt2.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add 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.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-alt1.M80P.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Net/cdesc-Net.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.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/Net/cdesc-Net.ri conflicts with the package ruby-mechanize-doc-0.9.3-alt1.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mini_portile2-doc-2.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-multipart-post-doc-2.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-dhcp-doc-1.3.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-http-pipeline-doc-1.0.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-ssh-multi-doc-1.2.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.5.0-alt1.1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-puppet-lint-doc-1.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/ri/site/String/cdesc-String.ri /usr/share/ri/site/String/constantize-i.ri conflict with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-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.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-makeconf-doc-0.3.0-alt1.svn20130509.noarch	Files /usr/share/ri/site/cache.ri /usr/share/ri/site/created.rid conflict with the package ruby-httpclient-doc-2.8.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.; Files /usr/share/ri/site/cache.ri /usr/share/ri/site/created.rid conflict with the package ruby-iconv-1.0.4-alt1.M80P.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Installer/cdesc-Installer.ri /usr/share/ri/site/Installer/new-c.ri conflict with the package ruby-idn-doc-0.1.0-alt2.M80P.4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/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/Installer/cdesc-Installer.ri /usr/share/ri/site/Installer/new-c.ri conflict with the package ruby-sigar-doc-0.7.3-alt1.2.M80P.1.noarch. 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-mechanize-doc-0.9.3-alt1.3.noarch	Files /usr/share/ri/site/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package chef-doc-12.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/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package ruby-bundler-doc-1.16.2-alt2.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mail-doc-2.6.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/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package ruby-mini_portile2-doc-2.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/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package ruby-multipart-post-doc-2.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-dhcp-doc-1.3.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-http-pipeline-doc-1.0.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-ssh-multi-doc-1.2.0-alt1.noarch. 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.8.2-alt1.noarch	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.noarch. 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-mini_portile2-doc-2.2.0-alt1.noarch	Files /usr/share/ri/site/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package chef-doc-12.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/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package ruby-bundler-doc-1.16.2-alt2.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mail-doc-2.6.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/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package ruby-mechanize-doc-0.9.3-alt1.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package ruby-multipart-post-doc-2.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-dhcp-doc-1.3.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-http-pipeline-doc-1.0.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-ssh-multi-doc-1.2.0-alt1.noarch. 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-1.3.0-alt1.noarch	File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-cli-doc-1.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-config-doc-2.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-log-doc-1.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-shellout-doc-2.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-mixlib-cli-doc-1.5.0-alt1.noarch	File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-authentication-doc-1.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-config-doc-2.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-log-doc-1.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-shellout-doc-2.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-mixlib-config-doc-2.1.0-alt1.noarch	File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-authentication-doc-1.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-cli-doc-1.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-log-doc-1.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-shellout-doc-2.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-mixlib-log-doc-1.4.0-alt1.noarch	File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-authentication-doc-1.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-cli-doc-1.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-config-doc-2.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-shellout-doc-2.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-mixlib-shellout-doc-2.0.1-alt1.noarch	File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-authentication-doc-1.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-cli-doc-1.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-config-doc-2.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Mixlib/cdesc-Mixlib.ri conflicts with the package ruby-mixlib-log-doc-1.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-msgpack-doc-1.1.0-alt0.M80P.5.x86_64	File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package chef-doc-12.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/Symbol/cdesc-Symbol.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package ruby-json-pure-doc-2.1.0-alt0.M80P.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.; File /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-multipart-post-doc-2.0.0-alt1.noarch	Files /usr/share/ri/site/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package chef-doc-12.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/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package ruby-bundler-doc-1.16.2-alt2.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mail-doc-2.6.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/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package ruby-mechanize-doc-0.9.3-alt1.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package ruby-mini_portile2-doc-2.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-net-dhcp-doc-1.3.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-http-pipeline-doc-1.0.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-ssh-multi-doc-1.2.0-alt1.noarch. 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-mustermann-doc-1.0.0-alt1.noarch	File /usr/share/ri/site/Sinatra/cdesc-Sinatra.ri conflicts with the package ruby-sinatra-doc-1.4.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	ruby-mysql2-doc-0.4.9-alt0.M80P.4.noarch	Files /usr/share/ri/site/ActiveRecord/cdesc-ActiveRecord.ri /usr/share/ri/site/Mysql2/cdesc-Mysql2.ri conflict with the package ruby-activerecord-mysql2-adapter-doc-0.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-em-synchrony-doc-1.0.5-alt1.noarch, for example, /usr/share/ri/site/ActiveRecord/cdesc-ActiveRecord.ri (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-net-dhcp-doc-1.3.2-alt1.noarch	File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package chef-doc-12.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/Net/cdesc-Net.ri conflicts with the package ruby-bundler-doc-1.16.2-alt2.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mail-doc-2.6.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/Net/cdesc-Net.ri conflicts with the package ruby-mechanize-doc-0.9.3-alt1.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mini_portile2-doc-2.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-multipart-post-doc-2.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-http-pipeline-doc-1.0.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-ssh-multi-doc-1.2.0-alt1.noarch. 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-http-pipeline-doc-1.0.1-alt0.M80P.1.noarch	File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package chef-doc-12.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/Net/cdesc-Net.ri conflicts with the package ruby-bundler-doc-1.16.2-alt2.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/HTTP/cdesc-HTTP.ri conflicts with the package ruby-http_parser.rb-doc-0.6.0-alt2.M80P.4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/HTTP/cdesc-HTTP.ri conflicts with the package ruby-httpclient-doc-2.8.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/Net/cdesc-Net.ri conflicts with the package ruby-mail-doc-2.6.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/Net/cdesc-Net.ri conflicts with the package ruby-mechanize-doc-0.9.3-alt1.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mini_portile2-doc-2.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-multipart-post-doc-2.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-dhcp-doc-1.3.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-ssh-multi-doc-1.2.0-alt1.noarch. 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-ssh-doc-4.2.0-alt0.M80P.1.noarch	File /usr/share/ri/site/Net/SSH/cdesc-SSH.ri conflicts with the package chef-doc-12.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/Net/SSH/cdesc-SSH.ri conflicts with the package ruby-net-ssh-multi-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.; 
warn	ruby-net-ssh-multi-doc-1.2.0-alt1.noarch	There are file conflicts with the package chef-doc-12.6.0-alt1.noarch, for example, /usr/share/ri/site/Net/SSH/Multi/Server/busy%3f-i.ri (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-bundler-doc-1.16.2-alt2.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mail-doc-2.6.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/Net/cdesc-Net.ri conflicts with the package ruby-mechanize-doc-0.9.3-alt1.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mini_portile2-doc-2.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-multipart-post-doc-2.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-dhcp-doc-1.3.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-http-pipeline-doc-1.0.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Net/SSH/cdesc-SSH.ri conflicts with the package ruby-net-ssh-doc-4.2.0-alt0.M80P.1.noarch. 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-octokit.rb-doc-4.7.0-alt1.noarch	File /usr/share/ri/site/Sawyer/cdesc-Sawyer.ri conflicts with the package ruby-sawyer-doc-0.8.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-oj-doc-3.5.0-alt1.1.M80P.1.noarch	File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package chef-doc-12.6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-alt1.M80P.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.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.; There are file conflicts with the package ruby-json-pure-doc-2.1.0-alt0.M80P.5.noarch, for example, /usr/share/ri/site/JSON/Ext/cdesc-Ext.ri (18 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-mail-doc-2.6.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-puppet-lint-doc-1.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-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.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/JSON/cdesc-JSON.ri conflicts with the package yajl-ruby-doc-1.3.0-alt0.M80P.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	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 ruby-httpclient-doc-2.8.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.; Files /usr/share/ri/site/cache.ri /usr/share/ri/site/created.rid conflict with the package ruby-iconv-1.0.4-alt1.M80P.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/cache.ri /usr/share/ri/site/created.rid conflict with the package ruby-makeconf-doc-0.3.0-alt1.svn20130509.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-pg-doc-0.19.0-alt1.M80P.4.noarch	File /usr/share/ri/site/PG/cdesc-PG.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-plist-doc-3.1.0-alt1.noarch	File /usr/share/ri/site/Plist/cdesc-Plist.ri conflicts with the package ohai-doc-8.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-facter-doc-2.0.1-alt1.M80P.1.noarch, for example, /usr/share/ri/site/Plist/Emit/cdesc-Emit.ri (51 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-polyglot-doc-0.3.5-alt1.noarch	File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package erubis-doc-2.7.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/Kernel/cdesc-Kernel.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-bundler-doc-1.16.2-alt2.M80P.1.noarch. Moreover, the packages have 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.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-hpricot-doc-0.8.6-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-json-pure-doc-2.1.0-alt0.M80P.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.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package yajl-ruby-doc-1.3.0-alt0.M80P.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	ruby-process-group-doc-1.1.0-alt0.M80P.1.noarch	File /usr/share/ri/site/Process/cdesc-Process.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Process/cdesc-Process.ri conflicts with the package ruby-process-pipeline-doc-1.0.1-alt0.M80P.1.noarch. 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-alt0.M80P.1.noarch	File /usr/share/ri/site/Process/cdesc-Process.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Process/cdesc-Process.ri conflicts with the package ruby-process-group-doc-1.1.0-alt0.M80P.1.noarch. 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.noarch	File /usr/share/ri/site/URI/cdesc-URI.ri conflicts with the package ruby-escape_utils-doc-1.2.1-alt0.M80P.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.; File /usr/share/ri/site/URI/cdesc-URI.ri conflicts with the package ruby-httpclient-doc-2.8.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-puppet-lint-doc-1.1.0-alt1.noarch	File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package chef-doc-12.6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/String/cdesc-String.ri /usr/share/ri/site/String/prepend-i.ri conflict with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.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/String/%25-i.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-fast_gettext-doc-1.1.0-alt1.M80P.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.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/String/cdesc-String.ri conflicts with the package ruby-mail-doc-2.6.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.5.0-alt1.1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/PuppetLint/cdesc-PuppetLint.ri conflicts with the package ruby-spec_helper-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-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.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-rack-doc-1.6.8-alt1.0.M80P.2.noarch	Files /usr/share/ri/site/Rack/Session/cdesc-Session.ri /usr/share/ri/site/Rack/cdesc-Rack.ri conflict with the package ruby-dalli-doc-2.7.6-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-escape_utils-doc-1.2.1-alt0.M80P.5.noarch, for example, /usr/share/ri/site/Rack/Utils/cdesc-Utils.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/Rack/cdesc-Rack.ri conflicts with the package ruby-rack-test-doc-0.6.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-rack-test-doc-0.6.3-alt1.noarch	File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-dalli-doc-2.7.6-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-escape_utils-doc-1.2.1-alt0.M80P.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.; File /usr/share/ri/site/Rack/cdesc-Rack.ri conflicts with the package ruby-rack-doc-1.6.8-alt1.0.M80P.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-rash-doc-0.4.5-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-hashie-doc-3.5.7-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-rbnacl-doc-5.0.0-alt0.M80P.1.noarch	File /usr/share/ri/site/RbNaCl/cdesc-RbNaCl.ri conflicts with the package ruby-rbnacl-libsodium-doc-1.0.16-alt0.M80P.1.noarch. 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-alt0.M80P.1.noarch	File /usr/share/ri/site/RbNaCl/cdesc-RbNaCl.ri conflicts with the package ruby-rbnacl-doc-5.0.0-alt0.M80P.1.noarch. 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-rgen-doc-0.7.0-alt1.noarch	File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-chef-sugar-doc-3.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch. Moreover, the packages have 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.1.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/Array/cdesc-Array.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-rr-doc-1.1.2-alt1.noarch	Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Hash/cdesc-Hash.ri /usr/share/ri/site/Regexp/cdesc-Regexp.ri conflict with the package asciidoctor-doc-1.5.6.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-amazon-ec2-doc-0.9.17-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch, for example, /usr/share/ri/site/Array/cdesc-Array.ri (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-chef-sugar-doc-3.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-deep_merge-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Hash/cdesc-Hash.ri conflict with the package ruby-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Enumerable/cdesc-Enumerable.ri conflicts with the package ruby-idn-doc-0.1.0-alt2.M80P.4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Range/cdesc-Range.ri /usr/share/ri/site/Regexp/cdesc-Regexp.ri conflict with the package ruby-json-pure-doc-2.1.0-alt0.M80P.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.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-rgen-doc-0.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/RR/Errors/cdesc-Errors.ri /usr/share/ri/site/RR/cdesc-RR.ri conflict with the package ruby-rspec-core-doc-3.6.0-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Hash/cdesc-Hash.ri /usr/share/ri/site/Range/cdesc-Range.ri conflict with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Enumerable/cdesc-Enumerable.ri conflicts with the package ruby-sigar-doc-0.7.3-alt1.2.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Object/new-c.ri conflicts with the package ruby-spec_helper-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-rspec-core-doc-3.6.0-alt0.M80P.1.noarch	Files /usr/share/ri/site/RSpec/Core/cdesc-Core.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package chef-doc-12.6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-cleanroom-doc-1.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/RR/Errors/cdesc-Errors.ri /usr/share/ri/site/RR/cdesc-RR.ri conflict with the package ruby-rr-doc-1.1.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/RSpec/Support/cdesc-Support.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-expectations-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/RSpec/Support/cdesc-Support.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-mocks-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-puppet-doc-0.1.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/RSpec/Support/cdesc-Support.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-support-doc-3.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/RSpec/Core/cdesc-Core.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-spec_helper-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-rspec-expectations-doc-3.4.0-alt1.noarch	File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package chef-doc-12.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/BasicObject/cdesc-BasicObject.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-cleanroom-doc-1.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/RSpec/Support/cdesc-Support.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-core-doc-3.6.0-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/BasicObject/cdesc-BasicObject.ri /usr/share/ri/site/RSpec/Support/cdesc-Support.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-mocks-doc-3.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/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-puppet-doc-0.1.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/RSpec/Support/cdesc-Support.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-support-doc-3.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/RSpec/Matchers/cdesc-Matchers.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-spec_helper-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-rspec-mocks-doc-3.4.0-alt1.noarch	File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package chef-doc-12.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/BasicObject/cdesc-BasicObject.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-cleanroom-doc-1.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Class/cdesc-Class.ri conflicts with the package ruby-json-pure-doc-2.1.0-alt0.M80P.5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/RSpec/Support/cdesc-Support.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-core-doc-3.6.0-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/BasicObject/cdesc-BasicObject.ri /usr/share/ri/site/RSpec/Support/cdesc-Support.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-expectations-doc-3.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/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-puppet-doc-0.1.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/RSpec/Support/cdesc-Support.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-support-doc-3.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/RSpec/cdesc-RSpec.ri conflicts with the package ruby-spec_helper-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-rspec-puppet-doc-0.1.6-alt1.noarch	File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package chef-doc-12.6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-cleanroom-doc-1.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-core-doc-3.6.0-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-expectations-doc-3.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/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-mocks-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-support-doc-3.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/RSpec/cdesc-RSpec.ri conflicts with the package ruby-spec_helper-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-rspec-support-doc-3.4.1-alt1.noarch	File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package chef-doc-12.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/File/cdesc-File.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-cleanroom-doc-1.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/File/cdesc-File.ri conflicts with the package ruby-idn-doc-0.1.0-alt2.M80P.4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/RSpec/Support/cdesc-Support.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-core-doc-3.6.0-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/RSpec/Support/cdesc-Support.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-expectations-doc-3.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/RSpec/Support/cdesc-Support.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-mocks-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-puppet-doc-0.1.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/File/cdesc-File.ri conflicts with the package ruby-sigar-doc-0.7.3-alt1.2.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/File/cdesc-File.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-spec_helper-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-sawyer-doc-0.8.1-alt1.noarch	File /usr/share/ri/site/Sawyer/cdesc-Sawyer.ri conflicts with the package ruby-octokit.rb-doc-4.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-sequel-doc-4.49.0-alt2.1.noarch	There are file conflicts with the package asciidoctor-doc-1.5.6.1-alt0.M80P.1.noarch, for example, /usr/share/ri/site/Array/cdesc-Array.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.; There are file conflicts with the package chef-doc-12.6.0-alt1.noarch, for example, /usr/share/ri/site/FalseClass/cdesc-FalseClass.ri (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-amazon-ec2-doc-0.9.17-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch, for example, /usr/share/ri/site/Array/cdesc-Array.ri (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.; File /usr/share/ri/site/Gem/cdesc-Gem.ri conflicts with the package ruby-bundler-doc-1.16.2-alt2.M80P.1.noarch. Moreover, the packages have 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.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Hash/cdesc-Hash.ri conflicts with the package ruby-deep_merge-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-alt1.M80P.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch, for example, /usr/share/ri/site/Array/cdesc-Array.ri (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.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.; Files /usr/share/ri/site/Range/cdesc-Range.ri /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflict with the package ruby-json-pure-doc-2.1.0-alt0.M80P.5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/String/cdesc-String.ri /usr/share/ri/site/String/constantize-i.ri conflict with the package ruby-mail-doc-2.6.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/Symbol/cdesc-Symbol.ri conflicts with the package ruby-msgpack-doc-1.1.0-alt0.M80P.5.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.5.0-alt1.1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/PG/cdesc-PG.ri conflicts with the package ruby-pg-doc-0.19.0-alt1.M80P.4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-puppet-lint-doc-1.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Array/cdesc-Array.ri conflicts with the package ruby-rgen-doc-0.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Array/cdesc-Array.ri /usr/share/ri/site/Hash/cdesc-Hash.ri /usr/share/ri/site/Range/cdesc-Range.ri conflict with the package ruby-rr-doc-1.1.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-spec_helper-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/String/blank%3f-i.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-treetop-doc-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.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-sigar-doc-0.7.3-alt1.2.M80P.1.noarch	File /usr/share/ri/site/Sigar/cdesc-Sigar.ri conflicts with the package ohai-doc-8.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Enumerable/cdesc-Enumerable.ri /usr/share/ri/site/File/cdesc-File.ri conflict with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-idn-doc-0.1.0-alt2.M80P.4.noarch, for example, /usr/share/ri/site/page-LICENSE.ri (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Installer/cdesc-Installer.ri /usr/share/ri/site/Installer/new-c.ri conflict with the package ruby-makeconf-doc-0.3.0-alt1.svn20130509.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Enumerable/cdesc-Enumerable.ri conflicts with the package ruby-rr-doc-1.1.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-rspec-support-doc-3.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/File/cdesc-File.ri conflicts with the package ruby-spec_helper-doc-1.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-simplecov-doc-0.12.0-alt1.M80P.1.noarch	File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-dalli-doc-2.7.6-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Rails/cdesc-Rails.ri conflicts with the package ruby-em-synchrony-doc-1.0.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/SimpleCov/Formatter/cdesc-Formatter.ri /usr/share/ri/site/SimpleCov/cdesc-SimpleCov.ri conflict with the package ruby-simplecov-html-doc-0.10.0-alt0.M80P.1.noarch. 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-simplecov-html-doc-0.10.0-alt0.M80P.1.noarch	Files /usr/share/ri/site/SimpleCov/Formatter/cdesc-Formatter.ri /usr/share/ri/site/SimpleCov/cdesc-SimpleCov.ri conflict with the package ruby-simplecov-doc-0.12.0-alt1.M80P.1.noarch. 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-sinatra-doc-1.4.8-alt1.noarch	File /usr/share/ri/site/Sinatra/cdesc-Sinatra.ri conflicts with the package ruby-mustermann-doc-1.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-spec_helper-doc-1.0.1-alt1.noarch	Files /usr/share/ri/site/Gem/cdesc-Gem.ri /usr/share/ri/site/RSpec/Core/cdesc-Core.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package chef-doc-12.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/File/cdesc-File.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/Gem/cdesc-Gem.ri /usr/share/ri/site/Rake/cdesc-Rake.ri conflict with the package ruby-bundler-doc-1.16.2-alt2.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-cleanroom-doc-1.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Puppet/cdesc-Puppet.ri conflicts with the package ruby-facter-doc-2.0.1-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/File/cdesc-File.ri conflicts with the package ruby-idn-doc-0.1.0-alt2.M80P.4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/PuppetLint/cdesc-PuppetLint.ri conflicts with the package ruby-puppet-lint-doc-1.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Object/new-c.ri conflicts with the package ruby-rr-doc-1.1.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/RSpec/Core/cdesc-Core.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-core-doc-3.6.0-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/RSpec/Matchers/cdesc-Matchers.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-expectations-doc-3.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/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-mocks-doc-3.4.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-puppet-doc-0.1.6-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ri/site/File/cdesc-File.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-support-doc-3.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/Gem/cdesc-Gem.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/File/cdesc-File.ri conflicts with the package ruby-sigar-doc-0.7.3-alt1.2.M80P.1.noarch. 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.noarch	File /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri conflicts with the package ohai-doc-8.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri conflicts with the package ruby-dalli-doc-2.7.6-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri conflicts with the package ruby-facter-doc-2.0.1-alt1.M80P.1.noarch. 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-text-doc-1.3.1-alt0.M80P.2.noarch	File /usr/share/ri/site/Text/cdesc-Text.ri conflicts with the package ruby-text-format-doc-1.0.0-alt3.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ruby-text-format-doc-1.0.0-alt3.1.noarch	File /usr/share/ri/site/Text/cdesc-Text.ri conflicts with the package ruby-text-doc-1.3.1-alt0.M80P.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-thor-doc-0.19.1-alt1.noarch	Files /usr/share/ri/site/Object/namespace-i.ri /usr/share/ri/site/Object/rake_namespace-i.ri /usr/share/ri/site/Object/task-i.ri conflict with the package ruby-bundler-doc-1.16.2-alt2.M80P.1.noarch. 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-treetop-doc-1.6.5-alt1.noarch	File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package chef-doc-12.6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-alt1.M80P.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.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/String/cdesc-String.ri conflicts with the package ruby-mail-doc-2.6.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.5.0-alt1.1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-puppet-lint-doc-1.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/ri/site/String/blank%3f-i.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.5.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	runawfe4-server-4.2.0-alt19.noarch	File /usr/share/jboss-as/standalone/deployments/runawfe.ear conflicts with the package runawfe4-server-local-4.2.0-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	runawfe4-server-local-4.2.0-alt13.noarch	File /usr/share/jboss-as/standalone/deployments/runawfe.ear conflicts with the package runawfe4-server-4.2.0-alt19.noarch. 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-DC-devel-4.9.18-alt1.x86_64	File /usr/include/samba-4.0/libsmbclient.h conflicts with the package libsmbclient-devel-4.9.18-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.7-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	screen-message-0.6-alt1.qa1.x86_64	Files /usr/bin/sm /usr/share/man/man1/sm.1.gz conflict with the package inn-2.4.5-alt6.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.; File /usr/bin/sm conflicts with the package python-module-servicemanager-0.0.16-alt1.git20141007.1.noarch. 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	sonic-vector-0.1-alt1.hg20140909.1.x86_64	There are file conflicts with the package sonic-visualiser-2.4-alt2.hg20140912.1.x86_64, for example, /usr/share/pixmaps/draw.png (4 file conflicts in 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	sonic-visualiser-2.4-alt2.hg20140912.1.x86_64	There are file conflicts with the package sonic-vector-0.1-alt1.hg20140909.1.x86_64, for example, /usr/share/pixmaps/draw.png (4 file conflicts in 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	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-alt1.qa1.1.x86_64	File /usr/bin/stress conflicts with the package golang-tools-0-alt5.git78926538.x86_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	syslinux-4.04-alt12.x86_64	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-alt12.x86_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	taskjuggler-3.5.0-alt1.noarch	File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package asciidoctor-doc-1.5.6.1-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package chef-doc-12.6.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-chef-sugar-doc-3.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Diff/cdesc-Diff.ri conflicts with the package ruby-diff-lcs-doc-1.2.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-alt1.M80P.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.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/String/cdesc-String.ri conflicts with the package ruby-mail-doc-2.6.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.5.0-alt1.1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-puppet-lint-doc-1.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-sequel-doc-4.49.0-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-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	tatham-puzzles-10286-alt1.1.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.70.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	tau-2.23-alt2.x86_64	File /usr/bin/pprof conflicts with the package gperftools-2.6.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	tcpflow+-1.4.4-alt1.x86_64	Files /usr/bin/tcpflow /usr/share/man/man1/tcpflow.1.gz conflict with the package tcpflow-0.21-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	tcpflow-0.21-alt1.qa1.x86_64	Files /usr/bin/tcpflow /usr/share/man/man1/tcpflow.1.gz conflict with the package tcpflow+-1.4.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	tetex-doc-2.0-alt12.1.1.x86_64	Files /usr/share/texmf/doc/tetex/TETEXDOC.pdf /usr/share/texmf/doc/tetex/teTeX-FAQ conflict with the package texlive-base-bin-2008.0-alt0.15.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.; 
warn	tetex-dvips-2.0-alt12.1.1.x86_64	File /usr/bin/dvi2fax conflicts with the package texlive-extra-utils-2008.0-alt0.15.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.; 
warn	tetex-xdvi-2.0-alt12.1.1.x86_64	File /usr/bin/xdvi conflicts with the package texlive-extra-utils-2008.0-alt0.15.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.; 
warn	tex4ht-1.0.2009_06_11_1038-alt1.x86_64	File /usr/bin/ht conflicts with the package ht-2.0.22-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	texlive-base-bin-2008.0-alt0.15.6.x86_64	Files /usr/share/texmf/doc/tetex/TETEXDOC.pdf /usr/share/texmf/doc/tetex/teTeX-FAQ conflict with the package tetex-doc-2.0-alt12.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	texlive-extra-utils-2008.0-alt0.15.6.x86_64	File /usr/bin/dvi2fax conflicts with the package tetex-dvips-2.0-alt12.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.; File /usr/bin/xdvi conflicts with the package tetex-xdvi-2.0-alt12.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	texvc-1.14.0-alt4.qa1.x86_64	Files /usr/bin/texvc /usr/bin/texvc_test /usr/bin/texvc_tex conflict with the package mediawiki-extensions-Math-texvc-1.24-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	thor-doc-0.19.1-alt1.noarch	Files /usr/share/ri/site/Object/namespace-i.ri /usr/share/ri/site/Object/rake_namespace-i.ri /usr/share/ri/site/Object/task-i.ri conflict with the package ruby-bundler-doc-1.16.2-alt2.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	tigervnc-common-1.7.0-alt1.M80P.2.x86_64	File /usr/bin/vncpasswd conflicts with the package turbovnc-server-1.2.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	tpg-3.2.2-alt1.noarch	Files /usr/bin/tpg /usr/lib/python2.7/site-packages/tpg.pyc /usr/lib/python2.7/site-packages/tpg.pyo conflict with the package python-module-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	translate-toolkit-1.13.0-alt1.noarch	File /usr/bin/pocompile conflicts with the package python-module-zest.pocompile-1.5-alt1.dev0.git20130705.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	trilinos10-headers-11.12.1-alt2.x86_64	File /usr/include/gtest/gtest.h conflicts with the package libgtest-devel-1.8.0-alt4.M80P.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/include/gmres.h conflicts with the package libimlxx-devel-1.2a-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 libnnti-devel-2.0-alt1.git20150304.x86_64, for example, /usr/include/Trios_config.h (4 file conflicts in 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	turbovnc-server-1.2.1-alt3.x86_64	File /usr/bin/vncpasswd conflicts with the package tigervnc-common-1.7.0-alt1.M80P.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	volumes-profile-centaurus-0.11-alt1.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-server-0.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-kdesktop-0.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/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-lite-0.4-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-master-0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-regular-0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	volumes-profile-cliff-server-0.14-alt1.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-kdesktop-0.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/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-lite-0.4-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-master-0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-regular-0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	volumes-profile-jeos-0.1-alt1.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-server-0.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-kdesktop-0.8.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-lite-0.4-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-master-0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-regular-0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	volumes-profile-kdesktop-0.8.0-alt1.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-server-0.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-lite-0.4-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-master-0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-regular-0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	volumes-profile-lite-0.4-alt1.M80P.1.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-server-0.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-kdesktop-0.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/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-master-0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-regular-0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	volumes-profile-master-0.2-alt1.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-server-0.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-kdesktop-0.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/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-lite-0.4-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-regular-0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	volumes-profile-regular-0.3-alt1.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.11-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-server-0.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-kdesktop-0.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/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-lite-0.4-alt1.M80P.1.noarch. Moreover, the 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-alt2.1.noarch	File /usr/bin/vzdump conflicts with the package pve-manager-5.2.3-alt8.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	wcalc-2.4-alt3.x86_64	File /usr/bin/wcalc conflicts with the package Wcalc-1.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	wildfly-as-10.1.0-alt2.M80P.1.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	xCAT-client-2.5.1-alt0.4.noarch	There are file conflicts with the package pssh-2.3.1-alt1.noarch, for example, /usr/bin/prsync (4 file conflicts in 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/bin/pscp conflicts with the package putty-0.68-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	xawtv4-common-4.0-alt3.git20081014.1.x86_64	File /usr/bin/record conflicts with the package marsyas-0.6.0-alt1.alpha.git20150301.x86_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	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-8.2-alt0.M80P.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	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-alt-sisyphus-xfce-settings-20161130-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 branding-alt-starterkit-xfce-settings-p8-alt0.M80P.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.; 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-altlinux-sisyphus-xfce-settings-20160315-alt1.noarch. 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 branding-school-server-xfce-settings-7.0.5-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /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-8.2-alt0.M80P.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 /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-alt-sisyphus-xfce-settings-20161130-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/skel/.config/xfce4/panel/panels.xml /etc/skel/.local/share/applications/defaults.list /usr/share/xfce4/backdrops/xdm.png conflict with the package branding-alt-starterkit-xfce-settings-p8-alt0.M80P.5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /etc/skel/.config/xfce4/desktop/icons.screen0.rc /etc/skel/.config/xfce4/helpers.rc conflict with the package branding-alt-tonk-xfce-settings-8.3-alt0.M80P.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /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-altlinux-sisyphus-xfce-settings-20160315-alt1.noarch. 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-school-junior-xfce-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.; 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.; Files /etc/skel/.config/xfce4/desktop/icons.screen0.rc /etc/skel/.config/xfce4/helpers.rc conflict with the package branding-school-master-xfce-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.; There are file conflicts with the package branding-school-server-xfce-settings-7.0.5-alt2.noarch, for example, /etc/skel/.config/xfce4/desktop/icons.screen0.rc (4 file conflicts in 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 /etc/skel/.config/xfce4/desktop/icons.screen0.rc /etc/skel/.config/xfce4/helpers.rc conflict with the package branding-school-teacher-xfce-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/.config/xfce4/helpers.rc conflicts with the package branding-simply-linux-xfce-settings-8.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	xfce-settings-lite-school-network-0.6-alt2.noarch	File /etc/skel/.config/xfce4/panel/launcher-10.rc conflicts with the package branding-alt-sisyphus-xfce-settings-20161130-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 branding-alt-starterkit-xfce-settings-p8-alt0.M80P.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.; 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-altlinux-sisyphus-xfce-settings-20160315-alt1.noarch. 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 branding-school-server-xfce-settings-7.0.5-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /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-alt-sisyphus-xfce-settings-20161130-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 branding-alt-starterkit-xfce-settings-p8-alt0.M80P.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.; 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-altlinux-sisyphus-xfce-settings-20160315-alt1.noarch. 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 branding-school-server-xfce-settings-7.0.5-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /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.; 
warn	xfce-settings-simple-1.0-alt6.noarch	There are file conflicts with the package branding-alt-education-xfce-settings-8.2-alt0.M80P.2.noarch, for example, /etc/skel/.config/xfce4/Xcursor.xrdb (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 branding-alt-sisyphus-xfce-settings-20161130-alt2.noarch, for example, /etc/skel/.Xdefaults (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-alt-starterkit-xfce-settings-p8-alt0.M80P.5.noarch, for example, /etc/skel/.Xdefaults (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-alt-tonk-xfce-settings-8.3-alt0.M80P.3.noarch, for example, /etc/skel/.config/xfce4/Xcursor.xrdb (8 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-altlinux-desktop-xfce-settings-5.9.9-alt3.noarch, for example, /etc/skel/.Xdefaults (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-xfce-settings-5.9.9-alt1.noarch, for example, /etc/skel/.Xdefaults (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-sisyphus-xfce-settings-20160315-alt1.noarch, for example, /etc/skel/.Xdefaults (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-junior-xfce-settings-7.0.5-alt1.noarch, for example, /etc/skel/.config/xfce4/Xcursor.xrdb (8 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.Xdefaults 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.; There are file conflicts with the package branding-school-master-xfce-settings-7.0.5-alt1.noarch, for example, /etc/skel/.config/xfce4/Xcursor.xrdb (8 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-school-server-xfce-settings-7.0.5-alt2.noarch, for example, /etc/skel/.config/xfce4/Xcursor.xrdb (8 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-school-teacher-xfce-settings-7.0.5-alt1.noarch, for example, /etc/skel/.config/xfce4/Xcursor.xrdb (8 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package branding-simply-linux-xfce-settings-8.2.0-alt1.noarch, for example, /etc/skel/.config/xfce4/Xcursor.xrdb (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	xorg-xcbproto-devel-1.12-alt1.noarch	File /usr/share/pkgconfig/xcb-proto.pc conflicts with the package libxcbutil-proto-1.12-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	yajl-ruby-doc-1.3.0-alt0.M80P.4.noarch	File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package erubis-doc-2.7.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/Kernel/cdesc-Kernel.ri conflicts with the package ruby-backports-doc-3.7.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-bundler-doc-1.16.2-alt2.M80P.1.noarch. Moreover, the packages have 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.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/Yajl/cdesc-Yajl.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-highline-doc-1.7.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-hpricot-doc-0.8.6-alt1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package ruby-json-pure-doc-2.1.0-alt0.M80P.5.noarch, for example, /usr/share/ri/site/JSON/GeneratorError/cdesc-GeneratorError.ri (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/JSON/cdesc-JSON.ri conflicts with the package ruby-oj-doc-3.5.0-alt1.1.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-polyglot-doc-0.3.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	zabbix-java-gateway-3.0.26-alt0.M80P.2.noarch	File /etc/zabbix/zabbix_java_gateway.conf conflicts with the package zabbix40-java-gateway-4.0.7-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	zabbix-proxy-3.0.26-alt0.M80P.2.x86_64	Files /etc/zabbix/zabbix_proxy.conf /usr/share/man/man8/zabbix_proxy.8.xz conflict with the package zabbix40-proxy-common-4.0.7-alt0.M80P.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	zabbix-server-common-3.0.26-alt0.M80P.2.x86_64	Files /etc/zabbix/zabbix_server.conf /usr/bin/zabbix_get /usr/share/man/man1/zabbix_get.1.xz conflict with the package zabbix40-server-common-4.0.7-alt0.M80P.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	zabbix40-java-gateway-4.0.7-alt0.M80P.1.noarch	File /etc/zabbix/zabbix_java_gateway.conf conflicts with the package zabbix-java-gateway-3.0.26-alt0.M80P.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	zabbix40-proxy-common-4.0.7-alt0.M80P.1.noarch	Files /etc/zabbix/zabbix_proxy.conf /usr/share/man/man8/zabbix_proxy.8.xz conflict with the package zabbix-proxy-3.0.26-alt0.M80P.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	zabbix40-server-common-4.0.7-alt0.M80P.1.x86_64	Files /etc/zabbix/zabbix_server.conf /usr/bin/zabbix_get /usr/share/man/man1/zabbix_get.1.xz conflict with the package zabbix-server-common-3.0.26-alt0.M80P.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	zziplib-utils-0.13.62-alt1.x86_64	File /usr/bin/zzcat conflicts with the package zzuf-0.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	zzuf-0.13-alt1.x86_64	File /usr/bin/zzcat conflicts with the package zziplib-utils-0.13.62-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.;